Models & routing
Governance and route simulation
Inspect bounded evidence without granting inference access
Governance read and route simulation use credentials that are deliberately separate from route scope. They expose content-free tenant evidence and route planning, not generation history or a consumer billing ledger.
Read the tenant governance summary
GET /v1/governance/summary requires governance:read, admin or * and always uses the tenant bound to the verified credential. event_limit is 1–200; optional key_id is a safe non-secret service-key filter.
GET https://api.octoryn.dev/v1/governance/summary?event_limit=50
Authorization: Bearer $OCTORYN_GOVERNANCE_KEYUnderstand the read-model boundary
The response contains exact-string tenant budget state, bounded usage aggregates, key attribution and metadata-only audit events. It reports whether its local event window is partial and never returns prompts, outputs, raw tokens or token hashes.
Simulate a route
POST /v1/route/simulate requires route:simulate, admin or *. It evaluates identity, product, policy, catalogue, health, circuit and provider preferences without resolving provider credentials, reserving budget or invoking a provider.
POST https://api.octoryn.dev/v1/route/simulate?operation=chat
Authorization: Bearer $OCTORYN_SIMULATION_KEY
Content-Type: application/json
{"model":"policy/frontier","provider":{"sort":"latency"}}Do not treat simulation as a reservation
A later live request can still fail budget, capacity or provider availability checks. Simulation is an explainability and review capability, not a guarantee or a content-bearing dry run.