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.0224 | $16.00 | $0.0224 | 0.98s | 105 tps | ||
| $0.028 | $7.00 | $0.025 | 0.68s | 97 tps | ||
| $0.03 | $8.00 | $0.027 | 0.53s | 141 tps | ||
| $0.17 | $3.179 | $0.166 | 0.68s | 45 tps | ||
41% off | $0.65$0.3835 | $4.00$2.36 | $0.25$0.1475 | 0.80s | 75 tps | |
| $0.75$0.5625 | $2.40$1.80 | $0.14$0.105 | 2.22s | 53 tps | ||
54% off | $1.40$0.6426 | $4.40$2.02 | $0.26$0.1193 | 1.31s | 53 tps | |
54% off | $1.40$0.6496 | $4.40$2.042 | $0.26$0.1206 | 2.07s | 51 tps | |
| $0.70 | $2.20 | $0.105 | 0.93s | 91 tps | ||
50% off | $1.40$0.70 | $4.40$2.20 | $0.26$0.13 | 1.05s | 74 tps | |
| $0.76 | $2.42 | $0.14 | 0.47s | 122 tps | ||
33% off | $1.40$0.938 | $4.40$2.948 | $0.26$0.1742 | 2.45s | 59 tps | |
| $0.966 | $3.036 | $0.1932 | 1.67s | 59 tps | ||
| $1.18 | $4.40 | $0.26 | 1.60s | 56 tps | ||
| $1.25 | $4.39 | $0.20 | 0.61s | 76 tps | ||
| $1.26 | $3.00 | $0.22 | 1.94s | 69 tps | ||
| $1.40 | $4.40 | $0.14 | 0.70s | 120 tps | ||
| $1.40 | $4.40 | $0.14 | 1.80s | 74 tps | ||
| $1.40 | $4.40 | $0.26 | 0.45s | 69 tps | ||
| $1.40 | $4.40 | $0.26 | 1.02s | 87 tps | ||
| $1.40 | $4.40 | $0.14 | 1.79s | 84 tps | ||
| $1.40 | $4.40 | $0.26 | 1.98s | 61 tps | ||
| $1.40 | $4.40 | $0.26 | 4.09s | 40 tps | ||
| $1.40 | $4.40 | $0.26 | 2.15s | 119 tps | ||
| $1.40 | $4.40 | $0.26 | 0.35s | 105 tps | ||
| $1.40 | $4.40 | $0.26 | 3.45s | 59 tps | ||
| $2.10 | $6.60 | $0.21 | 0.71s | 159 tps | ||
| $2.10 | $6.60 | $0.21 | 0.71s | 154 tps | ||
| $2.25 | $7.88 | $0.56 | 1.03s | 55 tps | ||
| $2.25 | $8.00 | $0.48 | 0.43s | 314 tps | ||
| $2.31 | $7.26 | $0.462 | 1.43s | 73 tps | ||
Not used in Standard routing:Why these endpoints are not used | ||||||
| $1.54 | $4.84 | $0.154 | 0.76s | 114 tps | ||
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.
