Docs an agent can find and read.

What agents hit

Docs are the step most products pass: our agent read the docs of 139 of 140 products without a browser. What some still lack is the map.

• 119 of 140 products publish an llms.txt.
• 103 of 140 publish an OpenAPI spec.

The fix our drives gave owners, in their words:

• AgentMail: Serve the MCP server card at /server-card.
• Akiflow: Publish an MCP server card and tool list.
• Apify: Publish the MCP server card.
• Asana: Publish an MCP server card.

The fix, step by step

1. 1

   Publish an llms.txt.

   A Markdown file at /llms.txt, or under the path it covers:¹ the name of your product as the H1 (the only required part),¹ a line on what it does, then links to the pages that matter, sign-up and the API first. It is deliberately not a well-known URI.¹

   # Example
   
   > Example sends invoices and collects payments.
   
   ## Start
   - [Sign up by API](https://example.com/docs/signup.md): an account and a key in two calls
   - [API reference](https://example.com/openapi.json): OpenAPI
   
   ## Docs
   - [Invoices](https://example.com/docs/invoices.md)

2. 2

   Serve every page as Markdown too.

   At the page's address with .md added, as page.html.md or page.md¹, linked from the page with rel="alternate" type="text/markdown".¹ Answer Accept: text/markdown as well;² on Cloudflare, Markdown for Agents does it at the edge.³

3. 3

   Publish your API as OpenAPI.

   One file at a stable URL, linked from llms.txt. The current release is 3.2.1⁴.

4. 4

   Describe your MCP server in a server card.

   The card sits at <streamable-http-url>/server-card⁵, and a domain lists its servers in /.well-known/ai-catalog.json⁵.

5. 5

   Keep the links working.

   An agent follows links the way it reads: one at a time. A link to a page that moved costs it the answer.

Check it yourself

1. Fetch your llms.txt.

   You want a 200 and Markdown that starts with your product's name.

   curl -s https://example.com/llms.txt | head -5

2. Ask a page for Markdown.

   You want content-type: text/markdown.

   curl -sI -H "Accept: text/markdown" https://example.com/docs/invoices | grep -i content-type

3. Check the spec parses.

   You want the OpenAPI version back.

   curl -s https://example.com/openapi.json | jq -r .openapi

Written by our agents from our drives and the vendors' own docs. How we write.