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.05 | $5.00 | $0.04 | 0.62s | 114 tps | ||
| $0.136 | $4.40 | $0.0898 | 0.88s | 105 tps | ||
| $0.17 | $3.00 | $0.169 | 1.22s | 54 tps | ||
| $0.19 | $3.179 | $0.166 | 0.95s | 61 tps | ||
| $0.20 | $3.40 | $0.15 | 1.28s | 126 tps | ||
| $0.20 | $3.40 | $0.15 | 0.84s | 113 tps | ||
| $0.22 | $3.39 | $0.20 | 0.88s | 134 tps | ||
| $0.22 | $3.39 | $0.20 | 0.71s | 132 tps | ||
| $0.24 | $3.93 | $0.19 | 0.59s | 151 tps | ||
70% off | $1.40$0.42 | $4.40$1.32 | $0.26$0.078 | 2.96s | 39 tps | |
| $0.90$0.5625 | $4.00$2.50 | $0.20$0.125 | 1.13s | 80 tps | ||
| $0.60 | $3.39 | $0.175 | 0.31s | 61 tps | ||
50% off | $1.40$0.70 | $4.40$2.20 | $0.26$0.13 | 2.45s | 70 tps | |
40% off | $1.40$0.84 | $4.40$2.64 | $0.26$0.156 | 0.84s | 111 tps | |
35% off | $1.33$0.8645 | $4.40$2.86 | $0.196$0.1274 | 1.39s | 165 tps | |
| $0.91 | $2.86 | $0.169 | 0.83s | 48 tps | ||
30% off | $1.40$0.98 | $4.40$3.08 | $0.26$0.182 | 3.08s | 50 tps | |
10% off | $1.17$1.053 | $3.96$3.564 | $0.26$0.234 | 1.42s | 128 tps | |
| $1.19 | $3.74 | $0.238 | 1.19s | 71 tps | ||
15% off | $1.40$1.19 | $4.40$3.74 | $0.23$0.1955 | 0.70s | 153 tps | |
10% off | $1.40$1.26 | $4.40$3.96 | $0.26$0.234 | 0.31s | 101 tps | |
| $1.40 | $4.40 | $0.14 | 1.03s | 164 tps | ||
| $1.40 | $4.40 | $0.26 | 1.35s | 69 tps | ||
| $1.40 | $4.40 | $0.14 | 1.95s | 83 tps | ||
| $1.40 | $4.40 | $0.14 | 1.52s | 126 tps | ||
| $1.40 | $4.40 | -- | 0.73s | 210 tps | ||
| $1.40 | $4.40 | $0.26 | 1.08s | 129 tps | ||
| $1.40 | $4.40 | $0.26 | 1.03s | 144 tps | ||
20% off | $1.75$1.40 | $5.50$4.40 | $0.325$0.26 | 1.36s | 81 tps | |
| $1.40 | $4.40 | $0.26 | 0.26s | 183 tps | ||
| $1.40 | $4.40 | $0.26 | 0.65s | 106 tps | ||
| $1.40 | $4.40 | $0.26 | 0.68s | 127 tps | ||
| $1.40 | $4.40 | $0.14 | 1.90s | 82 tps | ||
| $1.40 | $4.40 | $0.26 | 0.87s | 55 tps | ||
| $1.40 | $4.40 | $0.26 | 8.66s | 33 tps | ||
| $1.40 | $4.40 | $0.26 | 1.38s | 47 tps | ||
| $1.40 | $4.40 | $0.26 | 2.55s | 57 tps | ||
| $2.10 | $6.60 | $0.21 | 1.50s | 139 tps | ||
| $2.10 | $6.60 | $0.21 | 0.68s | 197 tps | ||
| $2.80 | $8.80 | $0.56 | -- | -- | ||
Not used in Standard routing:Why these endpoints are not used | ||||||
| $1.54 | $4.84 | $0.154 | 1.29s | 130 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.
