Choose your workspace
Open /demo to choose Builder, Enterprise, Buyer or Provider. /demo/builder covers sessions, budget routing and contribution review. /demo/enterprise connects an eight-stage action runner, processing map, policy editor, usage graphs and trace evidence. /demo/buyer covers catalog, provenance, purpose-specific license review and delivery gates. /demo/provider covers endpoint capabilities, certification, regional eligibility and canary rollback.
Connected enterprise state
The enterprise policy editor stages a draft separately from the active revision. Publishing a valid revision changes route eligibility and future runs. The runner supports normal output, required semantic denial, malformed output, optional timeout, stale policy and cancellation. Managed, customer-server and end-device placement labels follow each action event. Events in one batch run concurrently; required failures prevent release. An optional failure continues without its result. Inference already performed remains in usage even if output validation or cancellation blocks delivery.
Map, filters and usage
The routing map overlays fictional endpoints on a Natural Earth land basemap. Region, endpoint and eligibility filters change the displayed routes; they never change policy permission. The usage and overview views aggregate the same sample request records by time window, region, endpoint and outcome. Cost, tokens, request count and nearest-rank P95 latency are calculated from those records. Policy revisions remain pinned on historical traces. Geography alone is not proof of compliant processing.
Marketplace and provider gates
Buyer purpose and region selections reset offer approval. Missing consent, incomplete provenance or an incompatible license blocks the offer. No delivery occurs without authenticated acceptance and funding. Provider configuration changes invalidate certification and stop the canary. Sample health, region evidence, grammar and retention requirements must pass before a 1–5% pilot allocation. Rollback returns allocation to zero. Projected provider traffic is explicitly distinct from observed request usage.
Contract mapping
The demos run entirely in the browser with fictional fixtures. They do not call a gateway, execute external tools, register an endpoint, create credentials, transfer data or settle funds. The preview REST, CLI and MCP designs below specify how production integrations should expose these concepts after their release gates pass. They are not available backend implementations.
| Workspace view | Preview contract | Required authority |
|---|---|---|
| Action runner | POST /v1/actions/simulate | actions:simulate; bounded synthetic inputs |
| Routing map | POST /v1/routes/explain | routing:read; tenant policy |
| Usage & filters | GET /v1/usage | usage:read; tenant-scoped filters |
| Evidence | GET /v1/traces/{trace_id} | traces:read; metadata projection |
| Policy draft/publish | /v1/policies/* | policy read/write; explicit activation |
| Buyer review | POST /v1/marketplace/offers/preview | marketplace:read; license/consent checks |
| Provider certification | POST /v1/provider/certifications/preview | provider:validate; no live registration |
Contracts & examples
Download the preview, validate its shape locally and review the capability limits before planning an integration.
OpenAPI preview