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.57s | 76 tps | ||
| $0.03 | $0.15 | $0.03 | 1.73s | 22 tps | ||
| $0.03 | $0.17 | $0.03 | 0.35s | 86 tps | ||
| $0.03 | $0.18 | $0.03 | 0.55s | 55 tps | ||
| $0.03 | $0.187 | $0.03 | 0.32s | 149 tps | ||
| $0.037 | $0.17 | -- | 0.27s | 56 tps | ||
| $0.05 | $0.25 | $0.05 | 0.26s | 203 tps | ||
| $0.05 | $0.25 | -- | 0.62s | 78 tps | ||
| $0.05 | $0.25 | -- | 0.63s | 180 tps | ||
| $0.06 | $0.42 | $0.012 | 0.43s | 68 tps | ||
| $0.10 | $0.50 | $0.10 | 0.22s | 179 tps | ||
| $0.10 | $0.50 | $0.10 | 0.18s | 177 tps | ||
| $0.10 | $0.75 | $0.055 | 0.39s | 230 tps | ||
| $0.14 | $0.95 | -- | 0.91s | 374 tps | ||
| $0.15 | $0.60 | -- | 0.22s | 292 tps | ||
| $0.15 | $0.60 | -- | 0.39s | 268 tps | ||
| $0.15 | $0.60 | $0.075 | 1.16s | 59 tps | ||
| $0.15 | $0.60 | -- | 0.67s | 76 tps | ||
| $0.15 | $0.60 | -- | 0.19s | 154 tps | ||
| $0.15 | $0.60 | $0.075 | 0.16s | 349 tps | ||
| $0.15 | $0.75 | -- | 1.01s | 192 tps | ||
| $0.35 | $0.75 | $0.35 | 0.20s | 709 tps | ||
| $0.09 | $0.36 | -- | 0.68s | 68 tps | ||
Not used in Exacto routing:Why these endpoints are not used | ||||||
| $0.15 | $0.60 | -- | 0.40s | 203 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.