Providers#

Open Providers to connect external AI services and control how traffic reaches them. Register vendor endpoints, enable models, set per-provider quotas, and define routing and failover for Chat and API clients.

Use this page when you need to:

• Add or update a provider connection for the organization.
• Cap budget, tokens, or requests on a specific provider.
• Enable or disable models so only approved ones appear in Chat and routing.
• Steer traffic to preferred models, or define fallbacks when a target is unavailable.
• Troubleshoot “provider or model missing” reports after access or routing changes.

From this page you can see which connections are configured and healthy, which models are enabled, how provider-level limits are consuming quota, and which routing rules apply to matching requests.

Next: add a provider if none exist, enable the models you want to offer, then assign them to users in AI Access — Allowed providers. Use Routing Rules when requests must target specific providers or fall back on failure. Inspect individual requests on Traces after routing changes.

The area has two tabs:

• Providers — Connections, models, and per-provider limits. See Providers tab.
• Routing Rules — Match conditions, targets, priority, and fallbacks. See Routing rules tab.

Providers tab#

Use the Providers tab to create, review, and manage provider connections and their usage limits.

The table helps you identify connections, verify availability, manage usage limits, and edit or delete providers.

Click the provider name to open the details page, where you can enable or disable individual models to control availability in the organization.

Provider detail page#

Click a provider in the Providers table to open the provider detail page.

The Summary section contains provider metadata, including the provider name, API type, status, base URL, and description. EDIT (to modify or delete the provider) and REFRESH (to reload page data) actions are available.

The Limits panel displays per-provider budget, token, and request quotas with reset intervals, current usage, and last/next reset dates. Click the pencil icon next to the Limits caption to edit limits. See Configure provider limits.

The Available Models section lists models discovered for the provider. The table displays each model Name, Created at, and an Enabled toggle. Use Search to filter the model list by name. To turn models on or off, see Enable or disable a model.

Enable or disable a model#

Use the Enabled column in Available Models to control which models from a provider are offered in Chat, routing rules, and API requests.

1. Open Providers, select the Providers tab, and click a provider name to open its detail page.

2. In the Available Models section, locate the model (use Search if needed).

3. Turn the model on or off using one of the following options:

• Individual model — Use the Enabled toggle in the model row.
• All models — Use the Enabled toggle in the column header to enable or disable every model in the table at once.

Disabled models remain listed on the provider detail page but are not selectable elsewhere in the platform. Users can access enabled models only when the provider is also assigned through Allowed providers in AI Access.

Configure provider limits#

Per-provider Limits control budget spend, token volume, and API request count for traffic routed through a provider connection. Limits can be edited from the Providers tab or the provider detail page.

1. Open Providers and select the Providers tab.

2. Start editing using either option:

• Provider detail page — Click a provider Name to open its detail page, then click the pencil icon next to the Limits caption.

• Providers table — In the Limits column for the provider row, click the pencil icon.

3. In the Edit limits form, configure any combination of the following limits:

• Budget — Set the Budget limit and Budget reset duration.
• Tokens — Set the Token limit and Token reset duration.
• Requests — Set the Request limit and Request reset duration.

4. Click SAVE to apply the limits, or CANCEL to discard your changes.

5. Optional: click CLEAR LIMITS to remove all configured quotas for the provider.

Edit a provider#

1. Open the provider for editing using one of the following options:

• On the Providers tab, click Edit in the provider row.

• On the provider detail page, click EDIT.

2. Review the pre-populated configuration and update the editable fields as needed.

3. Click SAVE to apply the changes.

Optional actions:

• Click CANCEL to return without saving changes.

• Use DELETE to remove the provider. See Delete provider for step-by-step instructions.

Changes can affect which models are available in Chat after the provider is refreshed. To make the provider available to users, verify that it is assigned through Allowed providers in AI Access.

Delete a provider#

1. Open Providers and select the Providers tab.

2. Remove the provider using one of the following options:

• Use the Delete row action on the provider in the table on the Providers tab, or

• Click the provider name to open the detail page, click EDIT, then click DELETE on the edit form.

3. Confirm the deletion when prompted.

The provider is removed from the organization and is no longer available for Chat, routing rules, or AI Access assignments.

Routing rules tab#

Use the Routing Rules tab to decide which provider and model handle matching requests, in what priority order, and which fallbacks apply when preferred targets fail. Configure rules after at least one provider connection exists.

Use this tab when you need to:

• Direct traffic by scope (organization, team, or employee), model, or other conditions.
• Prefer a primary provider/model while keeping a fallback ready.
• Change priority so one rule takes precedence over another.

Next: Add a routing rule, then verify behavior with sample traffic on Traces.

Use + ADD to create a rule. Filters and search narrow the list by enabled status, scope, provider, and model. Click a rule name to open its detail page.

Routing rule detail page#

Click a rule name in the Routing Rules table to open the routing rule detail page. Use EDIT to modify the rule configuration and REFRESH to reload the page.

Summary cards at the top of the page display the enabled status, number of targets, priority, and creation date.

The Summary section contains rule metadata, including the rule name, identifier, description, enabled status, scope, scope identifier, priority, creation date, and last update date. A copy control is available for the rule identifier.

The Condition section displays the matching expression that determines when the rule applies. A copy control is available for the condition expression.

The Targets table lists preferred provider and model destinations for matching traffic, including the routing weight assigned to each target. A footer below the table displays the total number of targets.

The Fallbacks section lists alternative provider and model destinations used when preferred targets are unavailable. When no fallbacks are configured, the section displays No fallbacks.

Add a routing rule#

A routing rule requires at least one configured provider for target and fallback destinations. If needed, add a provider first.

1. Open Providers in the main menu, go to the Routing Rules tab, and click + ADD.

2. Configure the rule settings:

• Enter a Rule name.
• Optionally enter a Description.
• Turn Enable Rule on or off.
• Select a Scope. For Team or Employee scopes, enter a Scope ID.
• Set a Priority value.

3. Define the rule conditions in Rule Builder:

• Use + Add rule and + Add rule group to create conditions.
• Combine conditions with AND and OR operators.
• Configure filters such as request type, model, team, and other available attributes.
• Review the generated condition in CEL Expression Preview.

4. Configure the preferred destinations in Targets:

• Select a Provider and Model.
• Specify a Weight value.
• Use + ADD TARGET to add additional destinations if required.
• Ensure the weights of all targets sum to 1 when multiple targets are configured.

5. Configure fallback destinations in Fallbacks:

• Select a fallback Provider and Model.
• Use + ADD FALLBACK to add additional fallback entries if required.

6. Click SAVE to create the routing rule.

Optional actions:

• Click CANCEL to return to the Routing Rules tab without saving changes.

Notes

• When Enable Rule is enabled, the rule is evaluated for matching requests.
• Scope determines whether the rule applies to the entire organization or to a specific employee.
• Priority controls the order in which matching rules are evaluated.
• Fallback destinations are used when the preferred target destinations are unavailable.

Edit a routing rule#

1. Open the routing rule for editing using one of the following options:

• On the Routing Rules tab, click Edit in the rule row.
• On the routing rule detail page, click EDIT.

2. Review the pre-populated configuration and update the required settings. See the detailed field descriptions at add a routing rule.

3. Click SAVE to apply the changes.

Optional actions:

• Click CANCEL to return without saving changes.
• Click DELETE to start the routing rule removal process. See Delete routing rule for step-by-step instructions.

Delete a routing rule#

1. Open Providers and select the Routing Rules tab.

2. Remove the rule using one of the following options:

• Use the Delete row action on the rule in the table, or

• Click the rule name to open the detail page, click EDIT, then click DELETE on the edit form.

3. Confirm the deletion when prompted.

The rule is removed from the organization and is no longer applied to matching requests.