Updated October 14, 2026. Rank cannot separate these two. Price, access, and your workload decide. Public scores include evidence status and uncertainty.
Both of these models will change. Get the price, version and retirement notices for the pair, each with its source. Follow model changes
MiMo-V2.5-Pro has the higher public score estimate, 52.56 versus 52.13, but the 90% score intervals overlap. Treat that as a lead, not a settled winner. 8 results are shared. Category rows resting on Estimated evidence or different benchmark sets are marked directional and do not name a winner.
Recommendations appear only when a shared evidence basis or an explicit operating constraint supports the call. Secondary and unsupported use cases stay disclosed below the initial list.
Code generation, repair, and software-engineering tasks
MiMo-V2.5-Pro
MiMo-V2.5-Pro has the higher public coding point estimate, 43.5 to 34, with Supported evidence for both models. The conditional ranges do not establish rank confidence.
Tool use, computer use, and multi-step task completion
MiMo-V2.5-Pro
MiMo-V2.5-Pro has the higher public agentic point estimate, 36.8 to 36.2, with Supported evidence for both models. The conditional ranges do not establish rank confidence.
Prompts that approach the documented context limit
No clear pick
The documented context windows are equal.
1K fresh input + 500 output tokens
Not enough matched evidence
A complete comparable API-rate estimate is not available for both models.
200K cached + 20K fresh input + 10K output tokens
Not enough matched evidence
A complete comparable API-rate estimate is not available for both models.
50K fresh input + 3K output tokens
Not enough matched evidence
A complete comparable API-rate estimate is not available for both models.
Choose a job from the LLM Selector's task catalog to see the category row it rests on, under the same basis rules as the table below. A directional row stays directional; choosing a job never creates a winner.
The same task catalog as the LLM Selector. Each job names the evidence surface it rests on; nothing here adds a new score.
Like-for-like · BenchAlign v5.8
MiMo-V2.5-Pro has the higher coding point estimate. Conditional score ranges do not establish rank confidence.
Coding scores combine specific tasks and setups. Match the editor, harness, and effort to your workflow.
Shared results can support a head-to-head reading. Results present for only one model describe coverage, not superiority.
1 category rests on Estimated evidence or different evidence sets. Those rows remain visible for coverage context but do not name a winner.
Only shared public evidence is shown. Sparse evidence stays a ruled list rather than being closed into a radar shape.
Too few matched category axes support a radar. The ruled list below shows only shared benchmark results; positions use each benchmark’s normalized display scale when available.
LiveCodeBench (Vals)Coding
Normalized gap 4.1HLE w/o toolsKnowledge
Normalized gap 4.0SWE-bench ProCoding
Normalized gap 2.9HLEKnowledge
Normalized gap 2.0MMLU-Pro (Vals)Knowledge
Normalized gap 1.7Each row shows the public-lane category score for both models: the BenchAlign v5.8 lane for agentic, coding, and knowledge, and the weighted public rows elsewhere, with the same rank each model page reports. A row is like-for-like only when both scores rest on Supported evidence or the same weighted set. Directional and not-comparable rows remain visible, but they never receive a winner.
| Category | Inkling | MiMo-V2.5-Pro | Basis | Reading |
|---|---|---|---|---|
| Agentic | 36.2Supported · #72/124 | 36.8Supported · #69/124 | Like-for-likeBenchAlign v5.8 lane · 5 vs 5 public rows | MiMo-V2.5-Pro leads · intervals overlap |
| Coding | 34.0Supported · #80/149 | 43.5Supported · #56/149 | Like-for-likeBenchAlign v5.8 lane · 6 vs 4 public rows | MiMo-V2.5-Pro leads · intervals overlap |
| Knowledge | 54.5Supported · #62/181 | 52.1Supported · #70/181 | Like-for-likeBenchAlign v5.8 lane · 6 vs 4 public rows | Inkling leads · intervals overlap |
| Instruction following | 87.6#35/128 | 93.8#7/128 | Directional onlyProvisional lane · 1 vs 0 weighted rows | Directional only |
| Reasoning | 79.0#14/29 | 80.6Unranked · 2 rankable rows | Not comparableProvisional lane · 0 vs 0 weighted rows | Not comparable |
| Multimodal | 67.5#35/54 | Not ranked | Not comparableProvisional lane · 2 vs 0 weighted rows | Not comparable |
| Multilingual | Not ranked | Not ranked | Not comparableProvisional lane · 0 vs 0 weighted rows | Not comparable |
| Math | 58.3#11/12 | Not ranked | Not comparableProvisional lane · 3 vs 0 weighted rows | Not comparable |
Ranks count the models scored in each category’s lane, so the agentic, coding, and knowledge denominators (BenchAlign v5.8) differ from the provisional-lane categories. Unranked scores sit on the provisional lane’s scale but never name a winner. Like-for-like rows within 0.5 points read as a practical tie.
Three fixed token mixes turn per-token rates into comparable decisions. Each scenario states context fit and whether cached input had to fall back to the published list-input rate.
1K fresh input + 500 output tokens
MiMo-V2.5-Pro has no comparable published API token rate.
50K fresh input + 3K output tokens
MiMo-V2.5-Pro has no comparable published API token rate.
200K cached + 20K fresh input + 10K output tokens
MiMo-V2.5-Pro has no comparable published API token rate.
Sourced differences are shown directly. Missing facts stay explicit instead of being inferred from a model name or family.
Maximum documented context; output-token limits may be lower.
Inkling
1M
MiMo-V2.5-Pro
1M
Inkling
Not sourced
MiMo-V2.5-Pro
Not sourced
A missing cached-input rate falls back to the listed input rate only in the stated workload estimate.
Inkling
$0.374 per 1M cached input tokens
MiMo-V2.5-Pro
No comparable hosted API rate
Inkling
Not sourced
MiMo-V2.5-Pro
Not sourced
Inkling
Not sourced
MiMo-V2.5-Pro
Not sourced
Inkling
Not sourced
MiMo-V2.5-Pro
Not sourced
Inkling
Hybrid
MiMo-V2.5-Pro
Reasoning
Inkling
Open Weight
MiMo-V2.5-Pro
Proprietary
Inkling
Open Weight
MiMo-V2.5-Pro
Proprietary
Inkling
2026-07-15
MiMo-V2.5-Pro
2026-04-22
MiMo-V2.5-Pro has the higher public score estimate, 52.56 versus 52.13, but the 90% score intervals overlap. The higher estimate is not a decisive winner because the uncertainty ranges overlap.
MiMo-V2.5-Pro has the higher public coding point estimate, 43.5 to 34, with Supported evidence for both models. The conditional ranges do not establish rank confidence.
MiMo-V2.5-Pro has the higher public agentic tasks point estimate, 36.8 to 36.2, with Supported evidence for both models. The conditional ranges do not establish rank confidence.
Both models do not have comparable published API token rates, so this page does not name a universal price winner.
Both models list the same context window, 1M.
The full public result ledger is available for audit without forcing a wide desktop table onto a phone.
Terminal-Bench 2.1
Not directly comparable
BrowseComp
Not directly comparable
MCP Atlas
Not directly comparable
Terminal-Bench 2.1 (Vals)
MiMo-V2.5-Pro leads this result
CWE-bench v1
Not directly comparable
Claw-Eval
Not directly comparable
τ³-bench results
Not directly comparable
Terminal-Bench 2.0
Not directly comparable
Gert Labs
Not directly comparable
SWE-bench Verified
Not directly comparable
SWE-bench Pro
MiMo-V2.5-Pro leads this result
Terminal-Bench 2.1
Not directly comparable
FrontierSWE v2
Not directly comparable
LiveCodeBench (Vals)
Inkling leads this result
SWE-bench (Vals)
Inkling leads this result
Terminal-Bench 2.0
Not directly comparable
GPQA
Not directly comparable
GPQA-D
Not directly comparable
HLE
MiMo-V2.5-Pro leads this result
HLE w/o tools
MiMo-V2.5-Pro leads this result
GPQA Diamond (Vals)
Inkling leads this result
MMLU-Pro (Vals)
Inkling leads this result
IFBench
Not directly comparable
One weekly email when material rank, price, or benchmark evidence changes make this matchup worth revisiting.
Read a sample issueJoin 5,500+ readers.
Last updated October 14, 2026
