Sign in to use the playground
Run this model with your Chutes account, quota, and API access.
Model facts & API quick start
GLM-5.2 (zai-org/GLM-5.2-TEE) is served on Chutes inside a Trusted Execution Environment (TEE). Call it through the OpenAI-compatible API at https://llm.chutes.ai/v1 with a Chutes API key and "model": "zai-org/GLM-5.2-TEE".
GLM-5.2 at a glance
- Model ID
zai-org/GLM-5.2-TEE- Developer
- Z.AI
- Deployed by
- chutes
- Type
- LLM
- Input price
- $1.25 per 1M tokens
- Output price
- $3.95 per 1M tokens
- Cached input price
- $0.125 per 1M tokens
- Context length
- 1,048,576 tokens
- Modalities
- text in → text out
- Confidential compute (TEE)
- Yes, runs in a Trusted Execution Environment
- Precision
- NVFP4 (as served on Chutes, via NVIDIA ModelOpt; upstream weights BF16)
- Open weights
nvidia/GLM-5.2-NVFP4- Parameters
- 753B total (safetensors)
- Architecture
- Mixture-of-Experts transformer with sparse attention and IndexShare (indexer reused across every four sparse attention layers); 78 layers, 256 routed + 1 shared experts, 8 routed experts per token
- License
- MIT
- Released
- 2026-06
- Experts
- 256 routed + 1 shared, 8 routed active per token
- Layers / hidden size
- 78 / 6144
- Thinking effort
- Multiple effort levels to balance performance and latency
- Terminal Bench 2.1 (Terminus-2)
- 81.0 (model card)
- SWE-bench Pro
- 62.1 (model card)
- AIME 2026
- 99.2 (model card)
API quick start
- Base URL
https://llm.chutes.ai/v1- model
zai-org/GLM-5.2-TEE- Endpoint
POST /v1/chat/completions- Auth header
Authorization: Bearer $CHUTES_API_KEY
OpenAI-compatible: point any OpenAI SDK at the base URL above and pass your Chutes API key as the API key.
curl -X POST "https://llm.chutes.ai/v1/chat/completions" \
-H "Authorization: Bearer $CHUTES_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"model": "zai-org/GLM-5.2-TEE",
"messages": [
{
"role": "user",
"content": "Hello!"
}
],
"stream": true,
"max_tokens": 1024,
"temperature": 0.7
}'GLM-5.2 FAQ
What context window does GLM-5.2 support?
The config.json sets max_position_embeddings to 1,048,576 tokens: a true 1M-token window. Z.ai's long-context evaluations (FrontierSWE, SWE-Marathon, PostTrainBench) ran at the full 1M length. The chute's default max_tokens is 1,024, so raise it for long outputs.
How is GLM-5.2 different from GLM-5.1?
Three things: a 1M-token context (up from ~200K), stronger coding with selectable thinking effort levels, and an IndexShare architecture change that cuts per-token FLOPs 2.9x at 1M context. Benchmark deltas are large: Terminal Bench 81.0 vs 63.5, SWE-bench Pro 62.1 vs 58.4, HLE 40.5 vs 31.0.
What does NVFP4 mean for output quality?
This chute serves nvidia/GLM-5.2-NVFP4, a 4-bit quantization produced with NVIDIA's ModelOpt (TensorRT Model Optimizer). It substantially cuts memory and cost per token; outputs will not be bit-identical to the BF16 checkpoint, but the quantized release is published by NVIDIA specifically for production deployment.
What does the TEE suffix mean?
TEE stands for Trusted Execution Environment. Inference runs inside attested confidential-compute hardware, so your prompts and the model's outputs are processed within a hardware-isolated enclave rather than on an open host.
Can I use GLM-5.2 commercially?
Yes. GLM-5.2 is MIT-licensed, which the card highlights as pure open with no regional limits. The NVFP4 quantization is likewise governed by the MIT license and marked ready for commercial use.
Does it support function calling and tool use?
Yes. GLM-5.2 is built for agentic work, scoring 76.8 on MCP-Atlas (public set) and 48.2 on Tool-Decathlon. Send OpenAI-style tools in your chat completion request.
How do I call it from the OpenAI SDK?
Set base_url to https://llm.chutes.ai/v1 with your Chutes API key and model to zai-org/GLM-5.2-TEE. Chat completions, raw completions, and streaming work through the standard SDK methods.
What sampling settings should I use?
The upstream generation_config.json defaults to temperature 1.0 and top_p 0.95, which Z.ai also used for reasoning evaluations. Their coding-agent runs (SWE-Bench Pro, Terminal-Bench) used temperature 1.0 with top_p 1.0. The chute's own default temperature is 0.7.