Pricing
Flat monthly plans plus per-request usage. Failed requests are never billed.
Each plan carries a flat monthly fee, with usage billed per request on top. Failed requests are not billed. Usage is charged at a fixed USD rate per request — the rate depends on the fetch method the API selects and the proxy class the target site needs, and it is lower on higher-tier plans.
Plans
| Plan | Monthly fee |
|---|---|
| Starter | $20.00 |
| Growth | $100.00 |
Usage — per 1,000 requests
| Fetch path | Proxy class | Starter | Growth |
|---|---|---|---|
| Request-based fetch | Standard proxy | $0.30 | $0.20 |
| Request-based fetch | Premium proxy | $3.00 | $2.00 |
| Browser-based fetch | Standard proxy | $1.50 | $1.00 |
| Browser-based fetch | Premium proxy | $6.00 | $4.00 |
Antibot and captcha challenges may require browser-based methods and premium proxies, so they can cost more than a clean standard request.
AI structured extraction adds a dynamic fee
Requests that use jsonSchema add an extraction fee on top of the per-request
rate. It's metered per request and scales with the size of the page and the schema you request. The fee applies
whenever extraction runs, including requests that fall back
because the result didn't satisfy your schema. It isn't charged when extraction never ran, such as a page over the
size ceiling.
Search
Search has its own rate, separate from the fetch rates above:
| Usage | Starter | Growth |
|---|---|---|
| Per 1,000 searches | $1.50 | $1.00 |
A request with "aiOverview": true, which fills Google's streamed AI Overview with a second fetch, costs 2x a normal
search.
Browser WebSocket (CDP)
Remote CDP WebSocket sessions are billed by resource usage instead of the per-request table above: bandwidth transferred
and connection time are summed per session and charged when the session ends. These rates are the same on every plan,
and each session is metered on its own — usage is not batched across sessions. The bandwidth rate depends on the
session's proxy tier — premium (residential) is the default;
standard (datacenter) is selected with ?proxy=standard on the connect URL.
| CDP session metric | Rate |
|---|---|
Bandwidth transferred — premium proxy (default) | $10.00 / GB |
Bandwidth transferred — standard proxy | $5.00 / GB |
| Session duration (either tier) | $0.12 / hr |
Composer builds
From the date we gave your organization, each Composer build is paid from the same prepaid balance as your requests. Builds already running on that date are free.
- A build is priced by the work that build itself did, plus the web requests it made at your organization's own rates from the tables above.
- Time a build spends waiting for you, at a question, an approval or a publish review, costs nothing.
- A typical build costs about $2, and nine in ten cost less than $4.20. There is no estimate before a build starts.
- A build stops and asks you before it goes past $15.
- A build that fails because of a problem on our side is not charged. If a charge looks wrong, flag it from the build.