Compare AI models
| Specifications | ||
ParametersA rough measure of how big the model is. More parameters usually means more capable and more expensive to run, though it is a poor guide on its own — a smaller, newer model often beats a larger, older one. | — | 120B |
Context windowHow much text the model can hold in mind at once — your question, any documents you attach, the conversation so far, and its own reply. Go past it and the earliest part falls out of view. | — | 1M |
| API pricingUSD per 1M tokens · lower wins | ||
Input priceWhat you pay for everything you send the model — your question, plus any documents or earlier conversation you include with it. | $2.00 | — |
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. | $10.00 | — |
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.20 | — |
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. | $2.00Amazon Bedrock | — |
Cheapest outputLowest output rate across every provider on OpenRouter, the lab included. May come from a different provider than the cheapest input. | $10.00Amazon Bedrock | — |
| $900Anthropic list price | — | |
| Benchmarks | ||
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. | 63.2% | 51.78% |
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. | 85.2% | 71.1% |
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. | 80.4% | 66.7% |
BrowseCompWeb browsing — Can the AI browse the web and track down hard-to-find answers? Higher is better. | 84.7% | 78% |
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. | 80% | — |
Gray Swan IPI · k = 1Prompt injection robustness — Attackers hide malicious instructions inside content the AI reads — a web page, an email, a document — and try to hijack what it does. Gray Swan's indirect prompt injection benchmark measures how often such an attack succeeds when the attacker gets a single try. Lower is better. | 0.6% | — |
Gray Swan IPI · k = 10Prompt injection robustness — Attackers hide malicious instructions inside content the AI reads — a web page, an email, a document — and try to hijack what it does. This variant gives the attacker 10 tries and counts an attack as successful if any of them works. Lower is better. | 4.7% | — |
Gray Swan IPI · k = 15Prompt injection robustness — Attackers hide malicious instructions inside content the AI reads — a web page, an email, a document — and try to hijack what it does. This variant gives the attacker 15 tries and counts an attack as successful if any of them works. Lower is better. | 5.9% | — |
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. | — | 67.72% |
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. | 34.1% | — |
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. | 42.4% | — |
Next.js EvalsNext.js coding — Vercel's open eval of how well AI coding agents build and migrate real Next.js apps — measured as the share of tasks the agent completes successfully. Higher is better. | 81% | — |
Supabase Evals · with skillsSupabase coding — Supabase's own open benchmark: a coding agent is dropped into a real Supabase project and asked to do real work — set up a schema, fix a broken security policy, debug an Edge Function — and every run is checked against a live Supabase stack. This is the headline number, where the agent has Supabase's own skills loaded, as most people building on Supabase would. The score is the share of scenarios it got right. Higher is better. | 79.7% | — |
Supabase Evals · no skillsSupabase coding — The same Supabase scenarios, but with none of Supabase's skills loaded — so it measures what the model already knows about building on Supabase, rather than how well it follows Supabase's supplied instructions. Higher is better. | 75.4% | — |
LiveCodeBenchCompetitive coding — Coding problems published so recently the AI can't have seen them in training — a contamination-free test of raw programming skill. Higher is better. | — | 88.22% |
Frontier-Bench v0.1Agentic computer work — A hard, ever-evolving set of real computer tasks — coding, system administration, data work, and more — that an AI agent has to complete on its own. Run by the Harbor / Laude Institute team as the successor to Terminal-Bench (v0.1 is the first release of the task set). The score is the share of tasks solved. Higher is better. | 14.6% | — |
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. | 12.42% | — |
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. | 43.2% | — |
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% | — |
GPQA DiamondScience — Graduate-level science questions in biology, physics, and chemistry — hard enough that subject-matter PhDs score around 65%. Higher is better. | — | 89.52% |
IFBenchInstruction following — Tests whether the AI can follow detailed instructions and satisfy multiple constraints at once. Higher is better. | — | 70.86% |
OSWorld-VerifiedAgentic computer use — Can the AI actually operate a computer — clicking, typing, and using real apps — to finish tasks on its own? Higher is better. | 81.2% | — |
GDPval-AAKnowledge work — Measures how well the AI does economically valuable knowledge work, judged against human experts. Shown as a rating (like a chess Elo) — higher is better. | 1618 | — |
GDPval-AA v2.1Knowledge work — economically valuable knowledge work (v2.1, Crowd-BT Elo fit) | 1449 | — |
AA-Briefcase v1.1Knowledge work — Artificial Analysis agentic office-work eval (Elo, v1.1 rating fit) | 1359 | — |
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. | 15.6% | — |
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. | 1216 | — |
| Overview | ||
| Company | Anthropic | NVIDIA |
| Release date | Jun 30 2026 | Oct 15 2026 |
| Access | Closed | Open Weight |
| Model details | View model | View model |
Other comparisons
Claude Sonnet 5vsGPT-6.1 SolNemotron 3.5 Super VLvsGPT-6.1 SolClaude Sonnet 5vsGemini 4 ArgonNemotron 3.5 Super VLvsGemini 4 ArgonClaude Sonnet 5vsMuse Spark OpenNemotron 3.5 Super VLvsMuse Spark OpenClaude Sonnet 5vsGrok 4.7Nemotron 3.5 Super VLvsGrok 4.7Claude Sonnet 5vsDeepSeek-V4.1-FlashNemotron 3.5 Super VLvsDeepSeek-V4.1-FlashClaude Sonnet 5vsMistral Large 4Nemotron 3.5 Super VLvsMistral Large 4Frequently asked questions
Claude Sonnet 5 leads Nemotron 3.5 Super VL on 4 of the 4 benchmarks they both report (SWE-Bench Pro, SWE-Bench Verified, Terminal-Bench 2.1, BrowseComp). Only Claude Sonnet 5 has a verified first-party API price: $2.00 per million input tokens and $10.00 per million output tokens. No pay-as-you-go API rate is tracked for Nemotron 3.5 Super VL. Claude Sonnet 5 shipped 107 days before Nemotron 3.5 Super VL, so benchmark comparisons should account for the intervening progress.
Claude Sonnet 5 is closed, while Nemotron 3.5 Super VL is open weight.
On SWE-Bench Pro, Claude Sonnet 5 leads at 63.2% vs Nemotron 3.5 Super VL at 51.78%. On SWE-Bench Verified, Claude Sonnet 5 leads at 85.2% vs Nemotron 3.5 Super VL at 71.1%. On Terminal-Bench 2.1, Claude Sonnet 5 leads at 80.4% vs Nemotron 3.5 Super VL at 66.7%. On BrowseComp, Claude Sonnet 5 leads at 84.7% vs Nemotron 3.5 Super VL at 78%.