API reference

Runtime endpoints, authentication, response types and errors — the shape of the public API.

Bearer keys, each bound to exactly one project.

The one endpoint you will call most — OpenAI-compatible, with strict field checking.

List what your key can actually call — your project's set, not the whole catalogue.

Incremental server-sent events, and the terminator that tells you the reply is whole.

Request-rate protection and the spending ceilings that are not rate limits.

The error envelope, and every code worth branching on.

Your project's private flows — contracts, revisions, HTTP and MCP invocation.