90 days of the enterprise, pro and team plans free, no card needed. See the plans
Model comparison
Moonshot AI's Kimi K3 against Z.ai's GLM 5.2: vendor list prices, limits, abilities and the Artificial Analysis indexes side by side - and what OpenSmartRoute does when both are available.
GLM 5.2 lists at $1.76 per million tokens blended against $5.17 for Kimi K3 - 2.9x less.
Kimi K3 scores 44 on the intelligence index against 34 - 10 points apart.
Kimi K3 scores 76 on the coding index against 69 - 7 points apart.
Kimi K3 scores 50 on the agentic index against 38 - 12 points apart.
only Kimi K3 offers image input.
Vendor list prices per million tokens and published limits; indexes are Artificial Analysis composites (0-100).
| Specification | Kimi K3 | GLM 5.2 |
|---|---|---|
| Input price / 1M tokens | $0.23 | $0.01 |
| Output price / 1M tokens | $20.0 | $7.00 |
| Blended (3 in : 1 out) | $5.17 | $1.76 |
| Cached input / 1M | $0.22 | $0.01 |
| Context window | 1.0M | 1.0M |
| Max output | 944K | 944K |
| Input | text, image, video | text |
| Output | text | text |
| Tool calls | ||
| Structured output | ||
| Reasoning | ||
| Open weights | ||
| Intelligence index | 44 | 34 |
| Coding index | 76 | 69 |
| Agentic index | 50 | 38 |
| Released | Jul 16, 2026 | Jun 16, 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 | GLM 5.2 | Difference |
|---|---|---|---|
| Support chat20M tokens in, 5M out a month - a help desk answering a few thousand conversations. | $105 | $35.28 | $69.34 less on GLM 5.2 |
| Document summaries100M in, 5M out - long inputs, short answers. | $123 | $36.40 | $86.70 less on GLM 5.2 |
| Coding assistant60M in, 20M out - a team's editor assistant, output-heavy. | $414 | $141 | $273 less on GLM 5.2 |
GLM 5.2 takes the short and general requests - at $1.76 blended it is the default - and Kimi K3 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.2, kind: llm, metadata: { model: z-ai/glm-5.2 } }
- { 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: [glm-5.2]
weight: 0.8
- name: hard-requests-escalate
when: { min_complexity: 0.45 }
prefer: [kimi-k3]
weight: 0.8Every Moonshot AI and Z.ai model, with prices, is on the vendor pages; the rankings show what the router actually picks.