llms.txt
Feed these docs to an LLM.
If you're using an LLM (ChatGPT, Claude, an AI coding assistant, etc.) to help you integrate with this API, you can hand it these docs directly instead of relying on whatever it already knows.
What llms.txt is
llms.txt is an emerging convention for publishing documentation in a form LLMs can read directly: plain text and Markdown, without the navigation, styling, and page chrome an HTML page carries. Sites that support it publish one or more .txt files alongside their normal pages specifically for this purpose. This site publishes three:
| File | Contains |
|---|---|
/llms.txt | An index: every page on this site, with a short description and link. |
/llms-full.txt | The full content of every page on this site, concatenated into one document. |
| The Copy Markdown button on any page | Just that one page, as clean Markdown. |
How to use it
The right one depends on how you're working:
- Ask a quick question in a chat tool. Open
/llms-full.txt, copy it, and paste it in as context before you ask your question. It's the whole site, so the model has everything it might need in one go. - Working on one topic. Use the Copy Markdown button at the top of the page you're on (next to the title) and paste just that page in - less noise for the model to wade through.
- Using a tool or agent that can fetch URLs itself (an IDE assistant, an agent with a browsing or fetch tool), just give it the address -
/llms.txtif you want it to find its own way around,/llms-full.txtif you want it to have everything up front.
Treat the answer as a starting point
Feeding an LLM real documentation makes it far less likely to invent endpoints
or parameters that don't exist, but it doesn't make the answer authoritative.
Verify anything you get back against the API
reference before you rely on it, especially while the
API is at v0 and still changing.
These files cover the whole site, not just v0 - if a future version's docs are published alongside this one, they'll be in there too.