Leaderboard / large language models

LLM leaderboard 2026

The models underneath most of the products in the app builder index. Same harness for every model, one composite index on a 0 to 100 scale, list prices per million tokens next to it.

Index leader

Claude Opus 4.5

Composite 89.10

Cheapest output

$0.42

DeepSeek V3.2 per million output tokens

Widest context

1,000,000

Gemini 3 Pro tokens in one request

8 models measured

Sorted by composite index descending. Prices are list, per million tokens, in US dollars.

LLM Tier composite index for large language models
#ModelVendorIndexContextIn $/MTokOut $/MTokLab note
1Claude Opus 4.5
Anthropic
89.10
200,0005.0025.00Best sustained multi file editing in the coding harness. Most expensive output tokens in the set.
2GPT-5.1
OpenAI
88.40
400,0001.2510.00Highest agentic tool use score in our harness. Long context recall degrades less than the cohort mean.
3Gemini 3 Pro
Google
86.90
1,000,0002.0012.00Largest usable context in the set and the strongest result on the document grounded subtest.
4Claude Sonnet 4.5
Anthropic
85.60
200,0003.0015.00Close to the frontier on code tasks at a third of the flagship output price.
5Grok 4
xAI
82.30
256,0003.0015.00Fast first token and strong reasoning traces. Weaker on strict JSON schema adherence.
6Qwen3 Max
Alibaba
79.70
262,1441.206.00Strong multilingual performance and the best non English result in the specification writing subtest.
7DeepSeek V3.2
DeepSeek
78.50
128,0000.280.42By far the best index points per euro. Tool calling needs stricter prompting than the frontier models.
8Llama 4 Maverick
Meta
74.80
1,000,0000.220.85Open weights, so it is the only model here you can run on your own hardware without a licence negotiation.

The model index and the app builder index are separate measurements and are not comparable to each other. A product built on the top model does not inherit its score.

Why we run a separate model index

Almost every product in the app builder index is a harness around a frontier model. When a model ships an update, the products built on it change behaviour without shipping anything themselves. That makes the model layer worth measuring on its own, otherwise a product looks like it improved when in fact its supplier did.

The model harness is smaller and more specific than the app builder specification. It tests agentic tool use over a fixed tool set, sustained editing across a repository rather than single file completion, recall at three quarters of the advertised context window, adherence to a strict JSON schema under adversarial input, and refusal behaviour on ambiguous but legitimate requests. It does not test conversation quality, creative writing or multimodal input, because none of those predict how well a product built on the model will complete the vibeOps specification.

Prices sit next to the index rather than inside it. Cost matters enormously in practice and it changes faster than capability, so folding it into the score would make the ordering unstable for reasons that have nothing to do with the models.