Start with the model and the job you need to finish. For GPT-OSS 120B, one billion total tokens at a 5:1 input-to-output ratio costs $225 on Groq, $281.67 on SambaNova and $416.67 on Cerebras using the published rates checked on 29 October 2026. These are calculated token charges, before tax and extras. They do not establish which service returns an acceptable answer fastest, or which production tier you can actually buy.
Our recommendation is to shortlist on model access, measure your own response deadline and acceptance rate, then compare the bill for that workload. Groq has the lowest token charge in the 5:1 example. SambaNova narrowly undercuts it in the output-heavy example below. Cerebras's higher published developer rate needs a workload-specific benefit and a separate check of production terms. None of these calculations is a hands-on performance test.
Check access before comparing prices
The same vendor name does not guarantee the same model, service tier or contract. We use GPT-OSS 120B here because it appears in all three vendors' current model documentation. Confirm the exact endpoint and your account's access before building a production dependency.
Provider
GPT-OSS 120B endpoint
Access check
Groq
openai/gpt-oss-120b
Listed as a production model; account limits still apply.
SambaNova
gpt-oss-120b
Listed in the production model catalogue; check account capacity.
Cerebras
gpt-oss-120b
Listed in Shared Inference. The pricing page labels Developer for exploration, with production workloads under Enterprise.
INTERACTIVE 2026 BENCHMARK · WORKLOAD SIMULATOR
Interactive Groq LPU vs Cerebras Cost Simulator
Simulate your exact volume, calculate live effective costs, and evaluate overage fees for Groq LPU vs Cerebras.
⚡
Simulate Your Monthly Volume
Adjust slider or choose presets for million tokens / mo:
million tokens / mo
🏆Groq LPU (Llama 3.3 70B) is cheaper for this workload: save $58/mo ($696/year) compared to Cerebras (Llama 3.3 70B).
If you specifically need Llama 3.3 70B, do not substitute the older three-way price table. Groq's current catalogue marks that model Enterprise with Contact Sales pricing, while Cerebras's shared catalogue does not list it. That does not prove the model is unavailable under every enterprise agreement; it means a comparable self-service offer has not been established here.
Verified rates and the one-billion-token calculation
Prices below are USD per one million tokens, checked on 29 October 2026. We use ordinary uncached input rates, with no free credit, batch discount, tool call, tax or enterprise commitment deducted. Output means all billable output tokens in the scenario, not a promise about the length of the visible answer.
Formula: cost = input millions × input rate + output millions × output rate. One billion total tokens at 5:1 contains 833.333333 million input and 166.666667 million output tokens. Equivalently, cost per billion = (5 × input rate + output rate) ÷ 6 × 1,000. Round the final amount, not the token allocation halfway through the calculation.
For a monthly workload of 100 million input and 20 million output tokens, the same arithmetic gives $27 on Groq, $33.80 on SambaNova and $50 on Cerebras Developer. Ten times that usage costs $270, $338 and $500 respectively. These totals scale the assumed usage; they do not demonstrate that the purchased tier can process it at your required concurrency.
Your input/output mix can change the cheapest provider
A price ranking needs a defined workload. The following are three authored examples, each with one million requests. They count every assumed billable token and exclude retries, tools, cache savings and discounts.
Tokens per request
Groq / 1M requests
SambaNova / 1M requests
Cerebras Developer / 1M requests
1,000 input + 100 output
$210
$279
$425
500 input + 500 output
$375
$405
$550
100 input + 1,000 output
$615
$612
$785
SambaNova's input rate is $0.07 higher than Groq's per million, but its output rate is $0.01 lower. Their uncached token charges are equal when output volume is seven times input volume. Above that ratio SambaNova is cheaper on these rates; below it Groq is cheaper. The $3 difference in the last row is small enough that quality, retries or an existing discount could outweigh it. Recalculate with your actual usage rather than choosing a provider from a single headline rate.
Output speed is not a response-time measurement
A tokens-per-second figure describes only part of the wait. Artificial Analysis's methodology distinguishes time to first token, output speed after the first token, and complete response time. Its definitions also distinguish time to the first answer token for reasoning models. That distinction matters when a user is waiting for an answer or an agent must wait before its next action.
Measure
Question it answers
What to record in your trial
Time to first token / first answer token
When does something useful start arriving?
Separate reasoning output from the answer a user can read.
Output speed
How fast are tokens generated after output starts?
Model, tokenizer, input length, output length and concurrency.
Complete response time
When can the application use the finished result?
Elapsed request time, including failures and retry delay.
For example, 500 output tokens ÷ 500 tokens/second = 1 second of calculated generation time. It is not a measured one-second response. A separate assumed 0.8-second first-token delay would make an approximate total 1.8 seconds under a simplified steady-speed model. Input tokens are not added to the output-token numerator. Real streaming timings, reasoning behaviour and tokenization can change the result.
We do not publish a current measured speed winner here. The earlier throughput figures did not retain enough dated workload evidence to support a reproducible three-way ranking. Current vendor speed claims should not be combined with an older independent measurement and presented as one controlled test.
What would justify paying more?
Use the 500-input/500-output example: Cerebras Developer's calculated token charge exceeds Groq's by $175 per million requests. If your own trial finds a one-second improvement on each accepted response, the token premium is $0.000175 per request-second saved. The one-second improvement is an assumption for this example, not a result we observed. A production quote, rejected outputs or retries can change both sides of that comparison.
For an interactive assistant, define the deadline for the first usable answer and the finished response. For a background job, compare completed jobs per hour and cost per accepted result. For an agent, time the entire sequence, including tool calls: faster token generation cannot remove a slow external action. Do not assign financial value to saved seconds unless your application can actually use that time.
A small comparison you can reproduce
Freeze the task. Use the same prompts, model family, reasoning settings, output constraints and acceptance rubric. Record any provider-specific differences.
Run at the load you need. Test the intended concurrency and region, separate cold and warm cases, and retain timestamps and request IDs. A single fastest response is not a service guarantee.
Count failures. Keep throttled requests, timeouts, malformed tool calls and rejected answers in the results. Report typical and slow-tail completion times, not only the fastest successful run.
Reconcile the bill. Record charged input, cached input and output tokens from usage records. Divide total cost, including retries, by accepted results. Add any fixed commitment and required operational work.
These are proposed trial steps. We have not run paid API tests or certified that any provider meets your latency, quality, security or availability requirements.
Before you commit
Ask for the exact production model, tier, capacity, retention terms and payable rate. Keep a fallback for unavailable models and rate limits. Free trials are useful for initial checks; their credits and limits should not be treated as recurring production capacity. You can compare other routing choices in the inference-provider cost guide, and apply the same explicit workload rules in our calculation methodology.
Decision: start with Groq's lower charge for the illustrated input-heavy workloads, consider SambaNova when the billable mix is strongly output-heavy, and test whether a Cerebras production offer earns its premium on your real task. Choose on accepted results within your deadline, with the actual contract and bill beside the speed measurement.
Frequently asked questions
Is Groq cheaper than OpenAI for high-speed inference?
Groq offers significantly lower latency (often 200 to 500+ tokens per second on open models like Llama 3) and competitive per-token pricing compared to proprietary models, but self-hosting or dedicated hardware becomes more economical than on-demand API tiers only once monthly request volumes sustain multi-billion token throughput.
How does Cerebras compare with Groq on large context workloads?
Cerebras wafer-scale engine architecture provides consistent high throughput without standard memory bandwidth bottlenecks, making it particularly advantageous for long input prompts and large batch workloads, whereas Groq LPUs excel at near-instant first-token and streaming generation speeds on modest context lengths.
Do high-speed inference providers charge for cached prompt tokens?
Prompt caching pricing varies: while Groq and SambaNova support standard open weights pricing with reduced rates for cache hits, always check your model endpoint's specific cache duration and cache write versus cache read billing policies before deploying multi-turn agent loops.