Models
Explore and browse 300+ models and providers on our website, or with our API. You can also subscribe to our RSS feed to stay updated on new models.
Query Parameters
The Models API supports query parameters to filter the list of models returned.
output_modalities
Filter models by their output capabilities. Accepts a comma-separated list of modalities or "all" to include every model regardless of output type.
Examples:
The same parameter is available on the /v1/models/count endpoint so that counts stay consistent with list results.
supported_parameters
Filter models by the API parameters they support. For example, to find models that support tool calling:
sort
Sort models server-side before they’re returned. Accepts one of the following values:
Models without data for the requested sort dimension (e.g. no pricing, no throughput heuristics) sort last. Omitting sort preserves the default ordering (backward compatible).
Single Model Lookup
Look up a single model’s full details without fetching the entire list:
The endpoint resolves aliases automatically. For example, anthropic/claude-3-5-sonnet redirects to the canonical anthropic/claude-3.5-sonnet and returns its data.
Variant suffixes are also supported — append :free, :thinking, etc. to the slug:
Returns 404 if the model doesn’t exist and isn’t an alias for another model. The response shape wraps the same Model object used in the list endpoint:
Models API Standard
Our Models API makes the most important information about all LLMs freely available as soon as we confirm it.
API Response Schema
The Models API returns a standardized JSON response format that provides comprehensive metadata for each available model. This schema is cached at the edge and designed for reliable integration with production applications.
Root Response Object
Model Object Schema
Each model in the data array contains the following standardized fields:
Architecture Object
Pricing Object
All pricing values are in USD per token/request/unit. A value of "0" indicates the feature is free.
Top Provider Object
Benchmarks Object
Present only on models that have been evaluated in third-party benchmarks. Currently includes Design Arena rankings.
Rankings are computed among models listed on OpenRouter, not the full external leaderboard. Models without benchmark data omit the benchmarks field entirely.
Supported Parameters
The supported_parameters array indicates which OpenAI-compatible parameters work with each model:
tools- Function calling capabilitiestool_choice- Tool selection controlmax_tokens- Response length limitingtemperature- Randomness controltop_p- Nucleus samplingreasoning- Internal reasoning modeinclude_reasoning- Include reasoning in responsestructured_outputs- JSON schema enforcementresponse_format- Output format specificationstop- Custom stop sequencesfrequency_penalty- Repetition reductionpresence_penalty- Topic diversityseed- Deterministic outputs
Different models tokenize text in different ways
Some models break up text into chunks of multiple characters (GPT, Claude,
Llama, etc), while others tokenize by character (PaLM). This means that token
counts (and therefore costs) will vary between models, even when inputs and
outputs are the same. Costs are displayed and billed according to the
tokenizer for the model in use. You can use the usage field in the response
to get the token counts for the input and output.
If there are models or providers you are interested in that OpenRouter doesn’t have, please tell us about them in our Discord channel.
For Providers
If you’re interested in working with OpenRouter, you can learn more on our providers page.