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 | 2.17s | 41 tps | ||
| $0.07 | $7.00 | $0.065 | 0.79s | 91 tps | ||
| $0.10 | $7.00 | $0.095 | 0.84s | 95 tps | ||
| $0.131 | $3.179 | $0.147 | 0.86s | 36 tps | ||
| $0.16 | $4.40 | $0.053 | 0.77s | 108 tps | ||
| $0.17 | $3.00 | $0.169 | 1.26s | 38 tps | ||
| $0.19 | $4.40 | $0.19 | 0.88s | 108 tps | ||
| $0.20 | $3.40 | $0.15 | 1.03s | 120 tps | ||
| $0.20 | $3.40 | $0.15 | 1.41s | 73 tps | ||
70% off | $1.40$0.42 | $4.40$1.32 | $0.26$0.078 | 12.87s | 23 tps | |
| $0.60 | $3.39 | $0.20 | 0.86s | 62 tps | ||
50% off | $1.40$0.70 | $4.40$2.20 | $0.26$0.13 | 1.09s | 74 tps | |
40% off | $1.40$0.84 | $4.40$2.64 | $0.26$0.156 | 1.57s | 60 tps | |
| $0.91 | $2.86 | $0.169 | 0.94s | 50 tps | ||
30% off | $1.40$0.98 | $4.40$3.08 | $0.26$0.182 | 1.68s | 69 tps | |
| $1.19 | $3.74 | $0.238 | 0.99s | 69 tps | ||
15% off | $1.40$1.19 | $4.40$3.74 | $0.23$0.1955 | 0.63s | 156 tps | |
10% off | $1.40$1.26 | $4.40$3.96 | $0.26$0.234 | 0.60s | 133 tps | |
| $1.40 | $4.40 | $0.14 | 1.68s | 116 tps | ||
| $1.40 | $4.40 | $0.26 | 0.84s | 86 tps | ||
| $1.40 | $4.40 | $0.14 | 3.75s | 60 tps | ||
| $1.40 | $4.40 | $0.14 | 2.04s | 118 tps | ||
| $1.40 | $4.40 | -- | 0.65s | 125 tps | ||
| $1.40 | $4.40 | $0.26 | 0.59s | 167 tps | ||
| $1.40 | $4.40 | $0.26 | 1.49s | 106 tps | ||
20% off | $1.75$1.40 | $5.50$4.40 | $0.325$0.26 | 1.18s | 63 tps | |
| $1.40 | $4.40 | $0.26 | 0.25s | 164 tps | ||
| $1.40 | $4.40 | $0.26 | 0.71s | 106 tps | ||
| $1.40 | $4.40 | $0.26 | 0.36s | 143 tps | ||
| $1.40 | $4.40 | $0.14 | 3.24s | 64 tps | ||
| $1.40 | $4.40 | $0.26 | 1.12s | 50 tps | ||
| $1.40 | $4.40 | $0.26 | 1.80s | 40 tps | ||
| $1.40 | $4.40 | $0.26 | 1.27s | 70 tps | ||
| $1.40 | $4.40 | $0.26 | 2.75s | 47 tps | ||
| $2.10 | $6.60 | $0.39 | 0.81s | 119 tps | ||
| $2.10 | $6.60 | $0.21 | 0.76s | 145 tps | ||
| $2.10 | $6.60 | $0.21 | 1.01s | 153 tps | ||
| $2.80 | $8.80 | $0.56 | 0.74s | 69 tps | ||
| $0.18 | $4.40 | $0.19 | 0.49s | 124 tps | ||
| $0.90$0.5625 | $4.00$2.50 | $0.20$0.125 | 1.06s | 70 tps | ||
Not used in Standard routing:Why these endpoints are not used | ||||||
| $1.54 | $4.84 | $0.154 | 1.80s | 117 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.
