GLM-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.032 | $0.72 | $0.01 | 4.26s | 21 tps | ||
| $0.04 | $0.50 | $0.0125 | 0.90s | 57 tps | ||
| $0.045 | $0.60 | $0.0285 | 0.67s | 107 tps | ||
| $0.045 | $0.60 | $0.0285 | 0.84s | 128 tps | ||
| $0.06 | $1.60 | $0.04 | 1.49s | 112 tps | ||
| $0.07 | $0.50 | $0.04 | 0.54s | 62 tps | ||
| $0.07 | $0.50 | $0.03 | 0.51s | 46 tps | ||
| $0.15$0.075 | $0.50$0.25 | $0.03$0.015 | 1.73s | 12 tps | ||
44% off | $0.15$0.08385 | $0.50$0.2795 | $0.03$0.01677 | 1.33s | 38 tps | |
44% off | $0.15$0.084 | $0.50$0.28 | $0.03$0.0168 | 3.18s | 21 tps | |
40% off | $0.15$0.09 | $0.50$0.30 | $0.03$0.018 | 3.85s | 35 tps | |
38% off | $0.15$0.093 | $0.50$0.31 | $0.03$0.0186 | 0.92s | 35 tps | |
| $0.096 | $0.55 | $0.099 | 0.60s | 97 tps | ||
| $0.10 | $1.00 | $0.04 | 0.81s | 143 tps | ||
30% off | $0.15$0.105 | $0.50$0.35 | $0.035$0.0245 | 1.40s | 25 tps | |
25% off | $0.15$0.1125 | $0.50$0.375 | $0.03$0.0225 | 4.89s | 42 tps | |
| $0.13 | $0.70 | $0.04 | 0.93s | 62 tps | ||
| $0.15 | $0.50 | $0.03 | 0.30s | 87 tps | ||
| $0.15 | $0.50 | $0.03 | 0.47s | 109 tps | ||
| $0.15 | $0.50 | $0.03 | 0.78s | 118 tps | ||
| $0.15 | $0.50 | $0.05 | 0.71s | 153 tps | ||
| $0.15 | $0.50 | $0.03 | 2.51s | 48 tps | ||
| $0.15 | $0.50 | $0.03 | 0.98s | 91 tps | ||
| $0.15 | $0.50 | $0.03 | 0.58s | 115 tps | ||
| $0.15 | $0.50 | $0.03 | 2.10s | 35 tps | ||
| $0.15 | $0.50 | $0.03 | 0.67s | 40 tps | ||
| $0.15 | $0.50 | $0.03 | 0.66s | 81 tps | ||
| $0.15 | $0.50 | $0.03 | 1.04s | 92 tps | ||
| $0.15 | $0.50 | $0.03 | 0.38s | 107 tps | ||
| $0.15 | $0.50 | $0.03 | 1.36s | 82 tps | ||
| $0.15 | $0.50 | $0.03 | 3.37s | 29 tps | ||
| $0.1875 | $0.625 | $0.0375 | 0.97s | 105 tps | ||
Not used in Standard routing:Why these endpoints are not used | ||||||
| $0.225 | $0.75 | $0.045 | 0.61s | 100 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.
