Flagship, mid-tier, small: which AI model tier should you actually use?
Every vendor sells three or four sizes. How to match tier to task, and why most production traffic belongs on the middle one.

OpenAI, Anthropic and Google each sell a ladder of models. The names differ (Astra, Fable, Argon at the top; mini, Haiku, Flash-Lite at the bottom) but the shape is the same: each step down is several times cheaper and faster, and somewhat less capable on hard reasoning.
The tiers
- Top tier (GPT-6 Astra, Claude Fable 5.1, Gemini 4 Argon): best at long, multi-step reasoning, agent tasks and hard code. Priced around $10 / $50 per million tokens, or $2–4 / $10–20 at launch promotions. Slowest.
- Mid tier (Claude Opus 5.5 and Sonnet 5.5, GPT-5.6 Sol and Terra, Gemini Flash): most production workloads. $2–4 input, $10–20 output. Good reasoning, much faster.
- Small tier (Haiku, mini and nano, Flash-Lite): classification, extraction, routing, simple chat. $0.10–0.75 input. Very fast.
Exact prices are on the pricing tracker.
How to choose
- Start in the middle. Build and evaluate on a mid-tier model. It is the default recommendation from the vendors themselves for most tasks.
- Step up only on measured failures. If your evaluation set shows the mid tier failing on specific hard cases, route those cases to the top tier rather than moving everything.
- Step down aggressively. Anything that looks like "is this email about billing?" or "pull the invoice number out of this PDF" belongs on the small tier. The accuracy difference is usually nil and the cost difference is 20x.
- Route. A cheap model can classify the request and send it to the right tier. This single pattern typically cuts a bill by more than half.
The trap
Teams prototype on the flagship because it works first time, then ship on it. Six months later the bill is ten times what a routed system would cost, and nobody has measured whether the flagship was ever needed. Measure on day one.
Common questions
Is the top tier always more accurate?
On hard reasoning and long agentic tasks, usually. On simple, well-defined tasks the gap is often zero, and the smaller model is faster.
Can I mix vendors?
Yes. Many teams route by task to whichever vendor's tier is cheapest for that task. The cost is maintaining prompts for more than one model.
What about open-weight models?
Self-hosted open models can be cheapest at very high volume, at the price of running your own inference. For most teams below that scale, API tiers are simpler.
Related

How to read an AI benchmark without being fooled
Vendor charts always show the vendor winning. The handful of questions that separate a meaningful result from marketing.…

LLM API pricing explained: tokens, caching, batch and the cliffs
How per-million-token pricing works, why output costs more, and the four levers that cut a bill by half or more.…

Open-weight vs closed AI models: what the difference means for you
Open-weight models can be downloaded and run anywhere; closed models live behind an API. The trade-offs on cost, control…
Get the brief in your inbox
One email every morning: the stories that mattered in AI, each with a one-line "why it matters" for your role. Free, no ads, unsubscribe any time.
Published daily by AI Briefing. We never share your address.