Requesty
Sign in

identity

open weights
Xiaomi logo

mimo-v2.5-proXiaomi

from /1M in$0.43xiaomi
context1.0M131K out
providers21 region
price spread2.3x3 endpoints
endpoints
3
regions
1
api
chat
released
April 2026

capabilities 4/8

visionreasoningtoolscachingweb searchjson schemacomputer useimage gen

The same weights cost 2.3x more on deepinfra inc. than on xiaomi. That is what the endpoints table is for.

endpoints

3 / 1 region
Providers serving mimo-v2.5-pro, with pricing and measured performance. Best value in each column is coloured.
#flags
1XiaomiGlobal1.0M$0.43$0.87$0.0036no-train
2DeepInfra Inc.Global1.0M$0.80$2.40$0.16zdr
3DeepInfra Inc.Global1.0M$1.00$3.00$0.20zdr
provider price, no markupper 1M tokensblank where no qualifying sample

measured

through Sep 12

no measured traffic for this model yet. the endpoints table above carries provider pricing

benchmarks

artificial analysis
Benchmark scores, each normalised to 100
evalScore as a share of 100/100
τ²-Bench94.2
GPQA Diamond86.6
Coding Index60.2
SciCode50.6
Terminal-Bench Hard43.2
Humanity's Last Exam35.7
Intelligence Index26.4
7 evalsmean56.7

Scores from Artificial Analysis and public leaderboards, normalised to 100. Bar colour is the band, not the rank: green 80 and up, blue 55 and up, amber 30 and up. Benchmarks measure narrow skills, so test on your own workload before committing. Released 2026-04-22.

call it

model=
mimo-v2.5-pro

requesty routes this id across every provider serving mimo-v2.5-pro, picking on price and health and failing over automatically. the id stays valid when a provider changes underneath it

Base url is https://router.requesty.ai/v1 for every id here. One key reaches the whole catalog.

quickstart

openai compatible
main.py
from openai import OpenAI client = OpenAI(    api_key="YOUR_REQUESTY_API_KEY",    base_url="https://router.requesty.ai/v1",) response = client.chat.completions.create(    model="mimo-v2.5-pro",    messages=[        {"role": "user", "content": "Explain quantum computing in one paragraph."},    ],) print(response.choices[0].message.content)

Change the base url, use your Requesty key, set the model to any id in the call pane. Existing OpenAI SDK code needs no other edit, and the same key reaches every other model in the catalog, so switching later is a one-parameter change. Browse all models

notes

reference

MiMo-V2.5-Pro is an open-source Mixture-of-Experts (MoE) language model with 1.02T total parameters and 42B active parameters. It utilizes the hybrid attention architecture and 3-layers Multi-Token Prediction (MTP) introduced in [MiMo-V2-Flash](https://github.com/XiaomiMiMo/MiMo-V2-Flash).

questions 6

Which providers serve mimo-v2.5-pro?
mimo-v2.5-pro is available from 2 providers through Requesty: Xiaomi, DeepInfra Inc.. All endpoints share one OpenAI-compatible API and one key, and Requesty fails over between them automatically.
How much does mimo-v2.5-pro cost?
Pricing starts at $0.43 per million input tokens and $0.87 per million output tokens on the cheapest provider. Prices vary by provider and region; the table above shows every endpoint. Requesty charges exactly what the upstream provider charges, with no markup.
Is mimo-v2.5-pro open weights?
Yes. mimo-v2.5-pro is an open-weights model from Xiaomi, which is why multiple inference providers can host it. Provider choice affects price, latency, and data-privacy terms, all compared above.
What is the context window of mimo-v2.5-pro?
mimo-v2.5-pro supports up to 1.0M tokens of context, with up to 131K output tokens per response. Some providers expose a smaller window; check the per-endpoint context column above.
How do I use mimo-v2.5-pro with the OpenAI SDK?
Install the OpenAI SDK, set base_url to "https://router.requesty.ai/v1", set your API key to your Requesty key, and set the model to "mimo-v2.5-pro" or any endpoint id from the table above. The quickstart section shows Python, JavaScript and cURL snippets.
Should I call mimo-v2.5-pro by its managed id or a provider id?
Use the managed id, "mimo-v2.5-pro". Requesty picks which of the 2 providers serves each request based on price and health, and fails over when one degrades, so the id keeps working while the routing changes underneath it. Send a provider id like "xiaomi/mimo-v2.5-pro" only when you need one specific deployment and want no failover.

more from xiaomi 1

Other Xiaomi models
modelcontextfrom /Mproviders
mimo-v2.51.0M$0.142

route mimo-v2.5-pro through one endpoint

One key for 2 providers on this model and 600+ others. No markup on provider prices, automatic failover, caching built in. Weekly aggregates in the measured pane come from production traffic routed through Requesty, one line per provider on a shared axis. Methodology

mimo-v2.5-pro2 providers3 endpointsfrom $0.43 /1M inctx 1.0Mspread 2.3xupdated Sep 12