Docs for agents

In 2026, agents became the majority reader of documentation. Mintlify's 2026 State of Knowledge Report counted 257 million agent requests against 131 million human page loads across its hosted docs in August 2026, and 83% of that agent traffic arrived through machine-friendly routes: a .md version of a page, an llms.txt index, or an agent skill. Agents request those routes only when they know they exist.

Blode.md publishes every one of them from the same deploy as the HTML, so what an agent reads is what you merged. This page lists what ships, why the index matters more than the Markdown, and the few things you control from docs.json and frontmatter.

What every deploy publishes

Path	What it is	You control
/llms.txt	Index of every visible page as a .md link with the page description, plus Sitemap:, Full content: and Skills: lines and one /llms/<group>.txt segment per navigation group	name and description in docs.json; each page's description; hidden pages
/llms-full.txt	Every visible page as Markdown in one file	Same
/{page}.md	The page as Markdown. Also returned when a client sends Accept: text/markdown to the HTML URL	Frontmatter and body
Link header on every HTML page	llms.txt, llms-full.txt, the skills index, and the page's own Markdown alternate	Nothing; always on
X-Llms-Txt header	The llms.txt path, for clients that read headers before bodies	Nothing; always on
/.well-known/skills/index.json	A generated skill describing your docs for agents that install skills	name and description in docs.json
/robots.txt, /sitemap.xml	Crawler files with the same page set; robots.txt also names the agent routes in comments	seo.indexing

Do not hand-author copies of these in your docs folder. They are regenerated on every deploy and a committed copy would drift.

Why the index matters more than the Markdown