Governance, budgets & guardrails

Governance APIs constrain eligible choices before optimizer ranking. Use the customer portal or API to manage policies and virtual models.

Hard controls before ranking

Budgets, virtual-model policies, and fail-closed guardrails (PII/secret/injection first slices) run before offer ranking. When governance denies or constrains, look for X-Darouter-Governance-Explanation.

Portal and API workflows

The customer portal Governance panel composes virtual-model policies, drafts, activates, and rolls back via tenant APIs (/v1/virtual-models). That is not the operator VM console.

Use the API for advanced automation and the portal for supported interactive workflows.

Budgets & alerts

Budget pools and GET /v1/notifications/budget-alerts surface threshold firings in-portal. Email/webhook fan-out is not implied by viewing the inbox.

Optimizer (after governance)Features maturity

OpenAPI operations

Contract: /v1/openapi.json. Governance-related paths documented today:

GET/POST /v1/virtual-models, GET /v1/virtual-models/{id}
POST /v1/virtual-models/{id}/versions, .../activate, .../rollback
GET /v1/budgets, GET /v1/budgets/{id}, .../usage, .../alerts
GET /v1/notifications/budget-alerts

Hard governance still runs before optimizer ranking even when you only call POST /v1/chat/completions — look for X-Darouter-Governance-Explanation.