Requesty
Xiaomi logo

mimo-v2.6-flash

Xiaomi/Open weights/3 providers

MiMo-V2.6-Flash is the efficiency-balanced model in Xiaomi's MiMo-V2.6 series: a sparse Mixture-of-Experts model with 309B total and 15B activated parameters, natively omnimodal across text, image, video and audio, with a 1M-token context window. Trained with large-scale mixed reinforcement learning across coding, general agents, visual and cybersecurity tasks, it is built for agentic workloads such as long-horizon coding, tool use and computer use.More

Which id to call

mimo-v2.6-flash

Requesty routes this id across every provider serving mimo-v2.6-flash, picking on price and health and failing over automatically. The id stays valid when a provider changes underneath it.

From /1M input

$0.14

DeepInfra

Context

1.0M

131K output

Endpoints

3

1 region

Regions

1

chat

Capabilities 5/8

VisionReasoningTool callingCachingWeb searchJSON schemaComputer useImage generation

3 endpoints / 1 region

Providers serving mimo-v2.6-flash

Provider prices, per 1M tokens. Pay as you go adds 5%, or 0% on your own keys.

Providers serving mimo-v2.6-flash, with pricing and measured performance. The best value in each column is highlighted.
RankPrivacy
1DeepInfraGlobal1.0M$0.14$0.28$0.0027zdr
2TencentGlobal1.0M$0.14$0.28$0.0028no-train
3XiaomiGlobal1.0M$0.14$0.28$0.0028no-train

A column is blank where no qualifying sample exists, and every row links to that provider's endpoint page.

model=

Which id to call

One base url, https://router.requesty.ai/v1, and one key for every id here.

mimo-v2.6-flash

Requesty routes this id across every provider serving mimo-v2.6-flash, picking on price and health and failing over automatically. The id stays valid when a provider changes underneath it.

OpenAI compatible

Call it in three lines

Change the base url, use your Requesty key, set the model to any id on the left. Existing OpenAI SDK code needs no other edit.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
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.6-flash", messages=[ {"role": "user", "content": "Explain quantum computing in one paragraph."}, ], ) print(response.choices[0].message.content)

Artificial Analysis

Benchmark scores

Intelligence Indexreasoning
26.7%

Artificial Analysis Intelligence Index: a composite of multiple evaluations measuring overall model capability.

Scores from artificialanalysis.ai. They measure the model, not the provider, so they are the same on every endpoint above.

4

More from Xiaomi

Reference

mimo-v2.6-flash questions

Which providers serve mimo-v2.6-flash?

mimo-v2.6-flash is available from 3 providers through Requesty: DeepInfra, Tencent, Xiaomi. All endpoints share one OpenAI-compatible API and one key, and Requesty fails over between them automatically.

How much does mimo-v2.6-flash cost?

Pricing starts at $0.14 per million input tokens and $0.28 per million output tokens on DeepInfra, the cheapest endpoint. Prices vary by provider and region; the table above shows every endpoint. Those are the upstream provider rates: pay as you go adds 5% on top, or 0% if you bring your own provider keys.

Is mimo-v2.6-flash open weights?

Yes. mimo-v2.6-flash 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.6-flash?

mimo-v2.6-flash 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.6-flash 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.6-flash" or any endpoint id from the table above. The quickstart section shows Python, JavaScript and cURL snippets.

Should I call mimo-v2.6-flash by its managed id or a provider id?

Use the managed id, "mimo-v2.6-flash". Requesty picks which of the 3 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 "deepinfra/mimo-v2.6-flash" only when you need one specific deployment and want no failover.

Route mimo-v2.6-flash through one endpoint

One key for 3 providers on this model and 600+ others. No markup on provider prices, automatic failover, caching built in.

Benchmark rankings