Your token bill is the cheap part: dimensioning the real cost of an agent
Originally published on Loop & Retry — field notes on building LLM agents that survive production. The token bill is the cost you can see, because the provider mails you an invoice for it every month. So that's the number that gets optimized: people switch models, trim prompts, cache prefixes, and celebrate a 30% drop in spend. Meanwhile the same agent is holding a worker process open for ninety…
The token cost is just the visible expense, as providers send monthly invoices detailing it. The focus is on optimizing this number by tweaking models, condensing prompts, caching prefixes, and so on. However, the true cost of an agent includes more factors that aren't reflected in the invoice. These include latency, orchestration and infra costs, tool-call fees, human-in-the-loop processes, and idle/polling expenses.
Notably, token costs often represent only a small fraction of the total expense. The post presents a checklist of six factors an agent consumes, and calculates the cost for each across a typical task.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — it may contain errors, so check the original before relying on it.
