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 | 1.02s | 81 tps | ||
| $0.06 | $7.00 | $0.055 | 0.80s | 116 tps | ||
| $0.12 | $4.40 | $0.04 | 0.92s | 68 tps | ||
| $0.12 | $7.00 | $0.11 | 0.88s | 106 tps | ||
| $0.131 | $3.179 | $0.147 | 0.66s | 34 tps | ||
| $0.17 | $3.00 | $0.169 | 1.83s | 29 tps | ||
| $0.18 | $4.40 | $0.19 | 0.38s | 171 tps | ||
| $0.19 | $4.40 | $0.19 | 1.00s | 122 tps | ||
| $0.20 | $3.40 | $0.15 | 0.94s | 111 tps | ||
| $0.20 | $3.40 | $0.15 | 1.01s | 106 tps | ||
70% off | $1.40$0.42 | $4.40$1.32 | $0.26$0.078 | 6.79s | 15 tps | |
| $0.90$0.5625 | $4.00$2.50 | $0.20$0.125 | 1.31s | 59 tps | ||
| $0.60 | $3.39 | $0.20 | 0.40s | 52 tps | ||
50% off | $1.40$0.70 | $4.40$2.20 | $0.26$0.13 | 1.13s | 71 tps | |
40% off | $1.40$0.84 | $4.40$2.64 | $0.26$0.156 | 2.18s | 78 tps | |
| $0.91 | $2.86 | $0.169 | 0.41s | 31 tps | ||
30% off | $1.40$0.98 | $4.40$3.08 | $0.26$0.182 | 3.41s | 54 tps | |
| $1.19 | $3.74 | $0.238 | 1.03s | 74 tps | ||
15% off | $1.40$1.19 | $4.40$3.74 | $0.23$0.1955 | 0.95s | 135 tps | |
10% off | $1.40$1.26 | $4.40$3.96 | $0.26$0.234 | 0.54s | 137 tps | |
| $1.40 | $4.40 | $0.14 | 1.13s | 158 tps | ||
| $1.40 | $4.40 | $0.26 | 0.80s | 89 tps | ||
| $1.40 | $4.40 | $0.14 | 8.67s | 40 tps | ||
| $1.40 | $4.40 | $0.14 | 1.45s | 135 tps | ||
| $1.40 | $4.40 | -- | 1.33s | 61 tps | ||
| $1.40 | $4.40 | $0.26 | 0.49s | 168 tps | ||
| $1.40 | $4.40 | $0.26 | 2.90s | 81 tps | ||
20% off | $1.75$1.40 | $5.50$4.40 | $0.325$0.26 | 4.00s | 32 tps | |
| $1.40 | $4.40 | $0.26 | 0.79s | 92 tps | ||
| $1.40 | $4.40 | $0.26 | 0.81s | 110 tps | ||
| $1.40 | $4.40 | $0.14 | 8.19s | 49 tps | ||
| $1.40 | $4.40 | $0.26 | 1.34s | 53 tps | ||
| $1.40 | $4.40 | $0.26 | 4.01s | 44 tps | ||
| $1.40 | $4.40 | $0.26 | 1.31s | 70 tps | ||
| $1.40 | $4.40 | $0.26 | 2.91s | 44 tps | ||
| $2.10 | $6.60 | $0.39 | 1.25s | 100 tps | ||
| $2.10 | $6.60 | $0.21 | 0.75s | 155 tps | ||
| $2.10 | $6.60 | $0.21 | 0.88s | 144 tps | ||
| $2.80 | $8.80 | $0.56 | 0.63s | 64 tps | ||
| $1.40 | $4.40 | $0.26 | 0.42s | 110 tps | ||
Not used in Standard routing:Why these endpoints are not used | ||||||
| $1.54 | $4.84 | $0.154 | 0.43s | 162 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.
