What changed
Meta released Muse Spark 1.3 for Muse Code and Meta Model API. The company says the new model is better at long-horizon collaboration, multitasking, constraint retention, self-awareness and asking for clarification before consequential actions. In Meta’s engineering comparisons, Spark 1.3 used about 20% fewer tool calls and 25% fewer tokens than Spark 1.2. Independent Artificial Analysis testing also reports higher aggregate agent/coding performance, although not every benchmark improves and its maximum-reasoning mode can spend materially more reasoning tokens. Current published standard API pricing remains $1.25 per million input tokens and $4.25 per million output tokens.
Why it matters
For agent builders, model cost is not only a per-token price. A model that reaches the same result with fewer calls and fewer total tokens can lower end-to-end task cost and latency even when its rate card is unchanged. Spark 1.3 therefore matters as an efficiency/capability release rather than a simple benchmark bump. The caveat is that stronger reasoning settings can erase some of those savings on difficult tasks, so production routing should be evaluated at task level rather than from list price alone.
Meta is optimizing the behavior around the model, not only benchmark scores
Meta emphasizes constraint retention, multitasking, self-calibration and confirmation before consequential actions. Those properties matter in long-running coding and tool-using workflows where a capable model can still fail by forgetting earlier requirements or acting too aggressively.
Vendor-reported efficiency is unusually concrete
Meta says internal engineering comparisons against Spark 1.2 required about 20% fewer tool calls and 25% fewer tokens. Those are workload-specific vendor measurements, not universal guarantees, but they give builders a more useful hypothesis to test than an abstract benchmark score.
Independent results support a real capability gain with trade-offs
Artificial Analysis reports higher aggregate agentic performance for Spark 1.3, including improvements on several coding and tool-use benchmarks, while also recording regressions on some tests. Its maximum-reasoning mode improves some results further but uses substantially more reasoning tokens, which can change the real cost per completed task.
The rate card stays stable for now
Current independent reporting lists standard Meta Model API pricing at $1.25 per million input tokens and $4.25 per million output tokens, unchanged from Spark 1.2. That makes task-level token and tool-call efficiency the important economic variable rather than a headline price cut.