Scraping API PricesAll products / Anchor Browser
Anchor Browser pricing
How Anchor Browser bills task and infrastructure usage, what buyers cannot verify publicly, and which workloads fit.
published session-time meter only
Fixed for this page; volume is the control.Every available option was priced in advance from published vendor rules. Changing a control only switches between those checked options; nothing is sent anywhere and no account is needed.
Your job
What Anchor Browser counts
What you pay
Successes you want
200 browser hours
Your stated workload. Every vendor on this site is priced against this same number.
- ÷ 1
Attempts you are billed for
200 browser hours
Anchor Browser bills failed fetches. This workload assumes none fail, so nothing is added here.
- × 1
What the meter counts
200 browser_hours
One attempt is one billed unit for this workload.
- =
Cash per month
$200.00 /mo
Starter. Cheapest of every eligible purchase option, not the first plan that fits.
Bars share one linear scale across the 3 counted stages, so a multiplier shows as length. Units differ by stage and are labelled. Cash is not on that scale.
200 browser hours → 200 browser_hour → Starter $200.00/mo = $1.00 per browser hour
Cheaper for this job
Same 200 metered browser-session hours a month, excluding separate proxy and model charges, ranked by what you would actually be billed. Unknown totals never enter the numeric order.
Every Anchor Browser plan
| Plan | Monthly | If billed yearly | Prepaid pack | Included | Simultaneous sessions |
|---|---|---|---|---|---|
| Starter your job | $50.00 | n/a | n/a | 50 credit | 25 |
| Team | $500.00 | n/a | n/a | 500 credit | 50 |
| Growth | $2,000.00 | n/a | n/a | 2,000 credit | 200 |
What consumes a unit
This is where a bill actually grows. One operation is not one billed unit, and the multiplier is published here rather than on the pricing page.
| Operation | Costs | Per | Source |
|---|---|---|---|
| request.ai_extraction | 0.1 credit | task | source |
| browser.session_time | 0.05 usd | browser_hour | source |
| proxy.residential_bandwidth | 8 usd | gb | source |
| compute.unit | 0.01 usd | step | source |
What Anchor Browser does not publish
- Failure billing across task and infrastructure modes is not fully published.
- The public docs omit the Team plan that appears on the homepage.
- The homepage calculator and billing docs disagree on browser-hour price.
What Anchor Browser is
Anchor Browser provides hosted browser infrastructure for computer-use agents, including browser sessions and a task-oriented automation layer. It is for teams that need agents to operate websites rather than only download page content. Among nearby choices, Browserbase combines browser infrastructure with its Stagehand ecosystem and web data APIs, Browser Use Cloud combines hosted browsers with its own agent runtime, and Steel focuses on an open-source browser API and managed cloud. Anchor’s distinguishing commercial choice is that buyers can approach it through completed tasks or through lower-level infrastructure meters. Sources: Anchor Browser, Browserbase pricing, Browser Use pricing, and Steel, retrieved 2026-07-26.
How billing works
In the task model, one completed task consumes a fraction of a credit, so the workload multiplier is the number of completed tasks. In the infrastructure model, there is no single unit: creating a browser, keeping it active, transferring proxy traffic, and running AI steps can each add usage. Browser duration is rounded to the nearest full minute according to the billing documentation. The common buying mistake is to read the credit allowance as if it also describes the infrastructure path. It does not; session count, duration, traffic, and step count can all affect the infrastructure total. Sources: Anchor pricing documentation and Anchor Browser homepage calculator, retrieved 2026-07-26.
What Anchor Browser does not publish clearly
- A complete failure-billing rule across both completed-task and infrastructure modes. Source reviewed: Anchor pricing documentation, retrieved 2026-07-26.
- One reconciled browser-hour rate. The homepage calculator and the billing documentation show different inputs. Sources reviewed: Anchor Browser homepage and Anchor pricing documentation, retrieved 2026-07-26.
- Why the public documentation plan table and the homepage plan presentation do not show the same set of plans. Sources reviewed: Anchor Browser and Anchor pricing documentation, retrieved 2026-07-26.
- Whether all task plans receive the same treatment when a task starts but does not complete. Source reviewed: Anchor pricing documentation, retrieved 2026-07-26.
Who it suits
Anchor suits an agent team that values browser sessions, proxy access, and AI execution in one service and is willing to model the chosen billing path before launch. It is less suitable for procurement that requires a single, reconciled public rate card before a call, or for a simple fetch-only workload that does not need an interactive browser. The reason is the product’s breadth: it exposes several useful resources, but those resources make the infrastructure bill depend on more than request volume. Sources: Anchor Browser, Anchor pricing documentation, and browser-session API documentation, retrieved 2026-07-26.
Answer
Anchor Browser costs $200.00 for 200 browser hours on its Starter offer. Every figure is sourced and dated.
Recorded 2026-07-25 from the vendor's own pricing page.The published price on this page matched the vendor page when it was rechecked.