Guides
Choose a model
Read your catalog, name models three ways, and compare provider capabilities.
Read the catalog at runtime
Browse Supported Models for concise model labels,
providers, token limits, and capabilities. Those labels are for display and are
not guaranteed to be valid request values. GET /v1/models is authoritative
for the exact callable model IDs available to the caller's key, and the catalog
can change over time, so read it at runtime instead of hardcoding names. The
quickstart has the request.
Two ways to name a model
A model ID pins one exact model. Use an id from GET /v1/models:
{
"model": "your-model-id",
"input": "Classify this support request."
}An explicit list names providers directly and is tried in order. See Add fallbacks.
Provider and model syntax
Entries in a models list use provider:provider-model:
openai:gpt-5.4-mini
fireworks:accounts/fireworks/models/kimi-k2p7-codeAdd a service tier as a third segment to pin it, for example
openai:gpt-5.4-mini:flex. See
Service tiers.
Every candidate must be available to your key.
Capability differences
Streaming, function tools, and JSON Schema output work across providers, subject to model support. Input types differ more:
| Capability | OpenAI | Fireworks |
|---|---|---|
| Image input | Model-dependent | Model-dependent |
| File/document input | No Router upload API | Not supported |
| Audio input | Model-dependent | Not supported |
| Basic web search | Supported | Not supported |
Support varies by model within a provider, so test the features your request actually uses before putting a model into a fallback list.