MiMo V2.6 Pro
xiaomi/mimo-v2.6-proCompare xiaomi/mimo-v2.6-pro API pricing, supported endpoints, capabilities and access options on Modelsell.
- Starting price
- Input / Output · 1M
- Context
- 1.1M
- Maximum input window
- Max output
- 131.1K
- Maximum tokens per response
- Modalities
- →
Pricing by Supplier
Capabilities / Supported modalities
Provider & data privacy
BPE (vendor-specific)Performance
Benchmarks
Scores on standardized evaluations. Higher percentages are better — and rank percentile shows
Metrics sourced fromArtificial Analysis 2026-09-30·MiMo V2.6 Pro
This model is not included in the current benchmark snapshot.
Missing models or measurements are not zero scores.
Benchmark charts preserve the source model selection and reasoning settings. Missing models or measurements are not zero scores, and benchmark cost or speed is not this site’s service commitment.
About MiMo V2.6 Pro
从多种材料里还原问题
MiMo-V2.6-Pro 能把文本、图片、视频和音频放在同一任务中理解，并以文字给出分析、代码或工作结果。它适合处理信息分散的问题：用户录屏展示故障，截图补充界面细节，语音说明预期，再结合代码与日志寻找原因。材料之间有矛盾时，可以要求它指出差异和缺失证据，先把问题界定清楚。
面向复杂开发与智能体工作
模型重点覆盖编程、通用智能体和视觉任务。百万级上下文能够容纳较长的项目资料、工具轨迹和跨多轮工作记录，适合梳理模块关系、规划修改范围，以及在实现后继续分析测试反馈。接入文件、终端或界面操作工具后，应用可把真实执行结果交回模型，由它决定下一步；工具权限与执行环境需要由应用提供。
复杂任务可以拆成可验收的阶段。例如先重现上传失败，再检查接口与状态管理，完成最小修复，最后用同一段操作流程复测。每次工具返回后更新判断，比在开始时写出一份长计划后一直照做更有帮助。
把观察、推断和验证分开
给素材标明用途与时间顺序：录屏用于观察动作和状态变化，清晰截图用于查看细小文字，音频用于补充需求背景。要求回答区分直接观察到的现象、可能原因和已经验证的结论。跨会话继续开发时，保存已完成修改、关键工具结果与尚未解决的问题，让后续工作沿着已有证据推进。
Use cases and prompting
排查界面故障的提示词
“结合这段上传失败录屏、用户反馈音频、报错截图和相关代码，列出故障发生前后的状态变化。先提出可重现步骤，再检查接口调用与前端状态更新，给出最小修复及回归步骤。把已证实的原因和仍待验证的假设分开。”
录屏里细节看不清怎么办？
补充关键时刻的清晰截图，并注明对应时间点；不要要求模型猜测无法辨认的报错文字。
如何接续长时间开发？
保留最新代码、工具返回和阶段记录，明确本轮目标及验收条件。执行测试、读取文件等动作需要应用提供工具，并将真实结果传回。
API access
API documentation
Code samples
/v1/chat/completions| Parameter | Type | Default / range | Description |
|---|---|---|---|
temperature | number | = 10 ~ 2 | Sampling temperature; lower is more deterministic |
top_p | number | = 10 ~ 1 | Nucleus sampling probability mass |
max_tokens | integer | >= 1 | Maximum number of tokens in the response |
frequency_penalty | number | = 0-2 ~ 2 | Penalises repetition of frequent tokens |
presence_penalty | number | = 0-2 ~ 2 | Encourages introducing new topics |
stop | array | — | Up to 4 strings that stop generation |
seed | integer | — | Deterministic sampling seed (best-effort) |
n | integer | = 1>= 1 | Number of completions to generate |
stream | boolean | = false | Stream tokens via Server-Sent Events |
response_format | object | — | Force JSON object or schema-conforming output |
tools | array | — | Tool / function declarations the model may call |
tool_choice | string | autononerequired | Tool-choice policy or specific tool name |
logprobs | boolean | = false | Return per-token log probabilities |
top_logprobs | integer | 0 ~ 20 | Number of top log probabilities returned per token |
logit_bias | object | — | Per-token logit bias map |
user | string | — | End-user identifier for abuse monitoring |
Replace <YOUR_API_KEY> with the API key from your token settings.
Authentication
All requests must include Authorization: Bearer <TOKEN> header. Anthropic-formatted endpoints accept the x-api-key header instead.
Generate tokens from the Tokens page; you can scope them to specific models, groups, IPs, and rate-limits.
Supported parameters
| Parameter | Type | Default / range | Description |
|---|---|---|---|
temperature | number | = 10 ~ 2 | Sampling temperature; lower is more deterministic |
top_p | number | = 10 ~ 1 | Nucleus sampling probability mass |
max_tokens | integer | >= 1 | Maximum number of tokens in the response |
frequency_penalty | number | = 0-2 ~ 2 | Penalises repetition of frequent tokens |
presence_penalty | number | = 0-2 ~ 2 | Encourages introducing new topics |
stop | array | — | Up to 4 strings that stop generation |
seed | integer | — | Deterministic sampling seed (best-effort) |
n | integer | = 1>= 1 | Number of completions to generate |
stream | boolean | = false | Stream tokens via Server-Sent Events |
response_format | object | — | Force JSON object or schema-conforming output |
tools | array | — | Tool / function declarations the model may call |
tool_choice | string | autononerequired | Tool-choice policy or specific tool name |
logprobs | boolean | = false | Return per-token log probabilities |
top_logprobs | integer | 0 ~ 20 | Number of top log probabilities returned per token |
logit_bias | object | — | Per-token logit bias map |
user | string | — | End-user identifier for abuse monitoring |
Rate limits
| Supplier | RPM | TPM | RPD |
|---|---|---|---|
| XiaomiMIMO | Unlimited | Unlimited | Unlimited |
No restriction
Frequently asked questions about xiaomi/mimo-v2.6-pro
What is xiaomi/mimo-v2.6-pro?
Compare xiaomi/mimo-v2.6-pro API pricing, supported endpoints, capabilities and access options on Modelsell.
How do I call xiaomi/mimo-v2.6-pro?
Create an API key with access to xiaomi/mimo-v2.6-pro, then use the exact model ID and a supported endpoint from the API access section. Request fields depend on the selected endpoint.
How is xiaomi/mimo-v2.6-pro priced?
Pricing depends on the selected provider group and the model billing unit. The current input, output, request, or media prices are shown on this page before sign-up.
What is the context window of xiaomi/mimo-v2.6-pro?
The model catalog lists a context window of 1050000 tokens. Check the selected endpoint for request limits.
What is the maximum output of xiaomi/mimo-v2.6-pro?
The model catalog lists a maximum output of 131072 tokens. Your request settings may set a lower limit.
How should I evaluate xiaomi/mimo-v2.6-pro for my project?
Start with the use cases and prompting guidance on this page, then evaluate the model with representative inputs from your project.