ScraperAPI alternatives: hosted API plans
Compare hosted alternatives to ScraperAPI by the paid plan, included usage and conditions you would buy. Each row names its allowance and read date. Credits belong to the provider that issues them, so a larger allowance alone does not tell you how many usable pages your workload will return.
What happens to requests that fail or get cancelled?
When replacing ScraperAPI, compare the charge for a failed request as carefully as the monthly subscription. A provider can return a page, charge a credit, and still leave your application without the data it needs. Keep the target status, cancellation time and retry policy in your test results.
- Run the same target URLs with the same JavaScript and location settings.
- Check how cancelled requests and target errors affect the balance.
- Compare the paid tier that can handle your concurrent jobs, including what happens at its limit.
Use the scraping API cost calculator for a workload the collected rate cards can price.
Moving off ScraperAPI: what changes in code
The request shapes split these services in two. One group takes a GET with the target URL in the query string and hands back the page’s HTML; the other takes a POST with a JSON body and offers a menu of output formats. Moving between those groups is a rewrite of the request and the parser, not a base-URL change, and it is the first thing to cost in a migration.
| Service | Send | Get back | Documented switches |
|---|---|---|---|
| ScraperAPI (leaving) | GET with the target URL in the query string | The HTML response for the target URL | Query parameters switch on JS rendering, geolocation and premium proxies |
| Firecrawl | POST with a JSON body | A menu of output formats: markdown, html, rawHtml, json and more | Output formats are chosen per request; batch and crawl jobs are separate endpoints |
| ScrapingBee | GET with the target URL in the query string | The raw HTML content of the target URL | Rendering is on by default via a headless browser; premium proxies are a per-request switch |
| ZenRows | GET with the target URL in the query string | The page content, with request cost and final-URL headers | js_render and premium_proxy are documented request parameters, off by default |
Each cell paraphrases one or two sentences of the vendor’s own documentation, read 2026-09-16, and the links below carry the exact sentences. Services listed above whose docs have not been read carry no row here rather than a guessed one.
Hosted alternatives to ScraperAPI
Alphabetical order. Entry prices read 2026-09-08 or later. Open each row’s plan conditions for rollover, cancellation and billing details. Search-only products and raw proxies are outside this comparison.
We may earn commission through provider links. How this site is funded.
| Provider | Entry plan | Included usage | Buying conditions | Visit |
|---|---|---|---|---|
| Crawlbase | $99/moStarter · Billed monthlyPrice read 2026-09-08 | 200,000 credits/month 20 concurrent requests per token (default) JavaScript: yes, stated 20 concurrent requests per token by default, shared across subscribed Crawlbase products. Higher limits require contacting support and are not priced here. This is not an account-wide ceiling or measured requests per second. Concurrency read 2026-09-08 · Source Quoted concurrency conditionsConcurrent requests / 20 / per tokenContext: Default limits. Limit / Default / Scope. Every account starts with the same generous defaults. You don't need to ask for these - they're already on every token the moment you sign up.Read 2026-09-08 Endpoint specs and parameter references for every Crawlbase API. One token authenticates all of them; pricing and concurrency budgets are shared across the products you subscribe to.Read 2026-09-08 Higher concurrency contact usContext: Email support with your target throughput and use case.Read 2026-09-08 | Billing requires cb_status 200 and a listed target status, including 404 and 410. A 302 must return content after the redirect. Custom success-code overrides are outside this estimate. Plan conditions and sourcesPurchase conditions · Starter
Billable requests Crawlbase only charges requests where cb_status is 200 and original_status is one of: Code Meaning 200 OK 201 Created 204 No Content 301 Moved Permanently 302 Found - only when the redirect was followed and returned content 404 Not Found 410 Gone Any other original_status is free, and so is any non- 200 cb_status. Use this list when reconciling a usage invoice against your application logs.Billing policy read 2026-09-09 Bills in credit. Provider record checked 2026-08-20. | Visit Crawlbase |
| Firecrawl | $19/moHobby · Billed monthlyPrice read 2026-09-08 | 5,000 credits/month 5 concurrent requests JavaScript: not established | Returned documents are billable even for target errors such as 403 and 404. Some scans, guards, cache modes and other endpoints can also charge without a document. Plan conditions and sourcesPurchase conditions · Hobby
What decides the charge is whether Firecrawl returned a document, not whether the target site returned a successful HTTP status code. Firecrawl returned a document: 1 credit per page, plus any of the option costs above. This includes pages that come back with an error status such as 403 Forbidden or 404 Not Found. The target responded, Firecrawl captured that response, and you get it back as a document. Check the metadata.statusCode field in the response to spot these cases and stop retrying URLs that are consistently blocked. Firecrawl returned no document: 0 credits. A scrape that fails outright, for example because the site never responded or every rendering attempt failed, is not charged. A few cases still charge when no document comes back. They cover work that Firecrawl already performed on your behalf before the scrape ended. Case What is charged Threat protection scan 2 credits per scanned URL, including a scrape that the scan itself blocked Prompt injection check 5 credits, once the checkPromptInjection guard has run FIRE-1 agent Usage-based, for the navigation the agent already did lockdown cache miss 1 credit Monitor check A page that errors during a check is charged the base 1 credit per page Interact and Browser sessions Charged per browser minute of session time, with a one-minute minimum, whether or not the session got what you wantedBilling policy read 2026-09-09 Bills in credit. Provider record checked 2026-08-20. | Visit Firecrawl |
| Scrapfly | $30/moDiscovery · Billed monthlyPrice read 2026-09-08 | 200,000 API credits/month 5 concurrent requests JavaScript: yes, stated | Failed-request protection has excluded statuses and a fairness-policy billing exception. Plan conditions and sourcesPurchase conditions · Discovery
Scrape Failed Protection & Fairness Policy Scrapfly's Scrape Failed Protection ensures that failed scrapes are not billed to our customers. To prevent abuse, we also have a fairness policy in place. Fairness Policy Trigger: If more than 30% of failed traffic with eligible status codes (≥400 and not excluded) is detected within a minimum one-hour period, the fairness policy will be disabled and usage will be billed. Eligible Status Codes Status codes greater than or equal to 400 and not excluded (see below) are eligible for Scrape Failed Protection. Excluded status codes: 400, 401, 402, 404, 405, 406, 407, 409, 410, 411, 412, 413, 414, 415, 416, 417, 418, 422, 424, 426, 428, 456 Account Suspension: If an account deliberately scrapes a protected website without success and without using our Anti Scraping Protection (ASP), the account may be suspended at the discretion of our account managers.Billing policy read 2026-09-08 Bills in credit. Provider record checked 2026-08-20. | Visit Scrapfly |
| ScrapingBee | $19/moHobby · Billed monthlyPrice read 2026-09-08 | 75,000 API credits/month 25 concurrent requests JavaScript: yes, stated | HTTP 404, 410 and 413 are billable. Transparent status mode also bills target responses below 500. Plan conditions and sourcesPurchase conditions · Hobby
Response Status Code ScrapingBee returns the following HTTP status codes. These are ScrapingBee's own status codes, not the target page's. By default we do not forward the status the scraped site returned - see transparent HTTP status code for how the two relate, and for how to get the target's status instead. Code Billed? Meaning Solution 200 Yes Successful Call 400 No Bad request Incorrect parameters or parameters type. See the message in the response body. 401 No Out of credits, or an invalid API key Check the key, then upgrade your plan or contact sales. 403 No The account is banned, or the request was redirected to a blocked destination The response body says which. This is never the scraped page's own 403. 404 Yes Requested URL not found Provide a valid URL. 410 Yes Requested URL gone Provide a valid URL. 413 Yes The target page returned 413 (payload too large) Check the URL; the page itself refused the request. 429 No Too many concurrent requests. Please upgrade your plan or contact sales. 500 No We could not scrape the page, or the target returned a status we do not pass through Retry; the response body carries the reason. Transparent HTTP status code transparent_status_code [ boolean ] ( false ) By default ScrapingBee reports its own status rather than the target's: any 2xx becomes 200, 404, 410 and 413 are passed through, and everything else becomes 500. Redirects are followed first, so this is the status at the end of the chain. So a 403 from an anti-bot page, a 401 from a paywall or a 503 from an overloaded site all reach you as a 500, not as their own code. A 500 from us is not billed. To get the same body and status code as the requested URL in any circumstances, use the transparent_status_code=true parameter. When this parameter is set to true: Anything the target returns below 500 is billed, since we no longer replace it with a 500. A 5xx is still free. We do not retry. Without the parameter a failed scrape is tried again on another proxy; with it you get the first attempt.Billing policy read 2026-09-08 Bills in credit. Provider record checked 2026-08-20. | Visit ScrapingBee |
| ZenRows | $19/moBuild · Billed monthlyPrice read 2026-09-08 | 45,000 credits/month 20 concurrent requests JavaScript: yes, stated | HTTP 404 and 410 responses count as billable successes. Plan conditions and sourcesPurchase conditions · Build
Failed requests are never charged. Not Found (404) and Gone (410) responses count as successful results.Billing policy read 2026-09-08 Bills in credit. Provider record checked 2026-08-20. | Visit ZenRows |
| ZyteNot yet reviewed | No entry subscription price on record | Allowance not established Concurrency not established JavaScript: not established | Billing policy not established Plan conditions and sourcesBills in request. Provider record checked 2026-09-03. | Visit Zyte |
Read your current ScraperAPI plan before switching
Purchase conditions · Hobby
Unused credits do not roll over; the balance resets at subscription renewal.
Read 2026-09-08 · SourceQuoted policy
No, your ScraperAPI credit balance resets when your subscription renews. If your usage has changed, you can move up or down a plan anytime from the billing page.Context: ScraperAPI Pricing FAQs / Do my unused ScraperAPI credits roll over to the next billing cycle?
At 100% credit usage before renewal, the FAQ offers an upgrade or a custom support arrangement for this plan. No extra-credit price is collected.
Read 2026-09-08 · SourceQuoted policy
If you reach 100% of your ScraperAPI credits on a Hobby, Startup, or Business plan before your standard renewal date, you’ll be able to: 1) seamlessly upgrade to the next plan, which often provides a better price-per-credit, or 2) contact our support team to discuss a custom plan tailored to your specific needs. Customers on a Scraper API Scaling, Professional, Advanced, or Enterprise plan can continue using our services on a PAYG model, using extra credits at a fixed, predictable rate; of course, you can always reach out to our sales team to adjust your plan to your increasing needs.Context: ScraperAPI Pricing FAQs / What happens if I run out of ScraperAPI credits?
Requests above the plan's concurrent-thread limit receive HTTP 429 without an extra charge; they are rejected rather than queued.
Read 2026-09-08 · SourceQuoted policy
If you exceed your ScraperAPI limits, you’ll get a 429 response asking you to bring your concurrency back within your plan’s limit and try again. There’s no extra charge for going over, the request is simply turned away rather than queued.Context: ScraperAPI Pricing FAQs / What happens if I exceed my ScraperAPI "Concurrent Threads" limit?
Keep your current plan’s renewal date and unused balance beside the replacement quote. Try a small workload first, check the billed requests against the returned data, and confirm that your application can use the response before moving scheduled jobs.
Test the switch from ScraperAPI
Build a failure ledger before moving traffic
Choose a small set of URLs that represents your production traffic, including a missing page, a slow response and a target that sometimes blocks requests. Give every attempt an identifier. Record the target status, the API status, elapsed time, cancellation point and balance change. Keep retries as separate attempts instead of folding them into the original request. This makes it possible to distinguish a cheap successful fetch from a cheap attempt that needs several paid retries. Do not deliberately overload a target to create the test.
Price the completed job, including retries
Define what a usable response must contain before inspecting the results. A status code alone cannot tell you whether the required records arrived. Divide the total trial spend by accepted records, then inspect rejected responses individually. If your application times out sooner than the provider, check whether abandoned work can still consume credit. Repeat the exercise at the concurrency your paid tier permits. Keep subscription charges separate from variable usage so a small trial does not imply an unrealistic monthly saving.
Set a switching threshold
Write down the maximum acceptable spend and the minimum number of complete records for the job. Keep the existing job available until the replacement meets both. Move one scheduled job first, watch its billed balance, and then decide whether the remaining jobs should follow. A lower entry subscription is useful only if the replacement can complete the workload within those limits.
Common questions
- Which hosted APIs can I compare with ScraperAPI?
- The alternatives here are Crawlbase, Firecrawl, Scrapfly, ScrapingBee, ZenRows, Zyte. Compare the paid plan and its buying conditions, then test your own target pages before switching. The list is alphabetical and does not rank measured success rates.
- Are these free or self-hosted ScraperAPI alternatives?
- This page compares hosted commercial API plans. It does not compare self-hosted software or establish which free tier can handle your workload. Hosting costs, maintenance and output compatibility need a separate evaluation.
- Can I compare the included credits directly?
- Each provider defines its own credit. Rendering, proxy options and request type can change how many credits a page consumes. Compare a named workload and a purchasable tier; the biggest allowance alone does not establish the lowest cost.
Compare two services
All scraping APIs · How we check the sources · How this site earns commission
