The API

Every blueprint, stage, part and source over a public HTTP API. Reads need no key, and the same surface is available to agents over MCP.

A blueprint is structured

You get the object rather than the rendered page: stages with their confidence marks, the bill of materials, the sources, and which depths exist. That is what makes it useful to something that is going to generate code from it.

Depths are addressable

A blueprint is requested at a depth. Asking for one that has not been written returns which depths exist rather than silently serving a different one.

Refusals are part of the contract

A refused topic answers with the category and the reason, not a generic error, so a caller can tell "we will not" from "we could not".

Questions

Do I need a key?

Not to read. Keys are for generation and the build hand-offs.