Scraping API PricesAll products / ScrapeLens
ScrapeLens pricing
How ScrapeLens uses a single request credit rule, what its compact public documentation omits, 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 ScrapeLens counts
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
ScrapeLens bills failed fetches, so a 5% failure rate is billed work.
- × 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
$210.53 prepaid
10,000-credit pack. 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 pages divided by 95% success → 2,105,263 credit → 10,000-credit pack $210.53 prepaid = $2.11 per 1,000 pages kept
The arithmetic, line by line
- pages: 20 credit per requestsource
- request.js_render: no multiplier published, treated as included
- billed on up to 105,263 attempts, not 100,000 successes, because failure billing is not published; conservatively assumes every attempt consumes quotasource
- consumes 2,105,263.16 credit per month
- cheapest way to buy that: 10,000-credit pack prepaid purchase at $1.00 plus 2,095,263 over the allowance at $0.0001 each = $210.53 prepaid cash purchasesource
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. Unknown totals never enter the numeric order.
Every ScrapeLens plan
| Plan | Monthly | If billed yearly | Prepaid pack | Included | Simultaneous sessions |
|---|---|---|---|---|---|
| 10,000-credit pack your job | Not published | n/a | $1.00 | 10,000 credit | 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 |
|---|---|---|---|
| request.basic | 20 credit | request | source |
What ScrapeLens does not publish
- Failure billing is not published.
- Credit expiration and rate limits are not published.
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, retrieved 2026-07-27.
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, retrieved 2026-07-27.
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, retrieved 2026-07-27.
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. Source reviewed: ScrapeLens documentation, retrieved 2026-07-27.
- Credit expiration or rollover behavior. Source reviewed: ScrapeLens documentation, retrieved 2026-07-27.
- Numeric rate or concurrency limits. Sources reviewed: ScrapeLens and ScrapeLens documentation, retrieved 2026-07-27.
- A separate public meter for script complexity, extracted fields, or proxy class, and a public enterprise plan. Sources reviewed: ScrapeLens and ScrapeLens documentation, retrieved 2026-07-27.
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, retrieved 2026-07-27.
Answer
ScrapeLens's dated 2026-07-26 price snapshot gives $210.53 for 100,000 JavaScript-rendered pages on its 10,000-credit pack offer. This older figure is excluded from rankings; check the vendor before buying.
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.