Basic configuration
Define providers in your Traffic Policy:Provider fields
id
- Type:
string - Required: Yes
- Description: Provider identifier. Use built-in names (
openai,anthropic,google,deepseek) or custom names for self-hosted providers.
id_aliases
- Type:
array of strings - Optional: Yes
- Description: Alternative identifiers for this provider. Allows clients to reference the same provider by different names.
base_url
- Type:
string - Optional: Yes
- Description: Custom endpoint URL for self-hosted or alternative provider endpoints. Required for custom providers.
disabled
- Type:
boolean - Default:
false - Description: Temporarily disable this provider without removing its configuration.
metadata
- Type:
object - Optional: Yes
- Description: Custom metadata for tracking and organization. Not sent to providers. Available in selection strategies.
api_keys
- Type:
array - Optional: Yes
- Description: List of API keys for this provider. See Managing API Keys.
models
- Type:
array - Optional: Yes
- Description: List of model configurations for this provider.
Model configuration
Configure specific models within a provider:Model fields
id
- Type:
string - Required: Yes
- Description: Model identifier as recognized by the provider.
id_aliases
- Type:
array of strings - Optional: Yes
- Description: Alternative identifiers for this model. Allows clients to reference the same model by different names.
disabled
- Type:
boolean - Default:
false - Description: Temporarily disable this model.
metadata
- Type:
object - Optional: Yes
- Description: Custom metadata for the model. Available in selection strategies.
Custom provider example
Connect to self-hosted models or custom endpoints:Multi-provider configuration
Configure multiple providers for failover and flexibility:Complete example
Next steps
- Managing API Keys - Secrets and key rotation
- Restricting Access - Limit providers and models
- Model Selection Strategies - Custom routing logic