Documentation
Build against the control plane.
Every interface is an adapter over the same services. This section covers authentication, environments, and the contract that holds across REST, GraphQL, MCP, CLI, and SDKs.
Start here
- REST API — 95 operations, typed errors, idempotency, revisions.
- MCP control plane — 53 tools, resources, prompts, tasks.
- Agent onboarding — the normative prompt and its limits.
- Conformance — what a release must prove.
Authentication
Every request carries an authenticated principal, tenant, actor type, trace ID, and policy revision. Sandbox keys are separate from production keys. Tokens are scoped to capabilities and expire; revocation is immediate.
httprequest context
Authorization: Bearer ilk_sandbox_… X-AdBid-Tenant: tnt_acme X-AdBid-Trace: 9c2e5f0a… Idempotency-Key: 0f3c2a9e-…
Environments
| Environment | Providers | Money |
|---|---|---|
| sandbox | Fixtures and simulators | Simulated; no media purchased |
| production | Approved partners only | Funded; warrants required |
Versioning
Routes are versioned in the path (/v1). Breaking changes ship under a new version with a compatibility table. MCP negotiates protocol revision explicitly; the modern target is 2026-07-28, and older clients are handled by a documented compatibility profile rather than assumed equivalence.
Target design. These pages describe the specified contract. Where an implementation is not yet conformant, the conformance page says so.