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.063 | $4.40 | $0.0586 | 1.06s | 63 tps | ||
| $0.079 | $4.80 | $0.059 | 0.84s | 95 tps | ||
| $0.08 | $4.40 | $0.06 | 0.88s | 98 tps | ||
| $0.082 | $6.00 | $0.09 | 1.55s | 42 tps | ||
30% off | $0.20$0.14 | $6.00$4.20 | $0.15$0.105 | 1.81s | 24 tps | |
| $0.14 | $4.40 | $0.10 | 0.88s | 81 tps | ||
| $0.15 | $3.40 | $0.14 | 1.64s | 71 tps | ||
| $0.15 | $3.40 | $0.14 | 1.78s | 78 tps | ||
| $0.17 | $4.80 | $0.16 | 0.78s | 96 tps | ||
| $0.19 | $4.40 | $0.19 | 2.09s | 46 tps | ||
| $0.49 | $2.90 | $0.19 | 2.84s | 25 tps | ||
| $0.55 | $2.1956 | $0.18 | 0.76s | 94 tps | ||
| $0.90$0.5625 | $4.00$2.50 | $0.20$0.125 | 1.20s | 68 tps | ||
50% off | $1.40$0.6986 | $4.40$2.196 | $0.26$0.1297 | 0.79s | 75 tps | |
50% off | $1.40$0.70 | $4.40$2.20 | $0.26$0.13 | 2.30s | 55 tps | |
50% off | $1.40$0.70 | $4.40$2.20 | $0.26$0.13 | 3.59s | 45 tps | |
40% off | $1.40$0.84 | $4.40$2.64 | $0.26$0.156 | 3.10s | 34 tps | |
| $0.84 | $2.65 | $0.19 | 0.83s | 97 tps | ||
| $0.91 | $2.86 | $0.169 | 0.90s | 88 tps | ||
30% off | $1.40$0.98 | $4.40$3.08 | $0.26$0.182 | 3.64s | 43 tps | |
| $1.19 | $3.74 | $0.238 | 1.86s | 51 tps | ||
10% off | $1.40$1.26 | $4.40$3.96 | $0.26$0.234 | 0.63s | 96 tps | |
| $1.40 | $4.40 | $0.14 | 1.45s | 106 tps | ||
| $1.40 | $4.40 | $0.14 | 3.55s | 48 tps | ||
| $1.40 | $4.40 | $0.14 | 1.35s | 96 tps | ||
| $1.40 | $4.40 | $0.26 | 0.73s | 96 tps | ||
| $1.40 | $4.40 | $0.26 | 0.88s | 76 tps | ||
20% off | $1.75$1.40 | $5.50$4.40 | $0.325$0.26 | 1.05s | 58 tps | |
| $1.40 | $4.40 | $0.26 | 0.69s | 91 tps | ||
| $1.40 | $4.40 | $0.26 | 0.82s | 92 tps | ||
| $1.40 | $4.40 | $0.26 | 1.44s | 70 tps | ||
| $1.40 | $4.40 | $0.14 | 4.58s | 47 tps | ||
| $1.40 | $4.40 | $0.26 | 0.96s | 54 tps | ||
| $1.40 | $4.40 | $0.26 | 3.12s | 36 tps | ||
| $1.40 | $4.40 | $0.26 | 1.26s | 54 tps | ||
| $1.40 | $4.40 | $0.26 | 3.68s | 40 tps | ||
| $2.10 | $6.60 | $0.39 | 3.03s | 110 tps | ||
| $2.10 | $6.60 | $0.21 | 0.93s | 149 tps | ||
| $2.10 | $6.60 | $0.21 | 0.93s | 146 tps | ||
| $2.80 | $8.80 | $0.56 | 0.65s | 59 tps | ||
| $2.10 | $6.60 | $0.40 | 15.40s | 9 tps | ||
Not used in Standard routing:Why these endpoints are not used | ||||||
| $1.54 | $4.84 | $0.154 | 0.99s | 131 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 provider routing options.
