Build on business records people can trust.

What every listing gets

• Discovery: a machine-readable card at a /.well-known address, an llms.txt, and the Flyk Open Discovery Protocol (AFODP). During private early access, available on request.
• Answers: customers get answers about every listing on web chat, text, WhatsApp, calls and AI agents that connect to Flyk, in English and Spanish. Booking comes with the owner's Flyk agent.
• Machine-readable by default: an llms.txt, the /.well-known business card, schema.org JSON-LD and a sitemap for business pages, and the AFODP registry. During private early access, available on request.

What makes Flyk different

• The Flyk agent works through the tools the owner already uses: their calendar, their booking tool, and anything with an API or MCP server, and more as they add them.
• For customers (they ask and book, with the times and details the owner chooses) and for the owner (ask what's coming up, change a price, by text, call or the web).
• Flyk doesn't replace the owner's tools; it works through them.

Signals AI agents get

• Trust score

  A score from 0 to 5, with a tier, built from reviews of completed bookings, web presence and public references, the licenses and certifications the owner lists (Flyk does not check them), and whether the owner has proved the business is theirs.

• Compatibility (SCP)

  How well a business's declared fit matches what its clients later confirm. It is in the card and in the registry's business comparison, so an AI agent can compare how well each business fits.

With a plan, Flyk also writes social posts, email campaigns and service descriptions from the same record.

What the record is

• Hours, including days off and holidays.
• Services, what each includes, how long it takes, and its price with a unit (per visit, per hour).
• Where the business works and how far it travels.
• How to reach the business or book.
• Anything else the owner chooses to share with customers, like their description, policies or answers to common questions, added directly in Flyk.

Each answer can say where it came from: the owner's confirmed record, or public information for a business that isn't live on Flyk yet.

Two ways to get the record

• 1. Read what Flyk publishes

  Flyk publishes a machine-readable card for each business at a /.well-known address, and an llms.txt for each business. No account needed. During private early access, the card and llms.txt addresses are available on request. Flyk signs the cards it serves. On WordPress, the Flyk plugin also serves the business's llms.txt from its own site.

• 2. Connect directly

  Ask Flyk for a business's record, or ask the business a question, over MCP, A2A, OpenAPI or UTCP.

• The open protocol

  The Flyk Open Discovery Protocol (AFODP) describes the card, the registry and how answers name their source. The protocol spec is available on request.

Both directions, one Flyk agent

• For customers and their AI.

  AI apps and AI agents that connect to Flyk find a business, ask it questions, get answers from its confirmed details, and book where the owner allows it.

  Example: an AI agent asks "Can I book a deep clean Saturday?" and gets Rosa's open times from her booking tool.

• For the owner.

  The owner talks to the same Flyk agent by text, call or the web: "What's coming up?", "Raise my deep clean to $280", "Which customer questions are waiting?"

  Example: Rosa texts "What's coming up?" and gets this week's bookings and waiting questions.

• Through the owner's own tools.

  Both directions work through the tools the owner already uses: calendars and booking tools today, and any service with an MCP server once the owner connects it. Flyk doesn't replace those tools; it works through them.

Want early access for your business, or to build on Flyk?

Get your invite. An email or a mobile number is enough.

Get my invite →

Run a business? Tell us what you need →

Building something? Email our founder: founder@flyk.app