Scraping API PricesAll products / Browserbase
Browserbase pricing
How Browserbase separates browser, web API, agent, and proxy usage, what remains unclear, and which teams fit.
one default result set; no fan-out
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 Browserbase counts
What you pay
Successes you want
100,000 standard searches
Your stated workload. Every vendor on this site is priced against this same number.
- ÷ 1
Attempts you are billed for
100,000 standard searches
Browserbase bills failed fetches. This workload assumes none fail, so nothing is added here.
- × 1
What the meter counts
100,000 searchs
One attempt is one billed unit for this workload.
- =
Cash per month
$10,049.00 /mo
Startup. 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.
100,000 standard searches → 100,000 search → Startup $10,049.00/mo = $100.49 per 1,000 searches
Cheaper for this job
Same 100,000 standard search calls with one default-depth result set per call, ranked by what you would actually be billed. Unknown totals never enter the numeric order.
Every Browserbase plan
| Plan | Monthly | If billed yearly | Prepaid pack | Included | Simultaneous sessions |
|---|---|---|---|---|---|
| Developer | $20.00 | n/a | n/a | 100 browser_hour | 25 |
| Startup your job | $99.00 | n/a | n/a | 500 browser_hour | 100 |
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 |
|---|---|---|---|
| browser.session_time | 0.12 usd | browser_hour | source |
| search.query | 0.007 usd | request | source |
| request.basic | 0.001 usd | request | source |
| request.ai_extraction | 0.004 usd | request | source |
| proxy.residential_bandwidth | 12 usd | gb | source |
What Browserbase does not publish
- Agent-run overage pricing is not published as a fixed meter.
- The pricing page does not state success-only treatment for Fetch, Search, or Extract calls.
- Startup no-proxy Fetch overage conflicts within the pricing page.
What Browserbase is
Browserbase is cloud infrastructure for browser automation and web agents. Its platform includes hosted browsers, Agent runs, Search and Fetch APIs, identity and proxy capabilities, a model gateway, and observability. Stagehand, Browserbase’s open-source agent framework, adds higher-level browser actions and extraction. Browserless, Anchor Browser, and Browser Use Cloud are the closest named comparisons. Browserbase is distinguished by combining raw browser infrastructure, Stagehand, and separate web data APIs under one account rather than presenting only a browser-hour service or only an agent-task service. Sources: Browserbase pricing, Browserless pricing, Anchor Browser, and Browser Use pricing, retrieved 2026-07-26.
How billing works
The subscription contains several separate allowances. Browser sessions consume browser hours, Search consumes search calls, Fetch and Extract consume their own calls, and built-in proxy use consumes bandwidth. These meters can have different overage rates. Created browser sessions have a minimum billing period, and a keep-alive session continues to consume time until it is released or reaches its timeout. The common buying mistake is to treat the plan as one flexible credit pool. Unused browser hours do not automatically pay for more Search, Fetch, Extract, Agent, or proxy usage. Sources: Browserbase pricing, cost optimization documentation, and keep-alive documentation, retrieved 2026-07-26.
What Browserbase does not publish clearly
- A fixed public overage rate for Agent runs. Source reviewed: Browserbase pricing, retrieved 2026-07-26.
- Whether failed Search, Fetch, or Extract calls are excluded from billing. Source reviewed: Browserbase pricing, retrieved 2026-07-26.
- One reconciled no-proxy Fetch overage for the Startup plan. The plan card and comparison table show different figures. Source reviewed: Browserbase pricing, retrieved 2026-07-26.
- A way to exchange unused allowance from one meter for another on self-serve plans. Source reviewed: Browserbase pricing, retrieved 2026-07-26.
Who it suits
Browserbase suits development teams that want Playwright, Puppeteer, Selenium, or Stagehand on managed browser infrastructure and may also use search, fetch, models, identities, or proxies from the same provider. It is less suitable for a buyer who needs one success-only request unit, or for automation that leaves sessions idle without strict release handling. The reason is that Browserbase exposes a broad platform through separate meters, and elapsed browser time remains billable even when an unfinished workflow produces no useful output. Sources: Browserbase pricing, cost optimization documentation, and session timeout documentation, retrieved 2026-07-26.
Answer
Browserbase's dated 2026-07-25 price snapshot gives $10,049.00 for 100,000 standard searches on its Startup offer. This older figure is excluded from rankings; check the vendor before buying.
Recorded 2026-07-25 from the vendor's own pricing page.We could not confirm this price in the latest check, so it remains visible for context but cannot lead a price ranking. Check the vendor's pricing page before buying.