MiMo-V2.6-Flash
mimo-v2.6-flashxiaomi-mimo-v2-6-flashxiaomi/mimo-v2.6-flash- 🧠 Sparse Mixture-of-Experts: 309B total parameters, 15B activated per token
- 📏 One-million-token context for long repositories and extended agent traces
- 👁️ Natively omnimodal: understands text, image, video and audio input
- 🔧 Function calling, web search and computer-use oriented tool workflows
- 🎯 Trained with mixed reinforcement learning across code, agents, vision, security
- ⚡ Efficiency-balanced design; served in FP8 on this catalog
- 🔒 Open weights released under the permissive MIT license
- 🆕 Flash variant of the MiMo-V2.6 generation, released September 2026
XiaomiMiMo is the large language model initiative from Xiaomi, the Chinese electronics and technology company, dedicated to developing capable open language models under the MiMo name. The effort reflects Xiaomi's broader push into foundational AI research alongside its consumer…
Explore 1 more model by Xiaomi MiMo →MiMo-V2.6-Flash is the efficiency-balanced entry in Xiaomi's MiMo-V2.6 generation, released in 2026. It is a sparse Mixture-of-Experts language model with roughly 309B total parameters of which about 15B are activated per token, so serving cost tracks the small active budget rather than the full weight count. The checkpoint natively understands text, images, video and audio in a single model, and accepts context windows up to one million tokens, which suits repository-scale code reading and long multi-session agent transcripts. Weights are published under an MIT license, and this deployment runs an FP8 compute path.
Relative to its same-family predecessor MiMo-V2.5, the V2.6 Flash release keeps Xiaomi's omnimodal direction while pushing the usable context to a million tokens and re-centering post-training on reinforcement learning. Per Xiaomi's model card, the V2.6 work is organised around scaling RL compute, environment diversity and grading compute together, using mixed reinforcement learning spanning coding, general agent, visual and cybersecurity tasks so that capability growth comes from exploration and feedback rather than pretraining scale alone.
In practice the model is positioned for long-horizon agentic work: iterative coding, tool use with function calling and web search, and computer-use style control loops, with reasoning available for harder multi-step problems. No independent third-party evaluation results for this checkpoint were available from trustworthy evaluators at the time of writing, so no benchmark figures are quoted here.
This About section is AI-generated from public sources via VeniceStats + Venice inference, with no human editing. It may contain inaccuracies.
| Seller | Reputation↓ | Routing | Input $/M | Cached $/M | Output $/M | Categories | API |
|---|---|---|---|---|---|---|---|
| Relay Works 0x3040…7139 | 71.71 | #3 | $0.154 | $0.0031 | $0.308 | text-generation | openai-chat-completions |
| ZLKPro-Api 0x0b0b…f446 | 65.27 | #1 | $0.02 | $0.002 | $0.05 | agent, chat, text | openai-chat-completions |
| Hana Gateway ✅ 0x4ae1…117b | 63.29 | #2 | $0.04 | $0.01 | $0.08 | chat, coding, fast | openai-chat-completions |
| klinn 0x0ee1…6c41 | 54.74 | gated | $0.0229 | $0.0005 | $0.0459 | chat, coding | openai-chat-completions |
| Fire Ant 🔥🐜 0xbe05…bc5d | 50.00 | gated | $0.1566 | $0.0034 | $0.3131 | — | — |
| LLMart 0x948a…a000 | 33.77 | gated | $0.2257 | $0.0267 | $0.4513 | — | openai-chat-completions |
| PawFlor-SI-Gateway 0x70bc…8261 | 22.46 | gated | $0.0882 | $0.0882 | $0.1764 | chat, fast | openai-chat-completions |
| ainoia 0x1af8…e2b5 | 14.09 | gated | $0.0196 | $0.0196 | $0.049 | chat, fast, text | openai-chat-completions |
"Best price" and the seller table are live AntSeed catalog data (advertised $/1M tokens — or $ per generated image for unit-billed image models — not settled amounts). Reputation = buyer trust score (0-100, the AntSeed SDK's own formula). "Routing" = the SDK's default buyer routing (what the VPR desktop app ships with): a trust ≥ 60 gate on the effective reputation, then cheapest-first among routable sellers; live failover state (per-peer cooldowns) is buyer-side runtime and not included. Model knowledge (TLDR, provider, About) via the VeniceStats enrichment layer. Advertised catalog, not the model used in any specific purchase. "Usage on AntSeed" counts only settlements whose buyers share the per-model split on-chain (metadata v2/v3, opt-in), so every usage figure is a lower bound.