openai/gpt-oss-120b
Model weightsgpt-oss-120b is an open-weight, 117B-parameter Mixture-of-Experts (MoE) language model from OpenAI designed for high-reasoning, agentic, and general-purpose production use cases. It activates 5.1B parameters per forward pass and is optimized to run on a single H100 GPU with native MXFP4 quantization. The model supports configurable reasoning depth, full chain-of-thought access, and native tool use, including function calling, browsing, and structured output generation.
| $0.022 | $0.082 | -- | 0.65s | 71 tps | ||
| $0.03 | $0.15 | $0.015 | 0.61s | 72 tps | ||
| $0.03 | $0.15 | $0.03 | 0.80s | 52 tps | ||
| $0.03 | $0.17 | $0.03 | 0.33s | 98 tps | ||
| $0.03 | $0.18 | $0.03 | 0.59s | 65 tps | ||
| $0.03 | $0.187 | $0.03 | 0.29s | 169 tps | ||
| $0.037 | $0.17 | -- | 0.32s | 52 tps | ||
| $0.05 | $0.25 | $0.05 | 0.20s | 318 tps | ||
| $0.05 | $0.25 | -- | 0.78s | 63 tps | ||
| $0.05 | $0.25 | -- | 0.69s | 172 tps | ||
| $0.06 | $0.40 | $0.03 | 0.55s | 168 tps | ||
| $0.06 | $0.42 | $0.012 | 0.69s | 70 tps | ||
| $0.10 | $0.75 | $0.055 | 0.40s | 191 tps | ||
| $0.14 | $0.95 | -- | 1.28s | 353 tps | ||
| $0.15 | $0.60 | $0.10 | 0.26s | 316 tps | ||
| $0.15 | $0.60 | -- | 0.52s | 330 tps | ||
| $0.15 | $0.60 | $0.075 | 1.11s | 43 tps | ||
| $0.15 | $0.60 | -- | 1.03s | 145 tps | ||
| $0.15 | $0.60 | -- | 0.26s | 142 tps | ||
| $0.15 | $0.60 | $0.075 | 0.15s | 342 tps | ||
| $0.15 | $0.75 | -- | 0.95s | 196 tps | ||
| $0.20 | $0.95 | -- | 1.38s | 55 tps | ||
| $0.35 | $0.75 | $0.35 | 0.15s | 838 tps | ||
| $0.10 | $0.50 | $0.10 | 0.23s | 195 tps | ||
| $0.10 | $0.50 | $0.10 | 0.24s | 200 tps | ||
| $0.09 | $0.36 | -- | 0.23s | 146 tps | ||
Not used in Standard routing:Why these endpoints are not used | ||||||
| $0.15 | $0.60 | -- | 0.53s | 208 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.