z-ai/glm-5.3-flash
Model weightsGLM-5.3-Flash is a native multimodal model from Z.ai. It is suited for efficient coding and long-horizon agent tasks. Its hybrid sparse and linear attention architecture maintains accurate long-context behavior while reducing compute overhead.
| $0.048 | $0.20 | $0.006 | 0.55s | 90 tps | ||
| $0.12 | $0.388 | $0.032 | 0.35s | 120 tps | ||
| $0.15 | $0.50 | $0.03 | 0.43s | 161 tps | ||
| $0.15 | $0.50 | $0.03 | 0.40s | 163 tps | ||
| $0.13125 | $0.4375 | $0.03 | 0.89s | 111 tps | ||
| $0.15 | $0.50 | $0.03 | 0.62s | 133 tps | ||
| $0.15 | $0.50 | $0.03 | 0.36s | 99 tps | ||
| $0.15 | $0.50 | $0.03 | 0.56s | 124 tps | ||
| $0.15 | $0.50 | $0.03 | 0.71s | 108 tps | ||
| $0.15 | $0.50 | $0.03 | 0.39s | 119 tps | ||
| $0.12 | $0.50 | $0.03 | 0.41s | 152 tps | ||
| $0.07835 | $0.30 | $0.05223 | 0.97s | 84 tps | ||
| $0.07835 | $0.30 | $0.05223 | 1.03s | 67 tps | ||
Fast | $0.1875 | $0.625 | $0.0375 | 0.37s | 107 tps | |
| $0.15 | $0.50 | $0.03 | 0.85s | 78 tps | ||
| $0.10 | $0.69 | $0.075 | 0.79s | 103 tps | ||
| $0.126 | $0.65 | $0.045 | 0.99s | 80 tps | ||
| $0.25 | $0.70 | $0.075 | 0.62s | 103 tps | ||
40% off | $0.15$0.09 | $0.50$0.30 | $0.03$0.018 | 1.10s | 50 tps | |
| $0.15 | $0.50 | $0.03 | 3.06s | 52 tps | ||
44% off | $0.15$0.084 | $0.50$0.28 | $0.03$0.0168 | 2.39s | 37 tps | |
50% off | $0.15$0.075 | $0.50$0.25 | $0.03$0.015 | 1.93s | 34 tps | |
| $0.06 | $1.60 | $0.04 | 0.62s | 36 tps | ||
| $0.075 | $0.50 | $0.0075 | 1.81s | 30 tps | ||
15% off | $0.15$0.1275 | $0.50$0.425 | $0.03$0.0255 | 4.10s | 30 tps | |
| $0.08 | $0.50 | $0.012 | 2.15s | 20 tps | ||
| $0.15$0.075 | $0.50$0.25 | $0.03$0.015 | 0.80s | 60 tps | ||
| $0.14 | $0.47 | $0.024 | 0.83s | 81 tps | ||
| $0.15 | $0.50 | $0.03 | 2.06s | 46 tps | ||
| $0.15 | $0.50 | $0.03 | 0.39s | 156 tps | ||
| $0.15 | $0.50 | $0.02 | 0.53s | 196 tps | ||
| $0.15 | $0.50 | $0.03 | 0.68s | 75 tps | ||
| $0.15 | $0.50 | $0.03 | 2.81s | 56 tps | ||
Not used in Standard routing:Why these endpoints are not used | ||||||
| $0.225 | $0.75 | $0.045 | 0.44s | 138 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.
