Text-focused Xiaomi model with 1M context and deep thinking. Provider-service retirement is scheduled for October 21, 2026; app availability is separate.
Tool support requires the appropriate API integration; a supported tool is not automatically active in every chat.
Supported API features and tools
Text-focused Pro model for coding and reasoning workflows
Published 1M context and 128K maximum output
Deep thinking, streaming and tool calls documented by Xiaomi
Structured output, context caching and web search in supported integrations
Before you choose
The Pro model page specifies text input. Do not transfer the base model's image, audio or video support to Pro.
The published K/M labels are retained rather than converted into invented exact token counts.
The reviewed sources do not establish a knowledge cutoff. Supply current evidence for time-sensitive questions; a large context window is not live web access.
Provider retirement affects migration planning even if an old catalog URL remains available.
Extended thinking
Xiaomi documents deep thinking and shows a thinking.type disabled request example. This guide does not assert an unverified default, budget or low/medium/high effort mapping. Check the current endpoint and app controls.
The provider documents compatible API request formats, but model-specific media and thinking fields must follow Xiaomi's contract.
A system message in a sample request is not evidence of a model's actual training cutoff. No cutoff is claimed here.
Test tool results, output formats and failure behavior on the migration target. The V2.6 recommendation does not automatically choose or enable a replacement in your app.
Put it to work
Start with a more useful prompt.
Original examples from EZ Ai Assist. Adapt these to your task and the features available in your workspace.
Workflow 01
Audit a retirement migration
Turn a provider deadline into bounded engineering work.
Using these integration settings and provider lifecycle notices, make a migration checklist for our text model. Identify exact IDs, required parameters, output contracts and regression tests. Separate confirmed facts from assumptions. Define rollback criteria and owner approvals; do not assume a catalog entry proves the endpoint is live.
Workflow 02
Compare implementation proposals
Evaluate technical choices against supplied evidence.
Compare these implementation proposals against our requirements, operational limits and test results. Cite the relevant section for each conclusion, identify missing evidence and rank the largest risks. Recommend one small validation experiment before choosing an approach. Do not invent benchmark results or costs.
Workflow 03
Trace a code failure
Prioritize tests that can distinguish causes.
Use the error log and code below to map the failure path. Separate observed facts from hypotheses, cite the relevant functions, and propose three discriminating tests with expected outcomes. Suggest the smallest safe fix only when the evidence supports it; do not claim tools or tests were run.
Developer reference
Xiaomi MiMo API pricing
These are provider API reference prices, not EZ Ai Assist subscription prices.
Xiaomi MiMo published USD API rates · USD per 1,000,000 tokens
Token type
Price
Input · cache miss
$0.435
Input · cache hit
$0.0036
Output
$0.87
These are the current model page's USD rates, not currency conversions from launch pricing or Token Plan subscription allowances.
Cache-hit rates apply only to eligible cached input, not all prompts or output. Recheck current pricing and lifecycle status before calling the API.
Common questions
A few things worth knowing.
When is the provider service scheduled to retire?
October 21, 2026, at 10:00 Beijing time, according to Xiaomi's subscription documentation. This is a provider-service notice, not a statement of EZ Ai Assist availability.
Does Pro accept the same media as the base model?
No. The Pro page documents text input; the base MiMo-V2.5 page documents text, images, video and audio. Both return text.
Which replacement should I use?
Xiaomi points toward the V2.6 series. Verify the exact available endpoint and your modality, tool and output requirements before selecting a replacement; this guide does not invent a local replacement route.
Why is the knowledge cutoff not verified?
The reviewed model pages do not establish it. A cutoff string inside a sample system prompt is caller-supplied text, not authoritative model metadata.
Does this page guarantee access in EZ Ai Assist?
No. A catalog entry and provider capability reference do not establish current app access, enabled tools or available settings. Check the model selector and controls in your workspace.
Are these EZ Ai Assist subscription prices?
No. Provider API rates are developer references. Your subscription and any limits shown in the app are separate; use the website pricing page for plans.
How should I verify an answer?
Provide the relevant evidence and acceptance criteria, ask for source references or reproducible checks, and review the result. Distinguish a proposed tool action from a tool action actually executed.
Check the source
Official documentation
Specifications and API prices checked on . Example prompts and workflow advice are editorial guidance from EZ Ai Assist.