Routing Strategies
Smart Routing (Recommended for Most)
The platform automatically selects the best model for each request based on:- Request complexity and characteristics
- Available tier and provider constraints
- Real-time model performance and availability
- Maximizing cost-efficiency automatically
- Leveraging platform’s model optimization
- Not worrying about specific model selection
- Tier - Always use Budget/Standard/Advanced tier
- Provider - Restrict to OpenAI, Anthropic, or other provider
- Use Case - Hint toward specific category (Fast, Reasoning, Code, Creative)
Specific Model
You explicitly choose which model(s) to use. Optionally specify a budget model for cost optimization. Best for:- Consistent, reproducible behavior
- Using a specific model’s strengths
- Cost control with budget models
Supported Providers
OpenAI
- Models: gpt-5.1, gpt-5, gpt-4.5-turbo, gpt-4o, gpt-4o-mini, and more
- Best for: Broad capabilities, strong reasoning
- Cost: Standard to Premium pricing
Anthropic
- Models: claude-sonnet-4-5-20250929, claude-opus-4-1-20250805, claude-3.5-sonnet, and more
- Best for: Long context, nuanced reasoning
- Cost: Competitive with extended context pricing
Other Providers
Available depending on your account configuration. Check your model catalog in Console.Model Tiers
Tiers help classify models by capability and cost:| Tier | Cost | Capabilities | Examples |
|---|---|---|---|
| Budget | Lowest | Fast responses, simple tasks | gpt-4o-mini, claude-haiku |
| Standard | Medium | Balanced speed and capability | gpt-4o, claude-sonnet |
| Advanced | Highest | Complex reasoning, large context | gpt-5.1, claude-opus |
Budget Models
A budget model is a cheaper alternative the platform uses for simple requests, automatically detected per-request: Benefits:- Reduce costs on simple tasks without changing code
- Primary model handles complex reasoning
- Seamless fallback when budget model insufficient
- Must be same provider as primary model
- Usually a tier lower (e.g., Standard primary + Budget secondary)
Model Settings
Per-model configuration for fine-grained control:Parameters
| Parameter | Range | Default | Effect |
|---|---|---|---|
| temperature | 0.0-2.0 | 0.7 | Randomness (lower = deterministic) |
| top_p | 0.0-1.0 | 0.95 | Nucleus sampling threshold |
| max_tokens | 1-512K | Model default | Maximum output length |
| frequency_penalty | -2.0 to 2.0 | 0.0 | Reduce repetition |
| presence_penalty | -2.0 to 2.0 | 0.0 | Encourage new topics |
Fallback Behavior
When fallback is enabled (default), the platform automatically switches to an alternative model if your chosen model becomes unavailable. Fallback rules:- Stays within same provider (no cross-provider fallback)
- Respects tier constraints from Smart routing
- Maintains same model settings
Setting Model Routing
In Console (Agents)
- Go to Agents > Select Agent
- Click Settings > Model Configuration
- Choose Smart Routing or Specific Model
- Configure options (tier, provider, budget model, etc.)
- Click Save
In Console (MCP Gateways)
MCP Gateways use Smart Routing by default. Override by editing gateway specifications:- Go to Gateways > Select Gateway
- Click Specifications
- Add
model_routingsection - Click Save