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.0312 | $4.40 | $0.029 | 1.02s | 70 tps | ||
| $0.039 | $4.80 | $0.038 | 0.79s | 76 tps | ||
| $0.08 | $4.40 | $0.04 | 0.75s | 73 tps | ||
30% off | $0.20$0.14 | $6.00$4.20 | $0.15$0.105 | 0.84s | 51 tps | |
| $0.14 | $4.40 | $0.10 | 1.05s | 81 tps | ||
| $0.17 | $4.80 | $0.16 | 0.71s | 95 tps | ||
| $0.19 | $4.40 | $0.19 | 1.58s | 84 tps | ||
| $0.20 | $3.40 | $0.15 | 1.28s | 127 tps | ||
| $0.20 | $3.40 | $0.15 | 1.37s | 121 tps | ||
| $0.214 | $3.74 | $0.108 | 0.45s | 49 tps | ||
| $0.90$0.5625 | $4.00$2.50 | $0.20$0.125 | 1.16s | 76 tps | ||
| $0.60 | $3.39 | $0.20 | 0.82s | 91 tps | ||
50% off | $1.40$0.70 | $4.40$2.20 | $0.26$0.13 | 1.94s | 34 tps | |
40% off | $1.40$0.84 | $4.40$2.64 | $0.26$0.156 | 1.47s | 80 tps | |
| $0.8424 | $2.6477 | $0.1955 | 0.78s | 116 tps | ||
| $0.91 | $2.86 | $0.169 | 1.42s | 49 tps | ||
30% off | $1.40$0.98 | $4.40$3.08 | $0.26$0.182 | 3.67s | 42 tps | |
20% off | $1.40$1.12 | $4.40$3.52 | $0.26$0.208 | 1.69s | 69 tps | |
| $1.19 | $3.74 | $0.238 | 2.08s | 51 tps | ||
| $1.20 | $4.40 | $0.36 | 1.02s | 86 tps | ||
10% off | $1.40$1.26 | $4.40$3.96 | $0.26$0.234 | 0.31s | 89 tps | |
| $1.40 | $4.40 | $0.14 | 1.76s | 92 tps | ||
| $1.40 | $4.40 | $0.26 | 0.91s | 47 tps | ||
| $1.40 | $4.40 | $0.14 | 1.53s | 66 tps | ||
| $1.40 | $4.40 | $0.14 | 2.24s | 91 tps | ||
| $1.40 | $4.40 | -- | 0.53s | 202 tps | ||
| $1.40 | $4.40 | $0.26 | 0.70s | 117 tps | ||
| $1.40 | $4.40 | $0.26 | 1.70s | 128 tps | ||
20% off | $1.75$1.40 | $5.50$4.40 | $0.325$0.26 | 1.26s | 62 tps | |
| $1.40 | $4.40 | $0.26 | 0.26s | 107 tps | ||
| $1.40 | $4.40 | $0.26 | 0.87s | 116 tps | ||
| $1.40 | $4.40 | $0.26 | 0.20s | 74 tps | ||
| $1.40 | $4.40 | $0.14 | 1.60s | 50 tps | ||
| $1.40 | $4.40 | $0.26 | 1.02s | 46 tps | ||
| $1.40 | $4.40 | $0.26 | 1.30s | 47 tps | ||
| $1.40 | $4.40 | $0.26 | 3.77s | 39 tps | ||
| $2.10 | $6.60 | $0.39 | 0.94s | 129 tps | ||
| $2.10 | $6.60 | $0.21 | 0.74s | 148 tps | ||
| $2.10 | $6.60 | $0.21 | 0.75s | 160 tps | ||
| $2.80 | $8.80 | $0.56 | 0.83s | 91 tps | ||
| $1.40 | $4.40 | $0.26 | 2.91s | 36 tps | ||
Not used in Standard routing:Why these endpoints are not used | ||||||
| $1.54 | $4.84 | $0.154 | 1.27s | 126 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.
