mimo-v2.6-pro-ultraspeedXiaomi
- endpoints
- 1
- regions
- 1
- api
- chat
- released
- September 2026
capabilities 5/8
| # | flags | ||||||
|---|---|---|---|---|---|---|---|
| 1 | Global | 1.0M | $4.35 | $8.70 | $0.04 | no-train |
no measured traffic for this model yet. the endpoints table above carries provider pricing
no published benchmark scores for this model
xiaomi/mimo-v2.6-pro-ultraspeedthis model has no managed policy yet, so call the provider endpoint directly. every id in the endpoints table works the same way
Base url is https://router.requesty.ai/v1 for every id here. One key reaches the whole catalog.
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="xiaomi/mimo-v2.6-pro-ultraspeed", 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
Xiaomi MiMo V2.6 Pro UltraSpeed. Same 1T+ MiMo V2.6 Pro checkpoint served at roughly 10x output speed for latency sensitive workloads. Omni-modal input (text, image, video, audio), text output. 1M token context window, 128K max output. OpenAI-compatible.
questions 5
Which providers serve mimo-v2.6-pro-ultraspeed?
How much does mimo-v2.6-pro-ultraspeed cost?
Is mimo-v2.6-pro-ultraspeed open weights?
What is the context window of mimo-v2.6-pro-ultraspeed?
How do I use mimo-v2.6-pro-ultraspeed with the OpenAI SDK?
more from xiaomi 4
| model | context | from /M | providers |
|---|---|---|---|
| mimo-v2.6-flash | 1.0M | $0.14 | 3 |
| mimo-v2.6-pro | 1.0M | $0.43 | 3 |
| mimo-v2.5-pro | 1.0M | $0.43 | 3 |
| mimo-v2.5 | 1.0M | $0.14 | 2 |
route mimo-v2.6-pro-ultraspeed through one endpoint
One key for 1 provider 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
