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.12 | $0.388 | $0.032 | 0.42s | 132 tps | ||
| $0.048 | $0.20 | $0.006 | 0.94s | 70 tps | ||
| $0.15 | $0.50 | $0.03 | 0.33s | 110 tps | ||
| $0.13125 | $0.4375 | $0.03 | 0.88s | 116 tps | ||
| $0.15 | $0.50 | $0.03 | 0.61s | 140 tps | ||
| $0.15 | $0.50 | $0.03 | 0.87s | 118 tps | ||
| $0.15 | $0.50 | $0.03 | 0.76s | 124 tps | ||
| $0.15 | $0.50 | $0.03 | 0.76s | 107 tps | ||
| $0.07835 | $0.30 | $0.05223 | 0.95s | 78 tps | ||
| $0.15 | $0.50 | $0.03 | 0.66s | 114 tps | ||
| $0.15 | $0.50 | $0.03 | 0.25s | 106 tps | ||
| $0.07835 | $0.30 | $0.05223 | 1.03s | 54 tps | ||
| $0.123 | $0.65 | $0.044 | 0.89s | 83 tps | ||
40% off | $0.15$0.09 | $0.50$0.30 | $0.03$0.018 | 0.94s | 58 tps | |
| $0.10 | $0.69 | $0.075 | 0.66s | 85 tps | ||
| $0.15 | $0.50 | $0.03 | 1.69s | 76 tps | ||
| $0.06 | $1.60 | $0.04 | 0.55s | 154 tps | ||
44% off | $0.15$0.084 | $0.50$0.28 | $0.03$0.0168 | 2.24s | 40 tps | |
| $0.25 | $0.70 | $0.075 | 0.99s | 61 tps | ||
| $0.075 | $0.50 | $0.0075 | 1.84s | 27 tps | ||
| $0.15 | $0.50 | $0.03 | 1.13s | 60 tps | ||
| $0.15 | $0.50 | $0.03 | 3.14s | 50 tps | ||
15% off | $0.15$0.1275 | $0.50$0.425 | $0.03$0.0255 | 3.54s | 30 tps | |
Fast | $0.1875 | $0.625 | $0.0375 | 1.11s | 38 tps | |
| $0.08 | $0.50 | $0.012 | 2.03s | 21 tps | ||
| $0.14 | $0.47 | $0.024 | 1.36s | 80 tps | ||
| $0.15$0.075 | $0.50$0.25 | $0.03$0.015 | 1.03s | 34 tps | ||
50% off | $0.15$0.075 | $0.50$0.25 | $0.03$0.015 | 1.54s | 32 tps | |
| $0.15 | $0.50 | $0.03 | 0.54s | 129 tps | ||
| $0.15 | $0.50 | $0.02 | 0.57s | 199 tps | ||
| $0.08 | $0.39 | $0.03 | 0.50s | 155 tps | ||
| $0.15 | $0.50 | $0.03 | 6.85s | 46 tps | ||
| $0.15 | $0.50 | $0.03 | 3.11s | 49 tps | ||
Not used in Standard routing:Why these endpoints are not used | ||||||
| $0.225 | $0.75 | $0.045 | 0.63s | 137 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.
