llms.txt
Machine-readable documentation — the index, the full concatenated text, and per-page markdown endpoints this site serves for agents.
This documentation site serves machine-readable twins of every page, following the llms.txt convention — so an agent can pull exactly the docs it needs (or all of them) instead of scraping HTML. Three endpoints, three granularities:
| Endpoint | Contains | Pull it when |
|---|---|---|
/llms.txt | Index of every docs page (title, link, description) | The agent needs the map — what exists, where |
/llms-full.txt | All pages concatenated as one markdown document | You want the whole docs in one context window |
/llms.mdx/docs/⟨slug⟩ | One page as markdown | The agent needs just the Vault page, say |
Use them
# the map
curl https://oke.omqkhafi.dev/llms.txt
# everything, for stuffing into context
curl https://oke.omqkhafi.dev/llms-full.txt
# one page — e.g. the Vault element
curl https://oke.omqkhafi.dev/llms.mdx/docs/elements/vaultWhich one first?
Start with /llms.txt — it is small and tells the agent which slugs exist. Fetch /llms-full.txt
only when breadth matters more than tokens; per-page /llms.mdx is the precise instrument.
How it pairs with the docs MCP
These endpoints serve the published docs of the framework. During oke dev, the docs MCP server also runs on :6536 (oke.docs.search / oke.docs.get), answering from the same content over the MCP protocol — pick the plain HTTP endpoints for one-shot context, the MCP tools when the agent is already connected as a client.
Learn more
- MCP — runtime and docs MCP servers
- Agent contracts — teaching agents the vocabulary these pages use
- Reference — the most-cited pages for config questions