Claude Opus 5vsMuse Spark 1.3
Claude Opus 5 | Muse Spark 1.3 | |
|---|---|---|
| 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 | 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. | $5.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. | $25.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.50 | — |
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. | $5.00Amazon Bedrock | — |
Cheapest outputLowest output rate across third-party providers, excluding the lab itself. May come from a different provider than the cheapest input. | $25.00Amazon Bedrock | — |
| Benchmarks | ||
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% | 75.4% |
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. | 70.6% | 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. | 26% | 49.4% |
GDPval-AA v2Knowledge work — economically valuable knowledge work (v2, re-based Elo) | 1861 | 1754 |
| BenchmarksPublished by one model only | ||
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. | 73% | — |
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.2% | — |
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. | 1.6% | — |
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. | 2% | — |
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. | 79.2% | — |
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. | 96% | — |
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.5% | — |
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. | 59.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. | 53.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. | 92% | — |
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. | 91.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. | 89.9% | — |
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% |
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. | 43.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. | 51.82% | — |
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% |
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. | 29% | — |
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% |
BrowseCompWeb browsing — Can the AI browse the web and track down hard-to-find answers? Higher is better. | 90.8% | — |
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% |
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. | 56.3% | — |
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. | 64.7% | — |
ARC-AGI-3Novel problem-solving — The third generation of the ARC-AGI series: instead of static puzzles, the AI is dropped into small interactive game-like environments it has never seen and has to figure out the rules and solve them on its own. Higher is better. | 30.2% | — |
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.4% | — |
BioMysteryBench · hardBiology — Real unsolved-style biology puzzles — the AI has to reason its way to an answer the way a research biologist would. The “hard” split contains the toughest cases. Higher is better. | 49.4% | — |
BioMysteryBench · human solvedBiology — Real biology puzzles that human experts have managed to crack — can the AI reach the same answers? Higher is better. | 90.1% | — |
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% |
Harvey's Legal Agent Benchmark (Held-out)Agentic legal work — Harvey's test of whether an AI agent can complete real legal work, scored on a held-out set of tasks the model makers never see — making the numbers harder to game. Higher is better. | 11.7% | — |
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. | 59.8% | — |
AA-BriefcaseKnowledge work — Artificial Analysis agentic office-work eval (Elo) | 1685 | — |
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% |
| Overview | ||
| Company | Anthropic | Meta |
| Release date | Jul 24 2026 | Sep 2 2026 |
| Access | Proprietary | Proprietary |
Other comparisons
Claude Opus 5vsGPT-5.6 SolMuse Spark 1.3vsGPT-5.6 SolClaude Opus 5vsGemini 3.8 FlashMuse Spark 1.3vsGemini 3.8 FlashClaude Opus 5vsGrok 4.6Muse Spark 1.3vsGrok 4.6Claude Opus 5vsDeepSeek-V4-Pro-0813Muse Spark 1.3vsDeepSeek-V4-Pro-0813Claude Opus 5vsMistral Medium 3.5Muse Spark 1.3vsMistral Medium 3.5Claude Opus 5vsKimi K3Muse Spark 1.3vsKimi K3
Frequently asked questions
Claude Opus 5 and Muse Spark 1.3 are evenly matched across the 4 benchmarks they both report (DeepSWE 1.1, OSWorld 2.0, AutomationBench, GDPval-AA v2). Only Claude Opus 5 has a verified first-party API price: $5.00 per million input tokens and $25.00 per million output tokens. No pay-as-you-go API rate is tracked for Muse Spark 1.3. Claude Opus 5 shipped 40 days before Muse Spark 1.3, so benchmark comparisons should account for the intervening progress.
Context windows are 1M (Claude Opus 5) vs 1M (Muse Spark 1.3).
On DeepSWE 1.1, Muse Spark 1.3 leads at 75.4% vs Claude Opus 5 at 68.8%. On OSWorld 2.0, Claude Opus 5 leads at 70.6% vs Muse Spark 1.3 at 66.9%. On AutomationBench, Muse Spark 1.3 leads at 49.4% vs Claude Opus 5 at 26%. On GDPval-AA v2, Claude Opus 5 leads at 1861 vs Muse Spark 1.3 at 1754.
Claude Opus 5 was released by Anthropic on Jul 24 2026.
Muse Spark 1.3 was released by Meta on Sep 2 2026.
Muse Spark 1.3 leads on DeepSWE 1.1 — Claude Opus 5 68.8% vs Muse Spark 1.3 75.4%.
Only Claude Opus 5 has a verified first-party API price: $5.00 per million input tokens and $25.00 per million output tokens. No pay-as-you-go API rate is tracked for Muse Spark 1.3. Rates are pay-as-you-go API prices verified on August 18, 2026.
Claude Opus 5 has a 1M context window; Muse Spark 1.3 has 1M.