Model Aliases & Routing

Model aliases let you map friendly or custom model names to real provider model names.

Why Use Aliases?

• Hide provider-specific deployment names
• Create consistent model names across your organization
• Support for fine-tuned models and custom deployments
• Easier client-side usage

Creating Aliases

When adding or editing a provider key, use the Aliases table:

• Source: Model name your apps will request (e.g. gpt-4o)
• Target: Actual model sent to the provider (e.g. gpt-4o-2024-11-20)

You can also define global routing rules under Routing Rules.

Example Use Cases

• my-company-gpt4o → gpt-4o-2024-11-20
• search-gpt → gpt-4o-mini-search-preview-2025-03-11
• claude → claude-3-7-sonnet-20250219