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 | $16.00 | $0.03 | 1.00s | 99 tps | ||
| $0.04 | $6.00 | $0.035 | 0.76s | 134 tps | ||
| $0.08 | $6.00 | $0.075 | 0.73s | 141 tps | ||
| $0.12 | $4.40 | $0.04 | 0.47s | 107 tps | ||
| $0.131 | $3.179 | $0.166 | 0.85s | 60 tps | ||
| $0.20 | $3.40 | $0.15 | 1.42s | 67 tps | ||
| $0.20 | $3.40 | $0.15 | 1.06s | 85 tps | ||
| $0.24 | $3.93 | $0.19 | 0.44s | 194 tps | ||
| $0.55 | $3.39 | $0.165 | 0.31s | 66 tps | ||
| $0.90$0.5625 | $4.00$2.50 | $0.20$0.125 | 2.11s | 52 tps | ||
50% off | $1.40$0.70 | $4.40$2.20 | $0.26$0.13 | 4.30s | 59 tps | |
40% off | $1.40$0.84 | $4.40$2.64 | $0.26$0.156 | 3.02s | 62 tps | |
35% off | $1.33$0.8645 | $6.60$4.29 | $0.196$0.1274 | 1.21s | 75 tps | |
| $0.91 | $2.86 | $0.169 | 2.16s | 41 tps | ||
30% off | $1.40$0.98 | $4.40$3.08 | $0.26$0.182 | 3.19s | 29 tps | |
10% off | $1.17$1.053 | $3.96$3.564 | $0.26$0.234 | 1.59s | 127 tps | |
| $1.19 | $3.74 | $0.238 | 1.04s | 73 tps | ||
15% off | $1.40$1.19 | $4.40$3.74 | $0.23$0.1955 | 0.51s | 190 tps | |
10% off | $1.40$1.26 | $4.40$3.96 | $0.26$0.234 | 0.76s | 114 tps | |
| $1.40 | $4.40 | $0.14 | 1.09s | 171 tps | ||
| $1.40 | $4.40 | $0.26 | 0.82s | 89 tps | ||
| $1.40 | $4.40 | $0.14 | 1.81s | 89 tps | ||
| $1.40 | $4.40 | $0.14 | 1.10s | 182 tps | ||
| $1.40 | $4.40 | -- | 0.86s | 209 tps | ||
| $1.40 | $4.40 | $0.26 | 0.97s | 158 tps | ||
| $1.40 | $4.40 | $0.26 | 0.84s | 159 tps | ||
20% off | $1.75$1.40 | $5.50$4.40 | $0.325$0.26 | 1.30s | 65 tps | |
| $1.40 | $4.40 | $0.26 | 0.67s | 150 tps | ||
| $1.40 | $4.40 | $0.26 | 0.79s | 122 tps | ||
| $1.40 | $4.40 | $0.26 | 0.66s | 204 tps | ||
| $1.40 | $4.40 | $0.14 | 1.96s | 87 tps | ||
| $1.40 | $4.40 | $0.26 | 1.15s | 52 tps | ||
| $1.40 | $4.40 | $0.26 | 2.22s | 42 tps | ||
| $1.40 | $4.40 | $0.26 | 1.38s | 57 tps | ||
| $1.40 | $4.40 | $0.26 | 2.87s | 46 tps | ||
| $2.10 | $6.60 | $0.39 | 2.04s | 67 tps | ||
| $2.10 | $6.60 | $0.21 | 1.14s | 132 tps | ||
| $2.10 | $6.60 | $0.21 | 0.85s | 173 tps | ||
| $2.80 | $8.80 | $0.56 | 0.99s | 88 tps | ||
| $0.17 | $3.00 | $0.169 | 1.55s | 75 tps | ||
70% off | $1.40$0.42 | $4.40$1.32 | $0.26$0.078 | 3.16s | 33 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.
