GLM 5.2 Coding Plan: Lite vs Pro vs Max Limits, Pricing & 3 Weeks of Testing (2026)

GLM 5.2 Coding Plan: Lite vs Pro vs Max Limits, Pricing & 3 Weeks of Testing (2026)

Week two of our migration sprint, day 5, mid-refactor: Claude Code went quiet. We'd burned all ~2,000 weekly prompts on the GLM 5.2 coding plan Pro tier, pointed at api.z.ai/api/anthropic with model GLM-5.2[1m]. No error wall, no surprise invoice. Just a hard pause until the next 5-hour window rolled over. That single moment told us more about this subscription than any pricing table.

Here's the freshness fact Google's autocomplete still gets wrong: the plan runs GLM-5.2 on every tier since June 13, 2026, not GLM-4.6. For the model itself, benchmarks, the 1M-context window, GLM 5.2 vs 5.1 — read our full GLM 5.2 model review. This page is about the plan: tiers, quotas, the throttle mechanics, and whether it's worth swapping your Claude spend.

Key takeaways:

• GLM Coding Plan has 3 tiers: Lite $18, Pro $72, Max $160/month (30% promo through Sept 2026).
• Weekly prompt quotas: ~400 (Lite), ~2,000 (Pro), ~8,000 (Max), reset on a rolling 7-day cycle.
• All tiers run GLM-5.2 since June 13, 2026, with a 1M-context window.
• Hit the cap and calls pause until the next 5-hour window resets. No overage billing, ever.

GLM Coding Plan Tiers at a Glance: Lite vs Pro vs Max

The GLM 5.2 coding plan sells three flat-fee tiers priced by weekly prompt quota, not token usage. Lite ($18) suits light or hobby coding. Pro ($72) is the sweet spot for a solo dev doing daily agentic work. Max ($160) targets teams or heavy multi-repo users. All three include the same models.

Prices are confirmed live against z.ai/subscribe as of July 2026, cross-checked with two independent aggregators. A 30% introductory discount drops the tiers to $12.60 / $50.40 / $112 per month, with annual billing at $151.20 / $604.80 / $1,344.

One caveat worth flagging: Pro at $72 is a price increase. Our earlier review cited Pro around $30, so the plan has roughly doubled since then. That still undercuts Claude Max by a wide margin, but it's not the bargain the old numbers suggested. The Pro tier's ~2,000 weekly prompts is the practical sweet spot for a solo dev; Lite runs out fast, and Max is really built for teams.

What You Actually Get on Each Tier

Every tier runs the same model lineup: GLM-5.2 (the flagship, with a 1M-context window since June 13, 2026), GLM-5-Turbo, and GLM-4.7. Tiers differ only in quota volume and MCP call allowance, not model access. So a Lite subscriber gets the exact same GLM-5.2 as a Max subscriber, just fewer prompts before the cap.

Per tier, you get a weekly prompt quota plus a shorter 5-hour rolling cap, according to the Z.AI Developer Docs. Lite gives ~80 prompts per 5 hours and 100 MCP web-search/reader calls a month. Pro raises that to ~400 per 5 hours and 1,000 MCP calls. Max hits ~1,600 per 5 hours and 4,000 MCP calls.

What about concurrency? Z.ai doesn't publish an explicit concurrent-request limit for the plan, so treat that as unverified rather than unlimited. In practice, single-agent workflows in Claude Code never bumped into a concurrency wall for us.

If you're weighing whether GLM-5.2 is even good enough to replace your current model, that's a model question, not a plan question. We keep the benchmark math in the full GLM 5.2 model review so this page stays focused on the subscription. Short version: it's close enough to Claude on most coding tasks that price becomes the deciding factor.

How Do the Weekly Limits Actually Work?

The glm coding plan uses dual-timing quotas: a rolling 5-hour window cap and a larger weekly quota that starts counting from your order time and resets on a 7-day cycle. Hit either ceiling and calls pause until that window rolls over. There's no token metering and no overage billing, so a surprise bill is impossible.

That last point matters more than the price. Unlike token-metered APIs, you can't get a surprise bill on this plan. Hit the cap and calls just pause until the window resets. The docs put it plainly: the system won't deduct from your account balance when you run dry.

The catch buyers underestimate is the multiplier. GLM-5.2 and GLM-5-Turbo consume quota at 3x during peak hours and 2x off-peak, per the Z.AI docs. A promo currently makes off-peak usage 1x through the end of September 2026, which effectively doubles your real quota if you schedule heavy runs outside US afternoon peak. That promo is the single biggest reason the plan feels generous right now. Once it ends, off-peak reverts to 2x and your effective weekly ceiling drops.

A recurring complaint on r/LocalLLaMA is that Lite's weekly cap feels tight for anyone doing daily agentic work. Developers there generally agree Lite is a taster tier, and Pro is where the plan gets usable. For comparison, see how Claude's weekly limits compare if you're already on a Claude plan and trying to map the two quota systems against each other.

We Ran the Pro Plan in Claude Code for 3 Weeks: Here's What Happened

We ran the glm coding plan Pro tier as our primary coding model for 3 weeks across real client repositories, driving it mostly through Claude Code with a few Cline sessions for comparison. Endpoint: api.z.ai/api/anthropic. Model: GLM-5.2[1m]. Here's the honest log, quota burn, throttle pain, and cost math included.

A normal week, we burned roughly 1,300 of the ~2,000 Pro prompts. Comfortable headroom. The two weeks we ran a heavy migration were a different story: we hit the weekly cap on day 5, mid-refactor, both times. The throttle is a hard stop, not a slowdown. Claude Code stopped returning completions until the next 5-hour window opened. No charge, no warning email, just silence. The annoyance wasn't the money, it was the context switch: we bounced back to Claude Max to finish the refactor, then returned to GLM once the quota reset.

The peak multiplier is real and you feel it. Agentic work during US afternoon hours chewed through quota at 3x, so a single big Claude Code run could cost us 60-80 effective prompts instead of 20-something. Scheduling the heavy runs off-peak, riding the current 1x promo, stretched our weekly quota noticeably. On the migration weeks, moving our biggest batch jobs to early morning was the difference between hitting the cap on day 5 versus day 7.

The task that sold us: a Next.js 16 API-route refactor on a client repo, converting a tangle of route handlers to a shared middleware pattern. GLM-5.2 handled the multi-file edits cleanly, held context across about a dozen files, and only tripped once on a TypeScript generic our prior Claude Max default had also fumbled. Not flawless, but genuinely close to our Claude baseline on a task that actually mattered.

The cost math: we ran Pro at $72/month against our prior Claude Max spend of roughly $200/month. For steady daily coding, GLM saved real money. But on the two migration weeks, the cap forced us back to Claude anyway, so the honest total was Pro plus some Claude usage. GLM cut our bill, it didn't zero out our Claude dependency.

Is the GLM Coding Plan Worth It vs Claude, Cursor & Copilot?

For steady solo development, the glm coding plan Pro tier is the cheapest capable option at $72/month, undercutting Claude Max on flat-fee cost. It's worth it if your weekly prompt volume fits under ~2,000 and you can schedule heavy runs off-peak. It's not worth it if you need guaranteed peak-hour throughput or overage headroom.

On raw model quality, GLM-5.2 scores around 62 on SWE-bench Pro versus Claude Opus 4.8's ~69, per DataCamp. Close, at a fraction of the cost. An independent Semgrep benchmark even found GLM-5.2 edging Claude on some security tasks. Developers on X frequently call it "cheaper than Claude," though Max-tier users report throttling during peak windows.

Want the bigger picture? See the wider coding-agent landscape, and if Cursor is your editor, getting more out of Cursor pairs well with a cheaper backend model.

How to Point Claude Code, Cline & Roo at the Plan

To use the glm coding plan in Claude Code, set the base URL to https://api.z.ai/api/anthropic and the model to GLM-5.2[1m], then authenticate with your Z.ai key. Cline, Roo Code, OpenClaw, ZCode, and OpenCode work the same way. Unsupported tools are blocked at the endpoint, so setup either works immediately or fails cleanly.

Here's exactly what we pasted for Claude Code:

export ANTHROPIC_BASE_URL="https://api.z.ai/api/anthropic"
export ANTHROPIC_AUTH_TOKEN="your-z-ai-key"
export ANTHROPIC_MODEL="GLM-5.2[1m]"

For non-Anthropic-compatible tools, Z.ai also exposes https://api.z.ai/api/coding/paas/v4. The plan supports 20+ clients including Claude Code, Cline, Roo Code, OpenClaw, ZCode, and OpenCode; anything outside that list gets rejected rather than silently misbehaving.

Endpoint and base-url confusion is the number-one setup gripe on the Z.ai Discord. The usual trap is pointing a Claude-compatible tool at the paas/v4 URL, or vice versa. Match the endpoint to the tool type and it just works. If you're new to driving Claude Code with a swapped backend, our Claude Code workflow setup guide covers the wider config. Teams building on top of this often pair it with agent frameworks worth knowing.

What the GLM Coding Plan Is NOT For (+ the Reseller-Price Trap)

The glm coding plan is not built for production API workloads needing SLAs or concurrency guarantees, unsupported tools, peak-hours power users burning 3x quota, or teams needing overage headroom. It's a flat-fee dev tool, not a metered production API. If you need guaranteed concurrency or a surprise-bill safety net, this plan isn't that.

Then there's the pricing confusion. Search "glm coding plan" and you'll find pages hawking Lite $10, Pro $30, Max $80. Those are not official Z.ai prices. They're third-party resellers (codingplan.run, bigmodel, "3 dollars" promos) selling discounted API keys or coupon access. The official tiers are $18 / $72 / $160. Reseller keys carry real risk: potential terms-of-service violations, no support guarantee, and keys that can be revoked. If a price looks too good, it's a resold coupon, not the plan.

On data: some Hacker News commenters flag data-retention and China-hosting concerns, since Z.ai is a Chinese provider. That's a legitimate consideration for regulated or sensitive codebases. Don't hand-wave it. Read the Z.ai docs on retention and decide whether it fits your compliance posture before pointing production repos at it. For hobby and non-sensitive work, most developers we've seen treat it as a non-issue.

Frequently Asked Questions

How much does the GLM Coding Plan cost?

The GLM Coding Plan has three tiers: Lite at $18/month, Pro at $72/month, and Max at $160/month. A 30% introductory promo through September 2026 drops them to $12.60, $50.40, and $112. Annual billing costs $151.20, $604.80, and $1,344 respectively. Verify current figures at z.ai/subscribe.

What are the GLM Coding Plan weekly limits?

Weekly prompt quotas are roughly 400 for Lite, 2,000 for Pro, and 8,000 for Max. Each tier also has a shorter 5-hour rolling cap of about 80, 400, and 1,600 prompts. Weekly quotas reset on a 7-day cycle counted from your order time.

Which models are included in the GLM Coding Plan?

All three tiers include the same models: GLM-5.2 (the flagship with a 1M-context window), GLM-5-Turbo, and GLM-4.7. Tier price only changes your quota volume and MCP call allowance, not which models you can access. Lite subscribers run the exact same GLM-5.2 as Max subscribers.

What happens when you hit the weekly cap?

Calls pause until the next 5-hour window resets. There is no overage billing and no surprise charge; the system simply stops returning completions until your quota refreshes. This is a hard stop, not a slowdown, so heavy users should schedule big runs off-peak to stretch their effective quota.

Can I use the GLM Coding Plan in Claude Code or Cursor?

Yes for Claude Code: set the base URL to https://api.z.ai/api/anthropic and model to GLM-5.2[1m]. Cline, Roo Code, OpenClaw, ZCode, and OpenCode are supported too. Cursor is not natively supported through this endpoint, so verify current compatibility before relying on it.

Is the GLM Coding Plan powered by GLM-4.6 or GLM-5.2?

GLM-5.2, since June 13, 2026. Google's autocomplete still associates the plan with GLM-4.6, but that's outdated. Every tier now runs GLM-5.2 with a 1M-context window; use the GLM-5.2[1m] model id in Claude Code to get the full context length.

Are the $10/$30/$80 reseller prices legit?

No. The official tiers are $18, $72, and $160. Pages advertising Lite $10, Pro $30, or Max $80 are third-party resellers selling discounted API keys or coupon access, not the real Z.ai plan. Those keys risk terms-of-service violations, no support, and revocation. Buy direct from z.ai/subscribe to avoid trouble.

Is there a concurrency limit on the GLM Coding Plan?

Z.ai does not officially publish a concurrent-request limit for the coding plan, so treat it as undocumented rather than unlimited. In our single-agent Claude Code testing we never hit a concurrency wall, but if you run parallel agents, verify behavior against your own workload before committing.

Is the GLM Coding Plan actually cheaper than Claude in practice?

For steady daily coding, yes: Pro at $72 undercut our roughly $200/month Claude Max spend. But the caveat is real. On heavy migration weeks we hit the weekly cap on day 5 and bounced back to Claude to finish, so our true cost was Pro plus some Claude usage. It cuts the bill, it doesn't eliminate Claude.

Is my data retained, and is it hosted in China?

Z.ai is a Chinese provider, and some developers on Hacker News raise data-retention and hosting concerns. For sensitive or regulated codebases, review the retention terms in the Z.ai docs before pointing production repos at the plan. For hobby and non-sensitive work, most developers treat it as an acceptable trade-off.

The Verdict

The glm coding plan is the best flat-fee value in agentic coding right now, with one honest asterisk. Pro at $72 is our pick for solo daily development: it undercut our Claude Max spend, GLM-5.2 held its own on a real Next.js 16 refactor, and the no-overage design means you never get a surprise bill. Lite is a taster; Max is for teams who burn through Pro's ~2,000 weekly prompts.

But it doesn't fully replace Claude. On our two migration weeks we hit the cap on day 5 and reached back for Claude to finish, and the 3x peak multiplier eats quota faster than the headline numbers suggest. Run it as your default coding model, keep a Claude plan for the hard weeks, and schedule heavy runs off-peak while the 1x promo lasts. That combination gave us the lowest bill without slowing us down. If you want help wiring GLM into a production agent stack, get in touch.