The cost ticker
A running total the agent can't hide from.
Agentic products that don't show a live cost are products that are about to surprise you. A cost ticker isn't a feature. It's the minimum viable honesty of any system that can spend money, tokens, or time on the user's behalf.
The reason so few products ship one well is cultural. Pricing lives in billing; billing lives behind a modal; a modal is the least trusted surface in any product. A ticker drags the number into the main view and says: I are spending your budget right now, and I will tell you while I do.
"You can't trust a system that won't tell you the bill."
A corner number that tells the truth.
Put a single cost readout in the product chrome, visible at all times while an agent is running. Update it live as tokens stream and tools fire. Color-shift when the user's run is nearing the cap they set for themselves. Click-expand to a per-step breakdown — tool-by-tool, model-call-by-model-call, with real dollar amounts.
There is no elegant argument for hiding this. Products that try to hide it are either anxious about their cost structure or assuming the user doesn't care. Both are misreads.
- 01 · retrieve · docs.index$0.0018
- 02 · model · mid · draft$0.0094
- 03 · tool · browser.fetch$0.0072
- 04 · model · pro · refine$0.0261
- 05 · tool · email.compose$0.0004
The bill is part of the answer.
A user's trust in an agent has two inputs: the quality of the output and the cost of getting it. You can't separate them. A brilliant result that cost 40x what the user expected will feel worse than a mediocre result with a visible, proportional bill.
The ticker forces the agent to stay proportional to the task. An agent that knows the user can see the bill tends to take fewer detours.
The ticker I'd ship.
- Dollars, not tokens. Tokens are a unit the user doesn't have intuition for. Dollars are. Show both on hover if you must. Default to the unit that maps to the user's experience of value.
- A soft cap before a hard one. At 80% of the user's budget, warn with a persistent color change that requires an explicit dismiss. At 100%, halt. The user should never be surprised by the bill.
- Click-to-trace. Clicking the ticker opens the per-step breakdown. This is where the pattern earns its keep — a user who sees that one tool call was 60% of the bill can redirect the agent with information, not a guess.
Cost theater.
Some products ship a ticker that isn't real. It rounds aggressively, hides tool-call costs inside an ambient "platform fee," and under-reports compared to the bill that arrives at the end of the month.
If your ticker and your invoice disagree by more than a rounding error, you have a trust problem that a ticker alone won't solve. Fix the accounting first.
What this pattern gets wrong when it gets wrong.
- Silent cost bleed
- The product spends time, tokens, or money without surfacing the cost at the moment it is incurred.
- Runaway agent
- An agent that loops, spends, or edits past the user's intent with no visible cap.
- Throttle silence
- A rate limit, queue, or budget cap that silently slows or stops the product without telling the user why.
Three shipping variants worth copying.
- A corner counter that ticks as tokens stream, color-shifts near cap
- A per-step breakdown that reveals which tool call spent the most
- A soft cap that pauses the agent at 80% with a continue button