GLM-5.2
GLM-5.2 is a large language model from Zhipu in the GLM-5 family, offering a 1,000,000-token context window and multiple provider-hosted variants including a "fast" endpoint.
API Pricing
Cheapest on Deep Infra — 45% below avg| Provider | Input / 1M | Output / 1M | Cached / 1M |
|---|---|---|---|
| $0.750 | $2.40 | $0.140 | |
| $0.966 | $3.04 | $0.193 | |
| $1.20 | $4.10 | - | |
| $1.40 | $4.40 | - | |
| $1.40 | $4.40 | - | |
| $1.40 | $4.40 | - | |
| $1.40 | $4.40 | $0.260 | |
| $1.50 | $4.50 | $0.380 | |
| $1.55 | $4.88 | $0.776 | |
| $2.03 | $6.21 | - |
Prices updated daily. Last check: Aug 22, 2026
GLM-5.2 pricing by provider
Input, output, and batch rates, plus alternatives, for one provider at a time.
Performance & Benchmarks
Source: Artificial Analysis →Reasoning & Knowledge
- GPQA Diamond89.5%
- Humanity's Last Exam41.1%
Coding
- SciCode50.5%
Agentic & Tool Use
- Terminal-Bench Hard50.8%
- Terminal-Bench v2.177.9%
- τ²-bench99.1%
- τ-bench Banking34.6%
Instruction & Long Context
- IFBench73.3%
- Long-Context Reasoning76.7%
Benchmarks measured Aug 2026. Scores are independent evaluations, not vendor-reported.
Model Details
General
- Creator
- Zhipu
- Family
- GLM-5
- Context Window
- 1.0M
- Modalities
- Text
Capabilities
- Tool Calling
- No
- Open Source
- No
- Aliases
- glm-5.2, GLM-5.2, zai-org/GLM-5.2, THUDM/GLM-5.2, glm-5-2-fast, glm-5.2-fast, GLM-5.2-Fast
Strengths & Limitations
Strengths
- 1,000,000-token context window, enough for repository-scale code or large document collections in a single request
- Measured output throughput of about 137 tokens per second (Artificial Analysis), suitable for interactive streaming use
- Time to first token around 892 ms, keeping perceived latency low for chat-style interfaces
- Offered in both a standard and a separately routed "fast" variant (glm-5.2-fast), letting teams trade characteristics per workload
- Served under multiple provider aliases (zai-org/GLM-5.2, THUDM/GLM-5.2), so pricing and capacity can be compared across endpoints
- Part of Zhipu's ongoing GLM-5 family, giving a consistent naming and migration path from earlier GLM releases
Limitations
- We do not track verified reasoning, coding, or multilingual benchmark scores for GLM-5.2, so quality claims cannot be compared numerically here
- Modality support beyond text is not something we have confirmed for this model
- Effective quality across the full 1M-token window is unverified — long-context accuracy typically degrades well before the stated limit
- Throughput and latency figures reflect one measured endpoint; other providers serving the same alias may perform differently
- The distinction between GLM-5.2 and GLM-5.2-Fast is provider-defined and not documented in our metadata
Key Features
About GLM-5.2
Common Use Cases
GLM-5.2 is best matched to workloads where input length is the binding constraint: analyzing or refactoring large codebases in one pass, question answering over long contracts, filings, or documentation sets, summarizing extended meeting or support transcripts, and long-running agent sessions where tool outputs and prior turns accumulate into very large prompts. Its measured throughput near 137 tokens per second and sub-second time to first token also make it usable for streaming chat and developer-assistant interfaces rather than batch-only pipelines. Teams weighing it against other long-context models should benchmark retrieval accuracy at their actual prompt sizes, and should test both the standard and "fast" variants, since serving configuration rather than model identity often determines which endpoint fits a latency budget.
Frequently Asked Questions
How much does GLM-5.2 cost?
Pricing for GLM-5.2 varies by provider and by pricing type — input tokens, output tokens, and any cached or long-context surcharges are often billed differently, and the standard and "fast" variants may be priced separately. Check the pricing table on this page for current per-provider rates.
What is GLM-5.2 best used for?
It suits long-context work: codebase-wide analysis, document and transcript question answering, and multi-step agent loops that accumulate large prompts. The 1,000,000-token context window removes much of the need for chunking, while its measured throughput of about 137 tokens per second keeps it viable for interactive assistants as well.
What is the difference between GLM-5.2 and GLM-5.2-Fast?
The "fast" alias (glm-5.2-fast / GLM-5.2-Fast) is a separately routed serving variant of the same model offered by providers, typically aimed at lower latency or higher throughput. The exact configuration differences are provider-defined, so the practical approach is to test both endpoints on your own prompts and compare the listed rates in the pricing table.
Can GLM-5.2 really use the full 1 million token context effectively?
The 1,000,000-token figure is the maximum input the model accepts. As with all long-context models, retrieval accuracy and reasoning quality can degrade before that ceiling, and we do not track verified long-context recall benchmarks for GLM-5.2. Validate performance at the prompt sizes you actually plan to send.
Who makes GLM-5.2?
GLM-5.2 is developed by Zhipu as part of the GLM-5 family. It appears under several identifiers across providers, including glm-5.2, zai-org/GLM-5.2, and THUDM/GLM-5.2.