Requesty
Sign in

identity

open weights
Xiaomi logo

mimo-v2.5Xiaomi

from /1M in$0.14xiaomi
context1.0M131K out
best ttft787msdeepinfra inc.
price spread2.9x3 endpoints
endpoints
3
regions
1
best tok/s
77
api
chat
released
April 2026

capabilities 5/8

visionreasoningtoolscachingweb searchjson schemacomputer useimage gen

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

endpoints

3 / 1 region
Providers serving mimo-v2.5, with pricing and measured performance. Best value in each column is coloured.
#flags
1XiaomiGlobal1.0M$0.14$0.28$0.00281.84s77.0no-train
2DeepInfra Inc.Global262K$0.32$1.60$0.06787ms71.0zdr
3DeepInfra Inc.Global262K$0.40$2.00$0.08787ms71.0zdr
provider price, no markupper 1M tokensblank where no qualifying sample

measured

through Sep 12
median
497ms2.76s5.02s07-0608-0309-074.64s1.71s
hover the plot for weekly values
time to first token per provider: current value, window low and high, and change across the window
providernowlowhighchange
DeepInfra Inc.787ms874ms1.83s-6.9%
Xiaomi1.84s1.27s4.64s+266%

median wait before the first token lands. this is the number a user feels, and it moves with provider load through the day.

Lines are steps: each sample is one week of traffic held flat, not a slide from the week before. Click a name in the key to drop it from the plot. Measured through Sep 12.

benchmarks

artificial analysis

no published benchmark scores for this model

call it

model=
mimo-v2.5

requesty routes this id across every provider serving mimo-v2.5, 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",    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 is a native omnimodal model with strong agentic capabilities, supporting text, image, video, and audio understanding within a unified architecture. Built upon the MiMo-V2-Flash backbone and extended with dedicated vision and audio encoders, it delivers robust performance across multimodal perception, long-context reasoning, and agentic workflows.

questions 7

Which providers serve mimo-v2.5?
mimo-v2.5 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 cost?
Pricing starts at $0.14 per million input tokens and $0.28 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 open weights?
Yes. mimo-v2.5 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?
mimo-v2.5 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.
Which provider is fastest for mimo-v2.5?
In recent production traffic through Requesty, DeepInfra Inc. had the lowest median time to first token (787ms) for mimo-v2.5. Latency shifts over time, so Requesty's latency-based routing picks the fastest healthy provider per request automatically.
How do I use mimo-v2.5 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" or any endpoint id from the table above. The quickstart section shows Python, JavaScript and cURL snippets.
Should I call mimo-v2.5 by its managed id or a provider id?
Use the managed id, "mimo-v2.5". 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" only when you need one specific deployment and want no failover.

more from xiaomi 1

Other Xiaomi models
modelcontextfrom /Mproviders
mimo-v2.5-pro1.0M$0.432

route mimo-v2.5 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.52 providers3 endpointsfrom $0.14 /1M inctx 1.0Mttft 787msspread 2.9xupdated Sep 12