Same model, different API route

GPT-OSS 20B: GroqCloud or OpenRouter for lower API cost?

Compare a fixed GroqCloud endpoint with OpenRouter's current lowest catalog rate for GPT-OSS 20B. This comparison holds the model and token workload constant; it does not assume identical infrastructure, latency, or service limits.

OpenAI modelSources checked 2026-07-15
Official route fields

Provider pricing and route limits

Prices are USD per 1M tokens. “Not published” means the official tracked source does not expose that field.

FieldGroqCloudOpenRouter
Pricing basisFixed provider endpointCurrent catalog floor
API model IDopenai/gpt-oss-20bopenai/gpt-oss-20b
Input / 1M$0.075$0.03
Cached input / 1M$0.037 / 1M$0.03 / 1M
Output / 1M$0.30$0.13
Published route context131,072 tokens131,072 tokens
Published maximum output65,536 tokensNot published
Editable workload

GPT-OSS 20B monthly API cost

Token inference only. Provider payment, BYOK, tool, storage, and untracked request fees are excluded.

Fixed provider endpoint

GroqCloud

$2.25 / month
Input cost
$0.75
Output cost
$1.50
Per 1,000 calls
$0.225
Cache pricing
$0.037 / 1M
View GroqCloud pricing
Current catalog floor

OpenRouter

$0.95 / month
Input cost
$0.30
Output cost
$0.65
Per 1,000 calls
$0.095
Cache pricing
$0.03 / 1M
View OpenRouter pricing

OpenRouter is $1.30 lower per month for the default workload. This is a route-price result, not a service-quality ranking.

Additional fee boundary: OpenRouter credit purchases currently carry a separate 5.5% fee with a minimum charge. The token estimate below does not add payment or BYOK fees.
StackLens assessment

What to test before switching routes

  • OpenRouter's displayed model price can reflect the lowest available underlying route and may change with catalog routing.
  • OpenRouter credit-purchase or BYOK fees are separate from the token estimate.
  • Use provider pinning and fallback settings when predictable routing matters.
Same-model boundary

What this comparison controls

Both routes call OpenAI's GPT-OSS 20B using the published API model string. Provider infrastructure, quantization, request limits, routing, retention controls, and operational behavior can still differ.