Loading the catalogue…
Loading the catalogue…
Xiaomi's MIT-licensed efficiency-tier omnimodal reasoning model: a 309B/15B sparse MoE with a 1M-token context, native image, video and audio understanding, and a caller-controlled thinking switch.
Overview. MiMo-V2.6-Flash is Xiaomi's efficiency-tier reasoning model from the MiMo-V2.6 series, released in September 2026 under an MIT licence with published weights. It is a sparse Mixture-of-Experts model with 309B total parameters and 15B activated per token, drawing on 256 routed experts of which 8 fire per token, and it understands text, images, video and audio natively while returning text. A developer reaches for it when they need long-context reasoning over mixed media without stepping up to the flagship tier of the family.
Key strengths. The architecture balances capacity against serving cost: 309B total parameters behind only 15B active per token, plus a 1M-token context window with up to 128K tokens of output. It is an RL-trained reasoning variant with a caller-controlled thinking switch, and its strongest evidenced area is long-context, multimodal research work, where the curated domain signal leads the rest of the vector. On the Artificial Analysis Intelligence Index it scores 37.9, a mid-tier placement consistent with its position below the family flagship rather than a claim of frontier quality.
When to use it. Use this model for reasoning tasks that also need wide context — synthesising and analysing long documents, images, video or audio in a single pass, where a 1M-token window and native streams of image and audio input remove the need for pre-processing pipelines. It fits interactive applications, with a throughput-oriented sparse MoE and a binary thinking switch that lets you confirm the reasoning trace on when a task needs it and off when it does not. Prompt caching is exposed, which helps when the same long context is reused across calls.
Limitations. Tool calling and structured output are documented for this model, but parallel tool-call behaviour is not clearly specified, so multi-step agentic use should be treated as provisional. Reasoning is a binary on/off switch with no selectable effort levels, and while thinking is enabled the vendor fixes temperature and top-p, so sampling control is limited in that mode. Output is text only — the model understands audio and video but does not generate either — and Xiaomi has not published a training cutoff.
Sovereignty note. The creator is Xiaomi, based in China, and the weights are published under an MIT licence, which means the model can be self-hosted on infrastructure you control if you need full inference sovereignty. The Stav-hosted endpoint is delivered by DeepInfra, a US-incorporated provider, so that hosted endpoint does carry US CLOUD Act exposure; buyers in regulated EU jurisdictions should still confirm procurement and jurisdiction fit.
| Inference Provider | Sovereignty | Runs in | In / out per 1M | Status | Pin |
|---|---|---|---|---|---|
| L0 | €0.13 / 0.25 | Online |
27 use cases classified by the curator. The note says why.
1,048,576-token context holds whole repositories, with tool-calling for file and shell operations and extended thinking for patch planning. Not code-specialised, so treat the fit as architecture-driven rather than benchmark-proven.
Long-context reasoning is the core design point here: 1M tokens in, extended-thinking generation out. Vision input extends the same path to figure- and table-bearing PDFs.
Vision input handles screenshot-driven page state while tool-calling drives the action layer, and 1M tokens absorbs full DOM or session history. One of the few reasoning variants that pairs both modalities at this context length.
Vision input plus structured-output-friendly tool-calling covers the chart-to-data path, and the 1M context allows many charts to be processed in a single pass.
1M-token context permits full-repo or full-PR review passes, and extended thinking supports reasoning about cross-file impact. No published SWE-Bench-class score yet, so confidence rests on the architecture.
Tool-calling for order/account lookups, 1M-token context for full conversation and policy history, and 15B active parameters for economical high-volume serving. Open weights permit deployment inside regulated customer environments.
Million-token context lets the model read full repositories before explaining code paths, an advantage over sub-200K models. No code-specific benchmark scores are published for this variant.
Long-context reasoning supports multi-document policy Q&A; open-weights deployment addresses sovereignty requirements for internal compliance use. Specific grounding benchmarks not yet available.
Large context supports embedding-adjacent retrieval and long query expansion, but no dedicated retrieval or embedding benchmarks are published for this variant.
Audio input is documented as part of the omnimodal profile, so transcription is plausible, but no ASR benchmark or dedicated speech-output/word-timing capability is stated. Dedicated speech models remain the safer default.
1M context supports whole-document translation with term consistency, which is unusual for translation workloads. No translation benchmarks published for the Flash variant.
The model accepts audio input but has no documented audio generation capability — it cannot produce speech waveforms. Use a dedicated TTS system.
Voice agents need speech output in the loop, and this variant is input-only for audio. It could serve as the reasoning backend behind a separate TTS layer, but not as the voice interface itself.
Sourced numbers, not our own evaluations. Percentiles are against the whole Stav catalogue.
Computed from aa-intelligence-index, gpqa-diamond, aa-engineering-index, aa-coding-index, livecodebench, terminal-bench-v4, aa-lcr.
curl https://api.stav.ai/v1/chat/completions \
-H "Authorization: Bearer $STAV_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"model": "xiaomimimo/mimo-v2-6-flash",
"messages": [{"role": "user", "content": "Hello!"}]
}'→ X-Stav-Request-Id · X-Stav-Model · X-Stav-Provider → X-Stav-Sovereignty-Level — the rung the request was served at