Providers
Providers are the upstream AI services that the gateway routes requests to. The Providers page lets you register provider credentials, monitor health, and test connectivity.
Provider List
The main view displays a card grid of all configured providers. Each card shows the provider name, type, status, model count, and health indicator. Click any card to open its detail page.
If no providers are configured, an empty state prompts you to add your first one.
Adding a Provider
Click Add Provider to open the creation modal. Fill in the following fields:
| Field | Required | Description |
|---|---|---|
| Name | Yes | A display name (e.g. “Production OpenAI”) |
| Type | Yes | The provider type — see supported types below |
| API Key | Yes | Your provider API key (stored encrypted) |
| Base URL | No | Custom endpoint URL; leave blank for the provider’s default |
Supported Provider Types
The creation form offers these built-in types:
- OpenAI (
openai) - Anthropic (
anthropic) - Google AI (
google) - Azure OpenAI (
azure) - AWS Bedrock (
bedrock) - Custom (
custom) — for self-hosted or non-standard endpoints
The gateway itself supports 28 provider adapters. Providers not listed in the dropdown can be registered using the Custom type with the appropriate base URL.
Provider Detail Page
Clicking a provider card navigates to its detail page, which has three tabs:
Settings Tab
Edit the provider’s name, status (active / inactive), API key, base URL, and per-provider rate limit (requests per minute). Changes are saved via PUT /api/admin/providers/:id.
Models Tab
Lists all models registered under this provider, showing each model’s ID, capabilities (e.g. chat, embedding, vision), and status. Models are managed on the dedicated Models page but are displayed here for context.
Health Tab
Displays three health metrics:
- Status —
healthy,degraded, ordown - Latency — average response time in milliseconds
- Error Rate — percentage of failed requests
If no health data is available, the tab prompts you to run a connection test.
Testing Connectivity
Each provider card has a Test button, and the detail page has a Test Connection component. Testing sends a lightweight probe request through the gateway to the provider and returns:
success(boolean)latency(milliseconds)error(string, if the test failed)
Use this after adding a provider or rotating API keys to verify the connection before routing live traffic.
Provider Statuses
| Status | Meaning |
|---|---|
active | Provider is available for routing |
inactive | Provider is disabled; no traffic will be sent |
degraded | Provider is experiencing issues but still reachable |
Set a provider to inactive to temporarily remove it from routing without deleting its configuration.