z-ai/glm-5.3
Model weightsGLM-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.055 | $5.00 | $0.06 | 1.10s | 31 tps | ||
| $0.079 | $4.80 | $0.059 | 0.75s | 100 tps | ||
| $0.08 | $4.40 | $0.055 | 0.73s | 89 tps | ||
| $0.14 | $4.40 | $0.10 | 0.90s | 115 tps | ||
| $0.17 | $4.80 | $0.16 | 0.75s | 96 tps | ||
| $0.19 | $4.40 | $0.19 | 1.41s | 87 tps | ||
86% off | $1.40$0.1988 | $4.40$0.6248 | $0.26$0.03692 | 0.80s | 47 tps | |
| $0.20 | $3.40 | $0.15 | 2.18s | 72 tps | ||
| $0.20 | $3.40 | $0.15 | 1.97s | 73 tps | ||
| $0.49 | $2.90 | $0.19 | 1.60s | 52 tps | ||
| $0.90$0.5625 | $4.00$2.50 | $0.20$0.125 | 1.69s | 58 tps | ||
| $0.60 | $0.6248 | $0.20 | 0.73s | 92 tps | ||
50% off | $1.40$0.70 | $4.40$2.20 | $0.26$0.13 | 2.78s | 47 tps | |
40% off | $1.40$0.84 | $4.40$2.64 | $0.26$0.156 | 1.75s | 70 tps | |
| $0.91 | $2.86 | $0.169 | 1.29s | 43 tps | ||
30% off | $1.40$0.98 | $4.40$3.08 | $0.26$0.182 | 2.07s | 57 tps | |
| $1.02 | $3.22 | $0.23 | 0.86s | 90 tps | ||
20% off | $1.40$1.12 | $4.40$3.52 | $0.26$0.208 | 2.91s | 61 tps | |
| $1.19 | $3.74 | $0.238 | 1.37s | 76 tps | ||
10% off | $1.40$1.26 | $4.40$3.96 | $0.26$0.234 | 0.50s | 107 tps | |
| $1.40 | $4.40 | $0.14 | 1.56s | 108 tps | ||
| $1.40 | $4.40 | $0.14 | 2.85s | 49 tps | ||
| $1.40 | $4.40 | $0.14 | 1.12s | 103 tps | ||
| $1.40 | $4.40 | $0.26 | 0.60s | 110 tps | ||
| $1.40 | $4.40 | $0.26 | 1.37s | 102 tps | ||
20% off | $1.75$1.40 | $5.50$4.40 | $0.325$0.26 | 0.94s | 64 tps | |
| $1.40 | $4.40 | $0.26 | 0.32s | 175 tps | ||
| $1.40 | $4.40 | $0.26 | 0.99s | 84 tps | ||
| $1.40 | $4.40 | $0.26 | 0.42s | 106 tps | ||
| $1.40 | $4.40 | $0.14 | 2.92s | 48 tps | ||
| $1.40 | $4.40 | $0.26 | 0.82s | 50 tps | ||
| $1.40 | $4.40 | $0.26 | 1.33s | 38 tps | ||
| $1.40 | $4.40 | $0.26 | 1.31s | 45 tps | ||
| $1.40 | $4.40 | $0.26 | 2.33s | 59 tps | ||
| $2.10 | $6.60 | $0.39 | 2.35s | 107 tps | ||
| $2.10 | $6.60 | $0.21 | 0.90s | 150 tps | ||
| $2.10 | $6.60 | $0.21 | 0.77s | 159 tps | ||
| $2.80 | $8.80 | $0.56 | 1.66s | 77 tps | ||
30% off | $0.20$0.14 | $6.00$4.20 | $0.15$0.105 | 11.12s | 6 tps | |
| $0.60 | $2.50 | $0.10 | 26.71s | 31 tps | ||
| $2.10 | $6.60 | $0.40 | 1.99s | 33 tps | ||
Not used in Standard routing:Why these endpoints are not used | ||||||
| $1.54 | $4.84 | $0.154 | 0.72s | 146 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.
