Developers / API

Governed request API

The governed request contract

Limited — private production API

Under both the MCP tool and the client is one contract: a request for governed context. It is resource-oriented, uses standard HTTP status codes, and returns a typed governance decision. The wire types are generated from a single source and published as a canonical OpenAPI artifact, so the contract and the code never drift.

What this is, and isn’t. This is the private production API that the Elevated Context application and our own tools call. It is not a public, self-serve, licensed API product today: authentication is a browser Google sign-in, there is no external API-key program, no third-party application registration, and no usage-based billing. See API as a product for what that would require. The protocol is real and versioned (protocol_version "1"); access is early-access.

Base

Request context

POST /v1/context/requests — ask for governed context. The body carries only a controlled purpose plus optional narrow-only preferences. Fields that could widen authority are not accepted.

FieldRequiredMeaning
purpose_idyesA controlled purpose id (not free text). Server-verified; narrow-only.
requested_scopenoA client preference (e.g. a sensitivity ceiling). Narrows, never widens.
object_refsnoStructured references that select within what you may already see.
recipientnoA recipient reference. The server establishes the recipient; the client never declares its class.
correlation_idnoObservability only. Not an idempotency key.

Example request:

POST /v1/context/requests
Content-Type: application/json

{
  "purpose_id": "GENERAL_QA",
  "requested_scope": { "sensitivity_ceiling": "INTERNAL" }
}

Decisions

Every response carries a typed decision. The values a client may see:

Error envelopes carry a safe, generic message plus a correlation id; internal service names, policy logic, and stack traces are never returned to a client.

OpenAPI

The contract is generated from a single source of truth and exported as a canonical OpenAPI document (ec-protocol.v1.json), with automated drift checks between the contract, the generated types, and the running service. Today, the artifact is distributed with your access rather than hosted publicly.

API as a product (what it would take)

Selling API access as a distinct product requires capabilities that are deliberately not built yet. See the product and talk to us about contact the team. Today the honest status is:

← All developer paths Start with MCP →