Loading
90 days of the enterprise, pro and team plans free, no card needed. See the plans
Model comparison
Meta's Muse Spark 1.3 against Xiaomi's MiMo-V2.6-Pro: vendor list prices, limits, abilities and the Artificial Analysis indexes side by side - and what OpenSmartRoute does when both are available.
MiMo-V2.6-Pro lists at $0.544 per million tokens blended against $2.00 for Muse Spark 1.3 - 3.7x less.
Muse Spark 1.3 scores 48 on the intelligence index against 46 - 2 points apart.
MiMo-V2.6-Pro reads 1.1M tokens at once, Muse Spark 1.3 1.0M.
only MiMo-V2.6-Pro offers open weights.
Vendor list prices per million tokens and published limits; indexes are Artificial Analysis composites (0-100).
| Specification | Muse Spark 1.3 | MiMo-V2.6-Pro |
|---|---|---|
| Input price / 1M tokens | $1.25 | $0.43 |
| Output price / 1M tokens | $4.25 | $0.87 |
| Blended (3 in : 1 out) | $2.00 | $0.54 |
| Cached input / 1M | $0.15 | $0.004 |
| Context window | 1.0M | 1.1M |
| Max output | 944K | 131K |
| Input | text, image, video, file | text, image, video, audio |
| Output | text | text |
| Tool calls | ||
| Structured output | ||
| Reasoning | ||
| Open weights | ||
| Intelligence index | 48 | 46 |
| Coding index | 76 | - |
| Agentic index | 56 | - |
| Released | Sep 2, 2026 | Sep 21, 2026 |
| Available on this deployment |
List price times tokens for three typical workloads; your mix of input and output decides which model's pricing suits you.
| Workload | Muse Spark 1.3 | MiMo-V2.6-Pro | Difference |
|---|---|---|---|
| Support chat20M tokens in, 5M out a month - a help desk answering a few thousand conversations. | $46.25 | $13.05 | $33.20 less on MiMo-V2.6-Pro |
| Document summaries100M in, 5M out - long inputs, short answers. | $146 | $47.85 | $98.40 less on MiMo-V2.6-Pro |
| Coding assistant60M in, 20M out - a team's editor assistant, output-heavy. | $160 | $43.50 | $117 less on MiMo-V2.6-Pro |
MiMo-V2.6-Pro takes the short and general requests - at $0.544 blended it is the default - and Muse Spark 1.3 the ones whose complexity or quality floor rules the cheaper model out. The split is per request, not per app, and every decision carries the scores for both.
# targets.yaml - both models as routing targets (metadata.model links each to the catalogue entry)
targets:
- { id: mimo-v2.6-pro, kind: llm, metadata: { model: xiaomi/mimo-v2.6-pro } }
- { id: muse-spark-1.3, kind: llm, metadata: { model: meta/muse-spark-1.3 } }
# rules.yaml - the cheaper model by default, the stronger one when the request is hard
rules:
- name: simple-requests-stay-cheap
when: { max_complexity: 0.45 }
prefer: [mimo-v2.6-pro]
weight: 0.8
- name: hard-requests-escalate
when: { min_complexity: 0.45 }
prefer: [muse-spark-1.3]
weight: 0.8Every Meta and Xiaomi model, with prices, is on the vendor pages; the rankings show what the router actually picks.