GLM 5.2 Pricing: glm52.site Plans, Credits, and API Top-Ups
Compare glm52.site GLM 5.2 pricing, including Starter, Pro, Business, Team, monthly credits, prepaid top-ups, and API-ready usage.
GLM 5.2 pricing on glm52.site is based on credits. One credit balance supports playground testing today and API-ready workflows as you move toward hosted GLM 5.2 integrations.
For checkout and the latest live plan state, use the official site pricing page:
Monthly plans
The current glm52.site monthly plans are:
| Plan | Price | Monthly credits | Best fit |
|---|---|---|---|
| Starter | $9.90/month | 9,900 credits | Individual GLM 5.2 evaluation and light recurring use |
| Pro | $29/month | 30,000 credits | Serious coding, research, and agent tasks |
| Business | $79/month | 85,000 credits | Power users and small teams before Team |
| Team | $149/month | 160,000 credits | High-volume teams and API-heavy evaluation workflows |
Monthly credits roll for up to 60 days. Plans are designed for recurring GLM 5.2 testing, coding evaluations, long-context runs, and agent workflow checks.
Prepaid credit top-ups
You can also add prepaid credits when a benchmark pass, API prototype, or larger coding session needs more capacity.
| Top-up | Price | Credits | Use case |
|---|---|---|---|
| 5K Top-up | $5 | 5,000 credits | Small refill for quick tests |
| 10K Top-up | $10 | 10,000 credits | Extra prepaid credits for short usage spikes |
| 26K Top-up | $25 | 26,000 credits | API testing and larger playground sessions |
| 53K Top-up | $50 | 53,000 credits | Heavier API bursts without changing plans |
| 108K Top-up | $100 | 108,000 credits | Largest prepaid balance for teams and API-heavy weeks |
Top-ups are useful when your normal plan is enough most of the time, but you occasionally need extra room for larger prompts, longer outputs, or repeated evaluation runs.
Playground and API credit usage
The site credit model is designed around real usage rather than a flat guess. Playground and API-style requests can vary a lot because a short prompt is not the same as a long repository analysis.
Current usage settings in the site configuration include:
- minimum charge: 10 credits
- input pricing basis: 3,600 credits per 1M input tokens
- output pricing basis: 12,300 credits per 1M output tokens
This means long context, large outputs, and repeated agent loops consume more credits than simple short prompts. For API planning, measure the real prompts you expect to run instead of estimating from one small demo.
Which plan should you choose?
Choose Starter if you are validating GLM 5.2 with occasional prompts and light evaluation.
Choose Pro if you are doing regular coding, research, and agent workflow tests. It is the default plan for most individual developers who expect consistent usage.
Choose Business if you run heavier long-context evaluations, larger prompt batches, or frequent benchmark passes.
Choose Team if your workflow is API-heavy, shared across a team, or likely to involve repeated large requests.
If you are specifically preparing for API usage, read GLM 5.2 API Key and start from the API access page.
Related GLM 5.2 pages
Use GLM 5.2 Free to understand no-cost evaluation paths, GLM 5.2 Model to review model fit, and GLM 5.2 API Key when you are ready to create keys.
Evaluation path
Continue from this article into a practical GLM 5.2 evaluation flow: playground testing, API planning, context design, benchmark prompts, and performance evidence.
More Posts
GLM 5.2 vs Claude Opus 4.8: Which AI Assistant Is Better?
A practical comparison of GLM 5.2 and Claude Opus 4.8 for coding, long-context work, front-end output, and overall product value.
GLM 5.2 vs GPT 5.5: Which AI Model Is Better for Coding
A practical comparison of GLM 5.2 and GPT 5.5 for coding, long-context tasks, front-end output, and cost control.
GLM 5.2 Benchmark Prompts: A Realistic Test Set for Coding Teams
Five practical benchmark prompts for evaluating GLM 5.2 on coding, long context, UI generation, migration planning, and review quality.