GLM 5.2 API Pricing: OpenRouter, Z.ai, Free Access and Cost Examples
GLM 5.2 pricing depends on the provider route, token volume, and whether you are using ordinary chat completions, coding-agent loops, or long repository context. This page uses the currently listed OpenRouter numbers as a transparent baseline and points out where you must verify direct Z.ai pricing before production use.
Price comparison
| Model | Input / 1M | Output / 1M | Context | Access |
|---|---|---|---|---|
| GLM 5.2 (z-ai/glm-5.2)featured | $1.20 | $4.10 | 1M tokens | OpenRouter |
| GLM 5.2 (glm-5.2) | Check Z.ai | Check Z.ai | 1M tokens | Z.ai direct |
| Claude Fable | $3.00 | $15.00 | 200K | API providers |
| GPT-4o | $2.50 | $10.00 | 1M | OpenAI |
OpenRouter lists z-ai/glm-5.2 at $1.20 input and $4.10 output per 1M tokens, with 1M tokens of context. Provider pricing can change, so verify live dashboards before committing budget.
Free vs paid GLM 5.2 access
Searches for free GLM 5.2 API often mix two different ideas: hosted API trials and open-weight local usage. Hosted API calls are normally paid after credits or trial limits, because providers must serve the model on real infrastructure. Open weights can reduce provider dependency for research, but you still pay through hardware, cloud GPU rental, engineering time, or lower throughput. Treat any free or unlimited API claim as temporary until the provider confirms it.
Cost by use case
Chat app
Useful for ordinary assistant turns where output is shorter than the prompt context.
Coding agent
Planning, patch generation, and test-fix loops can increase both input and output tokens.
Long-context repo review
The 1M context is valuable, but large repository prompts should be budgeted separately.
Where to access GLM 5.2 API
Pricing next step
If you are still choosing between providers, read the GLM 5.2 API guide for model IDs and endpoints, then use the Coding Plan guide to estimate whether planning-heavy workflows will increase token usage.