Pricing & billing

How billing works

Every plan, every metered unit in credits and dollars, a calculator, and the exact rules for when billing starts, stops and runs out. For the short version, see pricing.

The model

Your account has one credit balance, and 1 credit = $0.0125 at list price. Browser time, Web Data calls, search result pages, captcha solves and residential bandwidth all draw from it, at the rates below. A plan adds credits every month; packs add credits that never expire. When the balance is empty, work stops unless you turned on auto top-up.

Fig 1 One balance
Pick a plan, open a tap · drag to turn

  • Credits left in the balance
  • What one grant buys at each meter
  • Credits flowing now

One credit balance feeds every product. Open a tap and the whole grant runs into that meter: 8 credits per browser-hour, 1 per page, 2 per search page, 1 per captcha solve. Past zero, auto top-up bills $0.0125 a credit until your monthly spend limit, then work stops.

Metered

  • Open browser pages, per second (8 credits an hour)
  • Web Data pages and reports, from 1 credit each
  • Search result pages (2 credits), cache hits included
  • Successful captcha solves (1 credit)
  • Residential bandwidth (320 credits per GB)

Never billed

  • Web Data calls that fail
  • Captcha solves that fail
  • Datacenter egress (the default exit)
  • Extract source pages served from cache
  • Polling a crawl for its results
  • Operation calls that fail, repairs and scheduled checks

Plans

Plans differ in credits, concurrency and seats. Yearly billing is 20% off twelve months, paid up front.

PlanMonthlyYearly (20% off)Credits / monthPages at onceSeats
Developer$19 / month$182.40 / year1,520201
Business$99 / month$950.40 / year9,00010010
Scale$499 / month$4790.40 / year46,00040050
EnterpriseCustomCustomCommittedup to 1,000up to 1,000

Usage rates

Every metered unit, in credits and in dollars at the list rate. The rates are the same on every plan; a plan or a large pack only lowers what each credit costs you.

ItemUnitCreditsAt list rateNotes
Browser API
Browser timeopen page, per hour8$0.10Metered per second while the page is open.
Browser timeopen page, per minute0.1333$0.001667Every page is billed for at least 60 seconds.
Browser timeopen page, per second0.002222$0.000028The ledger keeps thousandths of a credit and rounds up.
Residential bandwidthGB (10⁹ bytes)320$4Metered per byte, for sessions and Web Data calls that use a residential exit.
Datacenter egressGB0FreeThe default exit when you ask for no location.
Web Data API
Scrapepage1$0.0125Cache hits are billed: it is still a page you received.
Extractuncached source page1$0.0125Cached source pages are free, so re-running a prompt costs nothing.
Brand profileprofile10$0.1250Identity, colors, logos, links, and company metadata.
Screenshotcapture5$0.0625A clean page image with cookie cleanup and tall-page capture.
Crawlsuccessful page1$0.0125Starting and polling a crawl is free; failed pages are not billed.
Mapstarted block of 10 URLs2$0.0250Billed on the URLs returned: 10 URLs cost 2 credits, 12 cost 4.
Styleguidereport10$0.1250Colors, typography, fonts, and visual system signals.
Fontsreport5$0.0625Detected font families, sources, and available weights.
Output add-onpage+4+$0.05Screenshot, PDF or JSON output; charged once per page however many you ask for.
Summary add-onpage+2+$0.0250An LLM summary of the page.
Operations
Operation callcall that answers1$0.0125Any tier, cache hits included. Learning an operation costs 3 credits, only when it finds the data.
Search API
Web searchprovider page2$0.0250Cache hits are billed. A large limit can fetch more than one page.
Captcha API
Captcha solvesuccessful solve1$0.0125Any supported type. Failed or timed-out solves are free.

Cost calculator

Enter a month of usage. Pick a plan, or leave it on cheapest fit to compare every option. The page address keeps your inputs, so you can share the estimate.

How you pay
Browser API

Each page you open over CDP

8 credits an hour, per second; a page's last stretch is billed at least 60 s

Concurrency is counted per open page

Web Data API

1 credit per page, plus any add-ons below

Search, captchas, network

2 credits per provider page, cache hits included

1 credit per solve, only when it succeeds

320 credits per GB; the default datacenter exit is free

Team

Seats count project members plus pending invites

Estimated $276.50 a month on Business for 24,474 credits.

Your month

Business

Cheapest fit
Plan fee
$99
Usage
24,474 cr $305.93 at list rate
Plan credits used
9,000 of 9,000
Credits still needed
15,474 cr packs 1 × 1,000 + 3 × 5,000, $177.50; 526 roll over
Total a month $276.50
  • Browser time 2,000 pages × 5 min 1,334
  • Pages scraped 20,000 × 1 cr 20,000
  • Searches 1,000 × 2 cr 2,000
  • Captchas 500 × 1 cr 500
  • Residential 2 GB × 320 cr 640
Every way to pay for this month
  • Packs only 1 seat
  • Developer 1 seat
  • Business(cheapest fit) $276.50
  • Scale $499
  • Enterprise custom

An estimate at list rates ($0.0125 a credit). Auto top-up bills $0.0125 a credit on monthly card plans; packs cost less per credit and their unused credits roll over.

Worked example: a team of 3

These are the calculator's starting values. The team opens 2,000 browser pages a month for about 5 minutes each: 1,334 credits. It scrapes 20,000 pages (20,000 credits), fetches 1,000 search result pages (2,000), solves 500 captchas (500) and sends 2 GB through residential exits (640). That is 24,474 credits, or $305.93 at the list rate.

Three people rule out packs only and Developer, which include one seat. Business costs $99 and covers 9,000 credits. The other 15,474 would cost $193.43 through auto top-up, or $177.50 as packs, whose unused credits roll over. The month comes to $276.50.

Compare plans

Only volume and payment options change between plans. Everything in the second table comes with every plan, and with packs alone.

Per planPacks onlyDeveloperBusinessScaleEnterprise
Credits each monthNone (packs)1,5209,00046,000Committed
Pages open at once2020100400up to 1,000
Team seats111050up to 1,000
Price per plan credit—$0.0125$0.0110$0.0108Custom
Auto top-up past zeroNoMonthly card plansMonthly card plansMonthly card plansTalk to us
Yearly billing, 20% offNoYesYesYesTalk to us
Monthly spend limit on auto top-upNoMonthly card plansMonthly card plansMonthly card plansTalk to us
Session replays kept1 day1 day7 days30 days90 days
Included with every plan and with packs
Credit packs: 1,000 for $12.50, 5,000 for $55, 20,000 for $200; they never expire
Card checkout through Stripe, crypto checkout through NOWPayments
Browser API over CDP with Playwright, Puppeteer or any CDP client
Residential exits by country, region, city and ISP, with sticky sessions, or your own proxy
Viewport control per connection or per link
Live view of running sessions and opt-in session replays, at no credit cost
All eight Web Data endpoints, the Search API and the Captcha API
MCP server with eleven tools for AI agents
Projects, browser links and email invites (admin or member)
Scoped API tokens with expiry and revoke
Two-factor sign-in, device sessions, data export and PDF invoices

Billing lifecycle

A browser session, start to finish

  1. Connect

    Opening the WebSocket checks that your account has a plan or packs and at least enough credits for 60 seconds of browser time. If not, the socket closes with code 4005.

  2. Open pages

    Billing is per open page. Each page counts toward your concurrency cap; past the cap, opening a page fails with a CDP error and the pages you have keep running.

  3. Metered live

    Every 30 seconds the gateway debits the time each open page used, at 8 credits an hour. Residential traffic is sampled every 5 seconds and debited per byte.

  4. Close pages

    When a page closes, the time not yet metered is billed, plus whatever the page fell short of the 60-second minimum. Every page bills at least 60 seconds in total, never more than its open time above that. Close pages and disconnect when you are done: an open page bills until it closes.

  5. Cut off at zero

    If a debit cannot be paid, the gateway sends a CDP error and closes the socket with code 4402 (4408 for residential bandwidth). Turn on auto top-up to keep running past zero.

Your balance, period to period

Spend order
Your plan grant is spent first and expires at the end of each period. Pack credits are spent next and never expire.
At zero
With the grant and packs both empty, calls are refused (HTTP 402 on the REST APIs) and open sessions are closed. Nothing is billed that you did not approve.
Auto top-up
Off by default. When on, usage past your balance is billed to your subscription at the list rate of $0.0125 a credit. It needs a monthly plan paid by card.
Yearly plans
Pay twelve months up front at 20% off. Credits are still granted every 30 days, so the monthly allowance is the same. Auto top-up is not available on yearly plans; use packs.
Crypto payments
Plans and packs can be paid with crypto through NOWPayments. A crypto plan is prepaid for its period and ends when the period does; it does not renew by itself.
Invoices and changes
Card and crypto invoices are listed in the dashboard and download as PDF. Change or cancel a card plan in the billing portal; a cancellation takes effect at the end of the current period.

Concurrency and other caps are listed in Limits.

Spend limits

A spend limit caps what auto top-up can bill in one billing period. Plan fees and credit packs never count toward it. Credits are spent in this order: plan credits, then pack credits, then auto top-up at $0.0125 a credit, until the limit.

Set it
Usage → Auto top-up → Monthly spend limit, or POST /api/billing/spend-limit with {"monthlyLimitUsd": 200}. Whole US dollars from $5 to $100,000; null removes it. It needs your signed-in session, not an API token.
Read it
GET /api/billing/entitlements returns spendLimit with limitUsd, spentUsd, remainingUsd and stopped.
At 80%
The account owner gets one email per billing period.
At 100%
One more email, and usage stops as if the balance were empty. You are never billed past the limit.
Usage resumes
When the billing period renews, at once when you raise or remove the limit, or when you buy a credit pack.
Applies to
Auto top-up only, so monthly card plans. Without auto top-up, an empty balance is already a hard stop.

What each product returns at the limit

Responses when the spend limit stops usage
ProductResult
New browser sessionsClose with code 4005 and reason "Session not allowed: spend_limit_reached".
Running browser sessionsEnd with close code 4402 at the next meter tick.
Web Data and Search402 billing_blocked with reason "spend_limit_reached".
Captcha403 spend_limit_reached.
MCP toolsA tool error that names the reason.

Questions

Does an idle open page cost credits?

Yes. Browser time is billed while a page is open, whether or not it is doing anything, at 8 credits an hour. Close pages you no longer need and disconnect when your job ends.

What if I close a page after a few seconds?

Browser time is metered per second, every 30 seconds, and each page bills at least 60 seconds in total. A page that lives 5 seconds or 45 seconds is billed 60 seconds (0.133 credits); a page that lives 95 seconds is billed 95. Reuse a page for several steps instead of opening one per step.

Does a higher concurrency cap cost more?

No. Concurrency is a cap on how many pages can be open at the same moment; you only pay for the time pages are actually open. Ten pages open for six minutes cost about the same as one page open for an hour.

Am I billed for requests that fail?

Failed Web Data calls and failed captcha solves cost nothing. Credits are reserved before a browser is acquired and debited only once there is real output. Every Web Data response returns the credits it charged.

Are cache hits billed?

A scrape served from cache is billed, because you still received the page. Search result pages served from cache are billed too. Extract source pages served from cache are free, so re-running a prompt over the same URLs costs nothing.

When do I pay for bandwidth?

Only when traffic goes through a residential exit, at 320 credits per GB, metered per byte. The default datacenter exit is free. You choose a residential exit with country (and optionally region, city, ISP) on the connection, or with the proxy option on Web Data calls.

Should I buy packs or a plan?

A plan adds concurrency and seats, and its credits reset every period. Packs never expire, and the 20,000-credit pack has the lowest price per credit. Without a plan you get 20 pages at once and one seat. Many teams combine a plan with packs; the calculator above prices every option.

What happens when my credits run out mid-job?

Work stops. REST calls return HTTP 402, open browser sessions are closed, and a running crawl stops cleanly; the pages it already crawled stay readable. Buy a pack or turn on auto top-up to continue.

Can I get a refund?

For card payments, a refund is available only when the service was not used in that billing period. Crypto payments are final. See section 6 of the Terms of Service.