Muse Spark 1.1 vs Inkling
At a Glance
| Compare |  Muse Spark 1.1Meta |  InklingThinking Machines Lab |
|---|---|---|
| Intelligence, Cost, and Efficiency | ||
| IntelligenceHigher is better · MM Intelligence v4.4 | UnrankedNot in the 57-model eligible cohort | #27 of 5747.4 score · 3/3 sources · complete |
| CostLower is better · Published-token output estimate | UnrankedNot in the 27-model eligible cohort | #13 of 27$0.090 per LiveBench case |
| EfficiencyHigher is better · MM Efficiency v1.9 | UnrankedNot in the 27-model eligible cohort | #22 of 2742.0 score · 3/3 sources · complete |
| Pricing and Limits | ||
| Input priceFrom · USD / 1M tokens | Not reported | $0.95Deepinfra ↗ · Oct 15, 2026 |
| Output priceFrom · USD / 1M tokens | Not reported | $4.05Deepinfra ↗ · Oct 15, 2026 |
| Context windowMaximum documented tokens | 1,000K | 1,049K |
| Model facts checked | Sep 3, 2026View model evidence → | Sep 3, 2026View model evidence → |
Token prices are the lowest available sourced USD rates; input and output may use different providers. Cost ranking estimates output spend on LiveBench, not a full request bill. Ranking methodology →
Available Benchmarks
| Benchmark | Muse Spark 1.1 | Inkling |
|---|---|---|
| LMArena Agent Arenaagent-2026-10-16-0ebb411abf00 · outcome_score · leader | -6.43100% of row best · score · Muse Spark 1.1; 95% CI [-7.08799618, -5.77544358]; sessions 145940; observations 7748331; rank 44 | -14.3592% of row best · score · Inkling; 95% CI [-15.81859883, -12.88168979]; sessions 43507; observations 1662352; rank 50 |
| LiveBench2026-06-25-90f8d44da965 · overall · leader | 78.57100% of row best · percent · muse-spark-1.1-xhigh · 13,652 output tokens / case | 76.4797% of row best · percent · inkling-xhigh · 22,213 output tokens / case |
| Overall ResultCounted from the protocol-matched rows above | 2 benchmark winsOverall lead | 0 benchmark wins |
Third-party benchmark Only like-for-like primary-publisher results are shown; raw scores, relative scores, configuration, and token spend remain visible.
Side-by-Side Facts
| Field | Muse Spark 1.1 | Inkling |
|---|---|---|
| Developer | Meta | Thinking Machines Lab |
| Family | Muse Spark | Inkling |
| Model | Muse Spark 1.1 | Inkling |
| Version | Muse Spark 1.1 | Inkling |
| Lifecycle | preview | active |
| Released | 2026-07-09 | 2026-07-15 |
| Knowledge cutoff | Unknown | Unknown |
| Input modalities | Text, Image, Video, Audio | Text, Image, Video, Audio |
| Output modalities | Text | Text |
| Context window | 1,000K | 1,049K |
| Total parameters | Unknown | 975B |
| Active parameters | Unknown | 41B |
| License | Unknown | apache-2.0 |
| Open weights | No | Yes |
| API available | Yes | Yes |
| Self-hostable | No | Yes |
| Provider access | Unknown | Deepinfra (Standard), Fireworks Ai (Standard), Openrouter (Standard), Together Ai (Standard) |
| Capabilities | chat, computer-use, generation, reasoning, research, structured_outputs, tools | agents, chat, coding, generation, reasoning, tools, vision |
Muse Spark 1.1 Capabilities
Inkling Capabilities
Related Comparisons
All audio comparisons →| A | Pair | B | Context |
|---|---|---|---|
Seed 2.0 LiteByteDance Seed | vs | Muse Spark 1.1Meta | cross-developer peersaudio, image, text, video |
 Gemini 2.5 FlashGoogle DeepMind | vs | Muse Spark 1.1Meta | cross-developer peerstext |
Gemini 2.5 ProGoogle DeepMind | vs | Muse Spark 1.1Meta | cross-developer peerstext |
Gemini 3 FlashGoogle DeepMind | vs | Muse Spark 1.1Meta | cross-developer peerstext |
Gemini 3.5 FlashGoogle DeepMind | vs | Muse Spark 1.1Meta | cross-developer peerstext |
Gemma 4 E2BGoogle DeepMind | vs | Muse Spark 1.1Meta | cross-developer peersaudio, image, text, video |
Gemma 4 E4BGoogle DeepMind | vs | Muse Spark 1.1Meta | cross-developer peersaudio, image, text, video |
Lyria 3.5Google DeepMind | vs | Muse Spark 1.1Meta | cross-developer peersaudio, image, text |
Muse Spark 1.1Meta | vs | Muse Spark 1.3Meta | family variantsimage, text, video |
Muse Spark 1.1Meta | vs | Muse Glimmer 30BMeta | cross-developer peersimage, text |
Primary Evidence
Sources and Freshness
Questions
Muse Spark 1.1 vs Inkling FAQs
Is Muse Spark 1.1 or Inkling better for coding?+
This comparison does not currently contain a protocol-matched coding benchmark for both Muse Spark 1.1 and Inkling, so Model Markets cannot name a coding leader from pricing, context size, or capability labels alone.
Which is cheaper, Muse Spark 1.1 or Inkling?+
Only Inkling has a directly sourced input price: $0.95 per million tokens. Only Inkling has a directly sourced output price: $4.05 per million tokens.
Which has a larger context window, Muse Spark 1.1 or Inkling?+
Inkling has the larger sourced context window. Muse Spark 1.1 supports 1,000,000 tokens and Inkling supports 1,048,576 tokens.
Which performs better in benchmarks, Muse Spark 1.1 or Inkling?+
Muse Spark 1.1 leads the current overall benchmark count. The result uses 2 protocol-matched benchmarks from 2 publishers; it is not a universal quality score.
Can Muse Spark 1.1 or Inkling be self-hosted?+
Inkling is documented as self-hostable; Muse Spark 1.1 is documented as not self-hostable. Muse Spark 1.1 is not marked open weight; Inkling is open weight.
Can Muse Spark 1.1 and Inkling understand images?+
Muse Spark 1.1 is documented with image input; Inkling is documented with image input. This reflects supported input modalities, not vision quality.
Which can generate longer answers, Muse Spark 1.1 or Inkling?+
Neither model has a sourced maximum output in this comparison, so a larger limit cannot be determined.
Do Muse Spark 1.1 and Inkling support reasoning and tool use?+
Muse Spark 1.1: reasoning, tool calling, and image input. Inkling: reasoning, tool calling, and image input. Feature support does not establish relative quality.
Which is available from more inference providers, Muse Spark 1.1 or Inkling?+
Muse Spark 1.1 has 0 sourced provider routes; Inkling has 4, so Inkling has broader tracked availability.
Which offers better value, Muse Spark 1.1 or Inkling?+
There is no universal value winner. Compare the input and output prices above with the matched benchmark result for your workload: cheaper tokens can be offset by different quality, token usage, latency, or provider availability.