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.03 | $12.00 | $0.03 | 0.82s | 122 tps | ||
| $0.07 | $8.00 | $0.065 | 0.51s | 88 tps | ||
| $0.10 | $8.00 | $0.095 | 0.57s | 87 tps | ||
| $0.12 | $4.40 | $0.04 | 0.44s | 93 tps | ||
| $0.131 | $3.179 | $0.166 | 1.06s | 41 tps | ||
| $0.20 | $3.40 | $0.15 | 1.84s | 53 tps | ||
| $0.20 | $3.40 | $0.15 | 1.88s | 60 tps | ||
| $0.24 | $3.93 | $0.19 | 0.48s | 108 tps | ||
| $0.55 | $3.39 | $0.165 | 0.62s | 50 tps | ||
| $0.90$0.5625 | $4.00$2.50 | $0.20$0.125 | 14.75s | 14 tps | ||
50% off | $1.40$0.70 | $4.40$2.20 | $0.26$0.13 | 3.25s | 50 tps | |
35% off | $1.33$0.8645 | $6.60$4.29 | $0.196$0.1274 | 1.24s | 63 tps | |
| $0.91 | $2.86 | $0.169 | 1.04s | 49 tps | ||
30% off | $1.40$0.98 | $4.40$3.08 | $0.26$0.182 | 1.84s | 40 tps | |
10% off | $1.17$1.053 | $3.96$3.564 | $0.26$0.234 | 1.06s | 117 tps | |
| $1.19 | $3.74 | $0.238 | 1.09s | 73 tps | ||
15% off | $1.40$1.19 | $4.40$3.74 | $0.23$0.1955 | 0.68s | 139 tps | |
10% off | $1.40$1.26 | $4.40$3.96 | $0.26$0.234 | 0.31s | 145 tps | |
| $1.40 | $4.40 | $0.14 | 1.17s | 163 tps | ||
| $1.40 | $4.40 | $0.26 | 0.67s | 104 tps | ||
| $1.40 | $4.40 | $0.14 | 2.14s | 85 tps | ||
| $1.40 | $4.40 | $0.14 | 1.20s | 159 tps | ||
| $1.40 | $4.40 | -- | 3.02s | 220 tps | ||
| $1.40 | $4.40 | $0.26 | 0.92s | 84 tps | ||
| $1.40 | $4.40 | $0.26 | 1.22s | 163 tps | ||
| $1.40 | $4.40 | $0.26 | 0.86s | 100 tps | ||
| $1.40 | $4.40 | $0.26 | 0.56s | 143 tps | ||
| $1.40 | $4.40 | $0.14 | 2.35s | 73 tps | ||
| $1.40 | $4.40 | $0.26 | 1.13s | 53 tps | ||
| $1.40 | $4.40 | $0.26 | 1.93s | 35 tps | ||
| $1.40 | $4.40 | $0.26 | 1.36s | 52 tps | ||
| $1.40 | $4.40 | $0.26 | 2.66s | 54 tps | ||
| $2.10 | $6.60 | $0.39 | 1.22s | 185 tps | ||
| $2.10 | $6.60 | $0.21 | 0.88s | 165 tps | ||
| $2.10 | $6.60 | $0.21 | 0.75s | 182 tps | ||
| $2.80 | $8.80 | $0.56 | 1.03s | 69 tps | ||
| $0.17 | $3.00 | $0.169 | 1.14s | 52 tps | ||
70% off | $1.40$0.42 | $4.40$1.32 | $0.26$0.078 | 3.36s | 34 tps | |
40% off | $1.40$0.84 | $4.40$2.64 | $0.26$0.156 | 3.42s | 49 tps | |
20% off | $1.75$1.40 | $5.50$4.40 | $0.325$0.26 | 1.34s | 57 tps | |
| $1.40 | $4.40 | $0.26 | 0.46s | 128 tps | ||
Not used in Standard routing:Why these endpoints are not used | ||||||
| $1.54 | $4.84 | $0.154 | 1.13s | 99 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.
