Definition:
OpenRouter is a platform that provides access to artificial intelligence models from different providers through a common interface. It acts as an intermediary between an application and the services that run those models, centralising requests, usage tracking and certain billing options.
It is not a language model or an application that installs all those models on a device. It offers access through an API and a web interface for chatting with the available models.
Table of contents
How OpenRouter works
An application sends a request to the OpenRouter API and specifies the model it wants to use. The platform routes the request to a compatible provider and returns the response in a common format.
A model and a provider are not the same thing. The model defines the AI system’s capabilities; the provider operates the inference service that processes the request. The same model may be available through several providers, with differences in price, speed, availability or supported features.
Compatibility with the OpenAI API format makes it easier to reuse existing integrations. It does not mean that all models accept the same parameters, tools, input formats or context sizes.
On 19 August 2026, Stripe announced an agreement to acquire OpenRouter. The announcement did not disclose the price. TechCrunch, citing Bloomberg, reported a deal worth more than $7 billion.
Main features of OpenRouter
The platform brings together several features for integrating and managing access to models:
- Unified API: provides a common connection to different models, without developing a separate integration for every compatible provider.
- Model selection: its catalogue includes models from different organisations and families, such as GPT, Claude, Gemini, Llama and Mistral. Available versions and their capabilities change with the catalogue.
- Routing and alternatives: allows provider preferences and criteria such as price, latency or generation speed to be set. If a provider fails, it can try another when the configuration allows it. This does not guarantee continuous availability.
- Billing and usage: allows activity and costs to be reviewed, and credits to be used for paid requests. Rates depend on the model and provider; fees and options using users’ own keys may also apply.
- Monitoring tools: provide information for reviewing requests, usage and performance. These data describe use of the platform, not the editorial quality of each response.
- Access from applications: it can be integrated into web services, programs and mobile applications through its API. This does not mean that an official native application exists for every operating system.
- Documentation and integration: provides API references, development libraries and examples for implementing compatible features.
The routing documentation explains how to select providers and configure alternatives. Switching providers for the same model is different from choosing another model.
Benefits and limitations of OpenRouter
A common interface can reduce integration work and make comparing models easier. It also allows some monitoring and usage administration to be centralised when several AI services are used.
This centralisation does not eliminate every technical difference or ensure that switching models preserves an application’s behaviour. Instructions, parameters and the interpretation of responses may require adjustments.
The total cost depends on usage, the models and providers selected, and payment terms. Choosing a lower rate does not, by itself, demonstrate that a task will cost less: response length, retries or review work may change.
The platform adds an intermediary to the path taken by the data. OpenRouter’s policies must be distinguished from those of the provider processing each request; using a common API does not imply that every destination has the same data processing and retention conditions.
OpenRouter use cases
Access to different generative AI models can be applied to tasks such as the following:
- Working with content: generating drafts, translating or adapting texts with different models, while retaining editorial review of the result.
- Information processing: summarising documents, classifying messages or extracting data within a workflow.
- Conversational assistants: connecting an application to models that generate answers and, where supported, request the use of tools.
- Model comparison: running equivalent tasks and examining differences in responses, cost and processing time.
- Integration into digital products: incorporating AI features into SaaS services, websites or applications without building every provider connection from scratch.
OpenRouter facilitates access and routing. The application using it remains responsible for its logic, permissions and how responses are presented or used.
Configuring requests and responses
Requests can include instructions, parameters and tools, depending on what the model and provider support. Routing preferences allow destinations to be restricted or certain service characteristics to be prioritised.
Structured outputs allow responses following a JSON schema to be requested from compatible models and providers. Strict mode refers to compliance with that structure, not a guarantee that the data are true or that the model follows every instruction without errors.
An application can check both the structure received and the validity of its values before using them. Similarly, a request to use tools does not, by itself, execute an action: execution depends on the application or environment managing the tool.