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.0052 | $0.1985 | $0.0052 | 0.57s | 93 tps | ||
| $0.074 | $0.20 | $0.073 | 0.37s | 128 tps | ||
| $0.15 | $0.50 | $0.03 | 0.71s | 141 tps | ||
| $0.12 | $0.388 | $0.032 | 0.56s | 91 tps | ||
| $0.15 | $0.50 | $0.03 | 0.81s | 130 tps | ||
| $0.0052 | $0.1985 | $0.0052 | 1.48s | 56 tps | ||
| $0.13125 | $0.4375 | $0.03 | 0.67s | 125 tps | ||
| $0.15 | $0.50 | $0.03 | 0.84s | 114 tps | ||
| $0.07835 | $0.25 | $0.0261 | 1.05s | 62 tps | ||
| $0.15 | $0.50 | $0.03 | 0.94s | 102 tps | ||
| $0.15 | $0.50 | $0.03 | 1.02s | 77 tps | ||
| $0.07835 | $0.25 | $0.0261 | 0.85s | 60 tps | ||
| $0.15 | $0.50 | $0.03 | 0.87s | 127 tps | ||
| $0.15 | $0.75 | $0.05 | 1.08s | 100 tps | ||
| $0.15 | $0.65 | $0.042 | 1.55s | 49 tps | ||
| $0.08 | $1.60 | $0.04 | 0.93s | 86 tps | ||
| $0.18 | $0.69 | $0.075 | 0.86s | 68 tps | ||
44% off | $0.15$0.084 | $0.50$0.28 | $0.03$0.0168 | 4.19s | 36 tps | |
| $0.15 | $0.50 | $0.03 | 4.48s | 41 tps | ||
| $0.15 | $0.50 | $0.03 | 5.32s | 38 tps | ||
71% off | $0.15$0.0435 | $0.50$0.145 | $0.03$0.0087 | 2.20s | 29 tps | |
15% off | $0.15$0.1275 | $0.50$0.425 | $0.03$0.0255 | 4.61s | 27 tps | |
| $0.08 | $0.50 | $0.012 | 1.87s | 16 tps | ||
| $0.15 | $0.50 | $0.02 | 0.61s | 124 tps | ||
| $0.12 | $0.388 | $0.032 | 0.43s | 88 tps | ||
50% off | $0.15$0.075 | $0.50$0.25 | $0.03$0.015 | 1.10s | 55 tps | |
| $0.15 | $0.50 | $0.03 | 2.30s | 34 tps | ||
| $0.14 | $0.47 | $0.024 | 0.82s | 124 tps | ||
| $0.15 | $0.50 | $0.03 | -- | -- | ||
| $0.15 | $0.50 | $0.03 | 0.46s | 139 tps | ||
| $0.15 | $0.50 | $0.03 | 1.19s | 122 tps | ||
| $0.15 | $0.50 | $0.03 | 0.62s | 128 tps | ||
| $0.15 | $0.50 | $0.03 | 2.83s | 39 tps | ||
Not used in Standard routing:Why these endpoints are not used | ||||||
| $0.225 | $0.75 | $0.045 | 0.66s | 102 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.
