Home · Solutions · By who you are
For AI agents — a contract a model can read on its own
The spec, a plain-text map of the site, and an MCP server. Every route answers in the same envelope, so one tool definition covers the catalogue instead of one per platform.
The problem
An agent cannot ask a human what a field means. It needs the shape, the error list and the cost in a form it can fetch — and it needs absent data to say absent, because a model handed a zero will reason from the zero.
What answers it — 2 endpoints
bluesky/profilearchive/coverage
Shape, parameters and the errors each one returns are in the endpoint reference, generated from the same catalogue the router reads.
Surfaces outside the data catalogue
/llms.txt/llms-full.txt/api/mcp
The recipe
There is no recipe for this one yet. The 3 that exist are all about the archive, and pointing you at one of them from here would send you to steps that do not answer this question. The recipe index says which they are.