induwara.lk
induwara.lkDevelopers · AI

AI Computer-Use / Browser-Agent Cost Calculator

Estimate what a screenshot-per-step computer-use or browser agent costs to run. Every step re-sends the whole transcript — so cost climbs super-linearly with the number of steps. Price it across Claude and OpenAI, and see how screenshot pruning and caching cut the bill. No signup, no API key, nothing leaves your browser.

By Induwara AshinsanaUpdated Jul 11, 2026
Computer-use run cost

Price shown is input / output per 1M tokens. High-res models cap screenshots higher.

Options
CBSL indicative

320–2576

240–2576

Screenshot loops (1–500)

Tokens, re-sent every step

Assistant action tokens

Screenshot retention

Pruning old screenshots is the biggest lever on cost.

Quick presets
Cost per run
$1.11
no caching
Cost per run (LKR)
Rs 338
at Rs 305/USD
Total input tokens
354,860
3,000 output tokens
Image tokens / shot
1,366
× 20 in the final request

Each 1,280×800 screenshot ≈ (1,280 × 800) / 750 = 1,366 tokens (capped at 4,784 for high-res models).

Where the cost goes

Screenshots77.56%
System + tools8.11%
Replayed text10.27%
Output4.06%

How to cut the bill

Keep all screenshots
$1.11
Keep last 3 screenshots
$0.482656.51%
Keep all + prompt caching
$0.241778.22%

Anthropic recommends keeping only the last few screenshots for exactly this reason.

Per-step breakdown

StepScreensInput tokensStep costCumulative
112,866$0.0108$0.0108
224,432$0.0155$0.0264
335,998$0.0202$0.0466
447,564$0.0249$0.0716
559,130$0.0296$0.1012
6610,696$0.0343$0.1356
steps 715 hidden — input keeps climbing each turn
161626,356$0.0813$0.7373
171727,922$0.0860$0.8233
181829,488$0.0907$0.9141
191931,054$0.0954$1.01
202032,620$0.1001$1.11
Total354,860$1.11

The final step alone sends 32,620 input tokens versus step 1's 2,866.

Same task, every model

ModelImg tokensPer runPer run (LKR)
Claude Haiku 4.5
1,366$0.3699Rs 113
OpenAI computer-use
1,105$0.9362Rs 286
Claude Sonnet 5selected
1,366$1.11Rs 338
Claude Opus 4.8
1,366$1.85Rs 564

Sources cited: Anthropic vision, computer-use, pricing & prompt-caching docs (authoritative for Claude) and OpenAI computer-use / vision docs (transcribed, dated 2026-07-11). Full links are in the Sources & references section below. All figures are estimates from the parameters you enter — this tool does not call any API and sends no data anywhere.

How it works

A “computer use” or browser agent works in a loop: take a screenshot, send it to the model, the model replies with an action (click, type, scroll), you execute it, take a new screenshot, and repeat. The catch is that the API is stateless — on every step you re-send the entire conversation so far: the system prompt and tool definitions, plus every prior screenshot and every prior assistant action. Screenshots are billed as image tokens, so the run accumulates a large, growing bill.

Image tokens per screenshot.Anthropic's vision documentation gives the formula img = ceil(width × height / 750), capped at about 1,600 tokens on standard-resolution models and about 4,784 tokens on high-resolution models (Opus 4.8, Sonnet 5, long edge up to 2,576px). A 1280×800 screenshot is therefore about 1,366 tokens. OpenAI's computer-use model uses a tiled formula instead — roughly 85 base tokens plus 170 per 512×512 tile — so the same screenshot lands at a different token count, which the comparison row makes explicit.

Per-step and total input. Let S be the system-plus-tools tokens, img the image tokens per screenshot, A the average output tokens per step, and T a fixed 50-token tool-result envelope. Keeping every screenshot, step N sends S + N × img + (N − 1) × (A + T) input tokens; pruning to the last K replaces N × img with min(N, K) × img. Summing over all steps gives the total input; total output is simply steps × A. Cost is input/1e6 × rate_in + output/1e6 × rate_out, using each model's per-million rate from the pricing docs.

The two levers.Because the screenshot term grows with the square of the step count, keeping every screenshot is what makes long runs expensive. Anthropic's computer-use guide recommends pruning to only the last few screenshots — the calculator prices that directly. Prompt caching is the second lever: the stable prefix carried over each turn reads at 0.1× of the input rate after a one-time 1.25× write, per Anthropic's prompt-caching economics. The calculator applies the closed-form total and cross-checks it against a step-by-step summation, so the numbers reconcile to the token.

Worked examples

20-step task · Sonnet 5 · keep all screenshots

  1. Screenshot 1280×800 → 1,024,000 / 750 = 1,366 image tokens (< 4,784 cap)
  2. S = 1,500, img = 1,366, A = 150, T = 50
  3. totalInput = 20×1,500 + 1,366×210 + 200×190 = 354,860 tokens
  4. totalOutput = 20 × 150 = 3,000 tokens
  5. Cost = 354,860/1e6 × $3 + 3,000/1e6 × $15 = $1.065 + $0.045 ≈ $1.11 / run

Same task · keep last 3 screenshots (pruning)

  1. Σ min(N, 3) for N = 1…20 = 1 + 2 + 3×18 = 57 screenshots billed
  2. totalInput = 30,000 + 1,366×57 + 38,000 = 145,862 tokens
  3. Cost = 145,862/1e6 × $3 + $0.045 ≈ $0.48 / run
  4. That is a 57% cut from screenshot pruning alone — no quality change to the model.

Edge case · Opus 4.8 · 1920×1080 high-res

  1. Screenshot 1920×1080 → 2,073,600 / 750 = 2,765 image tokens (< 4,784 cap)
  2. totalInput = 30,000 + 2,765×210 + 38,000 = 648,650 tokens
  3. totalOutput = 3,000 tokens
  4. Cost = 648,650/1e6 × $5 + 3,000/1e6 × $25 = $3.243 + $0.075 ≈ $3.32 / run
  5. Higher resolution and the pricier model both push image cost up — visible in the breakdown bar.

Frequently asked questions

Sources & references

Rates and formulas on this page were last cross-checked against the sources above on 2026-07-11. The Claude figures are authoritative; the OpenAI row is transcribed and dated, since provider prices change. Every worked example is reconciled by hand in the module source.

Related tools

Rate this tool
Be the first to rate

Comments & feedback

Spotted a bug or want an improvement? Tell us — our team reviews every comment, and good ideas get built. Comments are public and anonymous.

Found a bug, edge case, or want to suggest an improvement?

Email me at [email protected] — most fixes ship within 24 hours.