Scraping API PricesAll products / ScrapingBee
ScrapingBee pricing
How ScrapingBee bills retrieval bundles, dedicated endpoints, and additive AI work, plus the details buyers still need.
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 ScrapingBee counts
What you pay
Successes you want
100,000 pages
Your stated workload. Every vendor on this site is priced against this same number.
- × 1
Attempts you are billed for
100,000 requests
ScrapingBee does not bill failed fetches, so failures cost nothing here.
- × 5
What the meter counts
500,000 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 → 500,000 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 request, combination rule not published, higher rate appliedsource
- consumes 500,000 credit per month
- cheapest way to buy that: Startup, 1,000,000 included = $99.00 per monthsource
- 500,000 of the included allowance goes unused, 50% of what you buy
Every ScrapingBee plan
| Plan | Monthly | If billed yearly | Prepaid pack | Included | Simultaneous sessions |
|---|---|---|---|---|---|
| Freelance | $49.00 | n/a | n/a | 250,000 credit | 50 |
| Startup your job | $99.00 | n/a | n/a | 1,000,000 credit | 100 |
| Business | $249.00 | n/a | n/a | 3,000,000 credit | 200 |
| Business+ | $599.00 | n/a | n/a | 8,000,000 credit | 400 |
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.premium_proxy | 10 credit | request | source |
| request.stealth | 75 credit | request | source |
| request.ai_extraction | 5 credit | request | source |
| target.google | 20 credit | request | source |
| target.walmart | 15 credit | request | source |
| target.amazon | 15 credit | request | source |
What ScrapingBee does not publish
- Annual pricing was not published.
- The single combine field cannot represent both bundled proxy/render prices and the additive AI charge.
What ScrapingBee is
ScrapingBee provides an HTML API for raw page retrieval, browser rendering, interactions, screenshots, selector-based extraction, Markdown, and AI-structured output. It also offers dedicated endpoints for search, Google, Amazon, Walmart, YouTube, and model responses. It is for developers who want one vendor for both general page access and selected ready-made data APIs while retaining control over output and interaction settings. Source: ScrapingBee, retrieved 2026-07-26.
ScraperAPI, ZenRows, and ScrapingAnt are the nearest named competitors. ScraperAPI emphasizes URL retrieval with target and mode credit classes, ZenRows combines a Universal Scraper API with a separately metered Scraping Browser, and ScrapingAnt includes browser, AI extraction, and MCP access under its API credits. ScrapingBee’s relevant distinction is the combination of replacement retrieval bundles, fixed-cost dedicated APIs, and an AI query charge that is added to the selected proxy mode. Sources: ScraperAPI pricing, ZenRows pricing, ScrapingAnt pricing, and ScrapingBee credit guide, retrieved 2026-07-26.
How billing works
One unit is one credit. Classic retrieval, JavaScript, premium proxy, premium plus JavaScript, and stealth are replacement request bundles with different credit costs. AI query adds credits to the selected proxy mode. Dedicated Google, Amazon, Walmart, search, and model endpoints have their own fixed request treatments. Only HTTP 200, 404, and 410 responses are charged. JavaScript rendering is enabled by default, so an unmodified HTML API request does not consume the same credits as a basic non-rendered request. The common buying mistake is to divide the plan allowance by the basic rate while leaving the default renderer enabled, or to forget that AI query is additive. Sources: ScrapingBee credit guide and ScrapingBee FAQ, retrieved 2026-07-26.
What ScrapingBee does not publish
- Annual self-serve pricing. Source reviewed: ScrapingBee pricing, retrieved 2026-07-26.
- One combination field that reconciles every retrieval bundle with the additive AI rule. The detailed examples and the stated AI addition do not fully reduce to a single universal formula. Source reviewed: ScrapingBee credit guide, retrieved 2026-07-26.
- A rollover benefit. Credits do not roll into the next billing period. Source: ScrapingBee pricing, retrieved 2026-07-26.
Who it suits
ScrapingBee suits teams that need both configurable HTML retrieval and selected ready-made APIs and can classify requests before forecasting. It is less suitable for buyers who expect one request to equal one credit under default settings or need one public formula for every AI and proxy combination. The reason is that several useful products share the balance but do not share one consumption rate. Sources: ScrapingBee, pricing, and credit guide, retrieved 2026-07-26.
Answer
ScrapingBee's dated 2026-07-26 price snapshot gives $99.00 for 100,000 JavaScript-rendered pages on its Startup offer. This older figure is excluded from rankings; check the vendor before buying.
Recorded 2026-07-26 from the vendor's own pricing page.A vendor page moved or could not be matched closely enough. Treat this as an older snapshot and check the vendor before buying.