OpenRouter pricing by model

Where this provider fits

An OpenAI-compatible routing layer that offers one API across multiple language-model providers and exposes route-level pricing.

What can change the bill

• Provider routing can affect latency and behavior
• Input, output, and cached-token rates must be compared separately

Who should evaluate this route

• Broad language-model catalog
• OpenAI-compatible interface
• Routing and provider visibility

Compare two nearby options

Use the same model, meter, configuration, and workload when comparing channels.

• XiuRouter pricing evidenceA usage-based model API router with documented OpenAI, Anthropic, and Gemini protocol routes, scoped API keys, usage records, and source-linked model pricing.
• fal.ai pricing evidenceA developer platform focused on fast inference for image, video, and audio models, with model-level pricing and serverless APIs.

Recorded price evidence

Checked evidence, not a ranking: fresh rows were checked against the linked first-party source on the shown date. APIDir does not name a cheapest provider unless exact configurations and units match. Recheck before purchasing.

Model price comparisons for this provider

Follow each model page to compare this provider route with other accepted, source-linked offers on matching billing meters.

• Claude API provider pricingCompare Claude API routes by exact model, context tier, input and output meter, direct or router channel, source, and effective date.
• Gemini API provider pricingCompare Gemini API routes by exact model, service channel, standard or batch tier, token meter, and first-party source.
• GLM-5.2 provider pricingCompare GLM-5.2 API token prices across provider routes with exact model identity, meter, tier, source, and check date.
• GPT API provider pricingCompare GPT API routes by exact model ID, context band, input, cached-input and output meters, provider channel, and source.
• GPT-OSS 120B provider pricingCompare source-linked GPT-OSS 120B input and output token prices across provider routes while keeping infrastructure compute meters separate.
• Grok API provider pricingCompare Grok API pricing by exact model, direct or router channel, context tier, token meter, and source-linked route.
• Kimi API provider pricingCompare Kimi API pricing across provider routes without mixing Kimi versions, token meters, context tiers, or service channels.
• Mistral Medium 3.5 provider pricingCompare Mistral Medium 3.5 owner-direct and routed API evidence without treating two access channels as independent infrastructure or declaring a winner.
• Qwen API provider pricingCompare Qwen API pricing by exact model ID, provider channel, input and output token meter, context, and official source.

Related provider comparisons

Use a named alternative and explicit decision dimensions instead of comparing provider brands in the abstract.

• OpenRouter vs Together AICompare product and route control before choosing a route.

Documented integrations

These pages describe public-source setup paths. They do not claim that a project uses this provider in a private production deployment.

• Open WebUI provider integrationsFirst-party documentation for a documented Open WebUI configuration path.
• LibreChat provider integrationsFirst-party documentation for a documented LibreChat configuration path.
• LiteLLM with OpenRouterFirst-party documentation for a documented LiteLLM configuration path.
• Continue with OpenRouterFirst-party documentation for a documented Continue configuration path.

Editorial review

Read the evidence, tradeoffs, and unresolved buying questions in the independent APIDir review.