Home / Web scraping APIs / ScrapeLens
ScrapeLens pricing
100,000 JavaScript-rendered pages a month cost $211.00 as a one-time prepaid purchase on ScrapeLens's 10,000-credit pack.
Checked Oct 12, 2026 on ScrapeLens's own pricing page
- 10,000-credit pack
Your workloadType an exact volume, change the success rate or copy a link to this jobEdit
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.
Every ScrapeLens plan
| Plan | Covers | Billed monthly | Billed yearly, per month | Included | Past the allowance | Concurrent |
|---|---|---|---|---|---|---|
| 10,000-credit pack fits your volume | 10K to 1M pages | $1.00 once | not offered | 10,000 credits | move to a bigger plan | not published |
Your job
What ScrapeLens bills you for
What you pay
About this price and its sources
How ScrapeLens uses a single request credit rule, what its compact public documentation omits, and who fits.
Cite this price
100,000 JavaScript-rendered pages a month cost $211.00 as a one-time prepaid purchase on ScrapeLens's 10,000-credit pack. Price read from https://doc.scrapelens.com/ on Oct 12, 2026. Scraping API Prices, https://scrapingapiprices.com/scrapelens-pricing
How the bill builds up
- Base rate20 creditsper request
- → JavaScript rendering20 creditsper request; replaces the base rate
- × Premium proxyNot requiredNot part of this workload
- ÷ Success rate0.95Failure billing is not published; this is an assumption
- = Billed units per page you keep21.0526 creditsFrom this bill’s calculation
- = per 1,000 pages kept$2.1110,000-credit pack, prepaid
Credits and multipliers
JavaScript rendering
Billed failures
Success rate
Concurrency
Free tier
Renews monthly The bill at your volume
100,000 pages per month · $211.00
Read the chart as a table
| Volume | Bill | Offer |
|---|---|---|
| 10,000 | $22.00 | 10,000-credit pack |
| 25,000 | $53.00 | 10,000-credit pack |
| 50,000 | $106.00 | 10,000-credit pack |
| 100,000 | $211.00 | 10,000-credit pack |
| 250,000 | $527.00 | 10,000-credit pack |
| 500,000 | $1,053.00 | 10,000-credit pack |
| 1,000,000 | $2,106.00 | 10,000-credit pack |
Follow each billed unit
-
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
Failure billing is not published, so this assumes all 105,263 attempts are billed.
- × 20
What the meter counts
2,105,263 credits
One attempt is not one billed unit here: this workload multiplies by 20 before any money is involved.
- =
One-time prepaid cash
$211.00 prepaid
10,000-credit pack: the cheapest way to buy this volume, not just the first plan big enough.
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 pages divided by 95% success → 2,105,263 credits → 10,000-credit pack $211.00 prepaid = $2.11 per 1,000 pages kept
The arithmetic, line by line
- pages: 20 credits per request source
- JavaScript rendering: 20 credits per request source
- billed on up to 105,263 attempts, not 100,000 successes, because failure billing is not published; conservatively assumes every attempt consumes quota source
- consumes 2,105,263.16 credits per month
- cheapest way to buy that: 211 prepaid 10,000-credit packs at $1.00 each = $211.00 prepaid cash purchase source
- 4,737 of the included allowance goes unused, 47% of what you buy
What makes it cost more
One page is not always one billed unit. These are ScrapeLens's published charges for each kind of work.
| Work | Costs | Per | Source |
|---|---|---|---|
| A standard page | 20 credits | request | source |
| JavaScript rendering | 20 credits | request | source |
Cheaper for this job
Same 100,000 JavaScript-rendered pages a month at a 95% success rate, ranked by what you would actually be billed. APIs without a full public price aren't ranked. Showing 6 of 15; see the rest.
What ScrapeLens does not publish
- Whether failed, timed-out, rate-limited, or otherwise unusable requests consume the 20 credits. The error table names those responses but does not state their billing treatment (ScrapeLens documentation, Jul 27, 2026).
- Credit expiration or rollover behavior (ScrapeLens documentation, Jul 27, 2026).
- Numeric rate or concurrency limits. Sources reviewed: ScrapeLens and ScrapeLens documentation, checked Jul 27, 2026.
- A separate public meter for script complexity, extracted fields, or proxy class, and a public enterprise plan. Sources reviewed: ScrapeLens and ScrapeLens documentation, checked Jul 27, 2026.
What ScrapeLens is
ScrapeLens is a developer-facing page extraction API. A request supplies a URL and can optionally include browser actions or an output description; without an output field, the API returns the full HTML. Its documentation also covers CSS and XPath extraction, waits, clicks, scrolling, headers, cookies, and form interaction, while JavaScript rendering and proxy rotation are handled inside the request. Sources: ScrapeLens and ScrapeLens documentation, checked Jul 27, 2026.
ScrapeOwl, ScrapingBee, and ZenRows are the nearest named competitors. ScrapeOwl exposes element selection and four proxy or rendering credit bundles, ScrapingBee offers a general HTML API plus dedicated structured endpoints, and ZenRows separates a Universal Scraper API from a Puppeteer or Playwright Scraping Browser. ScrapeLens is the compact option in this group: one POST endpoint, optional scripted interaction and extraction, and one published request meter. Sources: ScrapeLens documentation, ScrapeOwl documentation, ScrapingBee, and ZenRows, checked Jul 27, 2026.
How billing works
One unit is a credit purchased in pay-as-you-go packs. The public documentation assigns 20 credits to each request and says that the request includes JavaScript rendering and proxy access. There is no monthly fee in the published offer. The buying mistake to avoid is treating a credit as a request: one API call consumes a bundle of 20 credits, so the pack balance must be divided by that request cost. Source: ScrapeLens documentation, checked Jul 27, 2026.
Who it suits
ScrapeLens suits a developer who wants one request shape for rendered HTML, scripted page interaction, or selector-based extraction and prefers buying credits without a subscription. It does not suit procurement that needs published failure billing, expiry, concurrency, enterprise terms, or differentiated pricing for simple and complex requests. The reason is that the public commercial description is unusually small: it provides one request meter but leaves most operating limits and exception rules unstated. Sources: ScrapeLens and ScrapeLens documentation, checked Jul 27, 2026.