Agentic Context Tax
The agentic context tax is the way an AI agent's cost grows faster than its work: every tool call adds a turn, and each turn re-sends the whole conversation, so input tokens scale with roughly the square of the tool calls.
also: context tax · agent token cost · tool call cost
A single-shot LLM call bills the prompt once. An agent does not. Each tool call is another round trip where the model re-reads everything before it (the original prompt, every prior tool call, and every result) and then adds more. Sum that across turns and the input tokens grow with tool-calls × (tool-calls + 1) / 2, which is quadratic, not linear. Going from 3 tool calls to 6 does not double the input cost, it can multiply it several times over.
This is the line item most cost estimates miss, because they price one call and multiply by volume. It is also where the savings are: prompt caching (so re-sent context is not re-billed at full rate), trimming what each turn carries forward, capping the loop length, and summarising history instead of replaying it. Those levers attack the quadratic term directly, which is why an agent's bill can fall by more than half without changing the model.
faq
Questions & answers
- Why do AI agents cost so much more than a single LLM call?
- Because each tool call adds a turn and every turn re-sends the entire conversation so far before adding to it. Input tokens therefore grow with the square of the number of tool calls, so an agent that makes several calls per request pays many times the tokens of one prompt and answer.
- How do you reduce agent token cost?
- Cache the re-sent context so it is not billed at full rate each turn, carry forward only what later turns need, summarise history instead of replaying it verbatim, and cap the number of tool calls per request. These target the quadratic input growth, which is where most of the cost sits.
Want this applied to your stack, not just defined?
The free tools run the numbers; an audit tells you where the real cost and risk are. Book a call, or leave your email and I'll reach out.
Prefer proof first? See how this plays out in real case studies →