GLM-5.3 is a large-scale reasoning model from Z.ai, built for complex software engineering and long-horizon agent tasks. It supports text input and output with a 1M-token context window, and improves on GLM-5.2 in coding and in the balance between performance and token efficiency.
Reasoning is always on and cannot be disabled. Reasoning efforts low, high, and max are supported; max is the default.
| $0.039 | $6.00 | $0.038 | 1.01s | 99 tps | ||
| $0.08 | $4.40 | $0.055 | 0.77s | 122 tps | ||
30% off | $0.20$0.14 | $6.00$4.20 | $0.15$0.105 | 1.31s | 42 tps | |
| $0.14 | $4.40 | $0.10 | 1.03s | 115 tps | ||
| $0.17 | $6.00 | $0.16 | 1.11s | 105 tps | ||
| $0.19 | $4.40 | $0.19 | 0.83s | 80 tps | ||
| $0.20 | $3.40 | $0.15 | 1.44s | 82 tps | ||
| $0.20 | $3.40 | $0.15 | 0.87s | 87 tps | ||
| $0.393 | $6.00 | $0.108 | 0.98s | 38 tps | ||
| $0.90$0.5625 | $4.00$2.50 | $0.20$0.125 | 1.29s | 89 tps | ||
| $0.60 | $2.20 | $0.20 | 0.96s | 110 tps | ||
50% off | $1.40$0.70 | $4.40$2.20 | $0.26$0.13 | 1.59s | 58 tps | |
40% off | $1.40$0.84 | $4.40$2.64 | $0.26$0.156 | 2.19s | 63 tps | |
| $0.8424 | $2.6477 | $0.1955 | 0.71s | 131 tps | ||
| $0.91 | $2.86 | $0.169 | 0.69s | 47 tps | ||
| $0.95 | $4.40 | $0.26 | 1.02s | 64 tps | ||
30% off | $1.40$0.98 | $4.40$3.08 | $0.26$0.182 | 2.50s | 55 tps | |
20% off | $1.40$1.12 | $4.40$3.52 | $0.26$0.208 | 3.26s | 50 tps | |
| $1.19 | $3.74 | $0.238 | 3.06s | 55 tps | ||
10% off | $1.40$1.26 | $4.40$3.96 | $0.26$0.234 | 0.29s | 142 tps | |
| $1.40 | $4.40 | $0.14 | 1.53s | 139 tps | ||
| $1.40 | $4.40 | $0.26 | 1.69s | 79 tps | ||
| $1.40 | $4.40 | $0.14 | 1.18s | 72 tps | ||
| $1.40 | $4.40 | $0.14 | 1.14s | 163 tps | ||
| $1.40 | $4.40 | -- | 0.45s | 497 tps | ||
| $1.40 | $4.40 | $0.26 | 0.61s | 167 tps | ||
| $1.40 | $4.40 | $0.26 | 0.77s | 168 tps | ||
20% off | $1.75$1.40 | $5.50$4.40 | $0.325$0.26 | 1.00s | 63 tps | |
| $1.40 | $4.40 | $0.26 | 0.36s | 163 tps | ||
| $1.40 | $4.40 | $0.26 | 0.50s | 81 tps | ||
| $1.40 | $4.40 | $0.26 | 0.33s | 136 tps | ||
| $1.40 | $4.40 | $0.14 | 1.12s | 69 tps | ||
| $1.40 | $4.40 | $0.26 | 1.40s | 55 tps | ||
| $1.40 | $4.40 | $0.26 | 2.77s | 31 tps | ||
| $1.40 | $4.40 | $0.26 | 0.92s | 53 tps | ||
| $1.40 | $4.40 | $0.26 | 2.58s | 57 tps | ||
| $2.10 | $6.60 | $0.39 | 1.03s | 142 tps | ||
| $2.10 | $6.60 | $0.21 | 0.68s | 154 tps | ||
| $2.10 | $6.60 | $0.21 | 1.03s | 157 tps | ||
| $2.80 | $8.80 | $0.56 | 0.86s | 73 tps | ||
Not used in Standard routing:Why these endpoints are not used | ||||||
| $1.54 | $4.84 | $0.154 | 0.94s | 212 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.
