GPT-OSS 120B (hosted) is OpenAI's open-weights model served by many providers, and inside Atlas it is the cleanest natural experiment in the registry: the same Apache-licensed bytes cost $0.037 per Mtok input on DeepInfra and $0.35 on Cerebras and Cloudflare. That is a 9.5x spread for identical weights. Context is 131,072 tokens on Groq, Cerebras, Fireworks, DeepInfra, Together AI, and Databricks, and 128,000 on Cloudflare, Baseten, and NVIDIA NIM. Reasoning is enabled on every hosted listing.
What is GPT-OSS 120B (hosted) best at inside Atlas?
GPT-OSS 120B is best inside Atlas as a cheap, fast main model where provider choice is the real lever. The same Apache-licensed weights cost $0.037 per Mtok input on DeepInfra and $0.35 on Cerebras and Cloudflare, a 9.5x spread for identical bytes.
The interesting property of GPT-OSS 120B is that model selection and provider selection come apart. Because every host serves the same weights, whatever GPT-OSS 120B can do for you in Atlas, it can do at $0.037 per Mtok on DeepInfra or at $0.35 on Cerebras. The output side varies too, from $0.17 on DeepInfra up to $0.75 on Cerebras and Cloudflare. What you actually buy with the higher price is silicon and throughput, not capability. Inside Atlas that makes GPT-OSS 120B a good workhorse for the bulk of a session: reading code, proposing plans in the read-only plan agent, and producing diffs that Atlas computes as a unified diff and surfaces for approval before writing.
How much does GPT-OSS 120B cost across providers?
GPT-OSS 120B pricing in 2026 runs from DeepInfra $0.037/$0.17 per Mtok up through Databricks $0.072/$0.28, Baseten $0.10/$0.50, Groq $0.15/$0.60, Fireworks $0.15/$0.60, Nebius $0.15/$0.60, Hugging Face $0.25/$0.69, and Cerebras and Cloudflare at $0.35/$0.75, the top of the range.
Read that list as a menu, not a ranking. DeepInfra at $0.037/$0.17 per Mtok is the cheapest tokens for GPT-OSS 120B. Databricks at $0.072/$0.28 roughly doubles input. The $0.15/$0.60 tier is crowded, with Groq, Fireworks, and Nebius all landing there. Cerebras and Cloudflare sit at $0.35/$0.75, which is 9.5x DeepInfra's input price. Because the weights do not change, a team running GPT-OSS 120B in Atlas can cut its model bill by an order of magnitude by moving hosts, with no change in output quality. The counterweight is latency and output caps, which is where the higher tiers earn their price.
Does the 131,072 token context window of GPT-OSS 120B come with output limits?
GPT-OSS 120B carries a 131,072 token context on Groq, Cerebras, Fireworks, DeepInfra, Together AI, and Databricks, and 128,000 on Cloudflare, Baseten, and NVIDIA NIM. Output caps differ sharply: DeepInfra clips output at 16,384 tokens while Together AI allows the full 131,072.
The output cap is the trap in the cheap tier. DeepInfra gives you GPT-OSS 120B at $0.037 per Mtok input but caps output at 16,384 tokens, and Fireworks caps at 32,768, versus 131,072 on Together AI. In Atlas, output length is what a large multi-file patch consumes, so the cheapest input price can force you into more round trips to finish one edit. That is not fatal, since Atlas snapshots file changes as git patches so edits can be diffed and rolled back and a partial pass is recoverable, but it does mean the sticker price understates the cost of large refactors on a clipped host. Match the host to the shape of your work: cheap input for read-heavy exploration, generous output for patch-heavy sessions.
Is GPT-OSS 120B a reasoning model, and which host is fastest?
GPT-OSS 120B has reasoning enabled on every hosted listing in the Atlas registry in 2026. Groq serves GPT-OSS 120B with 65,536 max output on its LPU inference stack, and Cerebras runs the same weights on wafer-scale hardware, so at $0.35/$0.75 you are paying for silicon, not for the model.
Latency is the argument for the expensive end of the GPT-OSS 120B menu. Groq's LPU stack and Cerebras's wafer-scale hardware both exist to shorten time-to-first-token and raise tokens per second, and in a terminal agent that difference is felt every turn. Atlas is a terminal-native TUI rendered with SolidJS through the OpenTUI renderer, and the interactive loop rewards fast models. So the decision is concrete: if you are watching GPT-OSS 120B work and waiting on it, Groq at $0.15/$0.60 or Cerebras at $0.35/$0.75 buys back your attention. If GPT-OSS 120B is grinding through background subagents you are not watching, DeepInfra at $0.037/$0.17 is the rational pick.
How do you switch GPT-OSS 120B between providers in Atlas?
Atlas lets you switch the active model and provider on the fly with favorites and recents, so add the DeepInfra and Groq listings of GPT-OSS 120B to favorites in the `/models` dialog. Because the weights are identical, `model.cycle_recent` between them changes only price and latency, never behavior.
The practical Atlas workflow for GPT-OSS 120B is to keep two listings pinned. Set `"model": "deepinfra/openai/gpt-oss-120b"` in atlas.json as the default for cost, and keep `"groq/openai/gpt-oss-120b"` a keystroke away for when interactive speed matters more than cost. Run `atlas models deepinfra` (or groq, cerebras, fireworks-ai) to compare the gpt-oss-120b rows in each provider before you commit. Since GPT-OSS 120B is the same model on both sides of that switch, you can flip mid-session without resetting your mental model of what the agent will do. That is unusual: switching between different models normally changes tool-calling style and diff quality along with the price.
When should you pick a different model than GPT-OSS 120B?
Pick a different model than GPT-OSS 120B when the task is a hard multi-file refactor. GPT-OSS 120B is not a frontier coding model, and on that work it will lose to Kimi K2.7 Code or GLM-5.2 no matter how fast the silicon underneath it runs.
Speed does not substitute for capability. GPT-OSS 120B at $0.037 per Mtok on DeepInfra is excellent value for reading code, answering questions, and making contained edits, but a refactor that touches a dozen files and has to hold invariants across all of them is where a frontier coding model earns its price. Kimi K2.7 Code and GLM-5.2 are the alternatives to reach for there. The good news is that this is a per-task decision, not a per-project one, because Atlas lets you switch the active model and provider on the fly with favorites and recents. Run the exploration and the plan on GPT-OSS 120B, then switch the build agent to the stronger model for the patch itself.
Setup
- 01Decide what you are optimizing. Export DEEPINFRA_API_KEY for the cheapest tokens, or GROQ_API_KEY or CEREBRAS_API_KEY for the lowest latency.
- 02Run `atlas models deepinfra` (or groq, cerebras, fireworks-ai) and compare the gpt-oss-120b rows in each.
- 03Pin `"model": "deepinfra/openai/gpt-oss-120b"` in atlas.json, or `"groq/openai/gpt-oss-120b"` if interactive speed matters more than cost.
- 04Add both listings to favorites in the `/models` dialog. Because the weights are identical, `model.cycle_recent` between them changes only price and latency, never behavior.
- 05Check the output cap on your chosen host before a large refactor: DeepInfra caps output at 16,384 tokens and Fireworks at 32,768, versus 131,072 on Together AI.
Frequently asked questions
- how much does gpt-oss-120b cost per million tokens
- GPT-OSS 120B pricing ranges from DeepInfra at $0.037/$0.17 per Mtok to Cerebras and Cloudflare at $0.35/$0.75, with Databricks $0.072/$0.28, Baseten $0.10/$0.50, Groq $0.15/$0.60, Fireworks $0.15/$0.60, Nebius $0.15/$0.60, and Hugging Face $0.25/$0.69 in between.
- which provider is cheapest for gpt-oss-120b
- DeepInfra at $0.037/$0.17 per Mtok is the cheapest listed host for GPT-OSS 120B, about 9.5x cheaper on input than Cerebras and Cloudflare at $0.35/$0.75. DeepInfra caps output at 16,384 tokens, so check that before large patches.
- what is the context window of gpt-oss-120b
- GPT-OSS 120B has a 131,072 token context on Groq, Cerebras, Fireworks, DeepInfra, Together AI, and Databricks, and 128,000 tokens on Cloudflare, Baseten, and NVIDIA NIM.
- how do i run gpt-oss-120b in atlas
- Export DEEPINFRA_API_KEY (or GROQ_API_KEY or CEREBRAS_API_KEY), run `atlas models deepinfra` to confirm the gpt-oss-120b row, then pin `"model": "deepinfra/openai/gpt-oss-120b"` in atlas.json.
- does gpt-oss-120b support reasoning
- Yes. Reasoning is enabled on every hosted GPT-OSS 120B listing. Groq serves it with 65,536 max output on its LPU inference stack, and Together AI allows max output equal to the full 131,072 token context.
- is gpt-oss-120b good enough for refactoring
- For contained edits, yes. For a hard multi-file refactor, GPT-OSS 120B is not a frontier coding model and will lose to Kimi K2.7 Code or GLM-5.2 regardless of how fast the host hardware is.
- why is the same model cheaper on deepinfra than cerebras
- GPT-OSS 120B is Apache-licensed open weights, so every host serves identical bytes. The $0.037 to $0.35 per Mtok input spread reflects the inference hardware and throughput you are buying, not a difference in the model.
Try Atlas in your terminal
The terminal-native AI coding agent. Free core, single binary.
Install AtlasRelated guides
Self-Review Your Working Diff Before Committing with Atlas (2026 Workflow)
How to self-review your working diff before committing with Atlas in 2026: bash produces the diff, read checks each file, grep finds leftovers, session revert undoes bad edits.
Atlas for JavaScript in 2026
In 2026, Atlas empowers JavaScript developers with a terminal-native AI coding agent. It indexes code by AST, uses local embeddings, and offers permission-gated tools for safe, efficient development.
Atlas for Angular in 2026
Adopt Atlas, the terminal-native AI coding agent, for your Angular projects in 2026. Enhance development with intelligent code search, secure local embeddings, and granular control over AI actions.
Atlas vs Qodo: Choosing Your AI Coding Agent in 2026
Comparing Atlas, the terminal-native AI coding agent, with Qodo 2.0, the multi-agent PR reviewer, for developers in 2026. Evaluate features, pricing, and workflow.
Atlas for Kotlin in 2026
In 2026, Atlas empowers Kotlin developers with terminal-native AI coding. It integrates with Gradle and coroutines, offering secure, privacy-focused code assistance with local embeddings and granular control.
Atlas vs Warp: Choosing Your AI Coding Agent in 2026
Compare Atlas, the terminal-native AI coding agent, with Warp, a smart terminal with AI Agent Mode, for developers in 2026. Evaluate features, privacy, and workflow.
Write Unit Tests for Untested Code with Atlas in 2026
How to write unit tests for untested code with Atlas in 2026: the lsp tool enumerates exported symbols, grep copies repo conventions, and bash actually runs the suite.
Atlas for React in 2026
Adopt Atlas, the terminal-native AI coding agent, for React development in 2026. Enhance your workflow with intelligent code search, refactoring, and testing for React components and hooks.