Workspace activation
Activate a tenant, confirm the license tier, set the workspace owner, and verify the first operator can sign in.
- License and edition check
- Owner, admin, security, and viewer roles
- MFA and SSO readiness
Guided operating paths for provider setup, model rollout, routing, guardrails, spend controls, observability, identity, and go-live readiness.
Activate a tenant, confirm the license tier, set the workspace owner, and verify the first operator can sign in.
Connect managed APIs or self-hosted runtimes with the right endpoint, auth type, adapter, and readiness checks.
Scan provider models, choose approved IDs, classify capabilities, and expose only what each route should use.
Build route drafts, simulate candidate order, compare latency and cost behavior, then promote only after review.
Create policy bundles that protect runtime traffic without burying operators in one-off rules.
Track platform usage, model consumption, token volume, budgets, plan limits, and customer pressure signals.
Route metadata, health, policy outcomes, and audit events into the tools the customer already uses.
Manage operators, roles, activation, suspension, deletion, and review every sensitive administrative action.
Confirm runtime health, model coverage, route readiness, keys, traffic evidence, and rollback posture before production use.
Developers still get the minimum call shape when they need to send traffic through the gateway.
curl https://gateway.example.com/v1/chat/completions \
-H "Authorization: Bearer sk_live_..." \
-H "Content-Type: application/json" \
-d '{
"model": "chat",
"messages": [{ "role": "user", "content": "Explain the rollout risk" }]
}'