Developers / API
Governed request API
The governed request contract
Limited — private production APIUnder 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.
protocol_version "1"); access is early-access.
Base
- Origin:
https://api.elevatedcontext.com - Protocol version:
1(an unsupported version fails closed; there is never a silent reinterpretation) - Auth: an authenticated Elevated Context session (browser Google sign-in). A client never asserts its own identity, tenant, or authority.
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.
| Field | Required | Meaning |
|---|---|---|
purpose_id | yes | A controlled purpose id (not free text). Server-verified; narrow-only. |
requested_scope | no | A client preference (e.g. a sensitivity ceiling). Narrows, never widens. |
object_refs | no | Structured references that select within what you may already see. |
recipient | no | A recipient reference. The server establishes the recipient; the client never declares its class. |
correlation_id | no | Observability 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:
ALLOWED— governed context released (with a receipt).WITHHELD— policy held context back.DENIED— not authorized for the requested context (HTTP 403).PENDING_CONSENT— the owner must approve in the app, then retry.PURPOSE_REQUIRED/NOT_ADMITTED— the purpose was not admitted (structured HTTP 200 pre-admission insufficiency).SCOPE_INVALID— a malformed scope control field (HTTP 422).STEP_UP_REQUIRED— additional verification needed (HTTP 412).RECIPIENT_REQUIRED/RECIPIENT_INVALID/RECIPIENT_REPLAY/RECIPIENT_UNAVAILABLE.FAIL_CLOSED— when authority cannot be confirmed, the service holds back rather than widening access (HTTP 503 for service unavailability).
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:
- External developer identity & app registration — not built.
- API-key issuance & rotation — not built (auth is browser sign-in).
- Rate limits, quotas, usage metering & billing — not built.
- Tenant & purpose restrictions, recipient assurance, audit visibility — present in the governance core.
- Versioning — present (
protocol_versionwith fail-closed negotiation).