Virtual Browser Consumption & Pricing
When your agent needs to act like a human in a real browser — filling forms, clicking through pages, solving anti-bot challenges, or scraping hard targets — ToothFairyAI runs a Virtual Browser for the session. This page explains how that browser session is metered and billed in UoI, and how IP rotation works and what it costs when you enable it.
The Virtual Browser is optional: your agent uses it only when browsing is required for the task.
What is the Virtual Browser?
- A real browser instance, launched per session in our managed cloud — one dedicated browser per session.
- Each session runs isolated on its own virtual worker.
- It is metered by wall-clock time from the moment the session starts until it ends (including waiting on pages and any anti-bot solving).
Because one browser session uses one dedicated worker, you pay only while a session is actually running. There is no idle, standing, or per-request charge for the browsing itself.
How the Virtual Browser is priced
Billing is per-second, metered end-to-end, and is always drawn from your UoI credit balance (the same credits you use for LLM calls, images, etc.).
| Component | Detail |
|---|---|
| Meter | Wall-clock seconds of the browser session |
| Billing | To the nearest second |
| Currency | 1 UoI = $0.01 USD, drawn from your pre-paid credit balance |
Indicative rate
| Item | Approx. cost |
|---|---|
| Virtual Browser session | ~1 UoI per minute of session time |
A typical short task (load a few pages) runs in the low single-digit UoI range. Longer flows simply accrue more seconds at ~1 UoI per minute. This is a reliable planning guide; the exact per-second rate is calibrated to our infrastructure cost and may drift slightly with cloud pricing.
What counts toward the session clock
- Page loads and navigation
- Clicking, typing and scrolling
- Anti-bot challenge solving
- Waiting on slow pages
The clock stops when the session ends.
IP Rotation
Some sites (e.g. travel and booking sites, or challenge-heavy sites) block on IP reputation — a shared or over-used address can be flagged even from a fully genuine browser.
The setting
IP setting is controlled by a per-agent flag and is off by default.
| Value | Effect |
|---|---|
| Off (default) | The session uses a normal connection. No IP rotation is used and no rotation cost is charged. |
| On | The session routes through residential IPs with intelligent rotation, and rotation usage is billed (see below). |
Enabling it is deliberate and billed; leaving it off means no rotation is used and nothing for it is charged.
How rotation behaves
When IP rotation is on, the session:
- Tries a fresh IP when blocked. If a site shows a challenge or block, the session retries from a different IP each attempt, giving the best chance of finding a clean address.
- Keeps a working IP. Once a page loads successfully, that IP is kept for the rest of the session, so the site treats it as a consistent, returning visitor and does not keep re-challenging.
In plain terms: it switches IPs to get past a block, then stays on one IP once it is in — which minimises both blocks and repeated challenges.
What you can expect on a protected site:
| Scenario | With IP rotation ON | With IP rotation OFF |
|---|---|---|
| First visit | Usually loads normally | May load normally or be challenged |
| A block is detected | Retries from a fresh IP automatically | Keeps the same IP; if flagged, stays flagged |
| After a successful load | Keeps the working IP, no repeat challenges | Same single IP; may keep being challenged if it is flagged |
| Heavy or repeated requests | Spread across many IPs, less likely to be throttled | Same IP; more likely to be throttled or blocked |
What IP rotation costs
Rotation is charged only while the setting is on, as a separate line on the same session's UoI bill, measured by the data transferred through the proxy.
Indicative rate:
| Item | Unit | Approx. cost |
|---|---|---|
| IP rotation traffic | per GB | ~350 UoI / GB |
In practice, browser pages transfer only a few MB each, so real-world rotation usage is usually a small fraction of a gigabyte:
| Session | Approx. data | Approx. rotation cost |
|---|---|---|
| A simple page | ~5 MB | ~2 UoI |
| A longer multi-page task | ~30 MB | ~10 UoI |
| A heavy, large-scrape task | ~150 MB | ~50 UoI |
The rotation cost scales with how much data you actually pull through it. Light browsing is a small add-on; very large scrapes can rival the browser-time cost. It is present only when IP rotation is enabled on that agent — with it off, no rotation cost is charged at all.
A worked example
A short task on a protected booking site with IP rotation on — ~3 minutes of session time and ~30 MB through the proxy:
| Line item | Amount | Cost |
|---|---|---|
| Browser session (~3 min @ ~1 UoI/min) | 3 min | ~3 UoI |
| IP rotation (~30 MB @ ~350 UoI/GB) | 30 MB | ~10.5 UoI |
| Total | ~13.5 UoI ≈ $0.135 |
Running the same task with IP rotation off charges only the browser line (~3 UoI) — no rotation cost appears.
Observability
Both the browser time and any IP-rotation traffic appear in your workspace dashboard usage view as part of the agent's consumption, so you can see exactly what a session cost and how much was browser time vs. rotation, session by session.
Summary
- The Virtual Browser is a real, per-session browser billed by the second (~1 UoI per minute).
- IP rotation is off by default; enabling it routes traffic through rotating residential IPs to reduce blocks from IP reputation.
- Rotation is billed only when enabled, per GB at ~350 UoI / GB.
- Both appear on the same session's UoI bill — there are no standing or subscription charges; you pay only for the browser time and rotation traffic you actually use.