GLM 5.2
GLM 5.2 is Z.AI's flagship open-weight model for long-horizon coding and agentic engineering, released June 16, 2026. A 1.0M tokens context window carries project-level engineering state, and selectable reasoning effort tunes depth per request. Your use is subject to Z.AI's Terms & Privacy Policies.
View API reference- Input and output price
- Prices from: Input $0.70, Output $2.20, Per 1M tokens
- 24h uptime
- Loading AI Gateway uptime
import { streamText } from 'ai'
const result = streamText({ model: 'zai/glm-5.2', prompt: 'Why is the sky blue?'})Copy link to headingPlayground
Try out GLM 5.2 by Z.AI. Usage is billed to your team at API rates. Free users (those who haven't made a payment) get $5 of credits every 30 days.
GLM 5.2
Copy link to headingProviders
Route requests across multiple providers. Copy a provider slug to set your preference. Visit the docs for more info. Using a provider means you agree to their terms, listed under Legal.
| Provider |
|---|
Copy link to headingUptime24 hours
Direct request success rate on AI Gateway and per-provider. Visit the docs for more info.
Copy link to headingThroughput24 hours
P50 throughput on live AI Gateway traffic, in tokens per second (TPS). Visit the docs for more info.
Copy link to headingLatency24 hours
P50 time to first token (TTFT) on live AI Gateway traffic, in milliseconds. View the docs for more info.
Getting started
Call GLM 5.2 through AI Gateway with the AI SDK generateText and streamText functions, or through the OpenAI Chat Completions, OpenAI Responses, and Anthropic Messages APIs by changing the base URL. AI Gateway authenticates the request and routes it to an available provider.
Install the AI SDK (pnpm add ai dotenv), create an API key from the API Keys page, and set it as AI_GATEWAY_API_KEY in your environment. Full setup is covered in the text generation quickstart.
import { generateText } from 'ai';import 'dotenv/config';
async function main() { const result = await generateText({ model: 'zai/glm-5.2', prompt: 'Why is the sky blue?', });
console.log(result.text);}
main().catch(console.error);Top-level parameters
The same GLM 5.2 request in each API format AI Gateway supports.
import { generateText } from 'ai';import 'dotenv/config';
async function main() { const result = await generateText({ model: 'zai/glm-5.2', system: 'You are a concise technical assistant.', prompt: 'Summarize the tradeoffs between static generation and SSR.', maxOutputTokens: 1024, });
console.log(result.text);}
main().catch(console.error);Standard parameters like prompt, messages, temperature, and tools work as documented in the AI SDK docs. These are the parameters with model-specific behavior.
| Parameter | Type | Required | Description |
|---|---|---|---|
model | string | Yes | Model ID in the form creator/model, e.g. zai/glm-5.2. AI Gateway routes the request to an available provider. |
maxOutputTokens | number | No | Hard cap on generated tokens. GLM 5.2 supports up to 1,048,576 output tokens. Reasoning tokens count toward this limit. |
reasoning | 'provider-default' | 'none' | 'minimal' | 'low' | 'medium' | 'high' | 'xhigh' | No | Provider-agnostic reasoning effort, available in AI SDK 7 or later. Maps to the provider’s native reasoning configuration; reasoning settings under providerOptions take precedence when both are set. See the Reasoning section below. |
providerOptions | Record<string, JSONValue> | No | AI Gateway routing options under gateway, plus any provider-native options under the provider’s own namespace — see the table below. |
Input limits
| Input | Formats | Sources | Max count | Max size | Limits |
|---|---|---|---|---|---|
| Text | — | — | — | — | Prompt and response share the 1M-token context window |
Provider options
Set AI Gateway routing options under providerOptions.gateway. For provider-specific options, pass them under the provider’s namespace as documented by the AI SDK.
Learn more in the AI SDK provider docs.
import { generateText } from 'ai';import 'dotenv/config';
async function main() { const result = await generateText({ model: 'zai/glm-5.2', prompt: 'Why is the sky blue?', providerOptions: { gateway: { only: ['zai', 'baseten'], }, }, });
console.log(result.text);}
main().catch(console.error);These AI Gateway routing options apply to every model. Provider-specific options pass through under the provider’s own namespace (for example providerOptions.anthropic) exactly as documented by the AI SDK.
| Parameter | Type | Required | Description |
|---|---|---|---|
providerOptions.gateway.only | string[] | No | Restrict routing to these provider slugs. Requests fail over only within the listed providers. |
providerOptions.gateway.order | string[] | No | Preferred provider order. Listed providers are tried first; unlisted providers remain available as fallbacks. |
providerOptions.gateway.sort | 'cost' | 'ttft' | 'tps' | No | Rank candidate providers by price, time to first token, or tokens per second instead of the default routing order. |
providerOptions.gateway.zeroDataRetention | boolean | No | Route only to providers with a zero-data-retention policy for this model. |
Routing across providers
AI Gateway serves the same model through multiple providers and fails over automatically. order expresses a preference while keeping every provider eligible; only is a hard allowlist — if none of the listed providers are available the request fails instead of falling back.
Options under a provider's own namespace (for example providerOptions.anthropic) are forwarded to that provider with the request. Providers ignore option namespaces that don't apply to them, so it is safe to set provider options alongside gateway routing options.
Reasoning
AI Gateway bridges reasoning across every API format. The AI SDK exposes a provider-agnostic top-level reasoning level (none, minimal, low, medium, high, or xhigh); the Chat Completions and Responses formats take the same effort under reasoning.effort; and the Anthropic Messages format uses a native thinking token budget. Whichever you send, the gateway maps it to the target model’s native configuration, converting between effort levels and token budgets as needed. Reasoning-related settings under providerOptions take full precedence over the top-level reasoning value and are never merged. Reasoning tokens typically count toward your output-token usage, though how they’re reported and billed varies by provider.
Learn more in the AI Gateway reasoning guide.
import { generateText } from 'ai';import 'dotenv/config';
async function main() { const result = await generateText({ model: 'zai/glm-5.2', prompt: 'Explain the Monty Hall problem step by step.', reasoning: 'high', });
console.log(result.text);}
main().catch(console.error);Tool calling
Expose tools the model can call. Define each tool’s inputs with a Zod schema.
import { generateText, tool } from 'ai';import { z } from 'zod';import 'dotenv/config';
async function main() { const result = await generateText({ model: 'zai/glm-5.2', prompt: 'What is the weather in San Francisco?', tools: { getWeather: tool({ description: 'Get the current weather for a location', inputSchema: z.object({ location: z.string() }), execute: async ({ location }) => ({ location, temperatureC: 18 }), }), }, });
console.log(result.text);}
main().catch(console.error);Copy link to headingAbout GLM 5.2
GLM 5.2 was released June 16, 2026 as Z.AI's flagship model for long-horizon tasks, with weights published under the MIT License. GLM 5.2 succeeds GLM-5.1 and extends the context window to 1.0M tokens, up from 200K on GLM-5.1, so a single task can hold an entire project's code, history, and instructions.
The architecture is Mixture-of-Experts, activating roughly 40B parameters per token. An IndexShare sparse-attention design reuses the same indexer across every four sparse attention layers, cutting per-token compute by roughly 2.9 times at full context length. You control depth per request: toggle thinking on or off, and set a reasoning effort level up to max to trade latency and token budget for stronger results on hard problems.
The focus is agentic software engineering: codebase takeover, long-horizon refactoring, end-to-end feature work, and research reproduction. GLM 5.2 scores 81.0 on Terminal-Bench 2.1 and 62.1 on SWE-bench Pro in Z.AI's published evaluations, ahead of GLM-5.1 on both. Treat the numbers as vendor-reported until independent results accumulate.
Through AI Gateway, you call GLM 5.2 with a single API key using the AI SDK, the Chat Completions API, the Responses API, the Messages API, or other API formats. Built-in observability, provider routing, and failover come standard, and GLM 5.2 supports tool calling, structured output, streaming, and implicit caching.
Copy link to headingWhat To Consider When Choosing a Provider
- Configuration: Reasoning effort is the main dial. Higher effort improves results on hard, multi-step problems but consumes more tokens and time. Start at a moderate setting, then raise it only for tasks that need deep deliberation.
- Configuration: A 1.0M tokens window invites large prompts, and large prompts cost tokens on every request. Structure long-running agents to reuse stable context so implicit caching keeps repeat reads cheap, and watch spend in AI Gateway's observability tools.
- Configuration: Published benchmark numbers come from Z.AI's own evaluations. Run GLM 5.2 on your own tasks before standardizing on it, and keep code review in the loop for anything headed to production. If per-step latency dominates your workload,
glm-5.2-fastserves the same weights on faster infrastructure. - Zero Data Retention: Zero Data Retention is available for this model. It is offered on a per-provider and model basis. See the documentation for details.
- Authentication: AI Gateway authenticates requests using an API key or OIDC token. You do not need to manage provider credentials directly.
Copy link to headingWhen to Use GLM 5.2
Best for
- Long-Horizon Coding Agents: Multi-step engineering tasks that require planning, editing, testing, and iterating without losing the thread
- Project-Scale Refactors: Whole-repository context held in a single window instead of chunked retrieval
- Codebase Takeover: Onboarding onto an unfamiliar project by loading its code and history at once
- Adjustable Reasoning Depth: One model covering both quick edits and deep deliberation via effort settings
- Agentic Tool Use: Reliable function calling and structured output across long tool-call chains
Consider alternatives when
- Latency-Sensitive Loops:
glm-5.2-fastserves the same weights on faster infrastructure for interactive agents - High-Volume Lightweight Tasks: GLM-5-Turbo handles extraction and classification at lower per-token cost
- Vision or GUI Input: GLM-5V-Turbo adds screenshot and image understanding to the GLM-5 generation
- Simple Short Prompts: GLM-4.7-Flash keeps costs down when project-scale context is unnecessary
Copy link to headingConclusion
GLM 5.2 makes long-horizon, project-scale engineering practical with open weights, a 1.0M tokens context window, and tunable reasoning effort. Route GLM 5.2 through AI Gateway to get unified access, observability, and provider failover, and pair it with glm-5.2-fast when response speed outweighs per-token cost.
Copy link to headingFrequently Asked Questions
What's new in GLM 5.2 compared to GLM-5.1?
GLM 5.2 extends the context window to 1.0M tokens, up from 200K on GLM-5.1, and posts higher scores on coding benchmarks like Terminal-Bench 2.1 and SWE-bench Pro. GLM 5.2 also carries project-level engineering context across a single task and runs long-running tasks more reliably.
What is the context window for GLM 5.2?
1.0M tokens.
Is GLM 5.2 open source?
The weights are published under the MIT License. Through AI Gateway you call hosted providers with the
zai/glm-5.2identifier, so you get the model without managing weights or GPUs yourself.Does GLM 5.2 support reasoning controls?
Yes. You can enable or disable thinking per request and set a reasoning effort level up to
max. Lower effort answers faster; higher effort spends more tokens on hard problems.How does GLM 5.2 differ from GLM 5.2 Fast?
glm-5.2-fastserves the same underlying weights on inference infrastructure tuned for higher throughput, at different per-token rates. Compare live throughput, latency, and pricing on each model's page and pick per workload.What is the pricing for GLM 5.2?
Check the pricing panel on this page for today's numbers. AI Gateway tracks rates across every provider that serves GLM 5.2.
Does GLM 5.2 support Zero Data Retention?
Yes, Zero Data Retention is available for this model. Zero Data Retention is offered on a per-provider basis. See https://vercel.com/docs/ai-gateway/capabilities/zdr for details.
How do I access GLM 5.2 through AI Gateway?
Use the
zai/glm-5.2model identifier with your AI Gateway API key via the AI SDK, the Chat Completions API, the Responses API, the Messages API, or other API formats. No separate Z.AI account is needed. BYOK is also supported.