Compare AI models
| Specifications | ||
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 | ||
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. | — | $1.25Meta |
Cheapest outputLowest output rate across third-party providers, excluding the lab itself. May come from a different provider than the cheapest input. | — | $4.25Meta |
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. | — | 39% |
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. | — | 2.5% |
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. | — | 41.6% |
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. | — | 75.4% |
SWEAtlas CodeBase QnACodebase understanding — Questions about how an unfamiliar codebase actually works — where something is handled, what a change would touch — answered by reading the repository rather than editing it. Tests understanding rather than patch-writing. Higher is better. | — | 59.4% |
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. | — | 88.8% |
JobBenchProfessional tool use — Tests the AI on professional workplace tasks that require using real work tools — the kind of multi-step jobs an office worker handles. Higher is better. | — | 64.9% |
DeepSearchQAAgentic browsing — Questions that cannot be answered from one page: the AI has to search the web, follow the trail across several sources, and put the pieces together into an answer. Higher is better. | — | 89.4% |
Agentic IF Index (Internal)Instruction following — Meta's internal measure of whether a model keeps following the instructions it was given while working as an agent — over a long run of tool calls, not just in a single reply. Higher is better. | — | 57.8% |
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. | — | 66.9% |
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. | — | 49.4% |
GDPval-AA v2Knowledge work — economically valuable knowledge work (v2, re-based Elo) | — | 1754 |
MRCR · 256k-512kLong context — Tests whether the AI can find specific details buried inside a very long document, here across inputs of roughly 256k to 512k tokens — several books' worth of text. Higher is better. | — | 98.5% |
MRCR · 512k-1MLong context — The same buried-detail retrieval test run on even longer inputs, from roughly 512k up to a million tokens. Scores usually slip as the document grows, so read it against the shorter span above. Higher is better. | — | 98.1% |
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. | — | 1435 |
| Overview | ||
| Company | DeepSeek | Meta |
| Release date | Feb 5 2024 | Sep 2 2026 |
| Access | Open Weight | Closed |
| Model details | View model | View model |
Other comparisons
DeepSeek-MathvsClaude Haiku 5.5Muse Spark 1.3vsClaude Haiku 5.5DeepSeek-MathvsGPT-6.1 SolMuse Spark 1.3vsGPT-6.1 SolDeepSeek-MathvsGemini 4 ArgonMuse Spark 1.3vsGemini 4 ArgonDeepSeek-MathvsGrok 4.7Muse Spark 1.3vsGrok 4.7DeepSeek-MathvsMistral Large 4Muse Spark 1.3vsMistral Large 4DeepSeek-MathvsKimi K3Muse Spark 1.3vsKimi K3Frequently asked questions
DeepSeek-Math and Muse Spark 1.3 don't publish scores on any of the same benchmarks, so there's no direct head-to-head comparison. DeepSeek-Math shipped 940 days before Muse Spark 1.3, so benchmark comparisons should account for the intervening progress.
DeepSeek-Math is open weight, while Muse Spark 1.3 is closed.
Direct benchmark comparisons are unavailable — DeepSeek-Math and Muse Spark 1.3 don't publish scores on any of the same benchmarks.