Muse Spark 1.3
Muse Spark 1.3 is a chat-oriented large language model from Meta, tracked here with third-party throughput and latency measurements from Artificial Analysis.
API Pricing
| Provider | Input / 1M | Output / 1M | Cached / 1M |
|---|---|---|---|
| $1.25 | $4.25 | $1.00 | |
| $1.25 | $4.25 | $0.150 |
Prices updated daily. Last check: Oct 19, 2026
Muse Spark 1.3 pricing by provider
Input, output, and batch rates, plus alternatives, for one provider at a time.
Performance & Benchmarks
Source: Artificial Analysis →Reasoning & Knowledge
- GPQA Diamond93.5%
- Humanity's Last Exam48.7%
Coding
- SciCode58.8%
Agentic & Tool Use
- Terminal-Bench v2.184.3%
- τ-bench Banking50.5%
Instruction & Long Context
- Long-Context Reasoning83.0%
Benchmarks measured Oct 2026. Scores are independent evaluations, not vendor-reported.
Model Details
General
- Creator
- Meta
- Modalities
- Text
Capabilities
- Open Source
- No
Strengths & Limitations
Strengths
- Measured output throughput of approximately 110.75 tokens per second, fast enough for streaming long responses without visible stalling
- Attributed to Meta, a creator with an established track record of publicly documented language model releases
- Independent third-party performance measurement available from Artificial Analysis rather than only vendor-reported figures
- Steady generation rate suits long-form text output where total completion time is dominated by token count
- Latency profile is well suited to asynchronous and batch processing pipelines where first-token delay is not user-facing
- Listed as a general chat model, so it fits standard conversational and instruction-following API patterns
Limitations
- Measured time to first token of roughly 39,264 ms (about 40 seconds) makes it poorly suited to interactive, real-time chat interfaces
- Context window length is not confirmed in our data, so maximum input size cannot be planned against
- Input and output modalities beyond text are not confirmed — vision or audio support should be verified with the provider
- No accuracy benchmark scores (reasoning, coding, math) are tracked for this model, making capability comparison against peers difficult
- Limited public documentation relative to more widely covered models, which raises the effort required for evaluation
Key Features
About Muse Spark 1.3
Common Use Cases
Muse Spark 1.3 is best matched to text generation workloads that run out of band from a live user. Document drafting, bulk content generation, summarization jobs, offline data labeling, and scheduled report writing all tolerate a long start-up delay and benefit from the model's sustained ~110 tokens per second generation rate once output begins. It is a reasonable candidate for queue-backed pipelines where a request is submitted, processed, and the result delivered later by webhook or notification. Conversely, the measured ~40 second time to first token makes it a poor structural fit for live chat assistants, IDE autocomplete, voice interfaces, or any agentic loop that issues many short sequential calls, since each hop would inherit that startup cost. Because we do not track confirmed context window or accuracy benchmarks for this model, teams considering it for reasoning-heavy or long-document work should run their own evaluation before committing.
Frequently Asked Questions
How much does Muse Spark 1.3 cost?
Pricing for Muse Spark 1.3 varies by provider and by pricing type — input tokens, output tokens, and any cached or batch rates are typically billed differently. Rates also change over time as providers adjust their offerings. Check the pricing table on this page for current per-provider figures rather than relying on any fixed number.
What is Muse Spark 1.3 best used for?
It suits asynchronous text generation: batch content production, document drafting, summarization jobs, and other pipelines where the result is not needed instantly. Its measured throughput of about 110.75 tokens per second handles long outputs well, but the roughly 39-second time to first token makes it a weak fit for interactive chat or latency-sensitive agent loops.
Why is the time to first token so high?
Artificial Analysis measured approximately 39,264 ms before the first token appeared. Delays of that size usually come from extended pre-generation processing, endpoint queueing, or a heavily batched serving configuration. We cannot confirm the specific cause from the data we hold, and results may differ across providers or over time — measure against your own target endpoint if latency is critical.
What context window does Muse Spark 1.3 support?
We do not have a confirmed context window figure for this model in our database. That means the value is unverified on our side, not that the model is limited. Consult the documentation of the provider you plan to use for the maximum supported input length.
Who created Muse Spark 1.3?
Our catalog attributes Muse Spark 1.3 to Meta. It is listed as a chat model, meaning it is intended for conversational and instruction-following text generation through a standard chat completion API.