Muse Spark 1.3 vs Seed 2.1 Turbo

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

Meta AI ByteDance Text Generation

Muse Spark 1.3 vs Seed 2.1 Turbo at a glance

Muse Spark 1.3 from Meta AI and Seed 2.1 Turbo from ByteDance are both in the Text Generation category, available through the EmpirioLabs API.

Key differences

  • Muse Spark 1.3 is the newer release (Sep 2, 2026); Seed 2.1 Turbo was released on Jul 13, 2026.
  • Muse Spark 1.3 has the larger context window: 1M tokens, against 229.1K for Seed 2.1 Turbo.
  • Muse Spark 1.3 returns up to 131,072 output tokens per response, Seed 2.1 Turbo up to 65,536.
  • Input types only Muse Spark 1.3 accepts: Document.
  • Capabilities listed only for Muse Spark 1.3: multimodal, video understanding, structured output, web search, cache, document understanding.
  • Capabilities listed only for Seed 2.1 Turbo: vision, agentic coding.
  • Seed 2.1 Turbo lists the lower rate for Input (per 1M prompt tokens) and Output (per 1M generated tokens).

Muse Spark 1.3 vs Seed 2.1 Turbo: specs

SpecMuse Spark 1.3Seed 2.1 Turbo
Model IDmuse-spark-1-3seed-2-1-turbo
AuthorMeta AIByteDance
ReleasedSep 2, 2026Jul 13, 2026
Context window1M tokens229.1K tokens
Max output131,072 tokens65,536 tokens
Input
Text Image Video Document
Text Image Video
Output
Text
Text
Structured outputJSON SchemaJSON Schema
Region-Malaysia
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/seed-2-1-turbo:generateContent
Capabilities
reasoning multimodal video understanding function calling structured output web search cache document understanding
reasoning vision agentic coding function calling

Muse Spark 1.3 vs Seed 2.1 Turbo: 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 Seed 2.1 Turbo: 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.3Seed 2.1 Turbo
max_tokens16 to 131072 Default: 163841 to 65536
temperature0 to 2 Default: 1-
top_p0.01 to 1 Default: 1-
reasoning_effortminimal, low, medium, high, xhigh Default: mediumlow, medium, high Default: high
tool_web_searchboolean Default: false-
toolsarray Default: []-
tool_choiceobject-
parallel_tool_callsboolean-
response_formatenumenum
frequency_penalty--2 to 2 Default: 0
presence_penalty--2 to 2 Default: 0
stop-string
enable_thinking-boolean Default: true
enable_web_search-boolean Default: false
max_tool_calls-1 to 10 Default: 3
image_detail-low, high, xhigh Default: high

Muse Spark 1.3 vs Seed 2.1 Turbo: 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.

Seed 2.1 Turbo

Per-token pricing is flat across the full context window, with no higher rate above 128K. Reasoning is on by default; set enable_thinking to false to answer directly without it.

How to call Muse Spark 1.3 and Seed 2.1 Turbo

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 seed-2-1-turbo. 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 Seed 2.1 Turbo: tests and guides

Prompt tests and comparison runs that cover both models.

Muse Spark 1.3 vs Seed 2.1 Turbo: common questions

What is the difference between Muse Spark 1.3 and Seed 2.1 Turbo?

Muse Spark 1.3 is the newer release (Sep 2, 2026); Seed 2.1 Turbo was released on Jul 13, 2026. Muse Spark 1.3 has the larger context window: 1M tokens, against 229.1K for Seed 2.1 Turbo. Muse Spark 1.3 returns up to 131,072 output tokens per response, Seed 2.1 Turbo up to 65,536. The specs, rate cards, and parameters on this page come from the live EmpirioLabs catalog.

Which is newer, Muse Spark 1.3 or Seed 2.1 Turbo?

Muse Spark 1.3 is the newer release (Sep 2, 2026); Seed 2.1 Turbo was released on Jul 13, 2026.

Which has the lower rate, Muse Spark 1.3 or Seed 2.1 Turbo?

Seed 2.1 Turbo lists the lower 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 Seed 2.1 Turbo 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 Seed 2.1 Turbo 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.