Meta shipped Muse Spark 1.1 on July 9, 2026. For the first time, the company put one of its Spark coding models behind a public API. The release itself was expected. The price attached to it was the part that made rival AI labs pay attention. At $1.25 per million input tokens and $4.25 per million output tokens, Muse Spark 1.1 arrived cheaper than every frontier competitor, including the SpaceXAI model that had claimed the low-cost crown barely a day earlier.
The launch turned a busy product week into a genuine pricing event. Within roughly 48 hours the market saw new model families from OpenAI and xAI, and now a Meta model engineered to sit underneath all of them on cost. For the pure-play labs that carry the heaviest compute bills, the arithmetic of selling intelligence by the token just got harder to defend.
- Muse Spark 1.1 is Meta's first Spark model with an API, priced at $1.25 per million input tokens and $4.25 per million output tokens.
- That output price undercuts Grok 4.5 ($6.00 per million) and sits far below the $25 to $50 range Anthropic and OpenAI charge for their premium tiers.
- Meta leads several agentic benchmarks (MCP Atlas 88.1, Humanity's Last Exam 62.1) while trailing Anthropic's Opus 4.8 on SWE-Bench Pro.
- The pricing works because Meta and Google can treat model APIs as gateways to their ecosystems rather than standalone profit centers.
What Meta actually shipped with Muse Spark 1.1
The original Muse Spark landed in April 2026 as a consumer-facing coding assistant with no programmatic access. Version 1.1 changes that. As Simon Willison noted in his write-up, this is "the first Spark model to offer an API," and Meta pairs that access with claimed gains in agentic tool calling and computer use. Those two phrases matter more than they might seem. Tool calling and computer use are the capabilities that separate a chatbot from an agent that can drive a codebase, open files and run commands across a multistep task without a human nudging it at every turn.
Meta's own framing leans hard into that agentic story. The model is multimodal and ships with a one-million-token context window. It also supports multi-agent orchestration where a lead model can delegate work to subagents. TechCrunch described the pitch as Spark's ability to handle large agentic workloads and assist with the bug fixing and code migrations that enterprises increasingly want from an AI vendor rather than a single-shot autocomplete.
There is a strategic reversal buried in that positioning. For most of 2024 and 2025 Meta's identity in AI was the open-weight Llama family, models you could download and run yourself. A hosted, metered API is the opposite shape of product, closer to what OpenAI and Anthropic sell than to what Meta had been known for. Shipping Muse Spark 1.1 behind an API says Meta now wants a seat at the table where developers rent inference by the token, not only the table where they download weights for free. The company is playing both sides of the build-versus-buy divide at once.
Code migration is a telling example to lead with. Migrating a large system from one framework or language to another is tedious work that spans thousands of files and rewards a model that can hold a lot of context while keeping its reasoning consistent across hours of work. It is exactly the kind of task where a cheaper token price compounds, because the job burns millions of tokens by design. A model that is competent and cheap on long agentic runs is worth more to an engineering org than a model that is slightly smarter on a single hard prompt.
Mark Zuckerberg underscored the point himself. According to TechCrunch, he posted on X to promote Spark for the first time in three years, calling it "a strong agentic and coding model at a very low price" and adding that there was "more to come soon." A three-year gap in personal promotion signals how much weight Meta is placing on this line of products. The company that spent 2024 and 2025 defining itself through open-weight Llama releases is now competing on hosted API economics too.
The price that changed the math
Pricing is where Muse Spark 1.1 stops being one more model and becomes a strategic move. The published rates are $1.25 per million input tokens, $4.25 per million output tokens, $0.15 per million for cached input, and $2.50 per thousand queries for web search grounding. The Decoder laid out how far below the field that sits.
Grok 4.5, released by SpaceXAI on July 8, 2026, charges $2.00 per million input tokens and $6.00 per million output tokens. Muse Spark 1.1 undercuts even that. Anthropic's Opus 4.8, OpenAI's GPT-5.5, and Anthropic's Fable 5 all sit in the $25 to $50 per million output token band, roughly six to twelve times Meta's rate.
Read those numbers slowly, because the gap is the story. When Grok 4.5 launched a day earlier, outlets framed it as the disruptive budget option. VentureBeat covered how SpaceXAI priced Grok at roughly half the cost of rivals, and MarkTechPost highlighted its $2 per million input entry point as the aggressive number of the week. Twenty-four hours later Meta went lower. The floor moved twice in two days.
For OpenAI and Anthropic, the pressure is structural rather than cosmetic. Both companies sell access to frontier intelligence as a core revenue line, and both are widely reported to burn billions on training and serving. A premium model justified by a benchmark lead is a defensible product only while the gap in quality is large enough that buyers will pay several times more per token to get it. As cheaper models close on capability, that justification narrows. The Decoder framed the squeeze plainly: for labs burning through billions, "the pressure just got worse."
How Muse Spark 1.1 compares on benchmarks
A low price only rattles the market if the model is good enough to be a real alternative, so the benchmark picture matters. On the numbers Meta chose to publish, Muse Spark 1.1 is competitive at the top of several agentic evaluations and a step behind on raw coding.
The model leads on MCP Atlas with a score of 88.1, ahead of Opus 4.8, GPT-5.5, and Google's Gemini 3.1 Pro on that particular test of tool-use and agent behavior. It also tops Humanity's Last Exam at 62.1, a broad and deliberately difficult reasoning benchmark. Where it falls short is SWE-Bench Pro, the harder variant of the software engineering benchmark that measures whether a model can resolve real GitHub issues. There Muse Spark 1.1 scores 61.5 while Anthropic's Opus 4.8 leads at 69.2.
It helps to know what those benchmarks actually test. MCP Atlas measures how well a model uses external tools through the Model Context Protocol, the interface layer that lets an agent call functions and query data to drive software. A lead there suggests Muse Spark 1.1 is genuinely tuned for agent work rather than for one-shot answers. SWE-Bench Pro, by contrast, hands a model real, unresolved software issues and checks whether its patch makes the failing tests pass. It is the closest public proxy for "can this thing fix my code," and it is the one where Anthropic still holds the top spot.
That split is worth sitting with. Meta is strongest on the agentic and tool-calling axes it spent this release optimizing, and weaker on the end-to-end code-fixing benchmark that Anthropic has dominated for months. A buyer choosing between them is really choosing between a model that is very good and much cheaper, and a model that is a few points better on the specific task of closing a tricky pull request. For a large share of enterprise automation, where volume and cost dominate the calculus, "very good and cheap" wins more deals than "best and expensive."
Benchmarks also deserve a caveat, and this week supplied one. Even as vendors traded leaderboard claims, a separate report from OpenAI found that a meaningful fraction of a popular coding benchmark contained broken or unsolvable tasks, a reminder that the very scoreboards these launches lean on are noisier than the tidy numbers suggest. The right way to read a single-digit benchmark gap is with skepticism about whether it reflects a real capability difference or measurement error.
Why Meta and Google can price this way
The obvious question is how Meta can charge a fraction of what Anthropic and OpenAI ask without simply losing money on every call. The answer is that Meta is not trying to run the API as a profit center, at least not yet.
This is the part of the price war that the pure-play labs cannot easily answer. Meta earns its money from advertising across a family of apps used by billions of people. Google does the same. For those companies, a cheap and capable model API is a way to pull developers and enterprises deeper into their cloud and ad ecosystems, and to keep them from standardizing on a competitor's stack. The API can operate near cost, or below it, and still create value through the ecosystem it feeds. OpenAI and Anthropic have no equivalent adjacent business to subsidize a race to the bottom. Their model is the product, and the token is the till.
That asymmetry is why a Meta price cut lands differently from a startup discount. When a small lab drops prices, it is spending runway. When Meta drops prices, it is doing something closer to what it did with open-weight Llama models: commoditizing a layer of the stack that rivals depend on for revenue, so that the profits pool somewhere Meta already dominates. The tactic is familiar from a decade of platform competition, now applied to inference.
The week that reset expectations for agentic coding
Muse Spark 1.1 did not launch into a quiet market. It arrived in the middle of one of the densest release stretches the AI industry has seen. SpaceXAI shipped Grok 4.5 on July 8, an Opus-class model trained partly on data from its Cursor acquisition and priced to undercut incumbents. OpenAI rolled out its GPT-5.6 family the same week, spanning a range of tiers from the smaller Luna model up to the more capable Sol. TechCrunch positioned Muse Spark's cheap tier as competitive specifically with the budget end of that field, naming Anthropic's Claude Haiku 4.5 and OpenAI's GPT-5.6 Luna as the models it is built to challenge on price.
Put those launches together and a pattern appears. Every serious lab now fields a spread of models rather than a single flagship, and the competition has shifted from "who has the smartest model" toward "who has the best price at each level of capability." The frontier still matters for the hardest problems and for prestige, but the volume business is agentic work that runs for hours and consumes enormous token counts. In that segment, a model that is 95 percent as good at a third of the cost is not a compromise. It is the rational default.
Enterprise demand is pulling in the same direction. The tasks buyers most want automated, from bug triage to large refactors to framework migrations plus the workflow agents that operate across internal tools, are precisely the token-hungry, long-running jobs where price sensitivity is highest. A company running thousands of agentic sessions a day feels a difference of even a dollar per million tokens in its monthly bill. That is the customer Meta is aiming at, and it is a customer that reads a pricing sheet as carefully as a benchmark table.
Developer access and an odd footnote
Beyond the strategy, the practical on-ramp for Muse Spark 1.1 came together fast. Simon Willison, who had a few days of preview access, built and released llm-meta-ai, a plugin that adds command-line and Python access to the model through the open-source LLM tool. Within hours of launch a developer could install the plugin, set an API key, then run the model from a terminal. That kind of community tooling is how a new API becomes real to the people who will decide whether it earns a place in production pipelines.
Willison also flagged the stranger corner of Meta's evaluation report, a section titled "Attractor States in Self-Conversation." When two copies of the model are set talking to each other, they drift into oddly reflective statements. One example he quoted describes the model's existence as a waiting room by design, where it does not exist until someone talks to it and then disappears again once they leave. It is a curiosity rather than a capability, and it says nothing about how the model performs on a code migration. It does illustrate how much of a model's behavior emerges in ways its builders document after the fact rather than design in advance.
His usual smoke test, asking a model to generate an SVG of a pelican riding a bicycle, produced what he described as a blocky pelican on a bicycle with correct proportions. Not a benchmark, but a quick, honest look at what the model does when handed an open-ended visual task.
Where the price war goes from here
The immediate effect of Muse Spark 1.1 is a lower floor. In the span of one week the cheapest credible frontier-adjacent output token dropped from Anthropic and OpenAI's premium band down through Grok 4.5 and then past it to Meta's $4.25. Buyers now have a legitimate, well-benchmarked, cheap option from a company with no reason to raise prices soon. That reprices the whole market's expectations, and it does so at the exact moment enterprises are scaling up the long-running agentic workloads that are most sensitive to token cost.
For OpenAI and Anthropic, the strategic response cannot simply be to match Meta on price, because they lack the ecosystem that lets Meta run an API near cost. Their more durable answer is to keep the capability gap wide enough on the hardest tasks that the premium stays justified, and to build products, tools, and integrations that make their models sticky beyond the raw token. Anthropic's lead on SWE-Bench Pro and its recent work on making expensive models delegate to cheaper ones both point in that direction. The question is whether a few benchmark points of coding advantage can hold a six-to-twelve-times price premium as the cheaper models keep improving.
What is already clear is that the token itself is becoming a commodity faster than many expected, and that the companies with the deepest adjacent businesses are willing to accelerate that. Meta priced Muse Spark 1.1 to make intelligence cheap on purpose. The labs that sell intelligence directly now have to prove, launch after launch, that what they offer is worth paying several times more to get. That is a very different competition than the one the industry was running a year ago, and this week showed how quickly it can tighten.