GPT-OSS 120B
GPT-OSS 120B is served by 2 providers that kRouter can route to, with a 128K-token context window. Because more than one provider offers it, the price you pay depends on which one you route to — the same request, the same model, different bills.
Where to get GPT-OSS 120B
| Provider | Route as |
|---|---|
| Groq | groq/openai/gpt-oss-120b |
| SiliconFlow | siliconflow/openai/gpt-oss-120b |
What GPT-OSS 120B is suited for
At 128K the window is modest, so it is better suited to focused edits than to long agent runs that accumulate history. It supports extended reasoning, which helps on debugging and multi-step planning but spends output tokens on thinking before the answer appears — worth knowing when you set max_tokens. Tool and function calling are supported, so it can drive an agent loop.
Specs
- Context window
- 128K
- Max output
- 64K
- Input / 1M
- —
- Output / 1M
- —
- Extended reasoning
- Tool / function calling
GPT-OSS 120B FAQ
How much does GPT-OSS 120B cost?
GPT-OSS 120B has no published per-token rate here — it is served through plans or free tiers rather than metered billing.
Which providers serve GPT-OSS 120B?
2 providers: Groq, SiliconFlow. Through kRouter you can switch between them by changing the route prefix, without changing your tool.
What is GPT-OSS 120B's context window?
128K tokens, with up to 64K tokens of output. kRouter publishes this on /v1/models as context_length, so clients read the real number instead of guessing from the model name.
Route to GPT-OSS 120B from any tool
kRouter runs locally and gives Claude Code, Cursor, Codex and the rest one endpoint that reaches every provider above — with automatic failover. Free and MIT-licensed.
Install kRouter