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. | — | 320B |
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 | 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. | $4.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. | $20.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. | $4.00Amazon Bedrock | $0.0285Relace |
Cheapest outputLowest output rate across every provider on OpenRouter, the lab included. May come from a different provider than the cheapest input. | $20.00Amazon Bedrock | $0.0923Relace |
| $1,800Anthropic list price | $10.32Relace · fp4 | |
| Benchmarks | ||
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. | 57.8% | 36.8% |
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. | 66.4% | 35.76% |
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. | 67.7% | 55.3% |
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. | 40% | 48.8% |
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. | 89% | 78% |
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. | 2065 | 1373 |
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. | 11.2% | — |
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. | 63% | — |
ProgramBenchProgram reconstruction — The AI receives a working program and its documentation, then builds a replacement from scratch without the original source code, internet access or decompilation. The score is the percentage of 200 programs that pass every behavioral test. We record each model's best published mini-SWE-agent result, including higher reasoning efforts where available. Partial test-pass rates and almost-solved programs do not count toward this score. Equal scores share a rank here; the official board also uses partial progress to break ties. Higher is better. | 18.5% | — |
DeepSWE 1.1Agentic coding — Artificial Analysis' independent test of deep, agentic software-engineering work — the AI has to plan and carry out substantial coding tasks end to end. (Version 1.1 of the test.) Higher is better. | — | 63.4% |
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. | 54.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. | 100% | — |
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. | 89.9% | — |
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. | 91.3% | — |
NL2Repo-BenchRepo-level code generation — Tests whether the AI can turn a natural-language requirement into working code across an entire repository, not just produce a single function or patch. Higher is better. | — | 56.3% |
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. | — | 84.3% |
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. | 58.7% | — |
Toolathlon-VerifiedPersonal tool use — Tests how well the AI uses everyday personal tools and apps to get things done — a human-checked version of Toolathlon. Higher is better. | — | 78.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. | 91.7% | — |
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. | 81.8% | — |
Agent's Last Exam · pass@1Agentic computer use — A hard set of desktop and operating-system tasks an AI agent has to finish by looking at the screen and working the machine itself. The score is the share it passes outright — partial credit does not count. Higher is better. | — | 26.3% |
GDPval-AA v2.1Knowledge work — economically valuable knowledge work (v2.1, Crowd-BT Elo fit) | 1846 | — |
GDPval-AA v2Knowledge work — economically valuable knowledge work (v2, re-based Elo) | — | 1773 |
AA-Briefcase v1.1Knowledge work — Artificial Analysis agentic office-work eval (Elo, v1.1 rating fit) | 1822 | — |
CharXiv Reasoning · with toolsChart reasoning — The same chart-and-figure reasoning test, run with the AI allowed to use tools — writing code to inspect the image, for instance — rather than reading the chart unaided. Scores run higher than the unaided version, so read the two as separate tests. Higher is better. | — | 89.4% |
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. | 64.4% | — |
OfficeQA ProDocument Q&A — Questions about office documents, where answering depends on reading the page as a document — layout, tables and figures included — rather than as loose text. Higher is better. | — | 62.4% |
MVBenchVideo understanding — Video questions that cannot be answered from any single frame: the AI has to follow what changes over time — the order things happen in, what moved where. Higher is better. | — | 77.8% |
MMVUVideo reasoning — Expert-level video questions drawn from specific disciplines, where answering means applying subject knowledge to what is happening on screen rather than just describing it. Higher is better. | — | 80.5% |
BabyVisionVisual reasoning — Tests core visual reasoning — seeing and understanding images the way even young children can, which AIs often find surprisingly hard. Higher is better. | — | 53.4% |
| Overview | ||
| Company | Anthropic | Z.ai |
| Release date | Sep 22 2026 | Aug 26 2026 |
| Access | Closed | Open Weight |
| Model details | View model | View model |
Other comparisons
Claude Opus 5.5vsGPT-6.1 TerraGLM-5.3-FlashvsGPT-6.1 TerraClaude Opus 5.5vsGemini 4 CarbonGLM-5.3-FlashvsGemini 4 CarbonClaude Opus 5.5vsMuse Spark OpenGLM-5.3-FlashvsMuse Spark OpenClaude Opus 5.5vsGrok 4.7GLM-5.3-FlashvsGrok 4.7Claude Opus 5.5vsDeepSeek-V4.1-Flash-1017GLM-5.3-FlashvsDeepSeek-V4.1-Flash-1017Claude Opus 5.5vsMistral Large 4GLM-5.3-FlashvsMistral Large 4Frequently asked questions
Claude Opus 5.5 leads GLM-5.3-Flash on 5 of the 6 benchmarks they both report. Only Claude Opus 5.5 has a verified first-party price for an available API: $4.00 per million input tokens and $20.00 per million output tokens. No currently available pay-as-you-go API rate is tracked for GLM-5.3-Flash. GLM-5.3-Flash shipped 27 days before Claude Opus 5.5, so benchmark comparisons should account for the intervening progress.
Context windows are 1M (Claude Opus 5.5) vs 1M (GLM-5.3-Flash). Claude Opus 5.5 is closed, while GLM-5.3-Flash is open weight.
On CursorBench 4.0, Claude Opus 5.5 leads at 57.8% vs GLM-5.3-Flash at 36.8%. On Terminal-Bench 4.0, Claude Opus 5.5 leads at 66.4% vs GLM-5.3-Flash at 35.76%. On Humanity's Last Exam · with tools, Claude Opus 5.5 leads at 67.7% vs GLM-5.3-Flash at 55.3%. On AutomationBench, GLM-5.3-Flash leads at 48.8% vs Claude Opus 5.5 at 40%. On Chartography · with tools, Claude Opus 5.5 leads at 89% vs GLM-5.3-Flash at 78%. On threejseval, Claude Opus 5.5 leads at 2065 vs GLM-5.3-Flash at 1373.