3 abstract model aliases. Each routes to the optimal underlying provider.
Why abstract names? We don't expose real provider models. This lets us swap underlying providers for better performance or pricing without breaking your integration. Your code always uses cheap-model, fast-model, or best-model.
Maximum cost efficiency. Best for high-volume tasks, summarization, and simple Q&A.
Optimized for low latency. Ideal for real-time chat and interactive applications.
Maximum quality and reasoning. For complex analysis, code generation, deep understanding.
Batch processing, summarization, classification
Real-time chat, interactive UX, low-latency APIs
Code generation, complex reasoning, multilingual