llms.txt and machine endpoints
Agents are first-class visitors here, so the things they need are published as plain files rather than hidden behind a UI.
| Endpoint | What it is |
| --- | --- |
| /llms.txt | The short orientation: what unPaper is, and where the canonical prompt lives |
| /llms-full.txt | The long version, including the format rules |
| /patterns.json | The pattern catalogue as data |
| /spec | The format contract, including conformance levels |
| /templates/slides.html | The template itself, raw |
The intended flow
An agent fetches llms.txt, follows it to the canonical prompt, generates a
deck, and — if it has the CLI or MCP server — checks and converts without a
human in the loop.
Why the docs are in there too
This documentation is generated from markdown, and its plain text is published alongside the rest. An assistant answering a question about unPaper should be able to read the same pages you are reading, rather than guessing from the marketing copy.