TokenRate
Article · Cost Optimization4 min read

The Cheapest LLMs in the Compare Prices Grid (Ranked)

The cheapest LLMs from every provider, ranked side-by-side in TokenRate's Compare Prices grid — input rates, output rates, and quality scores compared.

Published

What "Cheapest LLMs" Means in 2026

Once you've narrowed a model shortlist on the main TokenRate calculator, the Compare Prices side-by-side view is where you stack them for a decision. Each row shows the provider, the model ID (the one you'd paste into your SDK), per-1M input and output costs, the context window, and the blended quality score. The "cheapest" LLM bucket in 2026 spans roughly $0.05 to $0.50 per 1M input tokens. Within that range, quality varies from 50 to 70 — a wide spread that the Compare Prices grid surfaces in seconds. The Compare Prices view makes the "Cheapest LLMs" picks visible at a glance — once you've ticked the candidates, the input-cost column does the budget filtering visually. For the underlying math, see tokens-to-dollars conversion; for routing strategy see multi-model routing with quality scores.

Who Fits the "Cheapest LLMs" Bucket

**Gemini 2.5 Flash-Lite** (Google): $0.075 / $0.300, Q55, 1M ctx. **GPT-4o mini** (OpenAI): $0.150 / $0.600, Q55, 128K ctx. **Llama 4 Scout** (Meta): $0.200 / $0.600, Q60, 1M ctx. **Mistral Small** (Mistral): $0.200 / $0.600, Q52, 32K ctx. **DeepSeek V3** (DeepSeek): $0.270 / $1.10, Q65, 64K ctx. All ticked together in /tools/compare-prices, the grid lays out the tradeoffs: quality varies from 52 to 65 within the budget, and output costs span $0.300 to $1.10/1M. Pick the highest-Value (quality ÷ input cost) entry that meets your quality floor.

Why Cheapest ≠ Best

Within the "Cheapest LLMs" bucket, the cheapest model is rarely the best Value pick. A model at $0.20 input / quality 60 has Value = 300; a model at $0.50 input / quality 70 has Value = 140 — the cheaper model wins by 2.1×. But if your workload's quality floor is 65, the cheaper model is disqualified even before Value enters the discussion. Always set the quality floor first, then optimize Value within it. For the framework, see why the cheapest LLM isn't always the best value.

The Cheapest LLMs Picks, Side-by-Side

In /tools/compare-prices, tick all candidates across their provider dropdowns. The grid renders input, output, context, and quality in stacked columns. For most Cheapest LLMs workloads, the order of operations is: quality floor first, then Value, then output cost. The grid makes all three visible in one scan. If your monthly volume is small (< 10M tokens), the model differences won't make material bill impact — pick on quality. If volume is high (> 1B tokens/month), even small input-cost deltas compound.

From Budget Bucket to Production

Once you've shortlisted within the Cheapest LLMs bucket, run the candidates through /tools/api-cost-estimator with your real workload volume to project monthly cost. For ongoing budget control, instrument token usage in production so you can catch cost regressions early — see token usage auditing. The grid pulls prices live from OpenRouter and quality from a blended Arena AI + Artificial Analysis pipeline — both refresh on a 60-minute incremental cache, so the comparison reflects current rates not a baked-in snapshot. Try the comparison yourself at /tools/compare-prices — it's the fastest way to stack model cost, context, and quality in a single grid.

Frequently Asked Questions

How do I open the Compare Prices grid?

Two ways: click the 'Compare Prices' tab at the top of the calculator card on the home page, or navigate directly to /tools/compare-prices. The standalone page is also linked from the main navigation under 'Tools'.

Can I share my comparison with teammates?

Yes — the page URL captures the current state. Send the link in Slack and your teammate sees the same grid. Useful for procurement and architecture-review meetings.

Is the data live or cached?

Live from OpenRouter (prices) and a blended Arena AI + Artificial Analysis pipeline (quality), refreshed on a 60-minute incremental cache. So the grid is at most an hour stale.

Where do I go after the grid to project monthly cost?

Once you've picked a winner, go to /tools/api-cost-estimator and plug in the model + your expected monthly token volume. The estimator does the per-1M math against your real workload mix.

Try the TokenRate Calculator

Try the comparison yourself at [/tools/compare-prices](/tools/compare-prices) — it's the fastest way to stack model cost, context, and quality in a single grid.

Open Calculator →