Open any AI provider's pricing page and you will see numbers like "$2.50 per million input tokens, $10 per million output tokens." If you have ever wondered what that actually means for your wallet, or how a token differs from a word, here is the plain explanation, along with some real numbers on how badly this can go wrong.
What a token actually is
AI models do not read in words, they read in tokens, roughly 3 to 4 characters or about three-quarters of a word in English. The standard method, called Byte Pair Encoding, builds a vocabulary by repeatedly merging the most common adjacent character pairs found in training text, which is why a word like "encoding" often splits into pieces like "encod" and "ing." As a rule of thumb used consistently across providers: about 4 characters, or 0.75 words, per token.
Why output always costs more than input
Every major provider charges more for what the model generates back to you than for what you send it, and the gap is consistent: current published rates put Claude Opus at $5 per million input tokens versus $25 output, GPT-5 class models around $1.25 in versus $10 out, and Gemini 3 Pro at roughly $2 in versus $12 out for smaller contexts. Output tokens cost four to six times more than input across every provider, because generating text is computationally heavier than reading it. Practically, this means a long, detailed prompt asking for a short answer is usually cheaper than a short prompt asking for a long one.
Where the real damage happens
This is not theoretical. Real, documented cases from 2025 and 2026:
- An Australian developer was hit with a $10,000 Google Cloud bill despite having set a $250 spending cap, because Google auto-upgrades new accounts to a $100,000 spending limit after just $100 of lifetime usage.
- One AWS Bedrock customer running Claude Opus received a bill between $30,000 and $38,000 against an expected few hundred dollars.
- A GitHub Copilot user's bill jumped from $29 a month to a projected $750 overnight when GitHub shifted from flat subscription pricing to token-based billing.
- A production AI agent project cost $15,000 a month at 500 users, three times the expected spend, because agentic workflows can burn 5 to 30 times more tokens than a simple chatbot exchange, thanks to retries, tool calls, and repeated context.
The mechanic behind the sneaky costs
Most chat-based tools resend the entire conversation history with every new message, so a long back-and-forth costs progressively more per message, not the same amount each time. One documented case found that by the 50th tool call in an agent session, resent conversation history alone exceeded 150,000 tokens, rebilled on every subsequent call. Retry loops compound this further, one analysis found a correction cycle that runs ten refinement passes on accumulated context can consume up to 50 times the tokens of a single clean pass.
Falling prices, rising bills
Here is the counterintuitive part: per-token prices have been falling roughly tenfold per year across the industry, and total enterprise AI spending is still rising. Global enterprise AI spend went from roughly $302 billion in 2025 to an estimated $407 billion in 2026, a 34.8% increase, because usage volume, especially from agentic workflows making many calls per task, is growing faster than the price per token is falling.
How to actually stay ahead of it
If you are using AI through an API rather than a flat subscription, the only reliable defense is watching usage as you go rather than checking an invoice after the fact. That is the exact gap our free AI Token Tracker tool is built to close, a live view of token usage while you work, so a surprise bill is not the first time you find out something went wrong.
