Most people check OpenRouter’s model list before they check the pricing page. That’s backwards.
The model you choose determines cost more than the platform does. Understanding how OpenRouter charges — and where the math can surprise you — is the prerequisite to running a sustainable API workflow.
Quick Answer: OpenRouter charges per token at provider-set rates with a small markup. Costs vary 10x–100x across models. Expensive doesn’t always mean better for your task. The real saving is in routing logic, not just model selection.
How OpenRouter pricing actually works
OpenRouter does not set model prices. Providers (Anthropic, OpenAI, Google, Mistral, etc.) set the base rate. OpenRouter applies a small platform markup on top — typically a few percent — and passes the rest through.
You pay per token: separately for input tokens and output tokens. Output tokens cost more than input across every major model.
Pricing is listed per million tokens (M tokens) on the model detail page. Most operators think in terms of calls, not tokens — the translation matters.
A typical 1,000-word output is roughly 750–900 output tokens. At $15/M output tokens (GPT-4o pricing as of mid-2026), that’s about $0.012 per call. At $3/M (Claude Haiku, Gemini Flash), it’s closer to $0.003.
At scale — 500 calls/day — that difference is $6/day vs $1.50/day. Over a month: $180 vs $45.
Where cost differences are largest
1. Frontier vs efficient models
The frontier tier — Claude Opus, GPT-4o, Gemini 1.5 Pro — costs 5x–20x more than efficient models like Claude Haiku, Gemini Flash, or Mistral Small.
For most content and classification tasks, efficient models perform within 10–15% of frontier models at a fraction of the cost.
2. Input token management
Long system prompts run on every call. A 2,000-token system prompt at $3/M input costs $0.006 per call in input alone. At 500 calls/day, that’s $3/day — $90/month — just from the system prompt.
Compress system prompts. Remove redundant instructions. Pass context only when needed.
3. Output length control
Uncontrolled output length is the most common cost leak. A model that writes 1,500 words when 600 would serve the task costs 2.5x more per call.
Add explicit output length instructions to your prompts. “Answer in under 300 words” is a valid system instruction.
Model tiers by price range (mid-2026)
| Tier | Models | Input $/M | Output $/M |
|---|---|---|---|
| Frontier | Claude Opus 4, GPT-4o, Gemini 1.5 Pro | $10–$30 | $15–$60 |
| Mid | Claude Sonnet 4, GPT-4o mini, Gemini 1.5 Flash | $1–$5 | $3–$15 |
| Efficient | Claude Haiku 4, Gemini 2.0 Flash, Mistral Small | $0.10–$0.80 | $0.30–$2.50 |
| Open (self-hosted routes) | Llama 3, Qwen3, Mistral 7B | $0.05–$0.30 | $0.10–$0.50 |
Prices fluctuate. Check the OpenRouter pricing page for current rates before building a budget.
When usage gets expensive
Three patterns consistently cause cost overruns:
Frontier model as default. Using GPT-4o or Claude Opus for every task regardless of complexity. A classification call does not need a frontier model.
No fallback routing. When your primary model has an outage, OpenRouter can route to a fallback. Without this, you retry on the same expensive model or fail silently.
Context window inflation. Passing entire conversation history on every call. With a 128k context model at $10/M input, 50k tokens of context per call costs $0.50 per call in input alone.
The routing logic that actually saves money
OpenRouter supports provider preferences and model fallback routing. A practical setup for content operators:
- Primary: efficient model (Haiku, Flash) for drafts and classification
- Fallback: mid-tier (Sonnet, GPT-4o mini) if primary fails
- Reserve: frontier only for final review or complex reasoning passes
This hybrid approach keeps cost at efficient-tier for 80–90% of calls while maintaining quality guarantees.
See the OpenRouter for Beginners guide for setup context, or the OpenRouter vs Direct API comparison if you’re deciding whether to use the aggregator at all.
Frequently Asked Questions
Is OpenRouter cheaper than going direct to providers? Not always on a per-token basis — there’s a small markup. The value is in convenience: one API key, one billing account, and routing across providers. For single-provider usage at high volume, going direct may save 2–5%.
Does OpenRouter charge for failed calls? If the model returns an error before generating tokens, you are not charged. If the model generates partial output and then fails, you pay for the tokens generated.
Can I set a spending limit on OpenRouter? Yes. OpenRouter supports credit limits and budget alerts. Set a monthly cap to avoid surprise bills during testing.
What’s the minimum cost to test a new model? Almost nothing. A single 500-token test call on an efficient model costs under $0.001. Testing 10 models with 5 calls each is under $0.05.
Are open-source model routes actually free? No. OpenRouter charges for the compute even on open models. Rates are lower than frontier models, but not zero. If you need truly free inference, run models locally.
How does billing work for team accounts? OpenRouter supports organization accounts with shared credits. All API keys under an org draw from the same credit pool. Usage is tracked per key for auditing.
Explore OpenRouter on MoltyFlywheel
If you are evaluating whether OpenRouter fits your operator stack — cost structure, routing options, and which models are worth testing — the OpenRouter tool overview walks through the practical setup decisions.