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.036 | $0.90 | $0.0108 | 5.66s | 18 tps | ||
| $0.04 | $0.50 | $0.0125 | 1.34s | 63 tps | ||
| $0.042 | $1.00 | $0.015 | 0.90s | 41 tps | ||
71% off | $0.15$0.0435 | $0.50$0.145 | $0.03$0.0087 | 1.72s | 33 tps | |
| $0.045 | $0.60 | $0.0285 | 1.48s | 82 tps | ||
| $0.045 | $0.60 | $0.0285 | 1.44s | 88 tps | ||
| $0.06 | $1.60 | $0.04 | 0.82s | 177 tps | ||
| $0.07 | $0.25 | $0.03 | 0.53s | 73 tps | ||
| $0.15$0.075 | $0.50$0.25 | $0.03$0.015 | 2.76s | 12 tps | ||
| $0.08 | $0.50 | $0.012 | 1.67s | 29 tps | ||
44% off | $0.15$0.084 | $0.50$0.28 | $0.03$0.0168 | 2.12s | 42 tps | |
40% off | $0.15$0.09 | $0.50$0.30 | $0.03$0.018 | 2.61s | 37 tps | |
38% off | $0.15$0.093 | $0.50$0.31 | $0.03$0.0186 | 0.91s | 57 tps | |
| $0.095 | $0.50 | $0.012 | 0.55s | 88 tps | ||
| $0.0999 | $0.55 | $0.099 | 0.54s | 87 tps | ||
25% off | $0.15$0.1125 | $0.50$0.375 | $0.03$0.0225 | 4.28s | 36 tps | |
| $0.13125 | $0.4375 | $0.03 | 0.91s | 42 tps | ||
| $0.14 | $0.47 | $0.024 | 0.41s | 96 tps | ||
| $0.15 | $0.50 | $0.03 | 0.29s | 157 tps | ||
| $0.15 | $0.50 | $0.03 | 0.54s | 81 tps | ||
| $0.15 | $0.50 | $0.03 | 0.77s | 92 tps | ||
| $0.15 | $0.50 | $0.05 | 0.54s | 226 tps | ||
| $0.15 | $0.50 | $0.03 | 2.19s | 59 tps | ||
| $0.15 | $0.50 | $0.03 | 1.04s | 141 tps | ||
| $0.15 | $0.50 | $0.03 | 0.38s | 140 tps | ||
| $0.15 | $0.50 | $0.03 | 1.71s | 48 tps | ||
| $0.15 | $0.50 | $0.03 | 0.38s | 155 tps | ||
| $0.15 | $0.50 | $0.03 | 0.66s | 128 tps | ||
| $0.15 | $0.50 | $0.03 | 0.54s | 77 tps | ||
| $0.15 | $0.50 | $0.03 | 0.85s | 91 tps | ||
| $0.15 | $0.50 | $0.03 | 2.61s | 47 tps | ||
| $0.1875 | $0.625 | $0.0375 | 1.23s | 132 tps | ||
Not used in Standard routing:Why these endpoints are not used | ||||||
| $0.225 | $0.75 | $0.045 | 0.49s | 176 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.
