Muse Spark 1.3 vs Muse Spark 1.2

Muse Spark 1.3 and Muse Spark 1.2 side by side: specs, capabilities, parameters, and live pricing from the EmpirioLabs catalog.

Meta AI Text Generation

Muse Spark 1.3 vs Muse Spark 1.2 at a glance

Muse Spark 1.3 and Muse Spark 1.2 are both Meta AI models in the Text Generation category, available through the EmpirioLabs API.

Key differences

  • Muse Spark 1.3 is the newer release (Sep 2, 2026); Muse Spark 1.2 was released on Aug 5, 2026.
  • Both models have a context window of 1M tokens.
  • Input types only Muse Spark 1.2 accepts: Audio.
  • Capabilities listed only for Muse Spark 1.2: audio input.
  • Both models list the same rate for Input (per 1M prompt tokens) and Output (per 1M generated tokens).

Muse Spark 1.3 vs Muse Spark 1.2: specs

SpecMuse Spark 1.3Muse Spark 1.2
Model IDmuse-spark-1-3muse-spark-1-2
AuthorMeta AIMeta AI
ReleasedSep 2, 2026Aug 5, 2026
Context window1M tokens1M tokens
Max output131,072 tokens131,072 tokens
Input
Text Image Video Document
Text Image Video Audio Document
Output
Text
Text
Structured outputJSON SchemaJSON Schema
Endpoints
POST /v1/chat/completions POST /v1/responses POST /v1/messages POST /v1beta/models/muse-spark-1-3:generateContent
POST /v1/chat/completions POST /v1/responses POST /v1/messages POST /v1beta/models/muse-spark-1-2:generateContent
Capabilities
reasoning multimodal video understanding function calling structured output web search cache document understanding
reasoning multimodal video understanding function calling structured output web search cache audio input document understanding

Muse Spark 1.3 vs Muse Spark 1.2: API pricing

Live rates from the EmpirioLabs catalog for both models. Each rate card always matches what the API charges.

Muse Spark 1.3 vs Muse Spark 1.2: API parameters

Request parameters each model lists on EmpirioLabs, with the allowed values or range where one applies. A dash marks a parameter the model does not list.

ParameterMuse Spark 1.3Muse Spark 1.2
max_tokens16 to 131072 Default: 163841 to 131072 Default: 16384
temperature0 to 2 Default: 10 to 2 Default: 1
top_p0.01 to 1 Default: 10.01 to 1 Default: 1
reasoning_effortminimal, low, medium, high, xhigh Default: mediumminimal, low, medium, high, xhigh Default: medium
tool_web_searchboolean Default: falseboolean Default: false
toolsarray Default: []array Default: []
tool_choiceobjectobject
parallel_tool_callsbooleanboolean
response_formatenumenum
presence_penalty--2 to 2 Default: 0
frequency_penalty--2 to 2 Default: 0
seed-integer

Muse Spark 1.3 vs Muse Spark 1.2: limits and notes

Muse Spark 1.3

Reasoning is always on and cannot be disabled. reasoning_effort accepts minimal through xhigh. On /v1/chat/completions the reasoning text is not returned; on /v1/responses you can request reasoning summaries with reasoning.summary, and reasoning tokens are billed as output tokens and count against the output budget either way. Text, image, MP4 video, and PDF inputs are supported; up to 50 images can be attached. Audio input is not supported on this checkpoint; the Muse Spark 1.1 and 1.2 checkpoints accept audio. PDFs use text from the first 100 pages and page images from the first 50 pages. Built-in web search adds $0.00825 per executed search query and reports the count in usage.tool_usage. OpenAI Responses requests also support custom tools and deferred tool search. tool_choice supports auto and none. Prompts and completions sent to this Standard checkpoint are not used by Meta to train its models.

Muse Spark 1.2

Reasoning is always on and cannot be disabled. Reasoning stays internal, and reasoning tokens are billed as output tokens and count against max_tokens. reasoning_effort accepts minimal through xhigh. Text, image, MP4 video, MP3/WAV audio, and PDF inputs are supported; up to 50 images can be attached. PDFs use text from the first 100 pages and page images from the first 50 pages. Built-in web search adds $0.00825 per executed search query and reports the count in usage.tool_usage. OpenAI Responses requests also support custom tools and deferred tool search. tool_choice supports auto and none. Prompts and completions sent to this Standard checkpoint are not used by Meta to train its models.

How to call Muse Spark 1.3 and Muse Spark 1.2

Muse Spark 1.3 serves the OpenAI-compatible Chat Completions API. Point any OpenAI SDK at https://api.empiriolabs.ai/v1 with your EmpirioLabs API key and use the model id muse-spark-1-3. Both models are called through the same endpoint. Set model to muse-spark-1-3 or muse-spark-1-2. Get an API key from the EmpirioLabs dashboard.

cURL
curl https://api.empiriolabs.ai/v1/chat/completions \
  -H "Authorization: Bearer $EMPIRIOLABS_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "muse-spark-1-3",
    "messages": [
      {"role": "user", "content": "Write a haiku about the ocean."}
    ]
  }'

Muse Spark 1.3 vs Muse Spark 1.2: common questions

What is the difference between Muse Spark 1.3 and Muse Spark 1.2?

Muse Spark 1.3 is the newer release (Sep 2, 2026); Muse Spark 1.2 was released on Aug 5, 2026. Both models have a context window of 1M tokens. Input types only Muse Spark 1.2 accepts: Audio. The specs, rate cards, and parameters on this page come from the live EmpirioLabs catalog.

Which is newer, Muse Spark 1.3 or Muse Spark 1.2?

Muse Spark 1.3 is the newer release (Sep 2, 2026); Muse Spark 1.2 was released on Aug 5, 2026.

Which has the lower rate, Muse Spark 1.3 or Muse Spark 1.2?

Both models list the same rate for Input (per 1M prompt tokens) and Output (per 1M generated tokens). Both live rate cards are on this page and always match what the API charges.

Can I switch between Muse Spark 1.3 and Muse Spark 1.2 without rebuilding my integration?

Yes. Both models use POST /v1/chat/completions with the same EmpirioLabs API key, so most integrations switch by changing the model value. Check the parameters table on this page first if you rely on a model-specific parameter.

Can I try Muse Spark 1.3 and Muse Spark 1.2 in the browser before integrating?

Yes. Open each model in the EmpirioLabs playground and run the same prompt on both, with the parameters the API exposes.

Ready to use better endpoints?

Check out our pricing or reach out if you want your own model deployed on our stack.