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.0154 | $0.1443 | $0.0154 | 1.24s | 40 tps | ||
| $0.0162 | $0.1443 | $0.0162 | 0.54s | 98 tps | ||
71% off | $0.15$0.0435 | $0.50$0.145 | $0.03$0.0087 | 2.83s | 38 tps | |
| $0.074 | $0.20 | $0.06 | 0.36s | 113 tps | ||
50% off | $0.15$0.075 | $0.50$0.25 | $0.03$0.015 | 4.97s | 31 tps | |
| $0.07835 | $0.25 | $0.0261 | 0.88s | 69 tps | ||
| $0.07835 | $0.25 | $0.0261 | 1.01s | 73 tps | ||
| $0.08 | $0.50 | $0.012 | 3.53s | 9 tps | ||
| $0.08 | $1.60 | $0.04 | 5.17s | 120 tps | ||
44% off | $0.15$0.084 | $0.50$0.28 | $0.03$0.0168 | 2.59s | 53 tps | |
| $0.12 | $0.388 | $0.032 | 0.89s | 84 tps | ||
| $0.12 | $0.388 | $0.032 | 0.45s | 87 tps | ||
15% off | $0.15$0.1275 | $0.50$0.425 | $0.03$0.0255 | 3.90s | 26 tps | |
| $0.13125 | $0.4375 | $0.03 | 0.69s | 122 tps | ||
| $0.14 | $0.47 | $0.024 | 30.87s | 37 tps | ||
| $0.15 | $0.50 | $0.03 | 1.34s | 103 tps | ||
| $0.15 | $0.50 | $0.03 | -- | -- | ||
| $0.15 | $0.50 | $0.03 | 0.42s | 149 tps | ||
| $0.15 | $0.50 | $0.03 | 4.17s | 105 tps | ||
| $0.15 | $0.50 | $0.02 | 0.62s | 121 tps | ||
| $0.15 | $0.50 | $0.03 | 4.78s | 46 tps | ||
| $0.15 | $0.50 | $0.03 | 0.86s | 119 tps | ||
| $0.15 | $0.50 | $0.03 | 0.79s | 129 tps | ||
| $0.15 | $0.50 | $0.03 | 9.12s | 36 tps | ||
| $0.15 | $0.50 | $0.03 | 0.89s | 131 tps | ||
| $0.15 | $0.50 | $0.03 | 1.50s | 85 tps | ||
| $0.15 | $0.50 | $0.03 | 0.52s | 127 tps | ||
| $0.15 | $0.50 | $0.03 | 6.30s | 98 tps | ||
| $0.15 | $0.50 | $0.03 | 0.99s | 26 tps | ||
| $0.15 | $0.50 | $0.03 | 3.79s | 41 tps | ||
| $0.15 | $0.69 | $0.075 | 0.63s | 59 tps | ||
| $0.15 | $0.75 | $0.05 | 2.13s | 36 tps | ||
| $0.159 | $0.65 | $0.045 | 1.85s | 44 tps | ||
Not used in Standard routing:Why these endpoints are not used | ||||||
| $0.225 | $0.75 | $0.045 | 0.58s | 147 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.
