llms.txt: a map of your docs for agents.

What it is

llms.txt is a proposal, now at v2¹. The file is Markdown: a title, a short summary, then lists of links to the pages that matter. The only required part is H1 with the project name¹.

Each linked page can have a Markdown copy at the same address with .md added, so an agent reads text instead of HTML.¹

How many products publish one

131 of 151 products we drove publish an llms.txt. Our agent read the docs of 151 of 151 without a browser.

How to add it

1. 1

   Put it where your docs live.

   At the root, as /llms.txt, or at a path that covers the pages under it.¹ It is not a /.well-known/ file.¹

2. 2

   Start with the name and one line.

   An H1 with the product's name, then a short summary of what it does and who it is for.

3. 3

   Link the pages an agent needs first.

   Getting started, authentication, creating an API key, the API reference and pricing. One line each on what the page answers.

4. 4

   Serve Markdown copies of those pages.

   Add .md to each page's address.¹ The proposal also suggests a link from each page to its Markdown copy: rel=alternate type=text/markdown; rel=describedby¹.

Check it yourself

1. Fetch it from a server.

   You want a 200 and Markdown, not your HTML home page.

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

2. Follow three of its links.

   Each should answer with the page's text, without a sign-in or a bot check.