90 days of the enterprise, pro and team plans free, no card needed. See the plans
Model comparison
Xiaomi's MiMo-V2.6-Pro against Z.ai's GLM 5.3: vendor list prices, limits, abilities and the Artificial Analysis indexes side by side - and what OpenSmartRoute does when both are available.
GLM 5.3 lists at $0.409 per million tokens blended against $0.544 for MiMo-V2.6-Pro - 1.3x less.
MiMo-V2.6-Pro scores 46 on the intelligence index against 45 - 2 points apart.
MiMo-V2.6-Pro reads 1.1M tokens at once, GLM 5.3 1.0M.
only MiMo-V2.6-Pro offers image input.
MiMo-V2.6-Pro was released about 1 month later.
Vendor list prices per million tokens and published limits; indexes are Artificial Analysis composites (0-100).
| Specification | MiMo-V2.6-Pro | GLM 5.3 |
|---|---|---|
| Input price / 1M tokens | $0.43 | $0.08 |
| Output price / 1M tokens | $0.87 | $1.40 |
| Blended (3 in : 1 out) | $0.54 | $0.41 |
| Cached input / 1M | $0.004 | $0.08 |
| Context window | 1.1M | 1.0M |
| Max output | 131K | 944K |
| Input | text, image, video, audio | text |
| Output | text | text |
| Tool calls | ||
| Structured output | ||
| Reasoning | ||
| Open weights | ||
| Intelligence index | 46 | 45 |
| Coding index | - | 75 |
| Agentic index | - | 53 |
| Released | Sep 21, 2026 | Aug 18, 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 | MiMo-V2.6-Pro | GLM 5.3 | Difference |
|---|---|---|---|
| Support chat20M tokens in, 5M out a month - a help desk answering a few thousand conversations. | $13.05 | $8.58 | $4.47 less on GLM 5.3 |
| Document summaries100M in, 5M out - long inputs, short answers. | $47.85 | $14.90 | $32.95 less on GLM 5.3 |
| Coding assistant60M in, 20M out - a team's editor assistant, output-heavy. | $43.50 | $32.74 | $10.76 less on GLM 5.3 |
GLM 5.3 takes the short and general requests - at $0.409 blended it is the default - and MiMo-V2.6-Pro the ones whose complexity or quality floor rules the cheaper model out. The split is per request, not per app, and every decision carries the scores for both.
# targets.yaml - both models as routing targets (metadata.model links each to the catalogue entry)
targets:
- { id: glm-5.3, kind: llm, metadata: { model: z-ai/glm-5.3 } }
- { id: mimo-v2.6-pro, kind: llm, metadata: { model: xiaomi/mimo-v2.6-pro } }
# 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: [glm-5.3]
weight: 0.8
- name: hard-requests-escalate
when: { min_complexity: 0.45 }
prefer: [mimo-v2.6-pro]
weight: 0.8Every Xiaomi and Z.ai model, with prices, is on the vendor pages; the rankings show what the router actually picks.