Scraping API PricesAll products / ScrapingBot
ScrapingBot pricing
How ScrapingBot combines request modes and AI credits, where its public allowances conflict, and who should shortlist it.
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 ScrapingBot 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
ScrapingBot bills failed fetches, so a 5% failure rate is billed work.
- × 5
What the meter counts
526,316 credits
One attempt is not one billed unit here: this workload multiplies by 5 before any money is involved.
- =
Cash per month
$99.00 /mo
Startup. 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 → 526,316 credit → Startup $99.00/mo = $0.99 per 1,000 pages kept
The arithmetic, line by line
- pages: 1 credit per requestsource
- request.js_render: 5 credit per requestsource
- billed on up to 105,263 attempts, not 100,000 successes, because failure billing is not published; conservatively assumes every attempt consumes quotasource
- consumes 526,315.79 credit per month
- cheapest way to buy that: Startup, 1,100,000 included = $99.00 per monthsource
- 573,684 of the included allowance goes unused, 52% of what you buy
Every ScrapingBot plan
| Plan | Monthly | If billed yearly | Prepaid pack | Included | Simultaneous sessions |
|---|---|---|---|---|---|
| Starter | $49.00 | n/a | n/a | 275,000 credit | 10 |
| Startup your job | $99.00 | n/a | n/a | 1,100,000 credit | 50 |
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 | 1 credit | request | source |
| request.js_render | 5 credit | request | source |
| request.stealth | 75 credit | request | source |
| request.ai_extraction | 5 credit | request | source |
| target.google | 10 credit | request | source |
What ScrapingBot does not publish
- The homepage plan grid and documentation disagree on included credits.
- The homepage itself disagrees between 1,000 monthly free credits in the plan grid and 100 signup credits in its FAQ.
- Failure billing and overage pricing are not published.
What ScrapingBot is
ScrapingBot combines a general web scraping endpoint with browser scenarios, AI extraction, Google search, and dedicated Amazon, Instagram, TikTok, and ChatGPT APIs. The same account and API key work across those products. It is for developers who want both configurable page retrieval and named platform endpoints without running their own browser and proxy layer. Sources: ScrapingBot and ScrapingBot documentation, retrieved 2026-07-27.
WebScraping.AI, ScrapingBee, and ScrapingAnt are the three nearest named competitors. All three combine managed retrieval with browser or AI options. ScrapingBot is easiest to distinguish by the breadth of its named social, commerce, search, and model endpoints alongside its general scrape API and scenario builder. Sources: ScrapingBot, WebScraping.AI, ScrapingBee, and ScrapingAnt pricing, retrieved 2026-07-27.
How billing works
One unit is a credit. A basic HTTP scrape consumes 1 credit, browser rendering replaces that with 5, and stealth replaces it with 75 while already including browser rendering. AI extraction adds 5 credits to the chosen scrape mode. The Google search endpoint has its own 10-credit request rate. The mistake to avoid is treating every option as either wholly additive or wholly substitutive: stealth already includes rendering, but AI extraction is added on top. Source: ScrapingBot documentation, retrieved 2026-07-27.
What ScrapingBot does not publish clearly
- One authoritative free allowance. The plan grid says 1,000 credits each month, while the signup banner and FAQ say a new account receives 100 free credits. Source reviewed: ScrapingBot, retrieved 2026-07-27.
- One authoritative paid allowance table. The homepage plan grid and documentation show different credit totals for plans with the same names. Sources reviewed: ScrapingBot and ScrapingBot documentation, retrieved 2026-07-27.
- A public price for additional credits, although the FAQ says they can be purchased, or a public overage rule for paid plans. Source reviewed: ScrapingBot, retrieved 2026-07-27.
- Whether failed or timed-out requests consume credits, and an annual self-serve billing schedule. Sources reviewed: ScrapingBot and ScrapingBot documentation, retrieved 2026-07-27.
Who it suits
ScrapingBot suits a team that wants one key for general scraping and several named platform APIs and can meter each request by mode. It does not suit procurement that needs to approve capacity from the public allowance table alone. The unresolved free and paid allowance conflicts should be confirmed in the account or in writing before a production forecast is accepted. Sources: ScrapingBot and ScrapingBot documentation, retrieved 2026-07-27.
Answer
Under the disclosed conservative assumptions, ScrapingBot costs $99.00 for 100,000 JavaScript-rendered pages on its Startup offer. It is excluded from cheapest claims until the missing billing rule is published.
Recorded 2026-07-26 from the vendor's own pricing page.The published price on this page matched the vendor page when it was rechecked.