Compare AI models
| Specifications | ||
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 | 1.05M |
| 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. | $8.00Verified organizations only | $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. | $40.00 | $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 | $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. | — | $1.00OpenAI |
Cheapest outputLowest output rate across every provider on OpenRouter, the lab included. May come from a different provider than the cheapest input. | — | $5.00OpenAI |
| $3,600Anthropic list price | $900OpenAI list price | |
| These models have no shared benchmark scores. | ||
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. | — | 71.9% |
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. | — | 59% |
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. | — | 68.8% |
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. | — | 78.3% |
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. | — | 78.3% |
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. | — | 49.39% |
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. | 75.3% | — |
De novo binder design (24 hr)Protein design — de novo protein binder design within a 24-hour budget, as reported by Anthropic | 85.1% | — |
CyScenarioBenchCybersecurity — multi-step cybersecurity scenarios; each lab runs its own unique task set, so scores from different labs do not compare | 76.3% | — |
CVE RediscoveryCybersecurity — Anthropic internal evaluation: share of 1,829 published CVEs a model finds on its own from a snapshot of the project before the fix | 89.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. | — | 89.58% |
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. | — | 60.5% |
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. | — | 56.4% |
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. | — | 33.2% |
HealthBench · full setHealthcare — physician rubric score on the full set of the original HealthBench evaluation | — | 47.1% |
HealthBench · full set, length-adjustedHealthcare — physician rubric score on the full set of the original HealthBench evaluation, adjusted for answer length | — | 53.2% |
HealthBench · hardHealthcare — physician rubric score on the hard subset of the original HealthBench evaluation | — | 22.1% |
HealthBench · hard, length-adjustedHealthcare — physician rubric score on the hard subset of the original HealthBench evaluation, adjusted for answer length | — | 30.1% |
HealthBench · consensusHealthcare — physician rubric score on the consensus subset of the original HealthBench evaluation | — | 95.8% |
HealthBench · consensus, length-adjustedHealthcare — physician rubric score on the consensus subset of the original HealthBench evaluation, adjusted for answer length | — | 96.2% |
HealthBench Professional · OpenAI grading, rawHealth — unadjusted physician-rubric score using the official OpenAI grading procedure | — | 59.5% |
HealthBench Professional · OpenAI grading, length-adjustedHealth — official OpenAI grading with the response-length penalty applied | — | 60.8% |
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. | — | 1622 |
| Overview | ||
| Company | Anthropic | OpenAI |
| Release date | Nov 9 2026 | Sep 22 2026 |
| Access | Closed | Closed |
| Model details | View model | View model |
Other comparisons
Claude Mythos 5.2vsGemini 4 CarbonGPT-6 SolvsGemini 4 CarbonClaude Mythos 5.2vsMuse EmberGPT-6 SolvsMuse EmberClaude Mythos 5.2vsGrok 4.7GPT-6 SolvsGrok 4.7Claude Mythos 5.2vsDeepSeek-V4.1-Flash-1017GPT-6 SolvsDeepSeek-V4.1-Flash-1017Claude Mythos 5.2vsMistral Large 4GPT-6 SolvsMistral Large 4Claude Mythos 5.2vsKimi K3.1 ProGPT-6 SolvsKimi K3.1 ProFrequently asked questions
Claude Mythos 5.2 and GPT-6 Sol don't publish scores on any of the same benchmarks, so there's no direct head-to-head comparison. GPT-6 Sol is cheaper on both input and output: $2.00 vs $8.00 per million input tokens, and $10.00 vs $40.00 per million output tokens. Figures are base-tier rates. Claude Mythos 5.2 requires organization verification. GPT-6 Sol shipped 48 days before Claude Mythos 5.2, so benchmark comparisons should account for the intervening progress.
Context windows are 1M (Claude Mythos 5.2) vs 1.05M (GPT-6 Sol).
Direct benchmark comparisons are unavailable — Claude Mythos 5.2 and GPT-6 Sol don't publish scores on any of the same benchmarks.