Muse Spark 1.3vsGPT-6 Sol
Muse Spark 1.3 | GPT-6 Sol | |
|---|---|---|
| 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 | 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. | — | $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. | — | $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 |
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 | — |
| 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. | 75.4% | 68.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% | 60.5% |
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% | 33.2% |
| BenchmarksPublished by one model only | ||
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% | — |
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% |
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. | 1529 | — |
| Overview | ||
| Company | Meta | OpenAI |
| Release date | Sep 2 2026 | Sep 22 2026 |
| Access | Proprietary | Proprietary |
Other comparisons
Muse Spark 1.3vsClaude Opus 5.5GPT-6 SolvsClaude Opus 5.5Muse Spark 1.3vsGemini 3.8 FlashGPT-6 SolvsGemini 3.8 FlashMuse Spark 1.3vsGrok 4.7GPT-6 SolvsGrok 4.7Muse Spark 1.3vsDeepSeek-V4.1-FlashGPT-6 SolvsDeepSeek-V4.1-FlashMuse Spark 1.3vsMistral Medium 3.5GPT-6 SolvsMistral Medium 3.5Muse Spark 1.3vsKimi K3GPT-6 SolvsKimi K3
Frequently asked questions
Muse Spark 1.3 leads GPT-6 Sol on 3 of the 3 benchmarks they both report (DeepSWE 1.1, OSWorld 2.0, AutomationBench). Only GPT-6 Sol has a verified first-party API price: $2.00 per million input tokens and $10.00 per million output tokens. No pay-as-you-go API rate is tracked for Muse Spark 1.3. Muse Spark 1.3 shipped 20 days before GPT-6 Sol, so benchmark comparisons should account for the intervening progress.
Context windows are 1M (Muse Spark 1.3) vs 1.05M (GPT-6 Sol).
On DeepSWE 1.1, Muse Spark 1.3 leads at 75.4% vs GPT-6 Sol at 68.8%. On OSWorld 2.0, Muse Spark 1.3 leads at 66.9% vs GPT-6 Sol at 60.5%. On AutomationBench, Muse Spark 1.3 leads at 49.4% vs GPT-6 Sol at 33.2%.