90 days of the enterprise, pro and team plans free, no card needed. See the plans
Model comparison
Moonshot AI's Kimi K3 against Xiaomi's MiMo-V2.6-Pro: vendor list prices, limits, abilities and the Artificial Analysis indexes side by side - and what OpenSmartRoute does when both are available.
MiMo-V2.6-Pro lists at $0.544 per million tokens blended against $3.16 for Kimi K3 - 5.8x less.
MiMo-V2.6-Pro scores 46 on the intelligence index against 44 - 3 points apart.
MiMo-V2.6-Pro reads 1.1M tokens at once, Kimi K3 1.0M.
MiMo-V2.6-Pro was released about 2 months later.
Vendor list prices per million tokens and published limits; indexes are Artificial Analysis composites (0-100).
| Specification | Kimi K3 | MiMo-V2.6-Pro |
|---|---|---|
| Input price / 1M tokens | $0.24 | $0.43 |
| Output price / 1M tokens | $11.9 | $0.87 |
| Blended (3 in : 1 out) | $3.16 | $0.54 |
| Cached input / 1M | $0.21 | $0.004 |
| Context window | 1.0M | 1.1M |
| Max output | 944K | 131K |
| Input | text, image, video | text, image, video, audio |
| Output | text | text |
| Tool calls | ||
| Structured output | ||
| Reasoning | ||
| Open weights | ||
| Intelligence index | 44 | 46 |
| Coding index | 76 | - |
| Agentic index | 50 | - |
| Released | Jul 16, 2026 | Sep 21, 2026 |
| Available on this deployment |
List price times tokens for three typical workloads; your mix of input and output decides which model's pricing suits you.
| Workload | Kimi K3 | MiMo-V2.6-Pro | Difference |
|---|---|---|---|
| Support chat20M tokens in, 5M out a month - a help desk answering a few thousand conversations. | $64.46 | $13.05 | $51.41 less on MiMo-V2.6-Pro |
| Document summaries100M in, 5M out - long inputs, short answers. | $83.58 | $47.85 | $35.73 less on MiMo-V2.6-Pro |
| Coding assistant60M in, 20M out - a team's editor assistant, output-heavy. | $253 | $43.50 | $210 less on MiMo-V2.6-Pro |
MiMo-V2.6-Pro is both cheaper and stronger on the intelligence index, so with both in the catalogue the router sends it almost everything; Kimi K3 earns a request only on something it alone offers - a longer context, a modality, a data boundary or a region your rules require.
# targets.yaml - both models as routing targets (metadata.model links each to the catalogue entry)
targets:
- { id: mimo-v2.6-pro, kind: llm, metadata: { model: xiaomi/mimo-v2.6-pro } }
- { id: kimi-k3, kind: llm, metadata: { model: moonshotai/kimi-k3 } }
# rules.yaml - the cheaper model by default, the stronger one when the request is hard
rules:
- name: simple-requests-stay-cheap
when: { max_complexity: 0.45 }
prefer: [mimo-v2.6-pro]
weight: 0.8
- name: hard-requests-escalate
when: { min_complexity: 0.45 }
prefer: [kimi-k3]
weight: 0.8Every Moonshot AI and Xiaomi model, with prices, is on the vendor pages; the rankings show what the router actually picks.