Back to Models
MiMo V2.5 Pro
xiaomixiaomi/mimo-v2.5-pro
API guide
Chat completion
Use the normal OpenAI chat-completions shape through TheRouter; the model id is the public TheRouter id, not Xiaomi's upstream bare id.
cURL
curl https://api.therouter.ai/v1/chat/completions \
-H "Authorization: Bearer $THEROUTER_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"model": "xiaomi/mimo-v2.5-pro",
"messages": [
{"role": "system", "content": "You are a careful coding agent."},
{"role": "user", "content": "Plan a safe refactor for this repository."}
],
"temperature": 0.2,
"max_tokens": 4096
}'Tool calling
MiMo-V2.5-Pro is most interesting when the router can keep tools, fallback, and cost accounting in one OpenAI-compatible request path.
cURL
curl https://api.therouter.ai/v1/chat/completions \
-H "Authorization: Bearer $THEROUTER_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"model": "xiaomi/mimo-v2.5-pro",
"messages": [{"role": "user", "content": "Should we roll back deploy abc123?"}],
"tools": [{
"type": "function",
"function": {
"name": "get_deploy_metrics",
"description": "Return error-rate and latency metrics for a deploy id.",
"parameters": {
"type": "object",
"properties": {"deploy_id": {"type": "string"}},
"required": ["deploy_id"]
}
}
}],
"tool_choice": "auto"
}'Structured JSON
Use response_format when the output feeds an evaluator, queue, or policy engine; validate anyway before acting on tool or deploy decisions.
cURL
curl https://api.therouter.ai/v1/chat/completions \
-H "Authorization: Bearer $THEROUTER_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"model": "xiaomi/mimo-v2.5-pro",
"messages": [{"role": "user", "content": "Classify this incident as rollback, watch, or ignore: error rate doubled for checkout."}],
"response_format": {"type": "json_object"}
}'Related news
Fact ledger β every claim on this page traces here
| source | URL | retrieved | |
|---|---|---|---|
| Release date | mimo.xiaomi.com β | 2026-07-21 | verified |
| Upstream model id | mimo.mi.com β | 2026-07-21 | verified |
| Architecture | mimo.xiaomi.com β | 2026-07-21 | verified |
| Parameters | mimo.xiaomi.com β | 2026-07-21 | verified |
| Context window | mimo.mi.com β | 2026-07-21 | verified |
| Maximum output | mimo.mi.com β | 2026-07-21 | verified |
| Capabilities | mimo.mi.com β | 2026-07-21 | verified |
| API rate limits | mimo.mi.com β | 2026-07-21 | verified |
| Upstream API pricing | mimo.mi.com β | 2026-07-21 | verified |
| Training data | mimo.xiaomi.com β | 2026-07-21 | verified |
| License | huggingface.co β | 2026-07-21 | to verify |
| PKU SysY compiler hidden tests | mimo.xiaomi.com β | 2026-07-21 | verified |
| ClawEval | mimo.xiaomi.com β | 2026-07-21 | verified |
| SWE-bench Pro | therouter.ai β | 2026-07-21 | to verify |
| SWE-bench Verified | therouter.ai β | 2026-07-21 | to verify |
| UltraSpeed decode throughput | mimo.xiaomi.com β | 2026-07-21 | verified |
| MiMo-V2.5-Pro-UltraSpeed speed tier changes the routing math | TheRouter Newsroom β | 2026-07-21 | verified |
| MiMo-V2.5-Pro compatibility matters for agent routing | TheRouter Newsroom β | 2026-07-21 | verified |
| Xiaomi open-sources MiMo-V2.5-Pro | mimo.xiaomi.com β | 2026-07-21 | verified |
| Is xiaomi/mimo-v2.5-pro the same as the upstream Xiaomi model id? | mimo.mi.com β | 2026-07-21 | to verify |
| Does MiMo-V2.5-Pro really support a 1M-token context window? | mimo.mi.com β | 2026-07-21 | to verify |
| What is the pricing source for MiMo-V2.5-Pro? | mimo.mi.com β | 2026-07-21 | to verify |
| When should I choose UltraSpeed instead of standard MiMo-V2.5-Pro? | mimo.xiaomi.com β | 2026-07-21 | to verify |
| Can I self-host MiMo-V2.5-Pro? | huggingface.co β | 2026-07-21 | to verify |