90 days of the enterprise, pro and team plans free, no card needed. See the plans
Best models
Every model in the live reference catalogue with a context window of at least 200k tokens, ranked by the intelligence index (Artificial Analysis, 0-100) with vendor list prices per million tokens. 12 qualify today.
Strongest first; price breaks ties. Value is index points per blended dollar. Click a model for its full specification, or compare two side by side.
| # | Model | Intelligence index | Input / 1M | Output / 1M | Context | Value | Compare |
|---|---|---|---|---|---|---|---|
| 1 | 58 | $4.00 | $20.0 | 1M | 7 | ||
| 2 | 56 | $2.00 | $10.0 | 1M | 14 | vs Claude Opus 5.5 | |
| 3 | 53 | $10.0 | $50.0 | 1M | 3 | vs Claude Opus 5.5 | |
| 4 | 53 | $10.0 | $50.0 | 1.1M | 3 | vs Claude Opus 5.5 | |
| 5 | 53 | $2.00 | $10.0 | 1.0M | 13 | vs Claude Opus 5.5 | |
| 6 | 52 | $2.00 | $10.0 | 1.1M | 13 | vs Claude Opus 5.5 | |
| 7 | 51 | $5.00 | $25.0 | 1M | 5 | vs Claude Opus 5.5 | |
| 8 | 50 | $10.0 | $50.0 | 1M | 2 | vs Claude Opus 5.5 | |
| 9 | 48 | $1.25 | $4.25 | 1.0M | 24 | vs Claude Opus 5.5 | |
| 10 | 48 | $2.00 | $10.0 | 1.1M | 12 | vs Claude Opus 5.5 | |
| 11 | 47 | $4.00 | $20.0 | 1.1M | 6 | vs Claude Opus 5.5 | |
| 12 | 46 | $2.00 | $6.00 | 500K | 15 | vs Claude Opus 5.5 |
A long document is a question of two numbers: whether the model can read it at all - the context window - and what reading it costs - the input price times the length. Only models accepting 200,000 tokens or more qualify here, which covers a long contract, a day of meeting transcripts or a mid-sized codebase in one request.
Input price dominates this task, the opposite of coding. A 150k-token contract summarised ten times a day is 1.5M input tokens against a few thousand output tokens, so a model with a low input rate and cached-input pricing wins even when its output rate is high. The cached-input column on each model page is the one to compare.
Two routing habits pay here. First, the request's size is one of the signals the router extracts, and a target whose context window does not fit it is not admissible, so a short question never pays for a long-context model. Second, retrieval narrowing can cut the input to the relevant passages before a model sees it - cheaper than any model choice.
Declare the models as targets and let the rule send the hard requests to the strongest one and the rest to the best value; the trace names the rule that fired.
# rules.yaml - long-documents: the strongest qualifying model for the hard requests, the best value for the rest
rules:
- name: long-documents-hard
when: { actions: [summarize, extract], min_complexity: 0.5 }
prefer: [claude-opus-5.5]
weight: 0.8
- name: long-documents-default
when: { max_complexity: 0.45 }
prefer: [muse-spark-1.3]
weight: 0.6