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.015 | $0.055 | -- | 0.89s | 72 tps | ||
| $0.03 | $0.15 | $0.015 | 0.60s | 103 tps | ||
| $0.03 | $0.15 | $0.03 | 0.79s | 52 tps | ||
| $0.03 | $0.17 | $0.03 | 0.24s | 114 tps | ||
| $0.03 | $0.18 | $0.03 | 0.65s | 67 tps | ||
| $0.03 | $0.187 | $0.03 | 0.30s | 149 tps | ||
| $0.037 | $0.17 | -- | 0.38s | 35 tps | ||
| $0.05 | $0.25 | $0.05 | 0.25s | 304 tps | ||
| $0.05 | $0.25 | -- | 0.85s | 69 tps | ||
| $0.05 | $0.25 | -- | 0.68s | 171 tps | ||
| $0.06 | $0.40 | $0.03 | 0.50s | 165 tps | ||
| $0.06 | $0.42 | $0.012 | 0.61s | 68 tps | ||
| $0.10 | $0.50 | $0.10 | 0.18s | 155 tps | ||
| $0.10 | $0.50 | $0.10 | 1.59s | 93 tps | ||
| $0.10 | $0.75 | $0.055 | 0.35s | 263 tps | ||
| $0.14 | $0.95 | -- | 1.13s | 389 tps | ||
| $0.15 | $0.60 | $0.10 | 0.26s | 327 tps | ||
| $0.15 | $0.60 | -- | 0.58s | 305 tps | ||
| $0.15 | $0.60 | $0.075 | 1.04s | 36 tps | ||
| $0.15 | $0.60 | -- | 2.52s | 106 tps | ||
| $0.15 | $0.60 | $0.075 | 0.18s | 340 tps | ||
| $0.15 | $0.75 | -- | 0.57s | 108 tps | ||
| $0.20 | $0.95 | -- | 1.41s | 59 tps | ||
| $0.35 | $0.75 | $0.35 | 0.17s | 795 tps | ||
| $0.15 | $0.60 | -- | 0.30s | 99 tps | ||
| $0.09 | $0.36 | -- | 0.42s | 62 tps | ||
Not used in Standard routing:Why these endpoints are not used | ||||||
| $0.15 | $0.60 | -- | 0.52s | 196 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.