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.12 | $4.00 | $0.08 | 0.94s | 65 tps | ||
| $0.131 | $2.992 | $0.147 | 0.78s | 76 tps | ||
89% off | $1.40$0.1554 | $4.40$0.4884 | $0.26$0.02886 | 1.31s | 68 tps | |
| $0.17 | $3.00 | $0.169 | 2.95s | 21 tps | ||
| $0.20 | $3.40 | $0.15 | 2.15s | 45 tps | ||
| $0.20 | $3.40 | $0.15 | 1.67s | 61 tps | ||
| $0.22 | $2.99 | $0.176 | 0.62s | 125 tps | ||
| $0.22 | $2.99 | $0.14 | 0.80s | 72 tps | ||
| $0.2219 | $3.39 | $0.1775 | 0.57s | 122 tps | ||
| $0.24 | $3.93 | $0.19 | 0.69s | 124 tps | ||
70% off | $1.40$0.42 | $4.40$1.32 | $0.26$0.078 | 3.02s | 37 tps | |
| $0.90$0.5625 | $4.00$2.50 | $0.20$0.125 | 1.64s | 42 tps | ||
| $0.60 | $3.39 | $0.1836 | 0.89s | 85 tps | ||
50% off | $1.40$0.70 | $4.40$2.20 | $0.26$0.13 | 1.06s | 100 tps | |
40% off | $1.40$0.84 | $4.40$2.64 | $0.26$0.156 | 1.00s | 101 tps | |
| $0.91 | $2.86 | $0.169 | 0.52s | 46 tps | ||
30% off | $1.40$0.98 | $4.40$3.08 | $0.26$0.182 | 1.41s | 66 tps | |
10% off | $1.17$1.053 | $3.96$3.564 | $0.26$0.234 | 0.98s | 104 tps | |
| $1.19 | $3.74 | $0.238 | 0.87s | 87 tps | ||
15% off | $1.40$1.19 | $4.40$3.74 | $0.23$0.1955 | 0.46s | 131 tps | |
10% off | $1.40$1.26 | $4.40$3.96 | $0.26$0.234 | 3.81s | 72 tps | |
| $1.40 | $4.40 | $0.14 | 1.37s | 117 tps | ||
| $1.40 | $4.40 | $0.14 | 2.20s | 74 tps | ||
| $1.40 | $4.40 | $0.14 | 1.22s | 133 tps | ||
| $1.40 | $4.40 | -- | 1.02s | 124 tps | ||
| $1.40 | $4.40 | $0.26 | 0.99s | 120 tps | ||
| $1.40 | $4.40 | $0.26 | 1.02s | 126 tps | ||
20% off | $1.75$1.40 | $5.50$4.40 | $0.325$0.26 | 2.20s | 43 tps | |
| $1.40 | $4.40 | $0.26 | 0.26s | 114 tps | ||
| $1.40 | $4.40 | $0.26 | 0.62s | 120 tps | ||
| $1.40 | $4.40 | $0.26 | 0.42s | 128 tps | ||
| $1.40 | $4.40 | $0.14 | 2.26s | 78 tps | ||
| $1.40 | $4.40 | $0.26 | 1.65s | 47 tps | ||
| $1.40 | $4.40 | $0.26 | 3.11s | 35 tps | ||
| $1.40 | $4.40 | $0.26 | 2.70s | 46 tps | ||
| $2.10 | $6.60 | $0.21 | 0.91s | 147 tps | ||
| $2.10 | $6.60 | $0.21 | 0.90s | 148 tps | ||
| $2.80 | $8.80 | $0.56 | 0.90s | 94 tps | ||
| $1.40 | $4.40 | $0.26 | 1.59s | 44 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.
