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.013 | $0.047 | $0.012 | 0.85s | 74 tps | ||
| $0.03 | $0.15 | $0.015 | 0.58s | 88 tps | ||
| $0.03 | $0.15 | $0.03 | 0.83s | 54 tps | ||
| $0.03 | $0.17 | $0.03 | 0.25s | 118 tps | ||
| $0.03 | $0.18 | $0.03 | 0.56s | 94 tps | ||
| $0.03 | $0.187 | $0.03 | 0.29s | 155 tps | ||
| $0.037 | $0.17 | -- | 0.39s | 38 tps | ||
| $0.05 | $0.25 | $0.05 | 0.20s | 362 tps | ||
| $0.05 | $0.25 | -- | 0.72s | 90 tps | ||
| $0.05 | $0.25 | -- | 0.68s | 191 tps | ||
| $0.06 | $0.40 | $0.03 | 0.46s | 177 tps | ||
| $0.06 | $0.42 | $0.012 | 0.69s | 69 tps | ||
| $0.10 | $0.50 | $0.10 | 0.15s | 188 tps | ||
| $0.10 | $0.50 | $0.10 | 0.15s | 176 tps | ||
| $0.10 | $0.75 | $0.055 | 0.37s | 212 tps | ||
| $0.14 | $0.95 | -- | 1.12s | 404 tps | ||
| $0.15 | $0.60 | $0.10 | 0.27s | 302 tps | ||
| $0.15 | $0.60 | -- | 0.80s | 101 tps | ||
| $0.15 | $0.60 | $0.075 | 1.29s | 37 tps | ||
| $0.15 | $0.60 | -- | 1.30s | 111 tps | ||
| $0.15 | $0.60 | -- | 0.26s | 137 tps | ||
| $0.15 | $0.60 | $0.075 | 0.16s | 352 tps | ||
| $0.15 | $0.75 | -- | 1.02s | 187 tps | ||
| $0.20 | $0.95 | -- | 1.33s | 57 tps | ||
| $0.35 | $0.75 | $0.35 | 0.15s | 818 tps | ||
| $0.09 | $0.36 | -- | 0.70s | 47 tps | ||
Not used in Standard routing:Why these endpoints are not used | ||||||
| $0.15 | $0.60 | -- | 0.52s | 202 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.