Model comparison · accepted catalogue facts 2026-11-16

Muse Spark 1.3 vs MiMo-V2.5-Pro

Neither model has both an equal-or-higher measured score and an equal-or-lower estimated price in this pair. Retaining your current model is a valid outcome.

Both models carry an independently measured score. This page is one cell of the rated catalogue pairwise set, not a frontier-membership verdict.

Muse Spark 1.3

LMArena general · Elo · higher is better

Scale starts at 1040 Elo

1489.9

Balanced effective USD / 1M tokens · lower is better

$2.00/M

MiMo-V2.5-Pro

LMArena general · Elo · higher is better

Scale starts at 1040 Elo

1465.0

Balanced effective USD / 1M tokens · lower is better

$0.544/M

Compare · model decision

Choose two or three models

Inspect the differences, estimate your workload and keep the evidence. All standard catalogue models are available, including unrated ones.

Catalogue facts
2026-11-16

2 / 3 selected · 0 requirements
Open public comparison link
Public workload and requirements

These settings are included in the share link. The fixed-request scenario and private evaluation data below are excluded.

A ↔ B

Neither model has both an equal-or-higher measured score and an equal-or-lower estimated price in this pair. Retaining your current model is a valid outcome.

Estimated blend: 75% input, 25% output; 0% cached input. Base context tier. Prompt length selects the billing tier. An unlisted cache-read rate uses that tier’s full input rate in this blend; missing required input or output rates prevent an estimate. The fixed-request estimate below validates actual context and output limits and requires a published cache-read rate when cache hits are assumed.

What changes between these models

Quality first, then estimated price. LMArena scores are human-preference measurements, not a benchmark of your application. A missing score is unrated.

  • Muse Spark 1.3 · Meets the stated model requirements
  • MiMo-V2.5-Pro · Meets the stated model requirements
Material differences and unknown evidence. Deltas compare each model with model A. Unknown facts remain visible.
Measured factA Muse Spark 1.3B MiMo-V2.5-Pro
LMArena general score (Elo)1,489.91,465Δ vs A: -24.9 Elo
Score interval half-width (± Elo)6.163.62Δ vs A: -2.54 Elo
Benchmark reasoning effortmaxdefault
LMArena document score (Elo)1,470.7Unknown
Estimated effective USD / 1M tokens$2$0.54375Δ vs A: -1.45625 USD/M
Base input USD / 1M tokens$1.25$0.435Δ vs A: -0.815 USD/M
Base output USD / 1M tokens$4.25$0.87Δ vs A: -3.38 USD/M
Base cached-input USD / 1M tokens$0.15$0.0036Δ vs A: -0.1464 USD/M
Context window (tokens)1,048,5761,024,000Δ vs A: -24,576 tokens
Output limit (tokens)943,718131,072Δ vs A: -812,646 tokens
Input modalitiestext, image, video, filetext
Open weightsUnknownUnknown
Recorded licenceUnknownUnknown
Model providerMetaXiaomi
Serving precision differs across offersNot supportedSupportedΔ vs A: +1
Recorded retirement dateUnknownUnknown
4 shared measured facts
Shared measured facts. Deltas compare each model with model A. Unknown facts remain visible.
Measured factA Muse Spark 1.3B MiMo-V2.5-Pro
Tool useSupportedSupportedΔ vs A: 0
ReasoningSupportedSupportedΔ vs A: 0
Distinct sellers in the catalogue22Δ vs A: 0
Retirement evidenceNone announced; not a guaranteeNone announced; not a guarantee

Provider counts and precision flags describe catalogue offers. They do not establish the precision, availability, region, tool behaviour or limits of your chosen endpoint. Open each model’s provider table before switching.

Complete price ladders and billing conditions

Muse Spark 1.3

Rates below are USD per 1M tokens. A threshold selects that whole input/output rate pair.

Input-token thresholdInputOutputCached input
Base, up to and including first threshold$1.25$4.25$0.15

MiMo-V2.5-Pro

Rates below are USD per 1M tokens. A threshold selects that whole input/output rate pair.

Input-token thresholdInputOutputCached input
Base, up to and including first threshold$0.435$0.87$0.0036
Migration preflight · compare each candidate with model A

Keeping Muse Spark 1.3 is a valid decision. No pairwise comparison certifies a drop-in replacement.

Muse Spark 1.3 → MiMo-V2.5-Pro

Known loss or failed requirement

  • Context window: 1,048,576 → 1,024,000 tokens.
  • Output limit: 943,718 → 131,072 tokens.
  • image input is not supported by the candidate.
  • video input is not supported by the candidate.
  • file input is not supported by the candidate.
  • Provider endpoint, serving precision, availability and task success need your own verification. Catalogue model capabilities do not certify an endpoint.
Check alternatives to Muse Spark 1.3

Estimate a fixed request shape

Private to this tab unless you save locally or explicitly export private details. These are estimates, not observed invoices. Cross-model token counts and task success are assumptions.

0.1 extra attempts means 10 extra full attempts per 100 requests. Cache writes, tool charges, taxes and unlisted charges are excluded.

  • Muse Spark 1.3Estimated total: $4.625 1,000 full attempts · base rates
  • MiMo-V2.5-ProEstimated total: $1.305 1,000 full attempts · base rates
Prompt and output sensitivity · sampled scenarios

Every point recalculates the entire request shape. Tier-boundary samples include one token below, at and above each threshold. Ordering between samples is not guaranteed. Lowest known cost excludes unknown estimates and is not a replacement recommendation.

Vary input; hold output, requests, cache and retries fixed.
Input tokensMuse Spark 1.3MiMo-V2.5-ProCoverage
2,000$4.625$1.305Lowest knownAll computed
4,096$7.245$2.21676Lowest knownAll computed
32,768$43.085$14.68908Lowest knownAll computed
131,072$165.965$57.45132Lowest knownAll computed
Vary output; hold input, requests, cache and retries fixed.
Output tokensMuse Spark 1.3MiMo-V2.5-Pro
128$3.044$0.98136
2,048$11.204$2.65176
8,192$37.316$7.99704

Bring your observed evaluation results

JSON is parsed locally. Prompts, filenames, individual responses and extra fields are not retained. Import only aggregate measurements for selected models. Task/version labels do not establish that two evaluations used the same dataset.

Expected format
[{"model":"provider/exact-model-id","task":"support-answer","version":"rubric-1","attempts":100,"successes":84,"costUsd":2.4,"latencyMs":950}]

Use the exact catalogue ID. Replace the example values with observed measurements. Omit costUsd or latencyMs when they are unknown. No public score is inferred from these observations.

Keep the decision and its evidence

A portable record retains selected facts, complete tier ladders, public requirements and the publication manifest. It also embeds the full permitted public catalogue to verify the input artifact checksum. Files are larger for this reason (up to 2 MB); local storage is limited to 12 records. Team review is local to this browser; there is no hosted collaboration.

Saving is opt-in and includes private review fields. Shared comparison links never include them. Version 1 Check references remain separate and are not overwritten or guessed into this format.

Saved local decisions · 0

No version 2 decision records are stored in this browser.

Questions this page answers

Is Muse Spark 1.3 a better-and-cheaper replacement for MiMo-V2.5-Pro?

Neither model has both an equal-or-higher measured score and an equal-or-lower estimated price in this pair. Retaining your current model is a valid outcome.

What scores and prices does this page use for Muse Spark 1.3 and MiMo-V2.5-Pro?

Muse Spark 1.3 scores 1489.9 on LMArena general (Elo). MiMo-V2.5-Pro scores 1465 on LMArena general (Elo). Prices are the catalogue’s published seller rates under the selected workload; missing modalities or context cuts are named rather than assumed away.

What is included in this comparison?

Accepted model capabilities, context and output limits, complete price-tier ladders, independent LMArena measurements and missing evidence. Provider endpoint precision and application success still need verification.

Can I compare a different workload or keep a decision record?

Yes. Change the public workload, prompt length and requirements in the comparison workspace. Fixed-request scenarios, aggregate evaluations and review notes stay local unless explicitly exported.