Token Prices Fell. AI Bills Did Not.

A vendor cuts its published token price 40 percent. Finance books the saving against next quarter. A quarter later the AI bill is up 156 percent, and no one did anything wrong. The price cut caused it.

This is Jevons paradox, and most cost essays stop there: make a resource cheaper and people consume more of it, often enough to raise total spend. True, and the dull half. The sharp half is that the token was never the expensive part of the work, so you are watching the wrong number deflate while the right number multiplies.

Price the task, not the call

A token price is the vendor’s unit. A completed task is yours, and the two barely overlap. Take a contract-redline workflow run by an agent. Tag every span with one task ID and let it propagate through orchestration, retries, and tool calls; most tracing stacks already do this, so you are adding one OpenTelemetry attribute and one join against the review log, not building a cost system. Each model call reports its tokens and cost against that ID, and you sum them. The review queue logs minutes against the same ID, and you multiply by a loaded labor rate. One finished task then reads:

• 11 model calls, 190K tokens, $0.46 of inference
• 7 reviewer minutes at $90/hour loaded, $10.50 of labor

$10.96 a task. Inference is four percent of it. Cut the token price 40 percent and the task drops to $10.78. The line finance celebrated moved eighteen cents. Everything that actually costs money lives in the other 96 percent: the retries, the context reassembled on every call, the human who reads the output before it ships. None of it shows on a per-token dashboard, and all of it scales with usage.

That split, labor dwarfing inference, holds wherever a human still reviews each output. Strip the reviewer (a fully autonomous, high-volume pipeline) and the mix inverts: inference becomes the dominant cost, and a 40 percent token cut is suddenly real money. The rule is not that tokens never matter. It is that you cannot tell which regime you are in until the task, not the token, is the unit you count.

Where the bill actually goes

Cheaper inference does not reduce demand. It removes the brake on it. The moment the task got cheap, the team pointed the agent at three more queues, and monthly volume went from 50,000 tasks to 130,000. Reviewer load scaled right with it, and newly automated work needs more review, not less, because the messy cases are the ones that were too marginal to touch before. Run the arithmetic: 50,000 × $10.96 is $548K a month; 130,000 × $10.78 is $1.40M. The bill rose 156 percent while every line item got cheaper. The token savings were real. They were a rounding error against the consumption they unlocked.

What to instrument

Make cost per completed task the accounting boundary, put one owner on each workflow end to end, then:

• Route by value and risk. Expensive reasoning is scarce inventory, reserved for tasks that justify it; cheap paths take the rest. Multi-model routing is not a discount, it is a governor.
• Cap the loop. A hard ceiling on retries and tool calls per task, because an uncapped loop is an open invoice.
• Price the human in. A workflow that needs a reviewer every time is expensive whatever the tokens cost, and the dashboard should say so out loud.
• Compare on finished work. Rank vendors and routes by cost per finished task , not headline token rates, or you keep buying the cheaper token that triples the call count.

The trap was never that someone lied about the price. It is that the cheapest part of the work got cheaper, loudly, while the parts that actually move the invoice went uncounted.