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.03 | $0.15 | $0.015 | 0.76s | 38 tps | ||
| $0.03 | $0.17 | $0.03 | 0.37s | 59 tps | ||
| $0.03 | $0.18 | $0.03 | 0.46s | 45 tps | ||
| $0.03 | $0.187 | $0.03 | 0.40s | 91 tps | ||
| $0.037 | $0.17 | -- | 0.54s | 28 tps | ||
| $0.046 | $0.169 | $0.041 | 0.96s | 71 tps | ||
| $0.05 | $0.25 | $0.05 | 0.12s | 176 tps | ||
| $0.05 | $0.25 | -- | 0.94s | 89 tps | ||
| $0.055 | $0.25 | -- | 0.92s | 38 tps | ||
| $0.06 | $0.40 | $0.03 | 0.39s | 164 tps | ||
| $0.06 | $0.42 | $0.012 | 0.92s | 54 tps | ||
| $0.10 | $0.50 | $0.10 | 0.24s | 116 tps | ||
| $0.10 | $0.50 | $0.10 | 0.28s | 115 tps | ||
| $0.10 | $0.75 | $0.055 | 0.37s | 181 tps | ||
| $0.14 | $0.95 | -- | 1.22s | 318 tps | ||
| $0.15 | $0.60 | $0.10 | 0.26s | 300 tps | ||
| $0.15 | $0.60 | -- | 0.61s | 194 tps | ||
| $0.15 | $0.60 | $0.075 | 1.24s | 25 tps | ||
| $0.15 | $0.60 | -- | 1.19s | 82 tps | ||
| $0.15 | $0.60 | -- | 0.30s | 99 tps | ||
| $0.15 | $0.60 | $0.075 | 0.21s | 297 tps | ||
| $0.35 | $0.75 | $0.35 | 0.28s | 572 tps | ||
| $0.03 | $0.15 | $0.03 | 1.31s | 34 tps | ||
| $0.20 | $0.95 | -- | 1.63s | 61 tps | ||
| $0.09 | $0.36 | -- | 0.55s | 51 tps | ||
| $0.15 | $0.75 | -- | 1.17s | 168 tps | ||
Not used in Standard routing:Why these endpoints are not used | ||||||
| $0.15 | $0.60 | -- | 0.39s | 180 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.