Fully Managed onboarding
Onboard a Fully Managed deployment through a one-time Admin Dashboard wizard: organization details, SSO, providers, and models. Complete Steps 1 to 4. Tetrate operates the data plane, so there is no Step 5.
The onboarding wizard
The wizard launches automatically on the first sign-in to the Admin Dashboard; there is no separate onboarding URL. Each step has Next and Previous controls. Next is enabled once the current step's required fields are filled; Previous returns to any earlier step to review or change a value.
Step 1
Organization Name
Identify the tenant and set the data-plane URL.
Step 2
Corporate Login
Configure SSO over OpenID Connect (OIDC). For evaluations without corporate IdP admin access, use Auth0 as a temporary IdP.
Step 3
LLM Providers
Connect providers such as OpenAI and Anthropic.
Step 4
LLM Models
Choose which models are exposed. Finish setup.
Plan for 15 to 30 minutes, plus any back-and-forth with the identity provider (IdP) team during Step 2.
Prerequisites
Have the following on hand before launching the wizard. Step 2 is hard to complete without the IdP details:
- Access to the Admin Dashboard. Tetrate provides the URL during provisioning.
- Initial admin credentials for the first sign-in. SSO is configured in the wizard; the first login uses these credentials.
- OIDC IdP details: issuer URL, client ID, client secret, scopes. Agent Router supports OIDC only; SAML and other protocols are not supported. For an evaluation without IdP admin access, use the Set up Auth0 for evaluation path instead.
- An IdP administrator reachable during Step 2. The wizard shows a redirect URI that must be registered on the IdP side before SSO works.
- API credentials for at least one LLM provider, for example an OpenAI API key.
- A planned hostname for the data plane, for example
proxy.example.com. This becomes the Proxy URL in Step 1; Tetrate operates the data plane at the hostname registered here.
Get started
The wizard appears automatically when the Admin Dashboard URL is first visited.
Click Start setup to begin.
Step 1: configure organization name
Fill in:
| Field | Required | Description | Sample value |
|---|---|---|---|
| Organization Name | Yes | The organization's display name | Acme Corp. |
| Proxy URL | Yes | The hostname for the Tetrate-operated data plane. Always include the scheme. | https://proxy.example.com |
The data plane does not need to exist yet. Onboarding only stores the value; Tetrate operates the data plane at that hostname.
Step 2: configure corporate login (single sign-on)
SSO lets users sign in with the organization's existing identity provider.
Use Auth0 as a temporary IdP rather than the corporate IdP. The Set up Auth0 for evaluation guide is the full spine: create the tenant, copy the Redirect URI from this step, register the Auth0 app, and paste the credentials back into this form.
Agent Router supports OIDC only. SAML, LDAP, and other protocols are not supported.
At Step 2, the wizard displays the OIDC redirect URI for the deployment, following the pattern:
https://dashboard.<your-mp-host>/login
Register Agent Router as an OIDC application in the IdP using that exact URI as an authorized redirect URI. Once the IdP-side application is registered and the issuer URL, client ID, and client secret are in hand, fill in:
| Field | Required | Description | Sample value |
|---|---|---|---|
| Issuer (IdP URL) | Yes | OIDC issuer URL exposed by the IdP | https://login.example.com/ |
| Client ID | Yes | OAuth client ID created for Agent Router | agent-router |
| Client Secret | Yes | OAuth client secret paired with the Client ID | •••••••• |
| Discovery URL | No | OIDC discovery document URL. If omitted, Agent Router constructs it as <Issuer URL>/.well-known/openid-configuration. Provide it only if the IdP serves discovery at a non-standard path. | https://login.example.com/.well-known/openid-configuration |
| Scopes | Yes | OAuth scopes to request | openid profile email |
| Admin email | Yes | At least one user granted admin rights after the first SSO login | [email protected] |
| Attribute mapping | Yes | Maps an IdP claim to the Agent Router user's email. The typical value is email. | email |
See the SSO configuration guide for details.
If SSO is misconfigured and blocks sign-in, sign back in with the initial admin credentials and reset the SSO configuration from the Dashboard's settings panel.
Step 3: configure LLM provider(s)
Connect Agent Router to one or more LLM providers. At least one provider is required to route traffic.
The wizard shows a radio button for each supported provider, including OpenAI, Anthropic, Google, Azure OpenAI, Mistral, Cohere, Together, and Perplexity. See Provisioning models and providers for the authoritative list. Select a provider, click Configure, then fill in:
| Field | Required | Description | Sample value |
|---|---|---|---|
| Display Name | No | Optional label shown in tables and filters | OpenAI |
| API Base URL | Yes | Base URL for the provider API. Pre-filled for supported providers. | https://api.openai.com/v1 |
| Auth method | Yes | Authentication method. Pre-filled per provider. | API Key |
| Secret Type | Yes | Password for single-string API keys; Service Account JSON for providers that authenticate with a JSON credential file. | Password |
| Provider Secret | Yes | API key, token, or service-account JSON | sk-proj-... |
| Enable provider | Yes | Defaults to on. Disable to keep the provider hidden until it is ready. | toggle |
Repeat for each provider to expose. The wizard returns to the provider selection screen after each one is saved.
Step 4: configure LLM models
The wizard shows a single list of all models Agent Router supports, maintained by Tetrate. By default, all models are selected. Deselect models to control cost, meet data-handling requirements, or scope to the intended use case. If a required model is missing, contact Tetrate support; custom model entries are not configurable in onboarding.
Complete the process
Click Complete setup to finish onboarding.
The Admin Dashboard can now be accessed by signing in with SSO.
Where to go next