GLM-5.2 is Z.ai’s flagship model for the era of long-horizon tasks. With a truly usable 1M-token context window, it can handle project-level engineering context, execute long-running tasks more reliably, follow engineering standards more consistently, and complete the full development workflow from requirements to multi-platform deployment in a single task.
glm-5.2 vs kimi-k3
Output tokens cost $1.97 per million on glm-5.2 and $15.00 per million on kimi-k3. Input tokens cost $0.56 per million on glm-5.2 and $3.00 per million on kimi-k3. Cached input tokens are billed at $0.14 per million on glm-5.2 and $0.30 per million on kimi-k3. Discounted rates are shown where a promotion is active. Context windows are 1,000,000 tokens on glm-5.2 and 1,048,576 tokens on kimi-k3. First-token latency measured on AIHubMix is 1.8s on glm-5.2 and 6.8s on kimi-k3. Measured output throughput is 46.9 tokens/s on glm-5.2 and 32.2 tokens/s on kimi-k3.
Kimi K3 is Kimi’s flagship model for long-horizon coding and end-to-end knowledge work, with a 1M-token context window and industry-leading intelligence.
Specs & Pricing
Prices are per million tokens. Latency and throughput are rolling averages measured on AIHubMix.
Promotional prices show the discounted rate; see each model page for promotion windows.
Usage on AIHubMix last 30 days
Daily traffic served through AIHubMix — how demand for each model is trending.
Tokens / day
Requests / day
Live Performance last 3 days
Measured on real AIHubMix traffic, hourly buckets. Gaps mean no traffic in that hour.
Throughput (TPS)
Latency (s)
Uptime (%)
Cost Calculator
Estimate your monthly bill for the same workload on each model.
Monthly = daily × 30. Discounted rates applied where a promotion is active.
FAQ
Which is cheaper: glm-5.2, kimi-k3?
glm-5.2: $1.97/M output tokens; kimi-k3: $15.00/M. Use the cost calculator above to estimate your own workload.
Which responds faster?
glm-5.2: 1.8s first-token latency measured on AIHubMix; see the live performance charts above for how each model behaves across the day.
How large is each context window?
glm-5.2 accepts 1,000,000 and kimi-k3 accepts 1,048,576 input tokens. Maximum output per request is 128,000 tokens on glm-5.2 and 1,048,576 tokens on kimi-k3.
Which one generates tokens faster?
glm-5.2 at 46.9 tokens/s and kimi-k3 at 32.2 tokens/s, measured as output throughput on AIHubMix — a separate metric from first-token latency.
What inputs and capabilities does each model support?
glm-5.2 accepts text input and supports thinking, tool calling, function calling and structured outputs; kimi-k3 accepts text, image and video input and supports thinking, function calling and structured outputs.
Can I call glm-5.2 and kimi-k3 with the same API key?
Yes. AIHubMix serves every model on this page behind one OpenAI-compatible endpoint, so switching between them is a one-line change to the model field — no second account, key or SDK.
Popular Comparisons
Related model match-ups readers also look at.
