GLM-5.3 API pricing
Zhipu's current flagship. Available at listed at platform rate (no published official USD price).
| Route | Input / 1M | Output / 1M |
|---|---|---|
| Platform rate | $0.7 | $2.2 |
USD, standard tier. Rate read from the live rate config on 2026-11-01. Zhipu publishes no USD list price for this model, so nothing here is cross-checked against one — this is a gateway rate, not a discount.
Specifications
| Vendor | Zhipu |
| Context window | — |
| Max output | — |
| Category | China |
What GLM-5.3 costs at your volume
| Usage level | Input / output per month | Monthly cost |
|---|---|---|
| Light (prototyping), a few thousand calls | 5M / 1M | $5.70 |
| Working, one developer, daily use | 50M / 10M | $57.00 |
| Heavy — team or agent loops in production | 500M / 100M | $570.00 |
Calculated at $0.7 input / $2.2 output per 1M tokens, 3.1× apart on this model, assuming a 5:1 input-to-output ratio. That ratio is the single largest source of error in this table: resend-heavy workloads drift well past it, and at 3.1× the correction is not linear. The cost calculator takes the actual figures.
When GLM-5.3 is the right call
At $0.7 in and $2.2 out per million tokens, GLM-5.3 lands where most production deployments actually live — cheap enough to leave running, expensive enough that you still look at the bill. The 3.1× output multiple is conventional, so standard cost intuition holds: output dominates, context matters, neither is pathological.
It is not the answer at either end. Bulk classification finds identical results several times cheaper, and the hardest reasoning problems reward moving up rather than staying here. Everything in between is this model's ground.
Where GLM-5.3 sits in the index
GLM-5.3 is 136 of 226 on input rate and 125 of 226 on output rate. A gap of 11 places, because on this model the output rate is 3.1× the input rate, flatter than the index median of 4.0× An output-heavy workload therefore leaves it almost where it started, which is why the cheapest model per input token is routinely not the cheapest per task. Percentile is the share of the 226 models in this index that cost more than GLM-5.3.
| Ranked by | Position | Percentile | Rate |
|---|---|---|---|
| Input rate | 136 of 226 | 40% | $0.70 |
| Output rate | 125 of 226 | 45% | $2.2 |
| Agent mix 1:3, blended | 127 of 226 | 44% | $1.825 |
On an agent mix the lowest blended rate in the same index is Gemma2 9B It at $0.01 per 1M tokens, about 182.5× less than this model at the same ratio. Across the whole index, sorting by input price alone moves a model by as much as 74 places; on GLM-5.3 specifically the shift is 11 — which is what the re-ranked index exists to show.
GLM-5.3 is 136 of 226 across every model in the index; the comparison that usually settles a choice is Zhipu's own lineup further down.
GLM-5.3 among the 10 China-family models
GLM-5.3 is the 7th cheapest of the 10 China-family models in this index at $0.7 per 1M input tokens. The range inside that group runs from MiniMax M3.1 Flash at $0.075 to Kimi K3 at $1.5 (a spread of 20×, and this one sits at 9).3× the group's cheapest tier.
| Model | In / 1M | Out / 1M | vs this |
|---|---|---|---|
| MiniMax M3.1 Flash | $0.075 | $0.3 | 0.11× |
| MiniMax M3 | $0.15 | $0.6 | 0.21× |
| DeepSeek V4.1 Flash | $0.15 | $0.6 | 0.21× |
| DeepSeek V4 Flash | $0.22 | $0.66 | 0.31× |
| DeepSeek R1 | $0.2899 | $1.1596 | 0.41× |
| DeepSeek V4 Pro | $0.66 | $1.98 | 0.94× |
| GLM-5.3 | $0.7 | $2.2 | — |
| Qwen3.8 Max | $1 | $3 | 1.43× |
| Kimi K3.1 Pro | $1 | $5 | 1.43× |
| Kimi K3 | $1.5 | $7.5 | 2.14× |
On input rate alone, stepping up to Qwen3.8 Max costs 1.4× the input rate and dropping to DeepSeek V4 Pro cuts it by 6%. Both measured at 2026-11-01, the same check as every other rate on this page.
Similarly priced alternatives
| Similarly priced | Vendor | In / out per 1M | vs this |
|---|---|---|---|
| Claude Haiku 4.5 | Anthropic | $0.5 / $2.5 | +$0.10 |
| GPT-6.1 Terra | OpenAI | $0.5 / $2.5 | +$0.10 |
| DeepSeek V4 Pro | DeepSeek | $0.66 / $1.98 | −$0.26 |
Blended comparison (input + output per 1M). Price is one axis These are the three closest to GLM-5.3 in blended rate, not interchangeable substitutes for it.
Calling GLM-5.3
The identifier you send is glm-5.3. Copy it exactly, because a mismatch
returns a model error rather than a connection error, which sends most people to debug the wrong
thing. Everything else is a base URL argument (GLM-5).3's own SDKs work unchanged.
from openai import OpenAI
client = OpenAI(base_url="https://aicomp.ai/v1", api_key="sk-...")
resp = client.chat.completions.create(
model="glm-5.3",
messages=[
{"role": "system", "content": "Answer in one short paragraph."},
{"role": "user", "content": "Explain what changed in this release."},
],
max_tokens=300,
)
# prompt_tokens / completion_tokens 是真实账单的唯一依据 —— 记下来,别猜
print(resp.usage.prompt_tokens, resp.usage.completion_tokens)
Log the usage object on every call, not just while you are optimising. On GLM-5.3 output costs 3.1× what input costs, so the same monthly token count bills very differently depending on how much of it comes back as output — measure your own split before extrapolating from the headline input rate, because rates move with vendor promotions.
Setting it up
Pointing an existing integration at GLM-5.3 is a base URL change, not a rewrite. Pick your tool:
- Claude Code — set the base URL via environment variables
- Cursor — override the API endpoint in settings
- OpenAI / Anthropic SDK — one
base_urlargument - Python, sync, streaming and async examples
- Cutting the bill — eight levers ranked by effect
What different usage shapes cost on GLM-5.3
A monthly token budget does not convert cleanly into a monthly invoice, and GLM-5.3 is an ordinary case rather than an extreme one: output is priced at 3.1× input, below the median of 4.0× across the 226 models in our index. Everything follows from that one number At 5:1 it is manageable, at 1:1 the same token count costs half as much. Below are five shapes real GLM-5.3 deployments fall into, each costing it out at the split it actually produces.
| Workload | Tokens | Output share | Monthly cost | vs cheapest in index |
|---|---|---|---|---|
| Classification / tagging 100k short jobs, 300 in / 20 out | 32M | 6% | $25.4 | 22.1× |
| Support triage 20k conversations, 1.5k in / 400 out | 38M | 21% | $38.6 | 16.4× |
| RAG question answering 50k questions, 6k in / 500 out | 325M | 8% | $265.00 | 21.2× |
| Agent loop (coding) 8k sessions, 400k in / 6k out | 3248M | 1% | $2345.6 | 26.2× |
| Long-form generation 5k documents, 2k in / 4k out | 30M | 67% | $51.00 | 12.0× |
The cheapest comparison is GPT-5 nano at $0.025 / $0.2 per 1M — 12.9× cheaper than GLM-5.3 on a blended rate. Treat it as a rate floor, not a recommendation: it says nothing about whether GPT-5 nano can do the work you need GLM-5.3 for.
Read the table as a sanity check rather than a forecast. If your own output share sits anywhere near 3%, everything above is priced almost entirely at GLM-5.3's $0.7 input rate; at 40% the $2.2 output rate has taken the larger half. Nobody's split is exactly the one you assumed when you picked the model, which is why the calculator asks for it before quoting anything.
FAQ
How much does GLM-5.3 cost per million tokens?
$0.7 per million input tokens and $2.2 per million output tokens. No official USD list price is published for this model, so it is billed at platform rate.
Is GLM-5.3 cheaper than buying direct?
There is no published official USD price to compare against for this model, it is billed at platform rate, and the reason to route it through a gateway is access and consolidated billing rather than a discount.
What does GLM-5.3 cost per month in practice?
At a 5:1 input-to-output ratio it is about $5.70 a month for light use (5M input tokens) and roughly $570.00 for heavy use (500M input). Agent workloads sit at the high end here because every turn resends the context and GLM-5.3 bills output at 3.1x input — see what actually drives Claude Code cost.
Which models cost about the same as GLM-5.3?
The comparison table further up this page lists the three closest to GLM-5.3's $2.9 blended rate. If you are choosing on cost alone, test the top two on your own prompts — $0.7 per input token is only half the equation, the other half is how many tokens a model needs before it finishes the task.
How do I start using GLM-5.3?
You need an API key, then point your client at the gateway base URL with glm-5.3 as the model id. On GLM-5.3 it is a one-line change in most SDKs — see the SDK setup guide, or the Claude Code and Cursor guides for those tools. The GLM-5.3 snippet is in the calling section above.
What is the GLM-5.3 API price per 1M tokens?
$0.7 per 1M input and $2.2 per 1M output. The two directions are quoted separately because a request is billed twice (once for what you send, once for what comes back) and on GLM-5.3 they differ by 3.1x.
How much more does GLM-5.3 charge for output than input?
Output tokens cost 3.1x what input tokens do here — $0.7 per 1M in against $2.2 per 1M out. The median output-to-input multiple across our full price index is 4.0x, so this model sits below that line. It matters more than it looks: on GLM-5.3 a coding agent's output takes 39% of the bill, so the input rate people usually compare is the smaller half. See why output pricing dominates.
How much does GLM-5.3 cost for a coding agent?
About $570.00 a month at 500M input and 100M output tokens, the shape a coding assistant really produces, because every turn resends the whole context and the model writes more than it reads. The biggest lever is not the model but how much context you resend each turn At 570 dollars a month on GLM-5.3, halving the resend roughly halves that. See what actually drives agent cost.
Does GLM-5.3 have an official list price?
No, Zhipu does not publish a USD list price for this model, so there is nothing to compare against and it bills at platform rate: $0.7 in / $2.2 out per 1M. The reason to route it through a gateway is access and one consolidated bill across vendors, not a discount.