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 | 2.36s | 41 tps | ||
| $0.044 | $0.45 | $0.01 | 2.66s | 21 tps | ||
| $0.045 | $0.60 | $0.0285 | 1.76s | 70 tps | ||
| $0.045 | $0.60 | $0.0285 | 1.77s | 78 tps | ||
| $0.06 | $0.50 | $0.012 | 2.20s | 43 tps | ||
| $0.06 | $0.75 | $0.015 | 1.17s | 35 tps | ||
| $0.06 | $1.60 | $0.04 | 1.32s | 161 tps | ||
54% off | $0.15$0.069 | $0.50$0.23 | $0.03$0.0138 | 1.71s | 43 tps | |
| $0.07 | $0.05 | $0.03 | 0.61s | 83 tps | ||
| $0.15$0.075 | $0.50$0.25 | $0.03$0.015 | 2.52s | 10 tps | ||
44% off | $0.15$0.084 | $0.50$0.28 | $0.03$0.0168 | 4.17s | 35 tps | |
38% off | $0.15$0.093 | $0.50$0.31 | $0.03$0.0186 | 1.27s | 64 tps | |
| $0.10 | $1.00 | $0.04 | 0.52s | 76 tps | ||
30% off | $0.15$0.105 | $0.50$0.35 | $0.035$0.0245 | 1.82s | 36 tps | |
25% off | $0.15$0.1125 | $0.50$0.375 | $0.03$0.0225 | 4.42s | 15 tps | |
| $0.12 | $0.55 | $0.099 | 0.64s | 90 tps | ||
| $0.15 | $0.50 | $0.03 | 0.29s | 118 tps | ||
| $0.15 | $0.50 | $0.03 | 0.63s | 122 tps | ||
| $0.15 | $0.50 | $0.03 | 0.73s | 162 tps | ||
| $0.15 | $0.50 | $0.05 | 0.66s | 239 tps | ||
| $0.15 | $0.50 | $0.03 | 0.80s | 114 tps | ||
| $0.15 | $0.50 | $0.03 | 1.09s | 144 tps | ||
| $0.15 | $0.50 | $0.03 | 1.11s | 43 tps | ||
| $0.15 | $0.50 | $0.03 | 0.68s | 123 tps | ||
| $0.15 | $0.50 | $0.03 | 1.01s | 104 tps | ||
| $0.15 | $0.50 | $0.03 | 0.62s | 111 tps | ||
| $0.15 | $0.50 | $0.03 | 1.72s | 74 tps | ||
| $0.15 | $0.50 | $0.03 | 4.19s | 42 tps | ||
| $0.1875 | $0.625 | $0.0375 | 1.04s | 164 tps | ||
40% off | $0.15$0.09 | $0.50$0.30 | $0.03$0.018 | 3.85s | 46 tps | |
| $0.15 | $0.50 | $0.03 | 7.02s | 36 tps | ||
| $0.15 | $0.50 | $0.03 | 2.02s | 47 tps | ||
Not used in Standard routing:Why these endpoints are not used | ||||||
| $0.225 | $0.75 | $0.045 | 0.66s | 85 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.
