Compare AI models
| Specifications | ||
ParametersThe learned values that shape how a model responds. B means billion and T means trillion. For mixture-of-experts models, the total count is larger than the number active for each token. Parameter count alone does not measure quality. | — | 4B |
Context windowHow much information the model can work with in one request, measured in tokens — pieces of words or other data. This includes your question, attachments, conversation and reply. Limits can vary by model variant and provider. | 1M | 256k |
| API pricingUSD per 1M tokens · lower wins · base tier | ||
Input priceWhat you pay for everything you send the model — your question, plus any documents or earlier conversation you include with it. | $0.10 | — |
Output priceWhat you pay for the text the model writes back. It is normally the dearer half: producing an answer costs more than reading one. | $0.50 | — |
Cached input priceA reduced rate for text you send over and over. If every request starts with the same instructions or the same document, the provider keeps a copy ready and charges less to read it again. | $0.01 | — |
Cheapest inputLowest input rate across every provider on OpenRouter, the lab included. The cheapest endpoint may run a quantised build or a shorter context — see "Available from" on the model page. | $0.10Amazon Bedrock | — |
Cheapest outputLowest output rate across every provider on OpenRouter, the lab included. May come from a different provider than the cheapest input. | $0.50Amazon Bedrock | — |
| $45.00Anthropic list price | — | |
| These models have no shared benchmark scores. | ||
BullshitBench v2Nonsense detection — Given a confidently-worded but nonsensical prompt, does the AI spot that it makes no sense and push back — instead of playing along and inventing an answer? The score is how often it clearly called out the nonsense. Higher is better. | 57% | — |
SWE-Bench ProAgentic coding — Can the AI fix real bugs in real software? It's handed actual problems from open-source projects and has to write code that genuinely solves them. Higher is better. | 64.8% | — |
SWE-Bench VerifiedCoding — Real coding tasks pulled from open-source projects — the AI has to find and fix actual bugs. A human-checked version of the original SWE-Bench. Higher is better. | — | 59.5% |
SWE-Bench MultilingualMultilingual coding — Like SWE-Bench, but the coding problems span many programming languages, not just one. Tests how broadly the AI can code. Higher is better. | 83.7% | — |
SWE-Bench MultimodalMultimodal coding — Real bug reports that arrive with pictures attached — a screenshot, a mockup, a page rendering wrongly — so the AI has to read the image as well as the code to work out what to fix. Higher is better. | 30.7% | — |
CursorBench 4.0Agentic coding — Cursor's own test of coding agents on ambiguous, multi-file tasks taken from real Cursor sessions — editing, refactoring, investigating a codebase, understanding what the user meant, managing jobs and following a design. Cursor runs each model at several reasoning efforts; each release here carries the score of its best listed effort. Scores aren't comparable with earlier CursorBench versions. Higher is better. | 48.4% | — |
FrontierSWE V2Ultra-long-horizon coding — Engineering problems that would occupy a person for days: systems implementation, performance work, scientific computing and AI research, with up to twenty hours per task. Partial credit is awarded, because finishing one outright is still rare. Higher is better. | 43.8% | — |
FrontierCode v1.1 (Main) · main splitAgentic coding — A set of very hard, frontier-difficulty coding tasks an AI agent has to complete end to end. The score is the share of tasks in the main split it solves. Higher is better. | 46.4% | — |
FrontierCode v1.1 (Extended) · extended splitAgentic coding — frontier-difficulty agentic coding tasks (v1.1, extended split) | 58.4% | — |
Terminal-Bench 4.0Agentic terminal coding — Can the AI work in a command-line terminal — running commands and finishing technical setup tasks the way a developer would? Version 4.0 recalibrated how much time, CPU and memory each task gets, removed eight tasks and fixed nineteen, so fewer runs fail for reasons that have nothing to do with the model. Scores are not comparable with earlier versions. Higher is better. | 39.2% | — |
Terminal-Bench 2.1Agentic terminal coding — Can the AI work in a command-line terminal — running commands and finishing technical setup tasks the way a developer would? Higher is better. | — | 18.1% |
Terminal-Bench-Science 0.1Agentic scientific computing — The same command-line setup as Terminal-Bench, pointed at scientific work: the AI has to drive research tooling and computational workflows through to a result, rather than administer a machine. Version 0.1 is the first release of the task set, and scores run lower than on the general board. Higher is better. | 20.6% | — |
Humanity's Last Exam · no toolsMultidisciplinary reasoning — Humanity's Last Exam — extremely hard expert questions across many subjects, written so you can't just look up the answer. “No tools” means the AI answers on its own. Higher is better. | 45.9% | — |
Humanity's Last Exam · with toolsMultidisciplinary reasoning — Humanity's Last Exam — extremely hard expert questions across many subjects. “With tools” means the AI is allowed to search the web or run code while answering. Higher is better. | 57.4% | — |
ARC-AGI-2Abstract reasoning — Puzzle-style tests of abstract reasoning and pattern-finding — the kind of thing people find easy but AIs often struggle with. Higher is better. | 61.25% | — |
GPQA DiamondScience — Graduate-level science questions in biology, physics, and chemistry — hard enough that subject-matter PhDs score around 65%. Higher is better. | — | 72.41% |
IFBenchInstruction following — Tests whether the AI can follow detailed instructions and satisfy multiple constraints at once. Higher is better. | — | 77.94% |
OSWorld 2.1 · offlineAgentic computer use — Can the AI actually operate a computer — clicking, typing, and using real apps — to finish tasks on its own? Version 2.1, in its offline setting. Scores are not comparable with version 2.0. Higher is better. | 72.4% | — |
HealthBench Professional · rawHealth — physician-graded conversations, scored before adjustment for answer length | 71% | — |
HealthBench Professional · length-adjustedHealth — The same physician-graded health conversations as HealthBench Professional, scored with an adjustment for how long the answer is — so a model cannot gain by padding its reply. The adjustment moves scores by several points, so these numbers are not interchangeable with the unadjusted ones. Higher is better. | 64.8% | — |
GDPval-AA v2.1Knowledge work — economically valuable knowledge work (v2.1, Crowd-BT Elo fit) | 1620 | — |
AA-Briefcase v1.1Knowledge work — Artificial Analysis agentic office-work eval (Elo, v1.1 rating fit) | 1578 | — |
Chartography · with toolsChart tasks — A chart-centred test run with tools available to the AI, reported separately from the chart-reading benchmarks above it. Higher is better. | 86.2% | — |
Chartography · no toolsChart tasks — The same chart-centred test with no tools: the AI has to read each chart unaided. Scores run far lower than the with-tools version, so read the two as separate tests. Higher is better. | 46.4% | — |
OfficeQA Pro · extracted textDocument Q&A — answering the 133 Treasury document questions with extracted text and code execution available | 60.3% | — |
threejsevalCommunity preference (Three.js) — Every model gets the same prompt — "the Eiffel Tower", "a glass fishbowl", "a robot arm picking toys into a box" — and builds a 3D scene in Three.js. Real people then see two scenes side by side, names hidden, and vote for the one they prefer. The votes become a chess-style Elo rating on threejseval.com, averaged across all the prompts. It measures whether the scene looks and moves right to a human eye, not whether the code passes a test. Higher is better. | 1409 | — |
| Overview | ||
| Company | Anthropic | NVIDIA |
| Release date | Oct 7 2026 | Oct 16 2026 |
| Access | Closed | Open Weight |
| Model details | View model | View model |
Other comparisons
Claude Haiku 5.5vsGPT-6.1 TerraNemotron Labs Dory 1.0 4BvsGPT-6.1 TerraClaude Haiku 5.5vsGemini 4 CarbonNemotron Labs Dory 1.0 4BvsGemini 4 CarbonClaude Haiku 5.5vsMuse EmberNemotron Labs Dory 1.0 4BvsMuse EmberClaude Haiku 5.5vsGrok 4.7Nemotron Labs Dory 1.0 4BvsGrok 4.7Claude Haiku 5.5vsDeepSeek-V4.1-Flash-1017Nemotron Labs Dory 1.0 4BvsDeepSeek-V4.1-Flash-1017Claude Haiku 5.5vsMistral Large 4Nemotron Labs Dory 1.0 4BvsMistral Large 4Frequently asked questions
Claude Haiku 5.5 and Nemotron Labs Dory 1.0 4B don't publish scores on any of the same benchmarks, so there's no direct head-to-head comparison. Only Claude Haiku 5.5 has a verified first-party price for an available API: $0.10 per million input tokens and $0.50 per million output tokens. No currently available pay-as-you-go API rate is tracked for Nemotron Labs Dory 1.0 4B. Claude Haiku 5.5 shipped 9 days before Nemotron Labs Dory 1.0 4B, so benchmark comparisons should account for the intervening progress.
Context windows are 1M (Claude Haiku 5.5) vs 256k (Nemotron Labs Dory 1.0 4B). Claude Haiku 5.5 is closed, while Nemotron Labs Dory 1.0 4B is open weight.
Direct benchmark comparisons are unavailable — Claude Haiku 5.5 and Nemotron Labs Dory 1.0 4B don't publish scores on any of the same benchmarks.