Unquant

Opening your workspace…

Unquant

Flat-rate vs per-token LLM APIs: when unlimited pays off

Per-token pricing looks cheap per request and gets expensive per month, because chat and agent workloads re-send their entire history every turn. Here is how to work out which model suits you.

Explainer2 min readUpdated 1 October 2026

Why token bills grow faster than you expect

Chat models are stateless: each request carries the whole conversation. A chat that has grown to 50,000 tokens sends those 50,000 tokens again on the next message, and the one after. Input tokens, not the replies, dominate most bills.

Three worked examples

These count tokens only; multiply by any provider's per-million price to see the bill.

Roleplay with a 60K-token history~91Mtokens a month~60K in, ~600 out per turn · 1,500 (50 a day) turns
Coding agent in a large repo~363Mtokens a month~120K in, ~1K out per turn · 3,000 (100 steps a day) turns
Analysing 200K-token documents~61Mtokens a month~200K in, ~2K out per turn · 300 (10 a day) turns

At tens to hundreds of millions of tokens a month, even low per-token prices add up quickly, and you only find out at the end of the month. Prompt caching discounts help where offered, but they vary by provider and usually still bill cached tokens.

What flat rate changes

  • Predictable costthe price is the same whether you send ten messages or ten thousand.
  • No self-rationingyou stop trimming context or avoiding regenerations to save money, which is usually what makes output worse.
  • Concurrency is the limit, not volumea plan sets how many requests run at once. Within that, use is unlimited.

When per-token is the better deal

Honestly: if you send a handful of short requests a week, pay-as-you-go will be cheaper. If you need dozens of requests in parallel for batch processing, per-token providers scale wider. Flat rate wins for sustained, interactive, long-context use: roleplay, writing, coding agents and research.

How Unquant prices it

Every plan includes unlimited tokens and messages; tiers differ by model, context window and concurrent streams. See all plans.

Keep reading