GLM-5.3
GLM-5.3
GLM-5.3 is a large-scale reasoning model built for complex software engineering and long-horizon agent tasks. It supports text input and output with a 1,048,576-token context window.
GLM-5.3 is available in beta. Access is granted per API key — contact us to request access.
At a glance
Key capabilities
Reason across large repositories, implementation plans, and multi-step coding tasks.
Use tool calling and extended context for workflows that require many dependent steps.
Process up to 1,048,576 tokens across the prompt and generated output.
Receive reasoning and final-answer deltas as server-sent events.
Quickstart
API reference
Call POST /v2/chat/completions or
POST /v2/responses with model: "glm5.3". Request
fields (n, logprobs, parallel_tool_calls, stream, and the rest) are defined in
those API references — not duplicated on this model page.
Reasoning
GLM-5.3 has three reasoning modes — low, high, and max — but which values you can
pass depends on the API:
Read the reasoning trace from choices[].message.reasoning_content on chat, or from the
reasoning item’s summary[0].text in output on Responses (its content field is
null there). Reasoning tokens are billed as output tokens either way, and count
against max_tokens on chat (defaults to 2048 when omitted) or max_output_tokens on
Responses (no default — omitting it means unbounded generation).
Response fields (chat)
Full response shape: Chat Completion V2.
Known limitations
- Output token budget.
max_tokenson chat defaults to2048when omitted;max_output_tokenson Responses has no default and allows unbounded generation. Reasoning counts against whichever budget applies, so a smallmax_tokenson chat can leave little or no room for the actual answer. - Parallel tool calls. GLM-5.3 only respects
parallel_tool_calls: true(or omitting the field). Passingfalseis accepted without error, but the model can still return more than one tool call in a turn. - Context-length checks are approximate, and more conservative for Latin-script text than for Indic scripts. Treat the model’s own limit as authoritative.
Parameter errors (n, logprobs, stop, and similar) are documented on
Chat Completion V2.