August 2026 edition · updated monthly

Which model for which job? The working cheat sheet.

Opinionated picks from a team that ships these systems weekly. No benchmarks theater — what we'd actually reach for first, and what we'd try if the budget says no.

How we pick

These recommendations come from production engagements, not leaderboard screenshots. For each job we weigh four things: quality on that job specifically (a great coding model can be a mediocre support agent), latency as users feel it, real per-request cost after prompt caching and batching, and operational maturity — rate limits, uptime, SDKs, structured-output support.

Prices below are banded: $ ≈ pennies per thousand requests, $$ ≈ tens of dollars per month at moderate volume, $$$ ≈ frontier-model pricing worth budgeting deliberately. For exact numbers on your workload, use our LLM cost calculator. We re-test monthly and after every major release.

Best model for high-volume customer-support chat

Top pickGemini 2.5 FlashGoogle
Also goodClaude Haiku 4.5Anthropic

Cheap enough to answer every customer, fast enough to feel instant, and good tone out of the box.

$ · pennies per conversationbudget-friendly

Best model for coding agents & code review

Top pickClaude Opus 5Anthropic
Also goodClaude Sonnet 5Anthropic

Strongest long-horizon agentic coding and real-bug detection; Sonnet covers interactive speed.

$$$ · worth it for eng time savedquality-first

Best model for RAG knowledge assistants

Top pickClaude Sonnet 5Anthropic
Also goodGPT-5.1OpenAI

Grounded answers with honest "not in the docs" behavior — the failure mode that matters in RAG.

$$ · cache the corpus, costs drop ~70%quality-first

Best model for batch summarization & extraction

Top pickGPT-5 miniOpenAI
Also goodGemini 2.5 Flash-LiteGoogle

At thousands of documents a day, small models + batch APIs (50% off) win — save the big guns for hard docs.

$ · route the hard 5% to a bigger modelbudget-friendly

Best model for deep research & complex reasoning

Top pickClaude Opus 5Anthropic
Also goodGemini 3 Pro (preview)Google

Multi-step analysis that holds together over an hour of work, not just a clever paragraph.

$$$ · budget per-task, not per-tokenquality-first

Best model for strict structured output (JSON)

Top pickGPT-5.1OpenAI
Also goodClaude Sonnet 5Anthropic

Schema-enforced outputs on both; pick by which ecosystem your pipeline already lives in.

$$ · validation failures ≈ zeroquality-first

Best model for on-prem & data-sovereign AI

Top pickLlama 3.3 70BMeta (self-host)
Also goodMistral LargeMistral

When data can't leave the building, a tuned open model on your GPUs beats no AI at all — by a lot.

$$ · infra cost, not token costopen-source

Best model for realtime voice agents

Top pickGPT RealtimeOpenAI
Also goodGemini LiveGoogle

Native speech-to-speech latency is the whole game; text models with TTS bolted on feel laggy.

$$ · per-minute pricing — watch idle timequality-first
📌 Pin this page. Model rankings shift monthly — we re-test and update this sheet with every major release. This edition: August 6, 2026.

Common questions

Which LLM is best for coding in 2026?

For long-horizon agentic coding and code review, Claude Opus 5 is the strongest pick. For fast interactive coding at lower cost, Claude Sonnet 5 gets close at a fraction of the price. Budget-constrained teams can route routine edits to a smaller model and reserve the frontier model for the hard tasks.

What's the cheapest good model for high-volume customer support?

Gemini 2.5 Flash and Claude Haiku 4.5 both handle support chat well at pennies per conversation. Combined with prompt caching for your knowledge base, per-conversation cost typically lands well under one cent.

Can I run a good LLM on-premises for data-sovereign workloads?

Yes. Llama 3.3 70B self-hosted on your own GPUs is the usual starting point, with Mistral Large as an alternative. Quality trails the frontier APIs, but for regulated data that can't leave your infrastructure, a tuned open model is far better than no AI at all.

Should I pick one model, or route between several?

Production systems increasingly route: a small, cheap model for the easy 80–95% of traffic and a frontier model for the hard remainder. Routing typically cuts cost 3–10× at near-equal quality — which is exactly why per-job model choice matters more than any single "best model".

How often does this cheat sheet change?

We re-test and update it monthly, and after every major model release. The edition date at the top of the page reflects the last review.

Got a shortlist? Put real monthly numbers on it for your exact workload.

Open the LLM Cost Calculator →

Picking the model is the easy 10%. The other 90% — evals, caching, routing, fallbacks, cost control — is what makes it production. That's the part Ahitrisan Intel builds.

Ask us anything →