What Running an AI Agent Actually Costs Per Month

“It ran 20 times” is not a usable AI budget. Each run may contain one model call or 40, replay 5,000 tokens or 500,000, and finish cleanly or burn another full attempt after a tool error. That is why people who do not watch API logs line by line can receive a bill that feels unrelated to the work they saw.

This guide builds a realistic AI agent cost per month from the bottom up. The example is a research-and-reporting agent used by a consultant, operations lead, recruiter, or analyst—not a toy weather bot and not a million-user SaaS. If you are choosing a consumer plan instead, start with our AI subscription buyer's guide.

TL;DR: realistic monthly ranges

The five-line bill hiding inside one agent task

The useful equation is:

run cost =
  uncached input tokens × input rate
  + cached input tokens × cache-read rate
  + output and reasoning tokens × output rate
  + provider tool fees
  + third-party tool and infrastructure fees

Then:

monthly cost = successful runs + failed runs + retries + scheduled runs nobody used

The last term is uncomfortable. A scheduled agent that produces a morning report every day still spends money on holidays, low-value days, and reports nobody opens. Cost governance starts with asking whether a run should happen at all.

Worked example: a weekday research-and-reporting agent

Our agent receives a question such as “What changed in this market this week, what matters to our company, and what should we do?” It searches, opens sources, extracts facts, compares them with an internal brief, drafts a recommendation, runs a critique pass, and formats the deliverable.

One successful run has this approximate ledger:

Why 450K input tokens when the source pack is nowhere near that large? Because the agent does not send each fact once. The harness carries conversation history, tool results, instructions, and work product forward. Repeated context is the central concept behind our context-window pricing explainer.

Assume 180K of the input hits a discounted prompt cache and 270K is uncached. With a representative frontier rate of $5 per million uncached input tokens, $0.50 per million cached input tokens, and $30 per million output tokens—the July 2026 GPT-5.5 API rate—the model bill is:

uncached input: 0.270 × $5.00  = $1.35
cached input:   0.180 × $0.50 = $0.09
output:         0.051 × $30.00 = $1.53
model subtotal:                 $2.97 per successful run

Search, browser, document parsing, and storage may add separate fees. Use $0.20 per run as a transparent planning allowance rather than pretending every provider's changing tool price is identical. That produces $3.17 per clean run.

From $3.17 per run to the real monthly number

Twenty-two weekday runs cost $69.74 if every run succeeds once. Agents do not behave that way. Add a conservative 20% retry/failure overhead: timeouts, weak source sets, invalid tool arguments, a reviewer rejecting the first draft, or the harness repeating a stage after context compaction.

22 scheduled runs × $3.17 = $69.74
20% execution overhead      = $13.95
logging/storage allowance   = $5.00
realistic monthly total     = $88.69

That is the useful answer for this workflow: about $90 per month, not “$5 per million tokens” and not “20 runs.” It is cheap compared with professional labor if the reports are used. It is wasteful if most reports are generic, late, or unread.

Three model strategies, same workflow

Using the frontier model on all 20 calls is simple but rarely rational. Google states that its managed agents bill underlying inference—including intermediate input and reasoning tokens—plus tool usage. Its July 2026 Gemini API pricing lists Gemini 3.6 Flash at $1.50/M input, $0.15/M cached input, and $7.50/M output. Applying those rates to the same ledger gives:

0.270 × $1.50 + 0.180 × $0.15 + 0.051 × $7.50
= $0.8145 model cost per run

After the same tool allowance, 22 runs, and 20% overhead, the monthly estimate is roughly $27. That does not prove Flash produces the same report. It shows the question a budget owner should ask: which stages truly need frontier reasoning?

The middle strategy is usually the winner. Source triage, formatting, and straightforward extraction do not deserve the same model budget as reconciling contradictory evidence or writing the final recommendation.

Why your bill can be five times this example

Long context crosses premium thresholds

GPT-5.5 supports a 1.05M-token context window, but requests above 272K input tokens are priced at a premium for the full session. Anthropic also documents premium long-context rates above model-specific thresholds. Capacity and price are separate; a model accepting the payload does not mean the whole payload stays on the base rate.

Output and reasoning are expensive

In the GPT-5.5 example, 51K output tokens cost more than all 450K input tokens combined. Agents that narrate plans, produce verbose tool commentary, or regenerate entire reports instead of patching sections burn the expensive side of the rate card.

Tool results become future input

A browser fetch might be free or cheap as a tool action but expensive when 30,000 tokens of page text are inserted into five later calls. Tool pricing alone cannot tell you tool cost. Measure the downstream tokens it creates.

Retries repeat the expensive prefix

A retry at the final stage is not merely one more answer. If the harness sends the full transcript again, it repeats planning, sources, tool output, and draft context. Cache hits help, but cache misses turn “try once more” into a material budget event.

Parallel agents multiply before they save time

Five agents investigating five hypotheses can improve coverage. They can also run the same expensive search and reread the same brief five times. Parallelism is a latency decision with a cost multiplier attached.

Cost controls that do not ruin the agent

Start with visible budgets rather than vague instructions to “be efficient.” A production harness should enforce:

budget:
  max_steps: 24
  max_retries_per_step: 1
  max_input_tokens_per_run: 600000
  max_output_tokens_per_run: 65000
  max_tool_spend_usd: 0.50
  max_total_spend_usd: 5.00
  require_approval_above_usd: 3.00

Then log four numbers for each completed task: total dollars, total calls, wall-clock time, and human acceptance. Cost per call is operational trivia; cost per accepted deliverable is the business metric.

Prompt caching is valuable when instructions, schemas, reference documents, and tool definitions remain stable at the beginning of the prompt. It is not magic. Cache writes may carry a premium, cache reads expire, and a frequently changing prefix can miss. See OpenAI's prompt-caching explanation and Anthropic's pricing documentation before modeling savings.

Context compaction is the second lever. Save decisions and verified facts; discard duplicated search snippets, verbose logs, and abandoned branches. The goal is not the shortest prompt. It is the smallest state that lets the next action remain correct.

What people are really asking

Is $90 per month expensive?

Not if the agent produces 22 reports a professional uses. At a loaded labor cost of $60/hour, saving two hours a month clears the bill. But the comparison is not “agent versus employee.” Include setup, review, failures, governance, and the opportunity cost of maintaining the workflow.

Should I use a $20 subscription instead?

Use a subscription when a human is present and can operate the chat product. Use an API when software must run on a schedule, call tools, integrate with systems, or produce structured output. Trying to resell or automate a consumer session can violate terms and is operationally brittle; our AI token black-market investigation shows the ugly end of that shortcut.

Can open-weight local models make it free?

They remove per-token vendor charges, not cost. Hardware, electricity, latency, setup, monitoring, and weaker completion rates still matter. Our laptop open-weight model guide separates what fits from what merely downloads.

A monthly budget worksheet

Before deployment, fill these inputs:

Recalculate using the exact live model and tool rates, then set a budget alert at 50%, 80%, and 100%. If spend passes 80% halfway through the month, pause scheduled low-value runs before you downgrade model quality on important work.

The result is deliberately ordinary: a good weekday agent can cost tens of dollars, a frontier-heavy one around a hundred, and a badly bounded one almost anything. Token rates matter. Harness design decides whether those tokens become work.

Related on explainx.ai

• Context-window pricing decoded
• The $600/day Varick agent teardown
• AI token costs surge: finance and governance
• What is an agent harness?
• Top 10 open and closed-source agent harnesses
• Which AI subscription is worth paying for?
• OpenRouter's Web Search Benchmarks — why failed searches are the hidden cost driver

Rates and product rules were checked July 26, 2026. Worked totals are transparent planning examples, not quotes from a provider; taxes, regional pricing, enterprise contracts, and changing tool fees are excluded.