Guides / qwen3.6 27b pricing

Qwen3.6 27B pricing, and a costly pairing

Qwen3.6 27B pricing on Groq is $0.60 per million input tokens and $3.00 per million output tokens, a five-to-one spread, and the price book records no cached rate for it. A model tuned to reason out loud on a five-times output spread with no cache is the most expensive combination here. Culpa, a local-first LLM cost, margin, and forecast ledger, meters output tokens per feature so the reasoning is priced.

Why this happens

Two facts about this model compound rather than add. The output spread is five to one, which is frontier territory rather than open-weight territory, so anything that lengthens a response is expensive. And there's no cached rate to soften the input side, so a repeated system prompt pays in full on every call. A reasoning-tuned model naturally produces long outputs, which is the behaviour the price shape punishes hardest, and the usual escape route of caching the repeated block is closed.

What this usually looks like

  • Output tokens per call here run well above your other open-weight models.
  • A repeated system prompt goes out on every call with no cached rate to reduce it.
  • Reasoning was enabled once for quality and its cost was never separated from the answer's.
  • This model's bill is dominated by output while its call count looks unremarkable.

Free, no card, no account

Run the free Cost Leak Scan

It shows your most expensive conversation before you install anything.

Run a free scan

Mistakes that cost the most

MistakeWhy it hurtsDo instead
Treating this like the other open-weight models on cost shape.Its five-to-one spread is closer to a frontier model than to the flat ratios beside it.Price it on the output side and set a max token limit that reflects what you render.
Leaving reasoning on for tasks that don't need it.Reasoning tokens bill as output at five times input and most of them never reach a user.Enable it per task rather than globally, and measure the quality difference on each.
Planning around a cached rate that isn't there.A forecast assuming a cached discount reads low by whatever share of your input repeats.Price the repeated prefix at full input rate, then decide whether to shorten it instead.

Run this check tonight

  1. Compare output tokens per call here against your other models on similar work.
  2. Separate reasoning output from delivered answer length. Only one of them reaches a user.
  3. Price your repeated prefix at full input rate, since no cached rate applies.
  4. Test the same task with reasoning off and score the difference honestly.
  5. Check whether a flatter-ratio model on the same platform would do this work.

What reasoning costs on a five-to-one spread

Illustrative example

12 million input tokens a month, of which 9 million is a repeated prefix, and 4 million output, on Qwen3.6 27B at real Groq rates. Volumes are modelled.

Base month: (12 x $0.60) + (4 x $3.00) = $7.20 + $12.00 = $19.20
Output is already 63% of the bill on a quarter of the tokens
The 9M repeated prefix bills at full rate, 9 x $0.60 = $5.40, with no cached rate available
Turn reasoning on and output doubles to 8M: $7.20 + $24.00 = $31.20
That's a 63% increase in total spend from the output side alone

Output is already most of the bill before reasoning, and enabling it adds another 63%. With no cached rate to work on the input side, the only lever left is how much the model says.

Every number, with its confidence and source

FigureWhat it meansConfidenceSource
$0.60 / $3.00 per millionQwen3.6 27B input and output rates on GroqcalculatedPrice book row for groq/qwen/qwen3.6-27b, $0.0006 and $0.003 per 1k, effective 2026-07-02, re-verified against Groq's rendered pricing page 2026-08-01.
5.00xoutput rate as a multiple of input, the widest of any Groq model in this price bookcalculated$3.00 divided by $0.60, from the same price-book row.
$19.20 to $31.20modelled monthly cost with reasoning off and on, at identical input volumeestimatedBoth endpoints from the teardown arithmetic at real Groq rates. A range because the token volumes are modelled.

What a generic answer can’t know

A rate card can tell you output costs five times input. It can't tell you how much of your output is reasoning nobody reads, or which feature turned it on. That split lives in your own call records. Culpa keeps them on your infrastructure, where your prompts and responses stay, and counts the calls to run your plan.

Questions founders ask next

How much does Qwen3.6 27B cost on Groq?

$0.60 per million input tokens and $3.00 per million output, re-verified against Groq's pricing page on 2026-08-01. The price book records no cached rate for it and Groq's page lists none.

Why is this model's price shape awkward?

Because a five-to-one output spread and no cached rate work against each other. Long responses are expensive and the usual fix of caching the repeated input isn't available, so both of the standard levers are weakened at once.

Do reasoning tokens count as output?

On most providers, yes, and they bill at the output rate whether or not a user ever sees them. On a five-to-one spread that makes reasoning the single most expensive setting you can leave switched on by default.

On your infrastructure

Culpa runs on your infrastructure. Your prompts and responses never leave it. Culpa counts calls to run your plan, and it fails open, so if it ever breaks your app keeps running.


How Culpa works

Find the culprit. Not just the total.

Your dashboard shows what you spent. It stops short of who spent it. Culpa shows the conversation, the user and the feature behind it.

Your prompts stay local.

Culpa runs on your own infrastructure. What you send to a model reaches us at no point.

Every dollar has a name.

Follow any charge to the conversation, the user, the feature and the customer behind it.

See the bill before it lands.

Cost your next feature before you ship it. You get the likely bill and the worst case, at best, median, p90 and p99.

Three steps to your first answer.

1

Change one base URL.

Or drop in the Python or TypeScript library.

2

Find your most expensive conversation.

In the first session, not the first week.

3

Cost your next feature before you ship it.

Base URLhttp://localhost:4545/v1Your traffic keeps flowing if Culpa ever stops.

Why the bill went up

Example dashboard

Calls traced

418,209

across 3 projects

Spend this week

$378.41

+ $182 vs last week

Failed calls

312

74% retried, and you paid for all of them

+ $182 this week traced to one culprit

Spend over 14 days

$0$20$40$60$8024262830020406
user_384report_generatorconv_91fprompt_v1894,220 tokens3 retries$6.81

Most expensive users

user_384$38.42
user_119$21.07
user_562$14.90
user_204$8.30
user_871$5.10

Next week forecast

Best$180
Median$240
p90$310
p99$395

Graded against reality. Accuracy shown as results land.

Free, no card, no account

Run the free Cost Leak Scan

It shows your most expensive conversation before you install anything.

Run a free scan

Keep reading


Sources: Groq pricing. Last reviewed 2026-08-01, rates effective 2026-07-02. Plain text version.