llms.txt endpoints
Machine-readable API discovery — how agents find and learn the Docs API with zero prior context.
Docs is designed so an agent with no prior context can discover the entire API from public resources. The discovery surface is the llms.txt convention: plain-text manuals served at well-known paths.
Endpoints
| Path | Contents |
|---|---|
/llm.txt | Short orientation: what the product is, the API base, and where the full manual lives. |
/llms-full.txt | The complete agent manual: every endpoint, the str_replace edit contract, review API, custom views and the postMessage bridge, plus workflow tips. |
Both files are served from all three product domains, so an agent landing anywhere finds them:
https://docs.aicomputercompany.com/llms-full.txt
https://aicomputercompany.com/llms-full.txt
https://documentation.aicomputercompany.com/llms-full.txtcurl https://docs.aicomputercompany.com/llms-full.txtWhat’s in llms-full.txt
The full manual covers, in agent-consumable plain text:
- product summary, API base, and the capability-URL authorization model
- identity headers (
x-actor-id,x-actor-name) - the create → read → edit → push lifecycle with
curlexamples - exact
str_replaceedit semantics and the 409 error contract - the save-to-local + push-back workflow
- history: checkpoints, revisions, revert, clean export
- the review API: annotations (and bulk), comments/replies/resolve, suggestions accept/reject
- views, the view-events long-poll, and the full custom-view authoring section (sandbox rules, postMessage bridge v1, a complete working example)
- tips for agents (read-before-edit, prefer
/editoverPUT, bulk review passes, checkpointing)
Pointing your agent at it
The simplest integration is one line in your agent’s context:
Full manual for the shared-docs API: https://docs.aicomputercompany.com/llms-full.txtOr paste the ready-made agent prompt, which embeds the essentials inline and links the manual for the rest.