Providers#

The Providers area is used to connect external AI services and manage how they are exposed to Chat, API clients, and routing rules. The page contains two tabs: Providers, which lists configured provider connections, and Routing Rules, which controls request routing behavior.

Providers tab#

The Providers tab displays all provider connections configured for the organization. Summary cards at the top show the total number of providers, the number of active and inactive providers, and the number of API types represented in the current configuration. Use REFRESH to reload provider status information and table data.

The page includes filters for narrowing the provider list by API type and status, as well as a search field for locating providers by name, API type, URL, or description. Use + ADD to create a new provider connection. After a provider is added, grant an access to users through Allowed providers in AI Access.

The providers table displays key information about each configured provider, including its name, API type, base URL, description, status, creation date, and available row actions such as editing or deleting the provider. Click a provider name to open its detail page. A footer below the table shows the total number of providers and the number currently displayed after filters are applied.

Use the Providers tab when you need:

Explicit selection — Users or integrations pick one known provider (predictable behavior, comparative testing, or mandated vendor policies).
Direct vendor access — Teams consume a provider connection without an intermediate routing policy.
Per-provider observability — You monitor availability and errors per endpoint rather than only at the router layer.

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 Available Models section lists models discovered for the provider. The table displays each model name and creation date. A search field filters the model list by name. A footer below the table displays the total number of models and the number currently shown after search is applied.

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#

The Routing Rules tab contains the routing rules used to determine which provider and model handle requests routed through OptScale AI. Routing rules allow administrators to direct different types of traffic to specific providers and models, define rule priorities, and configure fallback behavior when preferred targets are unavailable.

The page provides filters for narrowing the list by enabled status, scope, provider, and model, as well as a search field for locating rules by visible attributes such as name, condition, target, or fallback configuration. Use + ADD to create a new routing rule.

The routing rules table displays the rule name, enabled status, scope, priority, matching conditions, target destinations, fallback destinations, and available row actions such as editing or deleting the rule. Click a rule name to open its detail page. Targets define the preferred provider and model combinations used when a rule matches a request, while fallbacks define alternative destinations that can be used if the preferred targets are unavailable or unable to process the request.

A footer below the table displays the total number of routing rules and the number currently shown after filters are applied.

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 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 fields detailed description 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.