Muse Glimmervso3
Muse Glimmer | o3 | |
|---|---|---|
| Specifications | ||
ParametersA rough measure of how big the model is. More parameters usually means more capable and more expensive to run, though it is a poor guide on its own — a smaller, newer model often beats a larger, older one. | 30B | — |
| 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. | — | $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. | — | $8.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. | $0.30DeepInfra | — |
Cheapest outputLowest output rate across third-party providers, excluding the lab itself. May come from a different provider than the cheapest input. | $1.10Phala | — |
| 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. | — | 26% |
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. | 51.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. | 76% | — |
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. | 51.7% | — |
MCP AtlasMulti-step tool use — Can the AI chain together many tools and steps to complete one bigger task, rather than doing just a single thing? Higher is better. | 75.5% | — |
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. | 22% | — |
GPQA DiamondScience — Graduate-level science questions in biology, physics, and chemistry — hard enough that subject-matter PhDs score around 65%. Higher is better. | 83.5% | — |
OSWorld-VerifiedAgentic computer use — Can the AI actually operate a computer — clicking, typing, and using real apps — to finish tasks on its own? Higher is better. | 65.9% | — |
GDPval-AA v2Knowledge work — economically valuable knowledge work (v2, re-based Elo) | 953 | — |
CharXiv ReasoningChart reasoning — Can the AI read and reason about complex charts and figures, not just text? Higher is better. | 78.8% | — |
MMMU-ProMultimodal reasoning — A tougher version of MMMU — college-level questions that mix images, diagrams, and text together. Higher is better. | 74% | — |
| Overview | ||
| Company | Meta | OpenAI |
| Release date | Aug 10 2026 | Apr 16 2025 |
| Access | Open Weight | Proprietary |
Other comparisons
Frequently asked questions
Muse Glimmer and o3 don't publish scores on any of the same benchmarks, so there's no direct head-to-head comparison. Only o3 has a verified first-party API price: $2.00 per million input tokens and $8.00 per million output tokens. No pay-as-you-go API rate is tracked for Muse Glimmer. o3 shipped 481 days before Muse Glimmer, so benchmark comparisons should account for the intervening progress.
Muse Glimmer is open weight, while o3 is proprietary.
Direct benchmark comparisons are unavailable — Muse Glimmer and o3 don't publish scores on any of the same benchmarks.