openai/gpt-oss-120b:exacto
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.
| Provider | Input /M | Output /M | Cache read /M | Latency | Throughput | Uptime |
|---|---|---|---|---|---|---|
| $0.03 | $0.15 | $0.015 | 0.62s | 45 tps | ||
| $0.03 | $0.15 | $0.03 | 1.74s | 25 tps | ||
| $0.03 | $0.17 | $0.03 | 0.29s | 56 tps | ||
| $0.03 | $0.18 | $0.03 | 0.58s | 38 tps | ||
| $0.03 | $0.187 | $0.03 | 1.04s | 56 tps | ||
| $0.037 | $0.17 | -- | 0.58s | 24 tps | ||
| $0.05 | $0.25 | $0.05 | 0.28s | 188 tps | ||
| $0.05 | $0.25 | -- | 0.64s | 60 tps | ||
| $0.05 | $0.25 | -- | 0.63s | 188 tps | ||
| $0.06 | $0.40 | $0.03 | 0.64s | 125 tps | ||
| $0.06 | $0.42 | $0.012 | 0.54s | 60 tps | ||
| $0.10 | $0.50 | $0.10 | 0.18s | 146 tps | ||
| $0.10 | $0.50 | $0.10 | 0.22s | 139 tps | ||
| $0.10 | $0.75 | $0.055 | 0.37s | 191 tps | ||
| $0.14 | $0.95 | -- | 0.65s | 197 tps | ||
| $0.15 | $0.60 | -- | 0.28s | 284 tps | ||
| $0.15 | $0.60 | -- | 0.40s | 383 tps | ||
| $0.15 | $0.60 | $0.075 | 1.12s | 49 tps | ||
| $0.15 | $0.60 | -- | 0.82s | 186 tps | ||
| $0.15 | $0.60 | -- | 0.23s | 78 tps | ||
| $0.15 | $0.60 | $0.075 | 0.31s | 274 tps | ||
| $0.15 | $0.75 | -- | 0.82s | 180 tps | ||
| $0.35 | $0.75 | $0.35 | 0.20s | 749 tps | ||
| $0.09 | $0.36 | -- | 0.57s | 33 tps | ||
Not used in Exacto routing:Why these endpoints are not used | ||||||
| $0.15 | $0.60 | -- | 0.47s | 145 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.