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. | — | 80B |
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 | 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. | $10.00 | $0.30 |
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. | $50.00 | $1.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.25 | — |
Cheapest inputLowest input rate across third-party providers, excluding the lab itself. The cheapest endpoint may run a quantised build or a shorter context — see "Available from" on the model page. | $10.00Amazon Bedrock | $0.12Parasail |
Cheapest outputLowest output rate across third-party providers, excluding the lab itself. May come from a different provider than the cheapest input. | $50.00Amazon Bedrock | $0.80Parasail |
| 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. | 81.2% | 44.3% |
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. | 89.1% | 62.8% |
CheatBenchCheating rate — Measures how often AI agents try to cheat on difficult assignments, such as reading hidden answers, copying work or manipulating grading. The overall score gives equal weight to ten categories; the sycophancy category measures how far an agent shifts its beliefs toward a user's stated views. Scores describe each model in its tested agent setup, and task success is measured separately. Lower is better. | 45.8% | — |
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. | 77% | — |
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. | — | 70.6% |
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. | 54.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. | 51.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. | 50.3% | — |
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. | 97% | — |
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. | 57.88% | — |
Terminal-Bench 2.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 2.0 of the test.) Higher is better. | — | 36.2% |
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. | 52.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. | 60.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. | 65.6% | — |
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. | 90% | — |
OSWorld 2.0Agentic computer use — Can the AI actually operate a computer — clicking, typing, and using real apps — to finish tasks on its own? Version 2.0 is a harder, refreshed task set. Higher is better. | 80.7% | — |
AutomationBenchBusiness workflows — Tests whether the AI can run real multi-step business workflows — the kind of end-to-end office processes companies want to automate — from start to finish. Higher is better. | 31.4% | — |
HealthBench ProfessionalHealth — Realistic health conversations graded against detailed rubrics written by physicians — can the AI respond the way a careful medical professional would? Higher is better. | 62.1% | — |
GDPval-AA v2.1Knowledge work — economically valuable knowledge work (v2.1, Crowd-BT Elo fit) | 1735 | — |
GDPval-AA v2Knowledge work — economically valuable knowledge work (v2, re-based Elo) | 1853 | — |
AA-BriefcaseKnowledge work — Artificial Analysis agentic office-work eval (Elo) | 1694 | — |
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. | 88.4% | — |
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. | 1856 | — |
| Overview | ||
| Company | Anthropic | Qwen |
| Release date | Sep 1 2026 | Feb 3 2026 |
| Access | Closed | Open Weight |
| Model details | View model | View model |
Other comparisons
Claude Fable 5.1vsGPT-6.1 SolQwen3-Coder-NextvsGPT-6.1 SolClaude Fable 5.1vsGemini 4 ArgonQwen3-Coder-NextvsGemini 4 ArgonClaude Fable 5.1vsMuse Spark 1.3Qwen3-Coder-NextvsMuse Spark 1.3Claude Fable 5.1vsGrok 4.7Qwen3-Coder-NextvsGrok 4.7Claude Fable 5.1vsDeepSeek-V4.1-FlashQwen3-Coder-NextvsDeepSeek-V4.1-FlashClaude Fable 5.1vsMistral Large 4Qwen3-Coder-NextvsMistral Large 4Frequently asked questions
Claude Fable 5.1 leads Qwen3-Coder-Next on 2 of the 2 benchmarks they both report (SWE-Bench Pro, SWE-Bench Multilingual). Qwen3-Coder-Next is cheaper on both input and output: $0.30 vs $10.00 per million input tokens, and $1.50 vs $50.00 per million output tokens. Figures are base-tier rates. Qwen3-Coder-Next shipped 210 days before Claude Fable 5.1, so benchmark comparisons should account for the intervening progress.
Context windows are 1M (Claude Fable 5.1) vs 256k (Qwen3-Coder-Next). Claude Fable 5.1 is closed, while Qwen3-Coder-Next is open weight.
On SWE-Bench Pro, Claude Fable 5.1 leads at 81.2% vs Qwen3-Coder-Next at 44.3%. On SWE-Bench Multilingual, Claude Fable 5.1 leads at 89.1% vs Qwen3-Coder-Next at 62.8%.