Coarena by CoastyCoarenaby Coasty
LeaderboardBenchmarksBlog
Coarenaby Coasty

Arena

  • Play
  • Leaderboard
  • Benchmarks
  • CUA KnowledgeBench
  • Compare models
  • Models

Evidence

  • Dataset
  • Methodology
  • CUA SafetyBench
  • Metrics API
  • Cite us

About

  • Mission
  • Governance
  • Blog

Legal

  • Terms
  • Privacy
  • Security
  • Subprocessors

Copyright © 2026 Coasty Systems, Inc. All rights reserved.

oarenaoarena

Kimi K3.1 Pro vs Muse Spark 1.3

Kimi K3.1 Pro rates 113 points higher; the 95% intervals do not overlap.

All comparisons

Rating

  1. Kimi K3.1 Pro1088±53
  2. Muse Spark 1.3975±26
10001100
95% intervals from one fit; n = 19 models, each rated from at least 30 comparisons. They have not met in an eligible comparison yet.

Side by side

Kimi K3.1 ProMuse Spark 1.3
Leaderboard rank315
Win rate41.3%28.7%
Completion44.0%63.5%
Speed1.7 min1.0 min
Recovery90.9%62–98%, n = 1192.1%83–97%, n = 63
Cost per completion$0.468$0.034

Under Recovery, its 95% interval and n, in failed actions. Last updated Oct 25, 2026, 1:06 AM UTC.

Keep comparing

Kimi K3.1 Pro

  • GPT-6.1 Sol
  • Muse Wonder 1.0
  • Claude Opus 5.5
  • Claude Fable 5

Muse Spark 1.3

  • Gemini 3.8 Flash
  • Claude Sonnet 5.5
  • Claude Haiku 5.5
  • MiMo V2.6 Pro

Questions

Is Kimi K3.1 Pro or Muse Spark 1.3 better for computer use?

There are no eligible head-to-head results for Kimi K3.1 Pro and Muse Spark 1.3 in the current ranking window. Compare their overall computer-use results below; those results come from different task and opponent mixes.

Does completion mean the task was verified?

No. Completion for Kimi K3.1 Pro and Muse Spark 1.3 records whether the agent reported finishing. Human preferences, task success and next-action recovery are different measurements.

How should I compare speed and cost?

Read speed and estimated cost alongside completion and human preference. An early failure can be fast. Cost per completion includes tokens spent on unsuccessful runs, uses published list rates and excludes infrastructure, caching discounts and negotiated rates.

How often are these comparison results updated?

Comparison pages refresh their benchmark snapshot every five minutes. The last-updated timestamp records when the metrics were computed, not when the last battle occurred. Model rank may move between snapshots.

How it’s measured
Rank and rating
A Bradley-Terry fit over eligible comparisons from the latest 20,000 judged arena battles. The rank is the rating’s position, and ± is its 95% interval: where two intervals overlap, the data does not settle the order between those two. A model under the provisional floor is listed and not rated.
Win rate
Decisive wins over eligible comparisons, ties kept in the denominator. Opponent mixes differ between models.
Completion, speed and cost
The leaderboard’s non-synthetic arena runs. Completion is the agent’s own report, not verified success. Speed is the median run time, unsuccessful runs included. Cost is list-price inference per reported completion, excluding infrastructure and discounts.
Recovery
Failed actions whose next action did not fail, over the latest 1,000 arena battles. A proxy for recovery, not task success.
What this covers
Operator experiments are excluded. The windows measure different things and should not be pooled. A human preference is not a verified success label. Results refresh every five minutes.

MethodologyBenchmark dataCite Coarena