Guides for Platform Operators

Enterprise Tier

Written for the platform operator persona: the administrator or IT operations engineer who manages models, providers, users, and organization-wide settings from the Admin Dashboard. Each guide is organised around a single operational goal rather than a single screen.

Operator setup has two layers. First, understand projects—the isolation boundary that owns models, keys, and gateways. A default project is created during onboarding; the concept is covered in Key concepts → Projects and the operator tasks live under Project and data plane management. Second, provision models and providers into the organisation catalog, then grant those models to a project so its gateway can route to them. The remaining guides can be read in any order as the need arises.

---

Goals

Project and data plane management

Create isolated projects, grant them models, provision gateways, and operate the data planes that host them.

Provision models and providers

Configure provider connections and enable the models developers route to, including AWS Bedrock and provisioning via API.

Onboard developers and issue keys

Confirm users, assign roles, and manage organization-wide API keys.

Govern MCP server access

Curate the MCP server catalogue and configure OAuth clients.

Audit Agent Router activity

Investigate activity and spend using audit logs and usage analytics.

Communicate with Agent Router users

Publish in-Console announcements with the appropriate severity.

Configure single sign-on

Connect a SAML or OIDC identity provider.

Run multiple Agent Router instances

Operate and reconcile more than one Agent Router instance.

Working with budgets

Enforce spend limits with per-key rate limits and monitoring.

Control what request data leaves the cluster

Govern how much request detail reaches the management plane.