Agents Lookup

Learn / Practice

What agents cost to run: tokens, caching, batching

Why agents use more tokens than chatbots, a worked cost example for a support agent, and how caching, batching and model choice cut the bill.

Updated 2026-11-19. "(source N)" refers to the numbered list at the end.

You pay for tokens, many times over

Models are billed per token, a small chunk of text. On Anthropic's current tokenizer, a million tokens is about 555,000 words (source 10). There are separate prices for input you send and output you get back. Output is usually about five times dearer. Claude Sonnet 5.5, for example, costs $2 per million input tokens and $10 per million output (source 1).

Agents cost more than chatbots because they loop. Every step resends the instructions, the tool definitions and the conversation so far. Anthropic warns builders that agents trade higher cost and latency for better results, so the trade must be worth it (source 8).

Hidden extras

Watch for costs that do not show up in the headline price.

A worked example

Picture a support agent on Claude Sonnet 5.5. Each ticket takes 10 model calls. Every call sends a fixed 20,000 tokens of instructions, policy and tool definitions, plus about 5,000 tokens of conversation and tool results, and gets 600 tokens back. Prices are from Anthropic's pricing page (source 1).

Without caching, input is 250,000 tokens, which costs $0.50, and output is 6,000 tokens, which costs $0.06. That is about $0.56 a ticket, or $560 for 1,000 tickets a month.

Now add prompt caching for the fixed 20,000 tokens. The first call writes the cache at $2.50 per million, which costs $0.05. The next nine calls read it at $0.10 per million, which costs about $0.02. The changing 50,000 tokens still cost $0.10, and output is still $0.06. That comes to about $0.23 a ticket, or $230 a month, roughly 60% less.

Swap in Claude Haiku 5.5 for the same job and, at its base rate of $0.10 in and $0.50 out, the ticket costs under 3 cents before caching (source 1). Model choice is often the biggest lever of all, if quality holds.

How prompt caching works

Caching stores the start of a prompt so later requests can reuse it cheaply. It only works when the cached part is exactly the same each time, so put fixed content first and changing content last (source 2, source 5).

Easy ways to break the cache

Changing tool definitions, putting a timestamp near the top of the prompt, or switching settings such as thinking effort mid-conversation can all force a fresh, full-price read (source 2). Keep the top of the prompt boring and stable.

Batching: half price if you can wait

If the work does not need an instant answer, send it as a batch. Anthropic and OpenAI both charge 50% less for batch jobs (source 3, source 6). On OpenAI, GPT-6.2 Sol drops from $2 in and $10 out to $1 and $5 (source 4).

Good batch jobs

Overnight lead research, tagging last week's tickets, writing product descriptions for a new catalogue, and running your test suite all suit batch mode. Caching and batching can be combined on Claude for even bigger savings (source 1).

Other levers

Do the maths on paper before you build. A rough spreadsheet with calls per task, tokens per call and tasks per month will tell you whether an agent pays for itself long before the first invoice arrives.

Sources

Written by Agents Lookup in our own words. Facts come from these pages: