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 | 0.99s | 98 tps | ||
| $0.08 | $4.40 | $0.055 | 0.70s | 140 tps | ||
30% off | $0.20$0.14 | $6.00$4.20 | $0.15$0.105 | 1.19s | 47 tps | |
| $0.14 | $4.40 | $0.10 | 0.76s | 116 tps | ||
| $0.17 | $6.00 | $0.16 | 1.00s | 103 tps | ||
| $0.19 | $4.40 | $0.19 | 0.98s | 74 tps | ||
| $0.20 | $3.40 | $0.15 | 1.42s | 96 tps | ||
| $0.20 | $3.40 | $0.15 | 0.63s | 133 tps | ||
| $0.393 | $6.00 | $0.108 | 0.94s | 42 tps | ||
| $0.90$0.5625 | $4.00$2.50 | $0.20$0.125 | 1.26s | 74 tps | ||
| $0.60 | $2.20 | $0.20 | 0.65s | 161 tps | ||
50% off | $1.40$0.70 | $4.40$2.20 | $0.26$0.13 | 1.12s | 63 tps | |
40% off | $1.40$0.84 | $4.40$2.64 | $0.26$0.156 | 2.04s | 61 tps | |
| $0.8424 | $2.6477 | $0.1955 | 0.75s | 119 tps | ||
| $0.91 | $2.86 | $0.169 | 0.51s | 53 tps | ||
| $0.95 | $4.40 | $0.26 | 0.90s | 89 tps | ||
30% off | $1.40$0.98 | $4.40$3.08 | $0.26$0.182 | 1.84s | 56 tps | |
20% off | $1.40$1.12 | $4.40$3.52 | $0.26$0.208 | 3.21s | 49 tps | |
| $1.19 | $3.74 | $0.238 | 1.23s | 75 tps | ||
10% off | $1.40$1.26 | $4.40$3.96 | $0.26$0.234 | 0.48s | 124 tps | |
| $1.40 | $4.40 | $0.14 | 1.42s | 131 tps | ||
| $1.40 | $4.40 | $0.26 | 0.98s | 73 tps | ||
| $1.40 | $4.40 | $0.14 | 1.26s | 68 tps | ||
| $1.40 | $4.40 | $0.14 | 1.10s | 167 tps | ||
| $1.40 | $4.40 | -- | 0.46s | 161 tps | ||
| $1.40 | $4.40 | $0.26 | 0.56s | 165 tps | ||
| $1.40 | $4.40 | $0.26 | 0.93s | 151 tps | ||
20% off | $1.75$1.40 | $5.50$4.40 | $0.325$0.26 | 0.85s | 62 tps | |
| $1.40 | $4.40 | $0.26 | 0.28s | 162 tps | ||
| $1.40 | $4.40 | $0.26 | 0.52s | 81 tps | ||
| $1.40 | $4.40 | $0.26 | 0.40s | 128 tps | ||
| $1.40 | $4.40 | $0.14 | 1.34s | 63 tps | ||
| $1.40 | $4.40 | $0.26 | 0.73s | 56 tps | ||
| $1.40 | $4.40 | $0.26 | 2.64s | 27 tps | ||
| $1.40 | $4.40 | $0.26 | 0.91s | 57 tps | ||
| $1.40 | $4.40 | $0.26 | 2.53s | 51 tps | ||
| $2.10 | $6.60 | $0.39 | 1.49s | 141 tps | ||
| $2.10 | $6.60 | $0.21 | 0.79s | 166 tps | ||
| $2.10 | $6.60 | $0.21 | 0.68s | 186 tps | ||
| $2.80 | $8.80 | $0.56 | 0.83s | 70 tps | ||
Not used in Standard routing:Why these endpoints are not used | ||||||
| $1.54 | $4.84 | $0.154 | 1.04s | 208 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.
