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.65s | 75 tps | ||
| $0.0052 | $0.1985 | $0.0052 | 1.33s | 53 tps | ||
| $0.074 | $0.20 | $0.073 | 0.40s | 100 tps | ||
| $0.12 | $0.388 | $0.032 | 0.55s | 78 tps | ||
| $0.15 | $0.50 | $0.03 | 1.03s | 134 tps | ||
| $0.15 | $0.50 | $0.02 | 0.73s | 119 tps | ||
| $0.15 | $0.50 | $0.03 | 0.86s | 129 tps | ||
| $0.07835 | $0.25 | $0.0261 | 1.15s | 45 tps | ||
| $0.13125 | $0.4375 | $0.03 | 0.71s | 120 tps | ||
| $0.07835 | $0.25 | $0.0261 | 0.96s | 41 tps | ||
| $0.15 | $0.50 | $0.03 | 5.83s | 112 tps | ||
| $0.15 | $0.50 | $0.03 | 3.94s | 106 tps | ||
| $0.15 | $0.50 | $0.03 | 1.84s | 57 tps | ||
71% off | $0.15$0.0435 | $0.50$0.145 | $0.03$0.0087 | 2.59s | 31 tps | |
| $0.15 | $0.50 | $0.03 | 5.12s | 40 tps | ||
44% off | $0.15$0.084 | $0.50$0.28 | $0.03$0.0168 | 4.57s | 36 tps | |
| $0.08 | $1.60 | $0.04 | 4.55s | 114 tps | ||
| $0.15 | $0.65 | $0.042 | 2.81s | 42 tps | ||
| $0.15 | $0.75 | $0.05 | 1.50s | 34 tps | ||
15% off | $0.15$0.1275 | $0.50$0.425 | $0.03$0.0255 | 4.86s | 28 tps | |
| $0.15 | $0.50 | $0.03 | 5.97s | 36 tps | ||
| $0.08 | $0.50 | $0.012 | 2.71s | 12 tps | ||
| $0.12 | $0.388 | $0.032 | 0.39s | 81 tps | ||
| $0.15 | $0.50 | $0.03 | 1.15s | 120 tps | ||
| $0.15 | $0.50 | $0.03 | 7.26s | 33 tps | ||
| $0.14 | $0.47 | $0.024 | 8.19s | 56 tps | ||
| $0.15 | $0.50 | $0.03 | 0.90s | 126 tps | ||
| $0.15 | $0.50 | $0.03 | -- | -- | ||
| $0.15 | $0.50 | $0.03 | 0.45s | 146 tps | ||
| $0.15 | $0.50 | $0.03 | 0.77s | 138 tps | ||
| $0.175 | $0.69 | $0.075 | 1.50s | 53 tps | ||
| $0.15 | $0.50 | $0.03 | 5.20s | 40 tps | ||
50% off | $0.15$0.075 | $0.50$0.25 | $0.03$0.015 | 9.67s | 32 tps | |
Not used in Standard routing:Why these endpoints are not used | ||||||
| $0.225 | $0.75 | $0.045 | 0.69s | 103 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.
