Xiaomi MiMo API
MiMo API exposes named hosted models using OpenAI- and Anthropic-compatible interfaces, with per-token usage and a separate token-plan route.
Score calculation
(1 + 6 + 2 + 1 + 7) ÷ 5 = 3.4
5 of six dimensions rated. Unrated dimensions are excluded from the average.
Full scoring method ↗Setup details
Xiaomi MiMo hosted API for selectable model endpoints; MiMo web chat is excluded.
What fits your needs
Xiaomi MiMo hosted API for selectable model endpoints; MiMo web chat is excluded.
Fit
Use named MiMo models through compatible SDKs, with model choice in each API request.
Tradeoffs to expect
Tradeoff
Usage is billed by tokens or a separate token plan; confirm current model pricing and regional account terms before deployment.
How to switch
Getting started
Create a MiMo API key and replace the client base URL, key, and model identifier using the official quick start.
Practical questions
Prompt use and retention
The MiMo policy says prompts are not used for model training without prior consent; retention follows service purpose or legal requirements rather than a fixed number of days.
This grades published energy practices, not the service’s actual footprint.
See the evidence
The reviewed materials define the Xiaomi MiMo hosted model API and its functions but provide no service-specific reporting on electricity, emissions, water, sourcing, or resource-reduction controls. Missing measurements don’t show high consumption.
1 + 0 reporting + 0 electricity + 0 controls = 1/10. This grades documented practices and transparency.
No comparable service-level electricity, emissions, water, location mix, or independently reviewed footprint is established in these sources.
- Reporting0/3
- No service-specific operating boundary or footprint disclosure appears in the reviewed product material.
- Electricity sourcing0/3
- No route-specific clean-electricity sourcing or hourly power evidence is established.
- Resource controls0/3
- No route-specific measured efficiency or documented resource-reduction control is established.
Water disclosure
Water reporting has not been assessed for this choice.
The hosted route does not identify one fixed model and training data.
See the evidence
This Xiaomi MiMo hosted model API can expose multiple models or change its model selection over time. The product page is not a source-specific training-data and permissions record for every model served through the route.
Select the exact model and version, then review its training sources, permissions, creator controls, and any API-specific data terms.
The MiMo policy names API inputs, states prompts are not used for training without prior consent, and describes storage, sharing, and account controls.
See the evidence
Xiaomi’s MiMo privacy policy says prompts and uploaded media are processed for the chosen model, and states the company will not use user-provided text for model training or other purposes without prior consent. It also describes identity and billing data, cookie analytics, partner sharing, mainland storage for mainland use, and retention until the stated purpose or legal requirement ends.
Specific no-training-without-consent language and deletion/storage provisions support a stronger middle-band score, tempered by flexible retention, telemetry, and partner-sharing terms.
The policy gives no fixed prompt-retention duration or route-level human-review schedule; the policy notes separate terms may apply to use outside mainland China.
This is a hosted product route; its interface documentation does not disclose the hosted model implementation or grant access to its weights.
See the evidence
The reviewed Xiaomi MiMo hosted model API materials describe a hosted service, without publishing the service implementation or checkpoint weights for this route. Its openness rating concerns access to this product surface, not any separately released model family.
A hosted interface is documented, but source code, training artifacts, and route-specific downloadable weights are not established in these sources.
The exact model checkpoint and any route-specific release artifacts may change; this rating covers the named service route.
No model-specific worker safeguards are established for Xiaomi MiMo in the reviewed model sources.
See the evidence
The model release pages describe weights and technical properties, not conditions for employees, data annotators, evaluators, moderators, or infrastructure contractors. This is a source-bounded disclosure gap, not evidence of mistreatment. These findings concern the developer or operator. This product’s use in a particular deployment needs separate evidence.
1 base + 0 conditions + 0 worker voice/remedy + 0 evidence/follow-through = 1/10; this is a disclosure finding, not proof of abuse.
Worker locations, pay and conditions, supplier coverage, voice mechanisms, labor audits, and remediation outcomes are not established by these model-release sources.
- Pay & conditions0/3
- No worker-level conditions or supply-chain safeguards are established in this model-family source set. This is a disclosure gap, not proof of mistreatment.
- Worker voice & remedy0/3
- The model sources do not document a worker voice or remedy mechanism for data, evaluation, or infrastructure labor.
- Evidence & follow-through0/3
- No independent worker-level audit or remediation outcome is established in the reviewed model sources.
No route-specific military relationship or end-use oversight was established for this Xiaomi MiMo hosted API for selectable model endpoints; MiMo web chat is excluded..
See the evidence
The reviewed Xiaomi MiMo API materials describe user access, features, or account rules but don’t show a military customer, military deployment, or a model-specific restriction on military use. This route finding does not resolve the wider company’s government work.
7 base + 0 safeguard adjustment = 7/10 (0 of 9 safeguard points; every 3 adds 1). No military relationship was established in the cited sources. This ranks above known defense ties without claiming a verified clean record.
A separate, current company-level review is needed for defense contracts; downstream deployments and any customer-specific safeguards are not established here.
- Use restrictions0/4
- The cited route terms don’t spell out a specific restriction on military or surveillance use.
- Enforcement & oversight0/3
- The cited route terms don’t show route-level enforcement of military end-use restrictions.
- Relationship disclosure0/2
- The cited route material does not disclose a military customer or deployment for this route.
The cited Xiaomi MiMo API documentation covers product/API terms, but does not identify a military customer, deployment, or end-use restriction.
Military rubric ↗Xiaomi MiMo is not named in the two official BNC campaign lists checked. This is a limited list check, not BDS approval.
See the evidence
The official BNC consumer boycott/pressure guide and No Tech campaign page do not name Xiaomi MiMo among their current targets. BDS uses selective campaigns, so absence from these lists is neutral and should not be read as a clean record or approval. These findings concern the developer or operator. This product’s use in a particular deployment needs separate evidence.
This check covers only named targets in the two cited BNC campaigns; it does not cover all BDS campaigns, local groups, investments, suppliers, or downstream hosts. Lists and ownership may change.