What is llms.txt — and why your API needs one
The single highest-leverage file for making your API discoverable to AI agents.
The one-paragraph version
llms.txt is a plain-text index, placed at the root of your docs domain, that tells AI agents exactly which pages matter and in what order. Think of it as robots.txt for comprehension instead of crawling: not “what you may read,” but “here is the map.”
Agents have small context windows. A good llms.txt is the difference between an agent loading your three canonical guides and an agent giving up on a 400-page docs site.
What a good one contains
A short description of the API, then a curated list of links grouped by task — auth, core resources, webhooks, errors — each with a one-line summary. Keep it focused and well under the size budget; a bloated llms.txt scores worse than a tight one.
Pair it with llms-full.txt (the full text agents can load in a single request) when your core docs fit in a reasonable bundle.
How Discry scores it
Discry checks both presence (does llms.txt exist?) and quality (is it focused, current, and the right size?), and the behavioral scan follows your llms.txt as your declared agent-facing surface — if it routes agents to marketing pages, that is what gets graded. See the methodology page.