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.04 | $0.50 | $0.0125 | 1.49s | 45 tps | ||
| $0.045 | $0.60 | $0.0285 | 1.32s | 76 tps | ||
| $0.045 | $0.60 | $0.0285 | 1.48s | 67 tps | ||
| $0.06 | $1.00 | $0.015 | 0.85s | 104 tps | ||
| $0.06 | $1.60 | $0.04 | 0.52s | 177 tps | ||
| $0.15$0.075 | $0.50$0.25 | $0.03$0.015 | 2.09s | 18 tps | ||
| $0.08 | $0.50 | $0.012 | 1.57s | 19 tps | ||
44% off | $0.15$0.084 | $0.50$0.28 | $0.03$0.0168 | 1.51s | 61 tps | |
40% off | $0.15$0.09 | $0.50$0.30 | $0.03$0.018 | 3.89s | 36 tps | |
38% off | $0.15$0.093 | $0.50$0.31 | $0.03$0.0186 | 2.33s | 78 tps | |
| $0.10 | $0.15 | $0.03 | 0.78s | 79 tps | ||
| $0.108 | $0.55 | $0.099 | 0.84s | 64 tps | ||
25% off | $0.15$0.1125 | $0.50$0.375 | $0.03$0.0225 | 5.68s | 33 tps | |
| $0.12 | $0.50 | $0.012 | 0.50s | 179 tps | ||
| $0.13125 | $0.4375 | $0.03 | 1.02s | 75 tps | ||
| $0.15 | $0.50 | $0.03 | 0.32s | 102 tps | ||
| $0.15 | $0.50 | $0.03 | 0.57s | 69 tps | ||
| $0.15 | $0.50 | $0.03 | 0.61s | 153 tps | ||
| $0.15 | $0.50 | $0.03 | 1.14s | 145 tps | ||
| $0.15 | $0.50 | $0.03 | 0.63s | 149 tps | ||
| $0.15 | $0.50 | $0.03 | 1.34s | 38 tps | ||
| $0.15 | $0.50 | $0.03 | 0.49s | 128 tps | ||
| $0.15 | $0.50 | $0.03 | 0.95s | 74 tps | ||
| $0.15 | $0.50 | $0.03 | 0.35s | 73 tps | ||
| $0.15 | $0.50 | $0.03 | 0.64s | 66 tps | ||
| $0.15 | $0.50 | $0.03 | 2.66s | 54 tps | ||
| $0.1875 | $0.625 | $0.0375 | 1.17s | 97 tps | ||
| $0.036 | $0.90 | $0.0108 | 5.47s | 18 tps | ||
71% off | $0.15$0.0435 | $0.50$0.145 | $0.03$0.0087 | 1.36s | 39 tps | |
| $0.15 | $0.50 | $0.05 | 0.73s | 129 tps | ||
| $0.15 | $0.50 | $0.03 | 2.82s | 53 tps | ||
| $0.14 | $0.47 | $0.024 | 1.25s | 85 tps | ||
Not used in Standard routing:Why these endpoints are not used | ||||||
| $0.225 | $0.75 | $0.045 | 0.53s | 149 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.
