Muse Spark 1.3 API Pricing: Standard vs Contributor

The number most buyers see for Muse Spark 1.3 API pricing is $1.25 per million input tokens and $4.25 per million output tokens. That is a useful budget assumption, but not a cleanly documented 1.3 rate card in every public source: Meta says pricing matches 1.2, while some catalogs still show the predecessor row. The cheaper Contributor route is even less certain for 1.3 and carries a data-use trade-off.

The price you can budget today

Muse Spark 1.3 launched on September 2, 2026, with access through Muse Code and the Meta Model API. Meta’s launch material says the new version is priced like its predecessor. A September 5 price receipt from Model Price Watch reports that it read Meta’s own pricing page and found the following Standard-tier rates:

These are per million tokens, not per thousand. The tracker’s blended figure uses a 3:1 input-to-output weighting and comes to about $2.00 per million tokens; the bill scenarios below use a 5:1 workload mix. The tracker reports no separate long-context premium on the Standard tier.

There is one important qualification. A technical review by AI on Mac found that the public developer catalog still visibly documented Muse Spark 1.2 rather than a complete 1.3 pricing row. Its conclusion was that $1.25/$4.25 is the logical 1.3 expectation because Meta described pricing as unchanged, but the numeric chain was indirect in that review.

Practical answer: use $1.25 input and $4.25 output for an initial estimate, then verify the live Meta rate card before moving production traffic. Do not present the number as a permanently guaranteed 1.3 price just because a third-party page lists it.

Three workload bills

The arithmetic is straightforward:

input millions × input rate + output millions × output rate

\*The Contributor column uses the currently documented Muse Spark 1.2 reference of $0.10 input and $0.20 output per million tokens, as reported by Model Price Watch. It is not a confirmed 1.3 Contributor quote.

These examples use a fixed 5:1 input/output mix; cache hits, retries, reasoning output, and tool loops can materially change real bills. For an agent that repeatedly reads the same repository or instruction prefix, cache behavior may matter more than the headline input price.

Contributor is a data-policy decision, not only a discount

The Contributor tier is attractive on paper. Model Price Watch reports roughly $0.10 per million input tokens and $0.20 per million output tokens for Muse Spark 1.2, plus a much lower rate limit for the cheaper tier: 100 requests per minute versus 3,000 for Standard. It also describes different data-use terms.

That makes Contributor unsuitable as an automatic production default. A lower token bill can be irrelevant if the tier’s data policy conflicts with proprietary code, customer records, or regulated workloads.

The evidence collected for this article does not establish a confirmed 1.3 Contributor SKU, its final rate, or its current limits. The safest way to evaluate it is as a separate procurement option:

1. Confirm that the model catalog actually exposes a 1.3 Contributor identifier.
2. Read the current data-use and training language before sending private material.
3. Check request-per-minute and token-per-minute limits against your agent’s concurrency.
4. Run the same workload on Standard and Contributor with identical prompts and tools.
5. Compare total successful task cost, not just token price.

A real-user thread in r/opencode shows why the policy question is operational, not theoretical. u/MorpheusN_ described using the model for public-data work and highlighted speed, but also raised concerns about Meta’s data handling and restrictive guardrails. The thread contains no formal privacy analysis, so it is evidence of user concern—not proof of a particular retention policy.

“It’s about 50x faster than Claude code nowadays” — u/Routine-Gas-8264, in the same Reddit discussion; an unverified user claim, not a controlled benchmark.

What the API release actually gives you

Meta’s official Muse Spark 1.3 announcement positions the model for long-horizon agentic work, coding, tool use, and multitasking. The release is available through Muse Code and the Meta Model API.

The evidence supports four practical characteristics:

• Agentic execution: Meta says 1.3 is trained to maintain longer-running objectives, recover from planning gaps, ask for clarification, and confirm consequential actions.
• Coding: Meta reports improvements over 1.2 for repository-scale and tool-driven coding workflows.
• Multimodal input: Verify the current API documentation before assuming a format or endpoint is enabled.
• Long context: the launch evaluation reaches the 1M-token range, but an evaluation range is not automatically the same as a guaranteed production API ceiling.

Copy the model identifier from Meta’s current developer catalog because it may differ between a provider catalog, a direct API, and an aggregator.

The AI on Mac review noted that max reasoning was pending additional safety testing at launch; if your application depends on it, test the live endpoint rather than assuming the announcement schedule is current.

What the evidence supports for workload selection

Pilot Muse Spark 1.3 first for workflows where tool use, sustained context, and coding reliability matter more than polished one-shot answers. Meta’s own comparison reports about 20% fewer tool calls and 25% fewer tokens than Muse Spark 1.2. Those are vendor-side comparisons, so they should be treated as a production hypothesis to test, not as an independent cost guarantee.

The user evidence points in the same general direction but is uneven. In the Reddit thread, u/MorpheusN_ praised Muse Spark 1.3 for “mass web research,” review, classification, and raw tool-use speed. The same report criticized restrictive refusals, overuse of Python instead of native Linux tools, and weaker nuance. Those observations are anecdotal and may depend heavily on the harness, plan, and task.

Read the benchmarks as evidence, not a purchase order

The launch benchmark picture is broad, but the evidence status matters more than the number of rows. AI on Mac’s review separates Meta runs, launch reporting, and public leaderboard checks. Several 1.3 results were not visibly synchronized to the corresponding independent leaderboard when checked on September 2.

These benchmarks measure different capabilities and should not be averaged or cross-compared. A 98.1 retrieval score does not prove that arbitrary million-token synthesis will be equally reliable.

Agent benchmarks depend on the harness. Test your own repository and track completion, interventions, tool calls, tokens, latency, and effective cost.

The migration choice: 1.3, 1.2, or neither

For an existing 1.2 deployment, the answer is not an automatic upgrade. Run a canary with:

1. Ten representative repository tasks, including at least two failure-recovery cases.
2. The same tool definitions, system prompt, context budget, and timeout.
3. Standard-tier pricing first, so a Contributor discount does not hide quality regressions.
4. Measurements for success rate, tool calls, output tokens, intervention count, latency, and cost.
5. A review of refusals, clarification requests, and edits that compile but change unrelated behavior.

Choose the tier with the lower cost per successful task, not the lower token rate. The strongest case for Contributor is a high-volume, low-sensitivity workload using public data; the strongest case against it is any workflow where prompts or outputs contain material you are not prepared to share under the tier’s current data terms.

Muse Spark 1.3 API pricing FAQ

Is $1.25/$4.25 the confirmed 1.3 rate?

It is the strongest current Standard-tier budget figure: $1.25 per million input tokens and $4.25 per million output tokens, with cached input reported at $0.15. Verify the live Meta rate card because some public catalogs still expose the 1.2 row rather than a complete 1.3 entry.

Is there a confirmed 1.3 Contributor price?

Not from the evidence reviewed here. The commonly cited $0.10 input and $0.20 output rates are a Muse Spark 1.2 Contributor reference reported by Model Price Watch, not a confirmed 1.3 quote. Treat any 1.3 Contributor listing as provisional until it appears in the current provider catalog and its data-use terms are clear.

Does cached input cost less?

Yes, the current Standard reference reports $0.15 per million cached input tokens. Cache eligibility, cache duration, and actual hit rates still affect the bill, so estimate from request logs rather than assuming every repeated prefix is cached.

Is the one-million-token context limit guaranteed in the API?

Meta’s launch evaluation reaches the 1M-token range, but that result does not guarantee a production API ceiling. Check the live endpoint specification before designing around it.

Is Muse Spark 1.3 better than 1.2?

It is the more logical first test for a new long-horizon coding or agent workflow. Existing 1.2 systems still need regression tests because tool-call frequency, clarification behavior, refusal patterns, and output style can change without a prompt change.

Can I use the Contributor tier for private source code?

Do not assume that a lower price makes it appropriate. Confirm the current data-use, training, retention, security, and rate-limit terms with Meta; if those terms do not meet your requirements, use a tier approved for the repository or keep the workload on non-sensitive data.

Price 1.3 at Standard rates and treat Contributor savings as upside until the live Meta catalog confirms the SKU and data terms.