Everything your team does in Goliath, from your own code.
One endpoint. 622 operations, each one written and reviewed by us. Keys that act as you, so your code reaches exactly what you can reach in the app.
An example: a findContacts request for "Jane Doe" and its response listing one contact.
622 operations.
One door.
Every dot is a real operation in the catalog, clustered by domain and coloured by the scope it needs. You never send GraphQL: you send an operationId, and we run the exact operation we wrote, as the key's owner.
Hover a star to read it. Click one to open it.
Four ways in.
Your first call
A key, one request, one contact back.
Write without fear
Idempotency keys, replays and the 409 that means wait.
Every operation
Generated from the gateway on every release.
Webhooks
Push contacts in; get catalyst events out.
Your agent can read the whole API in one fetch.
GET /api/v1/helpThe full catalog as Markdown. No key.GET /api/v1/operationsJSON, with an authorized flag for your key./developers/llms.txtEvery page, as Markdown.Copy for your agentOn every reference page.From 180 to 622 operations since Jul 23.
How we build what you call.
785 lands a day: Orochi's second week
A full week at record volume: where we traded speed for correctness, the ideas we borrowed, a simulator for the land lane, and Argus, our nightly AI QA.
October 29, 2026 · Version controlTen days to Orochi: how we took our monorepo off GitHub's merge queue
How a small team and an AI agent fleet replaced GitHub's merge queue with Orochi, its own version control and CI, in ten days.