Scraping API PricesAll products / Scrapeless
Scrapeless pricing
How Scrapeless meters browser time and proxy traffic, what its separate scraping API leaves unpriced, and who fits.
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 Scrapeless counts
Nothing to count: Scrapeless publishes no rate for a page fetch. Its 2 published billing meters price other work.
What you pay
Successes you want
100,000 pages
Your stated workload. Every vendor on this site is priced against this same number.
- ÷ 0.95
Attempts you are billed for
105,263 requests
Scrapeless bills failed fetches, so a 5% failure rate is billed work.
- ∅
Cash per month
Not comparable here
no published rate for request.basic
Bars share one linear scale across the 2 counted stages, so a multiplier shows as length. Units differ by stage and are labelled. Cash is not on that scale.
Not comparable. This product publishes no rate for this kind of work.
no published rate for request.basic
This is a finding about what Scrapeless publishes, not a gap in the data. It stays visible so a definitive market claim cannot quietly ignore it.
Published exact bills for comparable products
Same 100,000 JavaScript-rendered pages a month at a 95% success rate, ranked by what you would actually be billed. Unknown totals never enter the numeric order.
Every Scrapeless plan
| Plan | Monthly | If billed yearly | Prepaid pack | Included | Simultaneous sessions |
|---|---|---|---|---|---|
| Scraping Browser pay as you go | Not published | n/a | n/a | n/a | n/a |
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.09 usd | browser_hour | source |
| proxy.residential_bandwidth | 1.8 usd | gb | source |
What Scrapeless does not publish
- The free-trial value is not published.
- Scraping Browser concurrency is not published on the reviewed billing page.
- The Universal Scraping API per-request price is not published on the reviewed public page.
What Scrapeless is
Scrapeless is a toolkit rather than one scraping endpoint. Its public product family includes a remotely controlled Scraping Browser, a Universal Scraping API, crawl tools, and proxy products. The browser documentation supports Puppeteer and Playwright sessions, while the Universal Scraping API accepts page requests and bills only successful ones. Sources: Scrapeless, Scraping Browser documentation, and Universal Scraping API introduction, retrieved 2026-07-27.
Browserbase, Browserless, and ZenRows are the nearest named competitors. Browserbase provides hosted browsers plus search and fetch APIs, Browserless exposes remote browser automation and separate web APIs, and ZenRows offers both a Universal Scraper API and a Puppeteer or Playwright Scraping Browser. Scrapeless is distinguished here by its published mixed browser bill, which adds session time to residential-proxy traffic, while its direct Universal Scraping API follows a separate per-request model. Sources: Scrapeless billing FAQ, Browserbase, Browserless, and ZenRows, retrieved 2026-07-27.
How billing works
For Scraping Browser, one meter is a browser hour and the other is a gigabyte of proxy traffic. The two charges add together, so longer sessions and heavier residential traffic independently increase the bill. Universal Scraping API is different: its unit is a successful request, but the reviewed public pages do not attach a self-serve per-request price. The buying mistake to avoid is forecasting either product from a URL count alone. A browser workload needs measured session time and traffic, while the direct API needs its unpublished request rate. Sources: Scrapeless billing FAQ and Universal Scraping API introduction, retrieved 2026-07-27.
What Scrapeless does not publish
- The Universal Scraping API’s self-serve per-request price on the reviewed billing and introduction pages. Sources reviewed: Scrapeless billing FAQ and Universal Scraping API introduction, retrieved 2026-07-27.
- A numeric Scraping Browser concurrency allowance on the reviewed billing page. Source reviewed: Scrapeless billing FAQ, retrieved 2026-07-27.
- The free trial’s value or expiry. Sources reviewed: Scrapeless and Scrapeless billing FAQ, retrieved 2026-07-27.
- Browser-time rounding, a minimum billable session, or how aborted sessions are treated. Sources reviewed: Scrapeless billing FAQ and Scraping Browser documentation, retrieved 2026-07-27.
Who it suits
Scrapeless suits a team that needs both programmable browser sessions and a direct page API and can collect browser-hour and traffic telemetry during a trial. It does not suit a buyer who needs a complete cash forecast from URL volume, or procurement that requires public concurrency, rounding, trial-value, and direct-API price terms before a call. The reason is that the published browser formula needs workload measurements and the separate request product remains publicly unpriced. Sources: Scrapeless billing FAQ, Scraping Browser documentation, and Universal Scraping API introduction, retrieved 2026-07-27.
Answer
What Scrapeless costs, what it publishes, and what it does not. Every figure sourced and dated.
Recorded 2026-07-26 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.