Same model, different API route

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

Compare two fixed serverless endpoints for GPT-OSS 20B using the same token workload. 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.

FieldGroqCloudTogether AI
Pricing basisFixed provider endpointFixed provider endpoint
API model IDopenai/gpt-oss-20bopenai/gpt-oss-20b
Input / 1M$0.075$0.05
Cached input / 1M$0.037 / 1MNot published
Output / 1M$0.30$0.20
Published route context131,072 tokens128,000 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
Fixed provider endpoint

Together AI

$1.50 / month
Input cost
$0.50
Output cost
$1.00
Per 1,000 calls
$0.15
Cache pricing
Not published
View Together AI pricing

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

StackLens assessment

What to test before switching routes

  • The underlying OpenAI model is the same, but provider context limits and operating terms can differ.
  • Test rate limits, latency, regional requirements, and failure behavior before moving production traffic.
  • Neither tracked route lists an extra per-request charge in this comparison.
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.