MiMo-V2.5 on VM0. Xiaomi's long-context omnimodal model
Xiaomi's OpenRouter-hosted omnimodal model on VM0. 1M-token context, text/image/audio/video input, and cost-saving x0.1 VM0 Managed pricing.
1M tokens · Text / Vision / Audio / Video / Code · Prompt cache
MiMo-V2.5 brings Xiaomi's long-context omnimodal model into VM0 through the OpenRouter route. It is the broadest-input low-cost option in the Built-in lineup, accepting text, image, audio, and video inputs while keeping a 1M-token context window.
Use it for cost-sensitive agents that need to inspect mixed media alongside text or code. It is not a dedicated coding provider route like Moonshot or a Z.AI direct route like GLM, so keep Sonnet or Kimi in reserve when tool routing quality is the main constraint.
What is MiMo-V2.5?
June 2026 · Xiaomi's general-purpose omnimodal model exposed through VM0 Managed via OpenRouter.
MiMo-V2.5 is Xiaomi's native omnimodal model on OpenRouter. VM0 exposes it as the canonical mimo-v2.5 model and routes Built-in runs to the upstream id xiaomi/mimo-v2.5.
The model combines a 1M-token context window with text, image, audio, and video input support. That makes it a practical low-cost choice when an agent has to read media-heavy evidence alongside normal text.
On VM0 Managed it sits at x0.1 credits. Teams that want vendor-direct billing can use an OpenRouter API key with the same upstream id.
What's notable about MiMo-V2.5
Headline architecture and capability features.
MiMo-V2.5 is exposed on VM0 through the OpenRouter Anthropic-compatible gateway with upstream id xiaomi/mimo-v2.5.
Specs at a glance
MiMo-V2.5 benchmarks
VM0 treats MiMo-V2.5 as a low-cost multimodal option. Public rankings can move quickly, so this page focuses on routing, modality coverage, context, and price.
MiMo-V2.5 pricing
Provider list price, per 1M tokens.
How MiMo-V2.5 behaves in practice
Observed behaviour from production agent runs.
Multimodal coverage
MiMo-V2.5 is the low-cost route to combine text, images, audio, and video inputs in one agent step.
Large context
The 1M-token context window gives agents enough room for long documents, transcripts, and supporting files without aggressive chunking.
Routing
VM0 Managed routes through OpenRouter using xiaomi/mimo-v2.5. OpenRouter BYOK users can select the same upstream model directly.
Best agent tasks for MiMo-V2.5
Mixed-media research pass
Use MiMo-V2.5 when the agent needs to inspect screenshots, clips, transcripts, and written notes together before producing a structured brief.
Low-cost multimodal triage
Run first-pass classification over media-heavy support cases or QA artifacts at x0.1 credits, then escalate only the hard cases.
Large-context document review
Load long source material with images or media references and ask for cross-document findings without moving immediately to a premium model.
When to skip MiMo-V2.5
Skip MiMo-V2.5 when you need the strongest Claude-style tool routing, or when the workflow is text-only and a cheaper narrow model is sufficient.
MiMo-V2.5 vs other models
MiMo-V2.5 vs GLM-5.2
Both offer 1M context through VM0 Managed. GLM-5.2 is the Z.AI long-context route; MiMo-V2.5 adds image, audio, and video input through OpenRouter.
MiMo-V2.5 vs Kimi K2.7 Code
Kimi is the stronger coding-focused Moonshot route. MiMo-V2.5 wins when broad multimodal input and a larger 1M context matter more.
MiMo-V2.5 vs Claude Sonnet 4.6
Sonnet remains the safer premium default for tool routing and hard reasoning. MiMo-V2.5 is the lower-cost multimodal exploration route.
MiMo-V2.5 vs Hy3 Preview
Hy3 Preview is cheaper and text-only with 256K context. MiMo-V2.5 is the better fit when image, audio, video, or a 1M window is needed.
Bottom line: should you use MiMo-V2.5?
Pick MiMo-V2.5 when a low-cost agent needs both 1M context and multimodal inputs through OpenRouter.
Frequently asked questions
Is MiMo-V2.5 available through VM0 Managed?
Yes. VM0 Managed routes MiMo-V2.5 through OpenRouter with the upstream id xiaomi/mimo-v2.5.
Can I use my own OpenRouter key?
Yes. Select the OpenRouter provider and use the upstream model id xiaomi/mimo-v2.5.
Does MiMo-V2.5 support image input?
Yes. OpenRouter lists text, image, audio, and video as supported input modalities for MiMo-V2.5.
Alternatives
Using MiMo-V2.5 on VM0
Two ways to access MiMo-V2.5 on VM0
VM0 supports MiMo-V2.5 as a Built-in model billed in VM0 credits, and through bring-your-own with a OpenRouter API key. The Built-in path uses VM0 Managed routing and the credit multiplier explained below; the bring-your-own path bills you directly with the upstream vendor and skips the VM0 credit conversion entirely.
VM0's recommendation
VM0 positions MiMo-V2.5 as a cost-saving option rather than a core agent model. Use it to optimise unit cost on non-core work, such as bulk classification, pre-filters, latency-critical short replies, or pinned legacy agents, while keeping Claude Opus 4.7, Claude Opus 4.6, or Claude Sonnet 4.6 on the steps that decide the run.
Credits and the ×0.1 multiplier
Every Built-in model on VM0 is priced as a multiple of Claude Sonnet 4.6, which sits at the ×1 credit baseline. MiMo-V2.5 bills at ×0.1 credits. The multiplier is what shows up on your VM0 invoice; the vendor list price in the pricing table above is what the upstream provider charges before VM0 converts it into credits.
MiMo-V2.5 bills at ×0.1, which means a step here costs only 0.1× the credits of an equivalent step on Sonnet 4.6 (the ×1 baseline). That puts it well below the credit baseline and makes it the natural pick for high-volume background work where cost-per-step matters more than peak reasoning quality.
Available on VM0 since June 2026.