Model management
Let clients use familiar model names, and understand where the prices used for cost estimates come from.
Two levels §
Model configuration is split across two places:
- Group's Models tab — Determines which models this Group exposes externally. Only models listed here can be requested.
- Model page — Global model pricing and specifications used for cost estimates.
Most day-to-day model configuration happens in Groups; see Groups and channels. This page covers Group-level models and aliases, then global pricing.
Model discovery §
Do not type model names manually. In the Group's Models tab, fetch the upstream model list and select the ones you need.
Discovery returns whatever the upstream lists. Some providers expose many models you do not use, so select only the models you actually use. A smaller set prevents accidental use of expensive models and simplifies troubleshooting.
If an available model is missing from the upstream list, you can add it manually.
The list reflects the upstream response. A model is exposed only after you select it.
Model aliases §
Configure aliases in Group's "Models and Aliases" tab to solve a common problem: the name requested by the client does not match the actual model name upstream.
Common use cases:
- Change vendors without changing code — Keep the model name in application code stable while mapping it to a different upstream model in the gateway.
- Unified naming — Normalize provider-specific names for the same model with an alias.
- Version convergence — Map dated model versions to one stable name.
The application requests the alias; the gateway substitutes the actual upstream model name when forwarding.
Where prices come from §
Cost estimation requires model prices. Prices come from two sources:
- Auto Sync — Fetch common-model prices from the public data source models.dev.
- Manual entry — Enter prices missing from the data source or replace them with your negotiated rates.
You can disable automatic price synchronization in settings; see Runtime settings. Once disabled, you maintain all prices manually.
Prices are defined by token category, which is required for accurate cost estimates:
- Input / Output — The two basic token categories.
- Cache read — Usually priced far below ordinary input tokens.
- Cache write — Some providers bill this separately.
Some models also support tiered pricing by context length. Configure higher unit prices beyond a context-length threshold.
Manually change the price §
Automatically synchronized prices can be overridden manually. The entry is then marked as manually maintained, and future synchronization does not overwrite your changes.
Use Reset to restore the automatically synchronized value.
Manually enter prices when you have negotiated enterprise rates, use a relay with its own pricing, or use a model missing from the public data source. In those cases, synchronized public prices are not authoritative.
What happens when a price is missing §
The absence of price data will not cause the request to fail. The model remains available, but that usage is excluded from cost estimates. The monitoring page reports it under Cost Unpriced.
If cost estimates look too low, check Data Completeness in Monitoring and troubleshooting. A high Cost Unpriced count means one or more models need pricing data.
One more point: price changes are not applied retroactively. A price added today affects only future statistics; earlier requests remain unpriced.