Text models
Arena rating
THE MODEL, IN DETAIL / xiaomi
mimo-v2.5
xiaomi/mimo-v2.5Open weightsReasoningMiMo-V2.5 is a native omnimodal model by Xiaomi. It delivers Pro-level agentic performance at roughly half the inference cost, while surpassing MiMo-V2-Omni in multimodal perception across image and video understanding...
#100
Context window
131.1K max output tokens
Input price
USD / million input tokens
Output price
USD / million output tokens
Inference providers
5 provider routes observed
Measured output speed
No model-level measurement
01 / PERFORMANCE
A clearer view of capability.
Read the score, understand the context, and explore where this model sits among its peers.
Performance fingerprint
Individual published accuracy scores · not a composite index
At least three published accuracy scores are needed for this view.
Performance meets price
Text models · same published source and version
GoogleAnthropicMetaxiaomi
In good company
Text models · Arena · official dataset
416 models in the source cohort. Showing selected nearby models. Evaluation settings can differ.
Evidence, by task.
Coverage is not a capability score.
0published results
0 evaluation sources
0 evaluation sources
ReasoningAwaiting evidence
CodingAwaiting evidence
MathematicsAwaiting evidence
VisionAwaiting evidence
AgenticAwaiting evidence
Long contextAwaiting evidence
Documented features, task evaluations, and preference rankings describe different things. Missing coverage does not imply a model cannot perform a task.
Explore our methodologyWhere people rank it
Published rankings for this exact model or configuration. Each source keeps its original metric.
02 / BENCHMARK EXPLORER
The numbers behind the model.
Original results, exact versions, and a direct path to the evidence behind every score.
Percentage-based evaluations will appear here when published.
0 percentage-based evaluations. Each benchmark measures a different task; compare results within the same evaluation and protocol.
Artificial Analysis indices
Published in the OpenRouter catalog · source-defined index values
Catalog observation: 17 Oct 2026. Index versions and evaluation settings are not supplied in this feed. These are not Singularity composite scores.
Artificial AnalysisDesign Arena
Source-reported Elo across individual design categories
Catalog observation: 17 Oct 2026. Category ratings have separate comparison pools.
03 / COST & VALUE
Know what your workload costs.
Explore token prices, see where the spend goes, and model a workload of your own.
Input$0.14per million tokens
Output$0.28per million tokens
Cache read$0.0028per million tokens
Cache write—per million tokens
Workload cost calculator
Change the numbers. See the trade-offs.
Token estimate only. Excludes cache writes, tools, and other provider fees. Actual token usage and provider limits vary.
Your estimated spend
1,000 requests · 11M tokens
Uncached input$1.4
Cached input$0
Output$0.28
Per request$0.0017
Without cache discount$1.68
Estimated cache savings$0
04 / INFERENCE NETWORK
One model. Different ways to run it.
Compare inference routes by price, context, quantization, and reported availability.
| Provider / route | Input / M | Output / M | Cache / M | Context | Output limit | Speed | Latency | Availability · 1d | Rates |
|---|---|---|---|---|---|---|---|---|---|
| GGMICloudFP8 | $0.119 | $0.238 | $0.0026 | 1.1M | 945K | — | — | 97.5% | |
| XXiaomiFP8 | $0.14 | $0.28 | $0.0028 | 1M | 131.1K | — | — | 98.33% | |
| SStreamLakeQuantization not disclosed | $0.168 | $0.336 | $0.0034 | 1M | 128K | — | — | 35.47% | |
| NNovitaFP8 | $0.168 | $0.336 | $0.0034 | 1M | 131.1K | — | — | 97.71% | |
| VVeniceFP8 | $0.4 | $2 | $0.08 | 1M | 65.5K | — | — | 92.08% |
Snapshot observed 17 Oct 2026. Speed and latency are the reported 30-minute median when available. This is a dated snapshot, not live monitoring.
Provider price comparison
USD per million tokens · input and output rates
InputOutput
GMICloudfp8
Input
$0.119
Output
$0.238
Xiaomifp8
Input
$0.14
Output
$0.28
StreamLake
Input
$0.168
Output
$0.336
Novitafp8
Input
$0.168
Output
$0.336
Venicefp8
Input
$0.4
Output
$2
Reported availability
Provider availability over the selected observation window
Output speed
Reported 30-minute p50 · tokens per second
No provider throughput measurements were returned in this snapshot.
Response latency
Reported 30-minute p50 · seconds
No provider latency measurements were returned in this snapshot.
Context by provider
Actual route limits can differ from the catalog maximum
05 / CAPABILITIES & MODALITIES
What goes in. What comes out.
A map of documented interfaces and API features, separate from benchmark performance.
INPUT MODALITIES
TextAudioImageVideo
mimo-v2.5Reasoning supported
OUTPUT MODALITIES
Text
Feature support
Listed catalog API parameters and documented pricing features
ReasoningSupported
Tool callingSupported
Tool choiceSupported
Structured outputsSupported
Response formatSupported
Reasoning detailsSupported
Seed controlSupported
Stop sequencesSupported
Prompt cachingSupported
TemperatureSupported
Room to work
Context capacity and completion limits
1.1Mtotal context tokens
Context window
131.1Kmax output
Output tokens share the total context budget. The maximum completion length is a separate limit, and individual provider routes may have smaller limits.
- Catalog context
- 1,050,000 tokens
- Maximum output
- 131,072 tokens
- Top-provider context
- 1,048,576 tokens
Features vary by route
Check the provider before depending on a specific API feature.
| Provider route | Reasoning | Tools | Structured output | Response format | Implicit caching |
|---|---|---|---|---|---|
| GMICloud · FP8 | Supported | Supported | Not listed | Not listed | Supported |
| Xiaomi · FP8 | Supported | Supported | Not listed | Supported | Supported |
| StreamLake | Supported | Not listed | Supported | Supported | Supported |
| Novita · FP8 | Supported | Supported | Not listed | Supported | Supported |
| Venice · FP8 | Supported | Supported | Supported | Supported | Supported |
06 / UNDER THE HOOD
The complete specification sheet.
Exact identities, model architecture, limits, and the defaults that shape a request.
Identity & architecture
- Developer
- xiaomi
- Exact identity
mimo-v2.5- Subject
- Model Configuration
- Access
- Open weights
- License
- MIT
- Parameters
- Not disclosed
- Tokenizer
- Other
- Instruction format
- Not disclosed
Reasoning & controls
- Reasoning
- Supported
- Mandatory reasoning
- No
- Reasoning by default
- Not documented
- Published configuration
- Not disclosed
- Supported reasoning efforts
- Not documented
- Default reasoning effort
- Not disclosed
- API parameters
- 15
- Provider moderation
- No
- Quantization variants
- fp8
Dates & limits
- Catalog added
- 22 Apr 2026
- Knowledge cutoff
- Not disclosed
- Catalog expiration
- 21 Oct 2026
- Specifications observed
- 17 Oct 2026
- Providers observed
- 17 Oct 2026
- Request limits
- Provider-specific / not supplied
- Canonical catalog ID
xiaomi/mimo-v2.5-20260422
API parameters & defaults
Availability is catalog-wide. Defaults can vary across providers.
frequency_penaltySupported · default not suppliedinclude_reasoningSupported · default not suppliedmax_tokensSupported · default not suppliedpresence_penaltySupported · default not suppliedreasoningSupported · default not suppliedrepetition_penaltySupported · default not suppliedresponse_formatSupported · default not suppliedseedSupported · default not suppliedstopSupported · default not suppliedstructured_outputsSupported · default not suppliedtemperatureDefault: 1tool_choiceSupported · default not suppliedtoolsSupported · default not suppliedtop_kSupported · default not suppliedtop_pDefault: 0.9507 / BUILD WITH THIS MODEL
From exploration to your first request.
Use the documented catalog identifier and keep your API key in an environment variable.
Make an API request
const response = await fetch(
"https://openrouter.ai/api/v1/chat/completions",
{
method: "POST",
headers: {
Authorization: `Bearer ${process.env.OPENROUTER_API_KEY}`,
"Content-Type": "application/json",
},
body: JSON.stringify({
"model": "xiaomi/mimo-v2.5",
"messages": [
{
"role": "user",
"content": "Explain the trade-offs in this design."
}
]
}),
},
);
if (!response.ok) throw new Error(`HTTP ${response.status}`);
const data = await response.json();
console.log(data.choices[0].message.content);08 / PROVENANCE & HISTORY
Every number has a story.
Follow the source, check the observation date, and distinguish published results from model specifications.
The source register
Direct links to the underlying records
OpenRouter model catalog
02Architecture, modalities, parameters, and starting prices
Observed 17 Oct 2026OpenRouter provider routes
03Provider limits, prices, availability, and reported measurements
Observed 17 Oct 2026Text models ranking
04Arena rating · source-reported ranking
Observed 15 Oct 2026Web development ranking
05Arena rating · source-reported ranking
Observed 13 Oct 2026Vision ranking
Arena rating · source-reported ranking
Observed 9 Oct 2026The observation trail
Recorded events, in chronological order
Added to the model catalog
Catalog creation date, as recorded by OpenRouter.
Model specifications observed
Catalog pricing, limits, and supported parameters captured.
Provider routes observed
5 inference routes in this snapshot.
Observation dates describe when data was captured. They do not represent newly run evaluations or continuous performance monitoring.
Published observation ledger
Historical evidence, with source and version preserved.
No published benchmark observations for this selection. Published preference rankings appear separately above.
09 / A FEW MORE DETAILS
Questions worth asking.
Quick answers, drawn from this model’s connected specifications.
How much does mimo-v2.5 cost?
Catalog starting rates are $0.14 per million input tokens and $0.28 per million output tokens. Cache-read pricing is $0.0028 per million tokens. Compare provider routes and service tiers above for their specific prices.
How much context can it handle?
1,050,000 tokens in the catalog context window. The catalog lists a maximum of 131,072 completion tokens. Provider limits can differ.
Does it support tools and structured output?
Tool calling: listed as supported. Structured outputs: listed as supported. See the provider feature matrix for route-specific differences.
How should I interpret these benchmark results?
Read the benchmark name, exact version, metric, source, and model configuration together. Different evaluation settings can change the result. Preference ratings and source-defined composite indices remain separate from task accuracy.
Are these prices and provider measurements live?
This page uses dated source snapshots. Catalog data was observed on 17 Oct 2026. Provider routes were observed on 17 Oct 2026. Missing measurements are not estimated or treated as zero.
KEEP EXPLORING
More from xiaomi.
Explore related identities from the same developer, or take them into a side-by-side comparison.