GLM 5.2 is a large-scale reasoning model from Z.ai. It supports text input and output with a 1M-token context window, and is suited for long-horizon agent workflows, project-level software engineering, and complex multi-step automation.
Reasoning efforts high and xhigh are supported; xhigh maps to max reasoning. It is particularly strong at coding and tool use across long-running tasks, able to maintain engineering context and follow standards consistently through a full development workflow, from requirements to multi-platform deployment, in a single task.
| $0.03 | $10.00 | $0.03 | 0.50s | -- | ||
| $0.084 | $4.30 | $0.083 | 0.76s | 56 tps | ||
| $0.19 | $4.30 | $0.18 | 0.67s | 52 tps | ||
| $0.20 | $4.40 | $0.13 | 0.47s | 152 tps | ||
57% off | $0.65$0.2795 | $4.00$1.72 | $0.25$0.1075 | 0.74s | 70 tps | |
75% off | $2.25$0.5603 | $7.88$1.962 | $0.56$0.1394 | 0.99s | 71 tps | |
| $0.75$0.5625 | $2.40$1.80 | $0.14$0.105 | 1.38s | 71 tps | ||
54% off | $1.40$0.6426 | $4.40$2.02 | $0.26$0.1193 | 1.19s | 50 tps | |
54% off | $1.40$0.6496 | $4.40$2.042 | $0.26$0.1206 | 3.96s | 40 tps | |
| $0.70 | $2.20 | $0.105 | 0.69s | 84 tps | ||
| $0.76 | $2.42 | $0.14 | 0.88s | 57 tps | ||
33% off | $1.40$0.938 | $4.40$2.948 | $0.26$0.1742 | 1.44s | 56 tps | |
| $1.18 | $4.40 | $0.26 | 1.72s | 58 tps | ||
15% off | $1.40$1.19 | $4.40$3.74 | $0.26$0.221 | 1.20s | 70 tps | |
| $1.26 | $3.00 | $0.22 | 1.31s | 73 tps | ||
| $1.39 | $4.39 | $0.25 | 0.23s | 202 tps | ||
| $1.40 | $4.40 | $0.14 | 0.94s | 105 tps | ||
| $1.40 | $4.40 | $0.14 | 1.94s | 53 tps | ||
| $1.40 | $4.40 | $0.26 | 0.53s | 58 tps | ||
| $1.40 | $4.40 | $0.26 | 3.26s | 31 tps | ||
| $1.40 | $4.40 | $0.14 | 1.66s | 64 tps | ||
| $1.40 | $4.40 | $0.26 | 1.74s | 67 tps | ||
| $1.40 | $4.40 | $0.26 | 4.59s | 48 tps | ||
| $1.40 | $4.40 | $0.26 | 0.63s | 106 tps | ||
| $1.40 | $4.40 | $0.26 | 0.54s | 71 tps | ||
| $1.40 | $4.40 | $0.26 | 2.74s | 50 tps | ||
| $2.10 | $6.60 | $0.21 | 0.68s | 164 tps | ||
| $2.10 | $6.60 | $0.21 | 0.68s | 151 tps | ||
| $2.31 | $7.26 | $0.462 | 0.97s | 77 tps | ||
| $2.50 | $9.00 | $0.54 | 0.42s | 320 tps | ||
| $0.124 | $3.553 | $0.137 | 5.40s | 16 tps | ||
| $0.966 | $3.036 | $0.1932 | 1.09s | 58 tps | ||
| $1.40 | $4.40 | -- | 0.40s | 185 tps | ||
Not used in Standard routing:Why these endpoints are not used | ||||||
| $1.54 | $4.84 | $0.154 | -- | -- | ||
P50, best across providers
P50, best provider
When an error occurs in an upstream provider, we can recover by routing to another healthy provider, if your request filters allow it. You can access per-provider uptime data programmatically through the Endpoints API. Learn more about our load balancing and customization options.
