For five years, Meta's strategy in AI infrastructure has been the same: build big, open-source it, let others run it. Llama 1, 2, 3, Scout, Maverick. All free, all downloadable, all self-hostable. That approach made Meta the default choice for any team that wanted to avoid vendor lock-in or needed a capable open-weight model they could run on their own infra.
That changed on July 9, 2026.
Meta Superintelligence Labs shipped Muse Spark 1.1, a proprietary, closed-weight reasoning model with a paid API. It's the first time in company history that developers have had to hand over a credit card to use a Meta model. The question isn't whether that's a shift. It obviously is. The question is whether what they're charging for is worth it.
What's in the Box
Muse Spark 1.1 is a multimodal reasoning model built specifically for agentic tasks. That framing isn't marketing copy. The architecture reflects it. The model is trained to operate in two distinct modes: as an orchestrator that gathers context, plans, and delegates execution across parallel subagents, and as a subagent that sticks to its assigned job and escalates when it hits a wall. Most models are bolted into agentic roles after training. Meta built it in from the start.
The context window is 1M tokens with active context compaction, meaning the model manages what stays in memory across long agent runs rather than blindly filling the context until something breaks. For persistent workflows where you're tracking state across dozens of tool calls, that matters more than raw context size.
Computer use and multimodal understanding are also in there.
The Pricing Math
$1.25 per million input tokens, $4.25 per million output tokens. Meta says that's roughly 25% of what Anthropic and OpenAI charge for comparable flagship models.
Claude Opus 4.8 runs at $15/$75 per million tokens. GPT-5.5 is in the same range. A team running 50 million output tokens a month pays around $3,750 with those models. With Muse Spark 1.1, the same load costs $212.50.
I haven't run Muse Spark in production yet, so I can't tell you whether the quality holds up at scale. But if the benchmarks translate, that price gap is real and it's large.
Where It's Actually Strong
Tool use is the standout result. On MCP Atlas, a benchmark that tests scaled, parallel tool use across many tools in sequence, Muse Spark 1.1 scores 88.1. Claude Opus 4.8 and GPT-5.5 are both in the high 70s to low 80s. That's a meaningful gap for agentic workloads where the model is calling external tools dozens or hundreds of times per session.
Muse Spark 1.1 also leads on JobBench, HealthBench Professional, and Finance Agent v2. These are domain-specific agent benchmarks, not general capability tests. If you're building a specialized agent for a vertical, those numbers matter more than broad MMLU-style scores.
The claimed zero-shot generalization to new MCP servers and custom tool schemas is worth testing directly. Meta says the model adapts to novel tools without fine-tuning. I'd verify that against your own schemas before trusting it in production.
Where It Falls Short
Pure coding is where the gap shows up. On SWE-bench Pro, Claude Opus 4.8 scores 69.2. Muse Spark 1.1 scores 61.5. That's not a rounding error. If your agent is doing heavy-duty software engineering, reviewing large PRs, or resolving complex merge conflicts at scale, you'll feel that difference.
Meta reports big gains on its internal Meta Internal Coding Bench. Proprietary benchmarks run on your own training data are worth treating with some skepticism until independent results come in.
For coding-heavy agents, staying on Opus 4.8 or running your own evals before switching is the right call. The tool-use advantage doesn't automatically offset the coding gap.
What This Means for Builders
Meta going paid is a bet that agentic infra is where the real money is. They're not competing on being the cheapest open-weight model anymore. They're competing directly with Anthropic and OpenAI, at a significant discount.
For teams building agents, this opens a genuine routing question. Tool-heavy, orchestration-intensive workflows where the model is coordinating across multiple external services? Muse Spark's MCP Atlas result justifies a serious evaluation. Software engineering agents or reasoning-heavy tasks? The SWE-bench gap is real enough that you shouldn't assume it's a drop-in replacement.
The bigger thing to watch is what this does to Llama. Meta says open source isn't going anywhere, and Llama 4 Scout and Maverick are still available. But there's now a two-tier strategy in place: free open models for the community and self-hosted edge cases, paid proprietary model for production agentic workloads. That's exactly the playbook OpenAI ran, and Anthropic.
Meta spent years arguing that ladder was unnecessary. Now they've built one.