Scraping API PricesAll products / ScrapingAnt
ScrapingAnt pricing
How ScrapingAnt bundles browser, proxy, search, extraction, and MCP access into request credits, with conflicting public guidance noted.
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 ScrapingAnt 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
ScrapingAnt does not bill failed fetches, so failures cost nothing here.
- × 10
What the meter counts
1,000,000 credits
One attempt is not one billed unit here: this workload multiplies by 10 before any money is involved.
- =
Cash per month
$249.00 /mo
Business. 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 → 1,000,000 credit → Business $249.00/mo = $2.49 per 1,000 pages kept
The arithmetic, line by line
- pages: 1 credit per requestsource
- request.js_render: 10 credit per request, combination rule not published, higher rate appliedsource
- consumes 1,000,000 credit per month
- cheapest way to buy that: Business, 3,000,000 included = $249.00 per monthsource
- 2,000,000 of the included allowance goes unused, 67% of what you buy
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 ScrapingAnt plan
| Plan | Monthly | If billed yearly | Prepaid pack | Included | Simultaneous sessions |
|---|---|---|---|---|---|
| Enthusiast | $19.00 | n/a | n/a | 100,000 credit | n/a |
| Startup | $49.00 | n/a | n/a | 500,000 credit | n/a |
| Business your job | $249.00 | n/a | n/a | 3,000,000 credit | n/a |
| Business Pro | $599.00 | n/a | n/a | 8,000,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 | 1 credit | request | source |
| request.residential_proxy | 25 credit | request | source |
| target.google | 10 credit | request | source |
| request.js_render | 10 credit | request | source |
What ScrapingAnt does not publish
- A reliable numeric concurrency limit was not obtainable.
- The pricing page's rendered-request capacity claim conflicts with the billing documentation.
What ScrapingAnt is
ScrapingAnt combines a web scraping API, headless Chrome, rotating proxies, Markdown output, natural-language structured extraction, and an MCP interface under one account. It also sells standalone proxy access separately by bandwidth. It is for developers and agent builders who want direct HTML, browser-rendered content, LLM-oriented text, or structured JSON without maintaining separate browser and proxy infrastructure. Source: ScrapingAnt, retrieved 2026-07-26.
ScraperAPI, ScrapingBee, and Tavily are the nearest named comparisons for different parts of that scope. ScraperAPI centers on managed page retrieval and target modes, ScrapingBee combines retrieval with AI extraction and dedicated APIs, and Tavily centers on search and retrieval for agents. ScrapingAnt’s distinction is that its direct API and MCP tools use the same monthly API-credit system, while standalone proxy bandwidth remains a separate product. Sources: ScraperAPI pricing, ScrapingBee pricing, Tavily API credits, and ScrapingAnt, retrieved 2026-07-26.
How billing works
One unit is one API credit. The documented request bundle depends on proxy class and JavaScript rendering: datacenter without rendering is the base path, while residential access, datacenter rendering, and residential rendering consume different replacement amounts. Google targeting has its own documented treatment. Blocked and error responses are not billed; the vendor describes billable delivery as HTTP 200 with content. The common buying mistake is to assume the default browser-rendered request has the same cost as a basic non-rendered request. It does not, and standalone proxy traffic also does not draw from the API-credit pool. Sources: ScrapingAnt credit-cost documentation, migration guide, and ScrapingAnt, retrieved 2026-07-26.
What ScrapingAnt does not publish consistently
- A reliable numeric concurrency ceiling. The pricing copy says plans have no enforced per-key cap, while public error documentation still includes a simultaneous-request error. Source reviewed: ScrapingAnt pricing, retrieved 2026-07-26.
- A reconciled rendered-request capacity statement. The Business-plan marketing example implies a different credit use from the explicit billing guide. Sources reviewed: ScrapingAnt pricing and credit-cost documentation, retrieved 2026-07-26.
- A rollover benefit. The pricing page states that monthly credits do not roll over. Source: ScrapingAnt pricing, retrieved 2026-07-26.
Who it suits
ScrapingAnt suits developers who want browser retrieval, proxy selection, extraction, and MCP access under the same API balance and can follow the explicit billing documentation. It is less suitable when procurement needs one unambiguous public concurrency figure or relies on the plan’s rendered-capacity marketing example for forecasting. The reason is that the detailed mode formula is usable, but two higher-level capacity statements do not fully reconcile. Sources: ScrapingAnt, pricing, and credit costs, retrieved 2026-07-26.
Answer
Under the disclosed conservative assumptions, ScrapingAnt costs $249.00 for 100,000 JavaScript-rendered pages on its Business 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.