scraperapi alternatives: cost per 1,000 results by job

ScraperAPI vs ZenRows, Bright Data, Firecrawl, Apify and EveryInfra: cost per 1,000 Amazon pages, Google searches and social posts, with 20 live calls.

Hand-drawn illustration on black: a large key ring on the left holds five white keys; a sixth, yellow key has come off the ring and sits in the middle one of three padlocks on the right, which springs open; the other two stay shut beside a box, a magnifier and a phone playing a video.

For 1,000 Amazon product pages, ScraperAPI costs $0.46 to $2.45 at its public prices on November 18, 2026, because each page uses 5 credits. From the $149 Startup plan up, that is cheaper than the $1.389 we charged at EveryInfra in our own test calls.

For 1,000 Google searches, ScraperAPI uses 25 credits per search. That is $2.30 to $12.25 per 1,000, which is 3.3 to 17.7 times the $0.694 we charged for the same job.

For social posts, the gap is wider. Bright Data charges $1.30 to $1.50 per 1,000 records, and the Apify Store tools for TikTok and Instagram charge $1.00 to $3.70. One EveryInfra request returns 20 to 30 posts, so 1,000 posts cost $0.0185 to $0.0278. For TikTok, that is 47 times less than Bright Data, the cheaper of the two. For Instagram, it is 54 times less than the lowest Apify post-tool price.

Isometric illustration: on the left, a conveyor drops one coin for each small parcel that passes a toll gate, which stands for billing per record; on the right, a teal crate holds twenty of the same parcels with a single coin beside it, which stands for one charge per request.
Billing per record and billing per request. When one request returns 20 rows, the unit price differs by a factor of 20. Illustration made for this article from the billing rules on the Bright Data and Apify pricing pages and the EveryInfra catalog

How we compared the scraperapi alternatives

This guide is a buyer's checklist. It does not repeat the full credit math for each ScraperAPI plan. Our ScraperAPI pricing breakdown does that line by line, and the ScraperAPI alternative page gives a short overview. Here we take four common jobs and put six services on the same unit: dollars per 1,000 results.

Competitor prices come from public pricing pages and documentation. We read them on November 18, 2026, between 00:17 and 00:40 Singapore time. We use monthly prices and assume that the full allowance is used. Annual discounts and custom contracts are not included.

Our own prices come from the charged_usd field in the responses to our test calls. We sent 20 requests between 00:15 and 00:41 Singapore time. Eighteen were charged, for $0.017474 in total. Seventeen amounts come from charged_usd. The async Instagram job shows no amount, so we counted it at the catalog price of $0.000556. One 429 rate-limit reply and one 422 reply were free. We also checked each charge against the price_usd value in our free catalog at GET /api/v1/social/catalog on the same day.

The six services return different field names, row limits and paging, so this article compares money and billing rules only.

The scraperapi alternatives table: units, failure rules, free tiers and AI tools

ServiceBilling unitPer 1,000 Amazon product pagesPer 1,000 Google searchesFailed or empty resultsLowest paid entryFree tierAI tool access
ScraperAPICredits, multiplied by request type$0.46–2.45 (5 credits)$2.30–12.25 (25 credits)Charges only 200 and 404, plus requests you cancel within 70 secondsHobby, $49/month5,000-credit trial for 7 days, then 1,000 credits/monthRemote MCP, 22 tools
ZenRowsCredits: 1 plain, 5 JS, 10 premium proxy, 25 protected$0.07–10.56 (per-site cost not published)Same rangeFailures are free; 404 and 410 count as successBuild, $19/month5,000 credits/monthRemote MCP
Bright DataPer delivered record or request$1.30–1.50$1.31–1.50Failed deliveries are freePay as you go, no monthly fee5,000 records/monthMCP, 5,000 free requests/month
FirecrawlCredits: 1 per page, plus 4 for JSON formatJSON $3.75–19.00, Markdown only $0.75–3.80$1.50–7.60 (2 credits per 10 results)No result is free; returned 403 or 404 pages cost 1 creditHobby, $19/month1,000 credits/monthMCP v3
ApifyPer event, one charge per result, cheaper on higher plans$3.00–5.00$1.80–4.50 (per page)Results written before a failure are chargedStarter, $19/month$5 of usage/monthRemote MCP
EveryInfraPer request, fixed price per call$1.389 (amazon/profile, charged)$0.694 (web search tool, charged)Failures and empty results are free; a missing parameter returns 422First top-up $10, balance does not expire$1 trial for starring two GitHub repositories, valid 24 hoursRemote MCP

Each range runs from the most expensive self-serve plan to the cheapest one per credit. ScraperAPI Hobby is $49 for 100,000 credits, which is $0.49 per 1,000 credits. ScraperAPI Advanced is $1,975 for 21.5 million credits, which is $0.0919 per 1,000 credits (ScraperAPI pricing).

The ScraperAPI plan list below shows the monthly price, credits, cost per 1,000 credits, concurrency and regions. It comes from the same pricing page.

ScraperAPI planMonthly priceCredits per monthPer 1,000 creditsConcurrent threadsRegions
Free$01,000Free5Not stated
Hobby$49100,000$0.4920US and EU
Startup$1491,000,000$0.14950US and EU
Business$2993,000,000$0.0997100Country level
Scaling$4755,000,000$0.095200Country level
Professional$97510,500,000$0.0929300Country level
Advanced$1,97521,500,000$0.0919500Country level

ZenRows Build is $19 for 45,000 credits, and its largest self-serve plan is $2,999 for 45 million credits (ZenRows pricing). Firecrawl Hobby is $19 for 5,000 credits, and Scale is $749 for 1 million credits (Firecrawl pricing).

The Bright Data Web Scraper API costs $1.50 per 1,000 records on pay as you go. Its Scale plan costs $499 a month and includes 384,000 records (Web Scraper API pricing). The SERP API costs $1.50 per 1,000 requests on pay as you go, and its Scale plan includes 380,000 requests (SERP API pricing).

Apify prices come from the public tool pages in the Apify Store. Each tool has four price tiers, one for each plan: Free, Starter, Scale and Business (Apify pricing, Store billing documentation).

How ScraperAPI credits multiply, and where its two documents disagree

Before you move away from ScraperAPI, find out how many credits each of your requests uses today. The multiplier depends on the target domain and on the parameters you send.

A plain web page costs 1 credit. Amazon, Walmart and eBay cost 5. Google and Bing searches cost 25, and LinkedIn costs 30. The parameter premium=true costs 10 and render=true costs 10. Both together cost 25. The parameter ultra_premium=true costs 30, and it costs 75 with rendering (credits and request costs).

This means that one Amazon page can cost 5 credits or 25 credits or more. The price per 1,000 pages can change by a factor of five. ZenRows and Firecrawl also sell credits, but their multipliers are different. The table below shows the three side by side.

Request typeScraperAPI (credits)ZenRows (credits)Firecrawl (credits)
Plain static page111
JavaScript rendering1051 (no extra charge)
Premium proxy1010Not listed
Heavily protected site30 (ultra_premium), 75 with rendering25Not listed
Amazon, Walmart, eBay5Billed by the setup that worked, per-site cost not published1, plus 4 for structured JSON
Google search25Billed by the setup that worked2 per 10 results

ScraperAPI gives you three tools to measure your real cost before you switch. The response header sa-credit-cost shows how many credits a request used. The parameter max_cost sets a limit, and a request above that limit returns 403 and does not run. The endpoint /account/urlcost shows the cost of a URL without a request (cost control documentation).

In June 2026, ScraperAPI also released a domain credit cost estimator (release note). Run your own URL list from last month through urlcost. You then know your real average multiplier, and you can compare it with the prices below.

ZenRows bills only the setup that worked when you use mode=auto. It does not publish which setup a given site needs, so you must test it (ZenRows API reference).

Screenshot of the ScraperAPI credits documentation. In the cost table, the E-Commerce row lists Amazon, Walmart and eBay with a cost of 5, and a teal box marks this row. The row above shows normal requests at 1, and the row below shows SERP at 25.
The ScraperAPI credits page lists Walmart with Amazon and eBay at 5 credits per request. ScraperAPI documentation screenshot, 2026-11-18 00:33 Singapore time

When we checked the Walmart price, we found that two ScraperAPI documents disagree. The credits page above puts Walmart in the e-commerce group at 5 credits. ScraperAPI also publishes a structured data page for AI tools. That page first says that a structured endpoint costs the same as the core API on the same domain. Its Walmart table then lists the product, search, category and review endpoints at 1 credit each (structured data page).

On the Hobby plan, 1 credit is $0.49 per 1,000 requests and 5 credits are $2.45. That is a factor of five. We do not have a ScraperAPI account, so we cannot confirm the real charge. Do you scrape Walmart at volume? Send a few real URLs and read the sa-credit-cost header before you sign. Keep a copy of the result.

Screenshot of the ScraperAPI structured data page for AI tools. The Walmart endpoint table has four rows for product, search, category and reviews, and the credits column shows 1 in each row. A teal box marks the credits column.
Another ScraperAPI page lists all four Walmart structured endpoints at 1 credit. ScraperAPI structured data page screenshot, 2026-11-18 00:35 Singapore time

On the same day, we searched for "wireless earbuds" with the EveryInfra walmart/search capability. At 00:27 Singapore time, it returned 20 products and charged $0.001389. That is $0.0695 per 1,000 products.

The ScraperAPI Walmart search endpoint returns one results page, but the documentation does not say how many products a page holds. If we assume 20, the cost is about $0.0046 to $0.0245 per 1,000 products at 1 credit, or $0.023 to $0.12 at 5 credits. For small, page-based Walmart jobs, ScraperAPI is a fair price. First, find out which of the two numbers is correct. The Walmart platform page lists all our Walmart capabilities and prices.

Job 1: Amazon product pages, where ScraperAPI wins from the Startup plan

The most common job is a daily check of price, rating and review count for a list of ASINs. The ScraperAPI structured Amazon endpoint costs 5 credits, the same as the core API. It returns title, price, rating, review count, ASIN, availability, images, description, specifications and seller information.

Across the six ScraperAPI plans, 1,000 product pages cost from $2.45 on Hobby to $0.459 on Advanced. On the $149 Startup plan, they cost $0.745. That is already less than our price.

We fetch one product per request with amazon/profile. The catalog price is $0.001389 per call. At 00:15 Singapore time, we requested ASIN B09FT58QQP. The call returned the TOZO A1 earbuds at $19.99, with a rating of 4.3 from 119,343 ratings. It took 53.3 seconds and cost $0.001389.

At 00:29 Singapore time, we requested the AirPods Pro 2 (B0BDHWDR12). The call returned a price of $265.77 and a rating of 4.7 from 57,993 ratings. It took 58.3 seconds and also cost $0.001389. Both calls used the catalog price, which is $1.389 per 1,000 product pages.

One product took almost one minute. If you build a live price comparison page, plan for this delay. ScraperAPI does not publish an average response time for its structured endpoints, so test both services with your own ASINs.

Horizontal range chart on a log scale of US dollars per 1,000 Amazon product pages, from 0.01 to 100, with one step per factor of 10. Seven rows: ScraperAPI at 5 credits from 0.459 to 2.45; ZenRows at 1 to 25 credits, per-site cost not published, from 0.0666 to 10.56; Bright Data per record from 1.30 to 1.50; Firecrawl JSON at 5 credits from 3.75 to 19.00; Apify Amazon tool from 3.00 to 5.00; EveryInfra amazon/profile as one teal point at 1.389 in the middle.

The result changes when you search by keyword. Our amazon/search capability costs $0.002236 per request and returns one page of results. At 00:16 Singapore time, a search for "wireless earbuds" returned 18 products. At 00:31 Singapore time, a search for "running shoes" returned 20 products. The average is $0.1177 per 1,000 products.

The ScraperAPI Amazon search endpoint also costs 5 credits per request. The number of products per page changes with the keyword. If we assume 20 per page, the cost is $0.023 to $0.12 per 1,000 products, which is close to our price.

Bright Data charges $1.30 to $1.50 per 1,000 records. The Apify Amazon product tool charges per result: $5.00 on Free, $4.00 on Starter, $3.50 on Scale and $3.00 on Business (Amazon product tool). For product lists, the three services that bill per page or per request are about ten times cheaper than the two that bill per record.

Amazon jobScraperAPIZenRowsBright DataFirecrawlApifyEveryInfra
One product detail, per 1,000$0.459–2.45$0.0666–10.56$1.30–1.50$3.75–19.00 (JSON)$3.00–5.00$1.389 (charged)
Keyword search, per 1,000 pages$0.459–2.45$0.0666–10.56Billed per record$0.75–3.80Billed per result$2.236 (charged)
Keyword search, per 1,000 productsAbout $0.023–0.12 (20 per page assumed)Not published$1.30–1.50Not published$3.00–5.00$0.1177 (charged, 38 products)

We also tried an ASIN that we expected to fail. At 00:30 Singapore time, we requested B000000000. Amazon sent this number to a real product, a bag of chips. The call returned normal data and cost $0.001389.

A made-up ASIN on Amazon does not always give an empty result. Clean your ASIN list before you run a large batch. We tested a real failure separately, in the section on failed requests.

This is a complete request for one product. Replace $EVERYINFRA_API_KEY with your own key:

bash
curl -s https://api.everyinfra.com/api/v1/social \
  -H "Authorization: Bearer $EVERYINFRA_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"platform":"amazon","action":"profile","params":{"url":"https://www.amazon.com/dp/B0BDHWDR12"}}' \
  | jq '{title: .results.title, price: .results.price, rating: .results.rating, rating_count: .results.rating_count, charged: .billing.charged_usd}'

Job 2: Google search, where 25 credits per search make ScraperAPI 3.3 to 17.7 times more expensive

Google search has one of the highest ScraperAPI multipliers. Each search costs 25 credits, and the structured Google search, shopping and news endpoints use the same rate (structured data page). On Hobby, 1,000 searches cost $12.25. On Advanced, they still cost $2.30. Our price is $0.694 per 1,000, so every ScraperAPI plan costs 3.3 to 17.7 times more for this job.

Horizontal range chart on a log scale of US dollars per 1,000 Google searches. Six rows: ScraperAPI at 25 credits from 2.30 to 12.25; ZenRows at 1 to 25 credits, not published, from 0.0666 to 10.56; Bright Data SERP API from 1.31 to 1.50; Firecrawl at 2 credits per 10 results from 1.50 to 7.60; Apify Google search tool per page from 1.80 to 4.50; EveryInfra web search tool as one teal point at 0.694 at the left.

The Bright Data SERP API costs $1.50 per 1,000 requests on pay as you go and $1.31 on its Scale plan. Firecrawl search costs 2 credits per 10 results, so one search of 10 results is $1.50 to $7.60 per 1,000. The Apify Google search tool charges per results page (Google search tool). The price is $4.50 on Free, $2.50 on Starter, $1.95 on Scale and $1.80 on Business. ZenRows does not publish the multiplier that Google uses with its general API.

Our search uses POST /api/v1/search with the tool name web. The tool list at /api/v1/search/tools is free to read. We ran three searches.

Time (Singapore)QueryResultsSecondsCharged (USD)Relevant
00:17scraperapi alternatives101.80.000694No, all unrelated
00:31best running shoes92.70.000694Yes
00:41scraperapi competitors101.90.000694Yes

At 00:31 Singapore time, "best running shoes" returned 9 results in 2.7 seconds for $0.000694. At 00:41 Singapore time, "scraperapi competitors" returned 10 results in 1.9 seconds for $0.000694. The top ten included the Firecrawl alternatives post, the ScraperAPI comparison page and several alternative pages from other scraping companies.

At 00:17 Singapore time, the search "scraperapi alternatives" also returned 10 results and cost $0.000694. But all 10 were unrelated sites with "alternatives" in the title, such as a youth service, a credit union and a Linux command page. When we changed the words to "scraperapi competitors", the results were correct. If you search for a brand plus a common word, put the brand in quotes or use more specific words.

For rank tracking, location also matters. The ScraperAPI Google endpoints can return results by country. However, the Hobby and Startup plans can only use exit points in the US and the EU. Country-level targeting starts on the Business plan.

Our web tool uses the location parameter. You can give a country name or a two-letter country code. If you give a city, the tool uses the country of that city. The tool also supports a site filter, a date window and paging.

The number of results per search also changes the price per result. In these tests, our searches returned 9 to 10 organic results each. The Bright Data SERP API returns a full parsed page with ads and related searches. The ScraperAPI Google endpoint also returns ads, featured snippets and the knowledge panel. If you only need the top ten links, the four services return a similar amount of data. If you need ad slots and answer boxes, read each field list first. Our SERP API alternatives test compares this group in more detail.

Job 3: TikTok and Instagram, where per-record billing costs 47 to 54 times more

The ScraperAPI credits page lists LinkedIn at 30 credits. Its solutions page lists TikTok as a 1-credit plain page that returns HTML, so you must parse it yourself. Instagram is not listed.

ZenRows and Firecrawl also bill per page. They do not publish how many videos a TikTok search page contains. Only three services can be compared per 1,000 posts. Bright Data and Apify bill per record, and EveryInfra bills per request with a known row count.

For ScraperAPI, we can only estimate. A TikTok page costs 1 credit, which is $0.092 to $0.49 per 1,000 pages from the Advanced plan down to Hobby. If one page gives 20 videos, as our call does, that is about $0.0046 to $0.0245 per 1,000 videos, in the same range as our $0.0278. If the page needs render=true before the content appears, each page costs 10 credits, which is about $0.046 to $0.245 per 1,000 videos.

ScraperAPI does not publish how many videos one page gives, and you must write the parser yourself. Run a few pages with your own keywords before you decide. Instagram is not listed on the ScraperAPI solutions page. At the plain-page rate of 1 credit, you must also parse the page and count the rows yourself, so we do not estimate a price per 1,000 posts.

Horizontal range chart on a log scale of US dollars per 1,000 social posts. Five rows: Bright Data per record from 1.30 to 1.50; Apify TikTok tool from 1.70 to 3.70; Apify Instagram post tool from 1.00 to 1.70; EveryInfra tiktok/search at 20 rows per page as one point at 0.0278; EveryInfra instagram/user_posts at 30 rows per page as one point at 0.0185. The two EveryInfra points are teal and sit far to the left of the other rows.

We ran tiktok/search three times with a limit of 20. The catalog price is $0.000556 per call. At 00:17 Singapore time, "wireless earbuds review" returned 20 videos in 11.4 seconds. At 00:31 Singapore time, "running shoes review" returned 20 videos in 22.6 seconds.

At 00:40 Singapore time, we searched for the random string "qzxvjkw9931plmnbt". After 62.6 seconds, the call still returned 20 videos and was charged. TikTok search returns similar videos for any keyword and does not return an empty list. If you use it for brand tracking, filter the results by title or hashtag. The three calls returned 60 videos, which is $0.0278 per 1,000.

For Instagram, we used instagram/user_posts on the NASA account with a limit of 30. This capability runs as an async job. At 00:27 Singapore time, we sent the request. After 14.1 seconds, we received a job ID. The job status went from running to finalizing to succeeded, and the job returned 30 posts with billing_state set to charged.

The async job result does not show the amount. We used the catalog price of $0.000556 for this call, which is $0.0185 per 1,000 posts. You can ask for up to 200 posts, and each page counts as one call.

Social jobBright DataApifyEveryInfra
TikTok videos, per 1,000$1.50 pay as you go, $1.30 on ScaleTikTok tool: Free $3.70, Starter $3.00, Scale $2.30, Business $1.70$0.0278 (charged, 20 per call)
Instagram posts, per 1,000$1.50 pay as you go, $1.30 on ScalePost tool: Free $1.70, Starter $1.50, Scale $1.30, Business $1.00. General tool $1.50–2.70$0.0185 (catalog price, 30 per call)
Billing unitEach delivered recordEach result written to the datasetEach request

Social data is also slower than web pages. Our three TikTok searches took 11.4, 22.6 and 62.6 seconds. The random keyword was the slowest, probably because the platform searched a wider range.

Instagram ran as an async job and gave a job ID after 14 seconds. On Bright Data, social "discover by keyword" requests also run as async jobs. On Apify, each request is a full actor run that takes from tens of seconds to minutes. For a live product, run social collection as a background job and show cached results.

The Apify prices come from each tool page (TikTok tool, Instagram post tool). Each tool has its own price. The TikTok tool page was updated on November 17, 2026, so read these pages again each month.

If your ScraperAPI work is mostly social data, a structured API that bills per record or per request removes your HTML parsing work. The TikTok platform page and the Instagram platform page list all the fields and prices we offer.

Job 4: arbitrary web pages and JavaScript, where ScraperAPI and ZenRows are cheapest at volume

The first three jobs use platform data. If your list has thousands of different websites and you need full HTML or page text, ScraperAPI is in its strongest area. A plain page costs 1 credit, which is $0.49 per 1,000 on Hobby and $0.092 on Advanced.

ZenRows also charges 1 credit for a plain page, which is $0.067 to $0.42 per 1,000. For JavaScript rendering, ZenRows charges 5 credits and ScraperAPI charges 10. Firecrawl charges 1 credit per page, handles JavaScript content and returns Markdown, at $0.75 to $3.80 per 1,000. Firecrawl is a good fit when the page goes straight into a language model.

Horizontal range chart on a log scale of US dollars per 1,000 pages. Six rows: ScraperAPI plain page at 1 credit from 0.0919 to 0.490; ScraperAPI JavaScript rendering at 10 credits from 0.919 to 4.90; ZenRows plain page at 1 credit from 0.0666 to 0.422; ZenRows JavaScript rendering at 5 credits from 0.333 to 2.11; Firecrawl at 1 credit per page from 0.749 to 3.80; EveryInfra read tool as one point at 0.694, without JavaScript rendering.

Our read tool costs $0.000694 per call, which is $0.694 per 1,000 pages. That is more than the plain-page price of ScraperAPI and ZenRows on their larger plans. At 00:27 Singapore time, we used it on quotes.toscrape.com/js/, a test page that builds its content with JavaScript. The call returned in 0.76 seconds and cost $0.000694. The text had only the title, a login link and a next-page link. It had none of the quotes.

In this test, our read tool did not run the page scripts. Some pages are single-page apps, some must wait for an element, and some need a screenshot. For these pages, use the ScraperAPI render=true and wait_for_selector options, or the ZenRows js_render option.

The same is true for a general proxy. ScraperAPI also sells a proxy port mode. It works as an HTTP proxy that rotates exit points.

You can connect it to an existing Scrapy or Playwright script without new parsing code. The country_code and session_number parameters fix the country and the session. EveryInfra sells APIs and structured data, not proxies. Maybe you already have your own crawlers and only need a way past blocks. Then ScraperAPI or ZenRows is a smaller change than a move to us.

Concurrency, regions and speed: three limits that the price table does not show

Two services with the same price per 1,000 can run very differently. The reasons are concurrency limits, available regions and the time per request.

ScraperAPI sets concurrency by plan. The free plan has 5 threads, Hobby has 20, Startup has 50, Business has 100, Scaling has 200, Professional has 300 and Advanced has 500. A request above the limit returns 429 and does not use credits. Regions also depend on the plan. Hobby and Startup can only use US and EU exit points, and country-level targeting starts on Business (ScraperAPI pricing). If you need local prices from Germany, Japan or Brazil, you need at least the $299 Business plan.

Firecrawl gives more detail. Concurrent browsers are 2 on Free, 5 on Hobby, 25 on Standard, 50 on Growth and 100 on Scale. Requests per minute for /scrape and /search go from 10 on Free to 10,000 on Scale (Firecrawl pricing).

The Bright Data Scraper API runs keyword discovery requests as async jobs. A sync request by URL can run longer than one minute. It then returns 202 with a snapshot_id and continues as an async job (sync and async requests). Apify starts a full run for each request, so it fits scheduled batches better than one-row live lookups.

Our test callCapabilityTime (seconds)Rows returnedCharged (USD)
00:15 one Amazon productamazon/profile53.310.001389
00:16 Amazon keyword searchamazon/search55.7180.002236
00:17 TikTok keyword searchtiktok/search11.4200.000556
00:27 Walmart keyword searchwalmart/search35.8200.001389
00:27 read one JavaScript pagesearch read tool0.81 (page shell only)0.000694
00:31 Google searchsearch web tool2.790.000694
00:40 TikTok random keywordtiktok/search62.6200.000556

All times in this table are Singapore time on November 18, 2026. Search and page reads returned in less than three seconds. Platform data took from ten seconds to one minute, and one Amazon product took almost one minute.

ScraperAPI also bills requests that you cancel within 70 seconds. So it expects some requests to need tens of seconds.

Our sync responses include an async_hint field. It tells you to add "mode":"async" to the request body for slow jobs. For a chat interface where a user waits, send platform requests as async jobs, then read the result with the job ID. Polling is free. For background batches, time matters less than concurrency and requests per minute.

How many Amazon pages each free tier buys

We converted the free tier of each service into one unit: Amazon product pages.

Horizontal bar chart of the number of Amazon product pages that each free tier buys. Seven bars: ScraperAPI 7-day trial 1,000; ScraperAPI free plan per month 200; ZenRows free plan at 25 credits 200; Bright Data free plan per month 5,000, the longest bar; Firecrawl free plan with JSON 200; Apify free plan with $5 of usage 1,000; EveryInfra $1 trial for 24 hours 719, in teal.
Free tierAllowanceAmazon product pagesLimits
ScraperAPI trial5,000 credits, 7 days1,000Expires after 7 days
ScraperAPI free plan1,000 credits per month2005 concurrent threads
ZenRows free plan5,000 credits per month200 (at 25 credits) to 5,000 (at 1 credit)Per-site cost needs a test
Bright Data free plan5,000 records per month5,000Billed per record
Firecrawl free plan1,000 credits per month200 (JSON)2 concurrent browsers
Apify free plan$5 of usage per month1,000No plan discount
EveryInfra trial$1, 24 hours719Star two GitHub repositories to claim it

In this unit, the Bright Data free plan is the largest at 5,000 records each month. The ScraperAPI trial lasts only 7 days. After that, the free plan gives 1,000 credits a month, which buys only 200 product pages at 5 credits each.

Our trial converts to 719 product pages. If you use it for amazon/search at 20 products per call, $1 buys about 8,900 product rows. The pricing page explains how to claim it.

Failed requests, empty results and timeouts: which services charge

The price table shows only half of the bill. The other half is failed requests.

ScraperAPI charges only for status codes 200 and 404. It also charges for a request that you cancel within 70 seconds, because the work has started (credits documentation). A request above your concurrency limit returns 429 and is free. ZenRows says on its pricing page that failed requests are never charged, and it counts 404 and 410 as successful results.

Firecrawl says that a scrape with no result is free. A target page that returns 403 or 404 is still delivered to you and costs 1 credit (billing documentation). Bright Data charges per delivered record. Apify charges per event, so results written to the dataset before a run fails are still charged.

CaseScraperAPIZenRowsFirecrawlBright DataApifyEveryInfra
Target returns 404ChargedCharged (counts as success)1 creditNo record, no chargeDepends on the toolFree
Blocked or timed outFreeFreeFreeFreeResults written so far are chargedFree, refunded on the same charge ID
Wrong parameterFreeFreeFreeFreeA start fee may apply422, free
You cancel the requestCharged within 70 secondsNot statedNot statedNot statedUsage so far is chargedNot tested

At 00:40 Singapore time, we sent amazon/profile with a wrong parameter, asin in place of the required url. After 0.13 seconds, the call returned 422 missing_param. The response named the required parameter, gave a working example request and said "Nothing was charged". The charged_usd field was empty.

In the same round, the random TikTok search returned 20 videos, so it was charged as a normal result. For slow requests, we hold the charge first. If the result fails or is empty, we refund it on the same charge ID. Our failure refund reconciliation guide shows how to check this in your own records.

ScraperAPI has two more rules. Credits do not roll over to the next month. Only the Scaling plan and higher can buy extra credits on pay as you go (plans and billing FAQ).

ScraperAPI states that you can ask for a refund within 7 days. Firecrawl rolls credits over for one month on Scale only. ZenRows annual plans give 12 months for the price of 10. Our prepaid balance does not expire and has no monthly fee. Workload A below, 30,000 product pages plus 3,000 searches, costs $43.75 a month with us. Cut the usage in half and the bill halves too, with no jump to a higher plan.

Measure your own failure rate: cost per successful page

A price table shows the cost per 1,000 requests. Your bill is the cost per 1,000 pages that you can use. The difference is the failure rate and the retries.

To run the test, pick 100 to 200 random URLs from your own list, from the five or six domains that you scrape most. Run them on each service. Record three values for each URL: the status code, the charge, and whether you can parse the fields you need. Then divide the total cost by the number of parsed pages and multiply by 1,000. Compare services on this number. The ScraperAPI trial lasts 7 days and ours lasts 24 hours, so run the same inputs on all services while the trials overlap.

Here is an example. One service costs $0.49 per 1,000 requests. Of 200 URLs, 170 parse correctly. The other 30 return a challenge page or an empty page, and the service charges for them because they return status 200. The real cost is 0.49 × 200 ÷ 170 = $0.576 per 1,000 successful pages, which is 18% above the list price.

A second service lists $0.60 and does not charge for failures, so its real cost is $0.60. The difference is now only 4%, and a harder set of domains can reverse it. A Reddit reply in the forum section below gives the same advice.

At EveryInfra, the billing.charged_usd field in each response shows the dollar charge, and failures show zero. At ScraperAPI, read the sa-credit-cost header. At ZenRows and Firecrawl, read the usage log in the dashboard. Save the test results in a spreadsheet and run the test again when a service changes its prices.

We applied the same method to the 20 calls in this article. Four groups of calls returned HTTP 200 and were charged, but some rows were of no use to us. The 10 results for "scraperapi alternatives" were all off topic. The 20 TikTok videos for the random keyword mean nothing for brand tracking. The wrong ASIN returned a bag of chips. When we remove these rows, the price per 1,000 rows is about 50% above the list price. The two amazon/search calls returned 38 rows, not 40, and the $0.1177 figure already uses the rows that came back.

Calls in this articleCost (USD)Rows returnedUseful rowsList price per 1,000 rowsPrice per 1,000 useful rows
Three web searches0.00208229190.07180.1096
Three tiktok/search calls0.00166860400.02780.0417
Three amazon/profile calls0.004167321.3892.08
Two amazon/search calls0.00447238380.11770.1177

Every service charges for some status 200 replies that you cannot use. ScraperAPI charges for 200, ZenRows counts 404 as a success, and Firecrawl charges 1 credit for 403 and 404 pages. Compare services on the price after you remove useless rows, because that price is closer to your monthly bill.

The filter rule depends on the platform. For search results, check that the title or URL contains the brand. For TikTok videos, check the caption and the hashtags. For Amazon products, compare the returned title with the product name in your list, and count a mismatch as a failure. Put these rules in your test script and use the same rules on every service. Keep the rules fixed between test rounds, or you cannot compare the results.

One month of usage: three workloads, six bills

The plan size also changes the bill. For three typical workloads, we picked the smallest monthly plan that covers the usage, or the pay-as-you-go price where one exists.

Monthly workloadScraperAPIZenRowsBright DataFirecrawlApifyEveryInfra
A: 30,000 Amazon product pages + 3,000 Google searchesStartup $149 (225,000 credits)Launch $99 (10 credits, 500,000-credit tier) to Growth $199 (25 credits, 1.2 million-credit tier)$49.50 pay as you goStandard $99 + $140 extra, $239 total$127.50 at Starter prices$43.75
B: 100,000 TikTok videos + 30,000 Instagram postsRows per page not publishedSame$195 pay as you goSame$345 at Starter prices$3.34 (6,000 requests)
C: 2 million plain pagesBusiness $299Growth $279 (2 million-credit tier)Not pricedScale $749 + $1,000 extra, $1,749 totalNot a fit$1,388 (read, no JavaScript)

For workload A, a mix of products and searches, EveryInfra and Bright Data pay as you go cost the least. The 3,000 Google searches use 75,000 ScraperAPI credits at 25 each, and this pushes the account to the $149 Startup plan.

For workload B, social data, billing per request is about 100 times cheaper than billing per record. At 20 videos per call, 100,000 TikTok videos need only 5,000 requests.

For workload C, a large number of plain pages, ScraperAPI and ZenRows cost less than $0.15 per 1,000 pages on their larger plans: $0.10 on the ScraperAPI Business plan and $0.14 on the $279 ZenRows Growth tier. Our read bill is four to five times higher and does not render JavaScript. We do not recommend that you move this workload to us.

These are the assumptions. For ScraperAPI and ZenRows, we picked the smallest monthly plan that covers the credits. The ZenRows Growth plan has three tiers: $199, $279 and $399 a month for 1.2 million, 2 million and 3 million credits. Rows A and C use different tiers. ZenRows does not publish its multipliers for Amazon and Google, so we show the result at 10 and at 25 credits.

For Firecrawl, we used 5 credits per structured product page. Extra credits cost $5 per 2,000 on Standard and $5 per 5,000 on Scale. For Apify, we used Starter prices and counted the $19 plan fee as prepaid usage. For EveryInfra, we used the prices charged in our tests. If your multipliers are different, change the unit prices and calculate again.

python
# Price one month with your own usage and multipliers
amazon_pages, google_searches = 30_000, 3_000
scraperapi_credits = amazon_pages * 5 + google_searches * 25      # 225,000
everyinfra_usd = amazon_pages * 0.001389 + google_searches * 0.000694
print(scraperapi_credits, round(everyinfra_usd, 2))               # 225000 43.75

Budget limits and overage: what happens when the allowance runs out

Your monthly bill also depends on the rules that apply when your credits run out. The ScraperAPI Hobby, Startup and Business plans cannot buy extra credits. When the credits run out, you wait for the next month, or you turn on auto-upgrade before that happens. Auto-upgrade moves the account to the next plan. From Hobby to Startup, the monthly fee goes from $49 to $149.

Pay as you go is available only on Scaling and higher, with a monthly spending cap that you set (ScraperAPI pricing). Annual billing gives 10% off, and credits reset each month. Is your usage between two plans? Then you pay for the larger plan, or you stop scraping for a few days at month end.

All paid Firecrawl plans can buy extra credits in $5 steps. One step buys 1,000 credits on Hobby, 2,000 on Standard, 2,500 on Growth and 5,000 on Scale. You set a monthly limit, or enter 0 to turn it off. Credits that you buy by hand expire when you cancel the subscription.

Overage ruleScraperAPIZenRowsFirecrawlBright DataApifyEveryInfra
Buy extra creditsScaling and higher onlyNot statedAll paid plans, $5 stepsPay as you goPlan fee is prepaid usageTop up any time
Unused credits roll overNoNot statedScale only, one monthNot applicableNot statedBalance does not expire
Spending limitmax_cost per request, cap on pay as you goCredit limit per keyMonthly pay-as-you-go limitNot statedLimit per runPrepaid balance is the limit
Annual discount10%2 months free16.7% to 20%Not applicableNot statedNo subscription

ZenRows added a credit limit per API key in early October. This is useful when you give a key to an AI agent. Bright Data pay as you go has no monthly fee. On Apify, the plan fee is prepaid usage for the month, and the Store discount tier follows your plan.

Connecting AI tools: MCP at all six services

All six services offer MCP. MCP is the Model Context Protocol, which lets AI tools such as Claude or Cursor call outside APIs (protocol introduction). The differences are the tool design and the billing.

ServiceMCP address or repositoryNotes
ScraperAPIhttps://mcp.scraperapi.com/mcpRemote server with 22 tools in the documentation, same credit rules as the API (MCP docs, repository)
ZenRowshttps://mcp.zenrows.com/mcpRemote server on one shared credit balance (MCP docs, repository)
Bright DataRemote or local5,000 free requests each month (MCP FAQ, repository)
FirecrawlRemote or localVersion 3 released on November 12, 2026 (MCP docs, repository)
Apifyhttps://mcp.apify.comFinds and runs Store tools (MCP docs, repository)
EveryInfrahttps://api.everyinfra.com/mcpBilled per request, slow jobs return a job ID (MCP setup page)

Before you give a key to an AI tool, set a spending limit. On ScraperAPI, the max_cost parameter stops a request above the limit with a 403. On ZenRows, you can set a credit limit per key since October. We bill per request, and the most expensive call in this article was amazon/search at $0.002236. One hundred calls from a model cost $0.22, so you know the upper limit before the calls start.

This is our configuration:

json
{
  "mcpServers": {
    "everyinfra": {
      "url": "https://api.everyinfra.com/mcp",
      "headers": { "Authorization": "Bearer ${EVERYINFRA_API_KEY}" }
    }
  }
}

ZenRows also has a self-serve purchase path for AI agents. An agent can pay for credits on its own at $0.50 per 1,000 credits (agentic payments). This is a little more than the $0.42 on the Build plan, but no person has to start a subscription.

Which scraperapi alternative fits your team

The four jobs and three monthly bills give the decision table below. "First choice" means the service with the lowest cost or the smallest change for the same usage. We use the public prices and test results in this article. Your multipliers, regions and concurrency needs can change the answer.

Main jobFirst choiceSecond choiceReason
Full HTML from thousands of sites, more than 1 million pages a monthScraperAPI or ZenRowsFirecrawl1 credit per plain page, below $0.15 per 1,000 on large plans
Single-page apps that need JavaScript and screenshotsZenRowsScraperAPIZenRows rendering is 5 credits, ScraperAPI is 10
Price and rating checks on hundreds of thousands of ASINsScraperAPI, Startup or higherBright Data$0.46–0.75 per 1,000
Amazon or Walmart product lists by keywordEveryInfraScraperAPI20 rows per call, $0.07–0.12 per 1,000 products
Rank tracking for thousands of Google keywords a dayEveryInfraBright Data$0.694 per 1,000, while ScraperAPI uses 25 credits per search
TikTok and Instagram monitoringEveryInfraApifyPer-request billing, $0.02–0.03 per 1,000 posts
Web pages as Markdown for a language modelFirecrawlEveryInfra readFirecrawl returns Markdown at 1 credit per page
Existing Scrapy or Playwright scripts that only need a proxyScraperAPIZenRowsProxy port mode, no parser changes

For a solo developer or a small team, the first step is usually a trial. The ScraperAPI trial gives 5,000 credits for 7 days. That is enough for 1,000 Amazon product pages or 200 Google searches. The Bright Data free plan gives 5,000 records each month and lasts the longest. Our $1 trial is valid for 24 hours and covers 1,440 Google searches or 1,798 TikTok searches.

Run your three most common jobs a few dozen times each on the free tiers. Record the cost and the row count of each call. Then choose a service and a plan.

When ScraperAPI is the better choice among scraperapi competitors

In these cases, it is cheaper or easier to stay on ScraperAPI.

Case where ScraperAPI fits betterScraperAPI costComparison
2 million plain pages a month$299 (Business)EveryInfra read $1,388, Firecrawl $1,749, ZenRows $279
JavaScript pages, waits, screenshots10 credits per rendered pageOur read returned only the page shell
Existing crawlers that need a proxyProxy port modeEveryInfra does not sell proxies
Single Amazon products at volume$0.459–0.745 per 1,000 (Startup and higher)EveryInfra $1.389 per 1,000

The first case is full HTML from many websites at volume. A plain page costs 1 credit, which is $0.092 per 1,000 on the large plans. Two million pages a month cost $299. Our per-request price is $1,388, and Firecrawl is $1,749. ZenRows is close to ScraperAPI here, at $279 for 2 million credits on its second Growth tier, and its JavaScript multiplier is lower.

The second case is single-page apps that need JavaScript rendering, a wait for an element or a screenshot. In our test at 00:27 Singapore time, our read tool returned only the page shell. The ScraperAPI render=true option with wait_for_selector waits for the content before it returns. If you move these pages to us, you will not get the data.

The third case is existing crawlers that only need proxies and block handling. The ScraperAPI proxy port mode connects directly to Scrapy or Playwright scripts. In October 2026, ScraperAPI made its Akamai bypass automatic, so you no longer need the premium parameter for those sites (release note).

The fourth case is a large volume of single Amazon product pages on Startup or higher. At $0.459 to $0.745 per 1,000, ScraperAPI is cheaper than our $1.389. In July, ScraperAPI also removed the 5x multiplier from DataPipeline, its batch service (release note). Scheduled scraping now costs less too.

In three other cases, ScraperAPI costs clearly more. Google search uses 25 credits per search. Social data needs your own HTML parser. Keyword product search is billed per page, but the row count per page is not fixed.

For these three jobs, look at three other services. Bright Data has per-record billing and a large free tier. Apify has many ready-made tools with settings. EveryInfra has per-request billing. Our Bright Data alternatives, Firecrawl alternatives, ZenRows pricing breakdown and Apify vs Firecrawl articles compare the market from those angles.

What to change when you move from ScraperAPI

A move from ScraperAPI changes three parts of your code. The first is the request format. ScraperAPI uses the query parameters api_key and url, and its structured endpoints use different paths. We use a JSON body with platform, action and params, and the key goes in the Authorization header. The catalog shows the required parameters and an example for each capability.

The second part is field names. The two services return different names, so you need a mapping layer. The common fields, such as price, rating and review count, are present on both sides, but the names and the nesting are different.

The third part is slow jobs. The ScraperAPI async service uses callbacks or polling. Some of our capabilities, such as instagram/user_posts, always run as async jobs and return a job ID. You read the result with GET /api/v1/jobs/{job_id}, and polling is free.

The table below maps the Amazon product fields. The ScraperAPI column uses the return items in its structured data page. The EveryInfra column uses the real field names from our amazon/profile call at 00:29 Singapore time. Both sides cover most of the same data. Our single-product capability has no separate field for specifications. Product bullet points are in features, and keyword search results also include description and bestseller_ranks.

DataScraperAPI structured endpoint (as documented)EveryInfra `amazon/profile` (real fields)
TitleTitletitle
PricePriceprice, currency
Rating and countRating, review countrating, rating_scale, rating_count
IDASINasin
StockAvailabilityin_stock
ImagesImagesimage_url, images
SellerSeller infoseller_name
Description and bulletsDescriptionfeatures
SpecificationsProduct specificationsNo separate field
Brand and categoryNot listedbrand, category, is_amazon_choice

Your cost tracking also changes. At ScraperAPI, you read the sa-credit-cost header. At EveryInfra, each sync response has billing.charged_usd with the dollar charge, and async jobs show billing_state. Log this field in your own system, and you can reconcile at month end without the dashboard.

What ScraperAPI changed in 2026: plans, batch jobs and protected sites

Before you move, look at the direction of ScraperAPI's own pricing. In May 2026, it added two plans above Scaling. Professional costs $975 for 10.5 million credits, and Advanced costs $1,975 for 21.5 million credits. For a limited time, they include 250,000 and 500,000 bonus credits, with 300 and 500 concurrent threads (release note). These plans bring the price to $0.093 and $0.092 per 1,000 credits.

In July, DataPipeline dropped its extra 5x multiplier, and ScraperAPI says that this makes it up to 80% cheaper. In June, it released the domain cost estimator. In October, it made the Akamai bypass automatic.

Changes in the last 30 days

  • On November 17, 2026, Firecrawl announced its first office outside San Francisco, in Toronto. The release repeats its $75 million Series B from September (Business Wire release). For readers: Firecrawl is focused on data sources for AI agents, and its scraping prices did not change.
  • On November 13, 2026, the Firecrawl changelog said that its Alexandria company data now covers more than 75 million companies (changelog). For readers: teams that need company data have one more credit-based source.
  • On November 12, 2026, Firecrawl released MCP version 3, with 60 times higher rate limits and 4 times more usage. For readers: Firecrawl free credits last longer in AI tools.
  • On November 16, 2026 and November 17, 2026, four of the five Apify Store tool pages in this article were updated. The Instagram post tool page shows no update time. For readers: Apify prices change per tool, so read them again each month.
  • On October 22, 2026, Firecrawl added a government and legal index. On October 30, 2026, it added an integration with eve, the Vercel open-source agent framework. For readers: Firecrawl is moving from scraping into ready-made datasets.
  • In October 2026, ScraperAPI made its Akamai bypass automatic. In early October, ZenRows added a Crawl endpoint and a credit limit per key (ZenRows changelog). For readers: if you used premium only for Akamai sites on ScraperAPI, test again without it, because your multiplier can go down.

What YouTube videos and forums say about scraperapi alternatives

We used the EveryInfra youtube/search capability to search for "scraperapi alternatives". At 00:17 Singapore time, it returned 10 videos for $0.000778. We took the transcripts of the three most relevant videos with youtube/transcript, at 00:26 Singapore time, for $0.000556 each.

The first video, uploaded on October 26, 2026, is a 30-second ad from another scraping company. It says that on the ScraperAPI trial, its test cost "over $2 per thousand standard pages". At public prices, a plain page costs 1 credit, which is at most $0.49 per 1,000. A cost above $2 means that those pages used 5 credits or more. The video does not give its URLs or multipliers, so we cannot check the claim.

The second video, from June 2, 2026, is a review. Its main point is that credits run out fast with JavaScript rendering and anti-bot bypass. It tells teams that scrape millions of pages a month to calculate their costs before they buy a large plan. The third video, uploaded on October 19, 2026, compares five services. Its conclusion is that each request type uses a different number of credits, so you must estimate cost for the sites that you actually scrape.

All three videos have zero comments, and their view counts are 9, 59 and 175. The discussion is still small, so the transcripts are the only source of pain points.

VideoUploadedViewsMain claimWhat it does not show
ScraperAPI Alternative Same Pages Lower Cost 2026 Benchmark2026-10-269Over $2 per 1,000 standard pages on the ScraperAPI trialTest URLs and credit multipliers
Scraper API Review: Best Web Scraper Tool in 2026?2026-06-0259Credits run out fast with rendering and anti-bot bypassHow to measure the cost per site
Best Web Scraping API: five-provider comparison2026-10-19175Each request type uses a different credit countAny price per 1,000 results

All three videos say "estimate cost per site", but none shows how. None of them uses the ScraperAPI /account/urlcost endpoint, the sa-credit-cost header, the max_cost limit or the domain estimator. The credit section of this article shows these tools. Run your own URL list through them to get your own multiplier.

On Reddit, a r/WebScrapingInsider thread asks which scraping API to use for e-commerce sites. One reply says to compare the cost per successful page for each domain. It cites a third-party benchmark in which 100,000 Amazon pages cost from $20 to $300 a month, depending on the provider.

A second thread is in r/scrapingtheweb. There, the poster says that credit-based services used credits too fast with JavaScript rendering and premium proxies. The poster later moved to Firecrawl.

Both are single-user reports without outside checks. Use them as a test list. First, calculate the cost per successful page for each domain. Next, check how much the multiplier goes up with rendering and premium proxies. Last, look at the monthly plan fee.

Legal limits

All six services collect data from public pages. You are responsible for the terms of the target site and for local law. If the reviews or posts that you collect contain personal data of people in the EU, follow the GDPR. This article compares prices and billing rules. It does not say whether a given site can be scraped, and it is not legal advice.

Get started: check the numbers with your own list

  1. Open the quickstart and sign up.
  2. Claim the $1 trial as the pricing page explains. It is valid for 24 hours.
  3. Open the Amazon platform page, the TikTok platform page or the data market.
  4. Run your own ASINs and keywords in the test panel.
  5. Record the row count and charged_usd for each call.
  6. Check the ScraperAPI multiplier for the same URLs with /account/urlcost.
  7. Put both prices into the Python example above to get your monthly bill.

FAQ

Which scraperapi alternatives are the cheapest?

(Source: Google suggestions "scraperapi free alternative" and "scraperapi competitors") It depends on the job. At public prices on November 18, 2026, we are the cheapest for Google search at $0.694 per 1,000, while ScraperAPI costs $2.30 to $12.25. For social posts, we charge $0.0185 to $0.0278 per 1,000, at least 47 times less than Bright Data and Apify. For full HTML from arbitrary sites, ScraperAPI and ZenRows cost less than $0.15 per 1,000 pages on large plans, which is cheaper than us.

How do I choose between scraperapi vs firecrawl?

(Source: Google suggestion "scraperapi vs firecrawl") For full HTML, proxies and block handling, choose ScraperAPI, at $0.092 to $0.49 per 1,000 plain pages. For web pages as Markdown for a language model, choose Firecrawl. It costs 1 credit per page, or $0.75 to $3.80 per 1,000. Structured JSON costs 4 more credits per page on Firecrawl, so Amazon data goes above $3.75 per 1,000.

Is ZenRows or ScraperAPI cheaper?

(Source: Google suggestion "zenrows vs scraperapi") For plain pages, the two are close, and the ZenRows large plans are a little lower at $0.067 per 1,000 credits. For JavaScript rendering, ZenRows uses 5 credits and ScraperAPI uses 10, so ZenRows costs half. ZenRows does not publish its credit cost for Amazon or Google. ScraperAPI does (5 and 25), which makes the budget easier to plan. Both say that failed requests are free.

scraperapi vs apify: which is better for social media data?

(Source: Google suggestion "scraperapi vs apify") The Apify Store has ready-made TikTok and Instagram tools that bill per result, at $1.00 to $3.70 per 1,000, and return structured JSON. ScraperAPI scrapes TikTok as a plain page and returns HTML that you must parse, and it does not list Instagram. For social data only, Apify saves development time. EveryInfra bills per request and returns 20 to 30 posts per call, about $0.02 per 1,000 posts.

Is there a pay-as-you-go scraperapi alternative with no subscription?

(Source: Google suggestion "scraperapi free alternative", and credit complaints in the r/scrapingtheweb thread) Yes, there are three. Bright Data pay as you go has no monthly fee and costs $1.50 per 1,000 records. Firecrawl sells extra credits only on paid plans. EveryInfra uses a prepaid balance with a $10 first top-up that does not expire. Each request is charged at the catalog price, and failures and empty results are free. ScraperAPI offers pay as you go only from the Scaling plan up.

Does ScraperAPI have a free tier, and what happens when it runs out?

(Source: Google suggestions "scraperapi free tier" and "scraperapi free plan") Yes. A new account gets a 7-day trial with 5,000 credits. After that, the free plan gives 1,000 credits a month with 5 concurrent threads. Credits do not roll over, and plans below Scaling cannot buy extra credits. At 5 credits per Amazon page, the free plan covers only 200 pages a month. The Bright Data free plan gives 5,000 records a month, the most in this unit.

Is ScraperAPI safe and legal to use?

(Source: Google suggestions "is scraperapi legit" and "is scraperapi legal") ScraperAPI is an established commercial service with public prices, a 7-day refund window and documented billing rules. Whether your use is legal depends on the sites you scrape and how you use the data, and this is the same at every provider. Follow the terms of each target site, and handle personal data under the law where you operate.

References

  1. ScraperAPI pricing, ScraperAPI, read 2026-11-18, https://www.scraperapi.com/pricing/
  2. Credits and Requests Costs, ScraperAPI documentation, read 2026-11-18, https://docs.scraperapi.com/getting-started/quick-start/credits-and-requests-costs
  3. Plans and Billing FAQ, ScraperAPI documentation, read 2026-11-18, https://docs.scraperapi.com/resources/faq/plans-and-billing
  4. Cost Control, ScraperAPI documentation, read 2026-11-18, https://docs.scraperapi.com/control-and-optimization/cost-control
  5. MCP Server, ScraperAPI documentation, read 2026-11-18, https://docs.scraperapi.com/integrations/llm-integrations/mcp-server
  6. scraperapi-mcp repository, GitHub, read 2026-11-18, https://github.com/scraperapi/scraperapi-mcp
  7. Structured Data (AI version), ScraperAPI, read 2026-11-18, https://www.scraperapi.com/docs/ai/structured-data
  8. Pricing (AI version), ScraperAPI, read 2026-11-18, https://www.scraperapi.com/docs/ai/pricing
  9. Akamai-protected sites now unblocked automatically, ScraperAPI release notes, October 2026, https://docs.scraperapi.com/resources/release-notes/october-2026/akamai-protected-sites-now-unblocked-automatically
  10. DataPipeline is now up to 80% cheaper, ScraperAPI release notes, July 2026, https://docs.scraperapi.com/resources/release-notes/july-2026/datapipeline-is-now-up-to-80-cheaper
  11. New Domain Credit Cost Estimator, ScraperAPI release notes, June 2026, https://docs.scraperapi.com/resources/release-notes/june-2026/new-domain-credit-cost-estimator
  12. More credits, higher limits: new growth plans, ScraperAPI release notes, May 2026, https://docs.scraperapi.com/resources/release-notes/may-2026/more-credits-higher-limits-introducing-new-growth-plans-on-scraperapi
  13. ScraperAPI documentation index (llms.txt), read 2026-11-18, https://docs.scraperapi.com/llms.txt
  14. ZenRows pricing, read 2026-11-18, https://www.zenrows.com/pricing
  15. Universal Scraper API reference, ZenRows documentation, read 2026-11-18, https://docs.zenrows.com/fetch/api-reference
  16. Agentic payments, ZenRows documentation, read 2026-11-18, https://docs.zenrows.com/first-steps/agentic-payments
  17. MCP integrations, ZenRows documentation, read 2026-11-18, https://docs.zenrows.com/integrations/mcp/mcp-integrations
  18. zenrows-mcp repository, GitHub, read 2026-11-18, https://github.com/ZenRows/zenrows-mcp
  19. ZenRows changelog, read 2026-11-18, https://docs.zenrows.com/changelog
  20. Amazon ASIN scraping page, ZenRows, read 2026-11-18, https://www.zenrows.com/scrape/amazon-asin
  21. Bright Data pricing overview, read 2026-11-18, https://brightdata.com/pricing
  22. Web Scraper API pricing, Bright Data, read 2026-11-18, https://brightdata.com/pricing/web-scraper
  23. SERP API pricing, Bright Data, read 2026-11-18, https://brightdata.com/pricing/serp
  24. SERP API introduction, Bright Data documentation, read 2026-11-18, https://docs.brightdata.com/scraping-automation/serp-api/introduction
  25. MCP Server FAQs, Bright Data documentation, read 2026-11-18, https://docs.brightdata.com/products/mcp-server/faqs
  26. brightdata-mcp repository, GitHub, read 2026-11-18, https://github.com/brightdata/brightdata-mcp
  27. Sync vs async requests, Bright Data documentation, read 2026-11-18, https://docs.brightdata.com/concepts/sync-vs-async
  28. Firecrawl pricing, read 2026-11-18, https://www.firecrawl.dev/pricing
  29. Billing, Firecrawl documentation, read 2026-11-18, https://docs.firecrawl.dev/billing
  30. Scrape, Firecrawl documentation, read 2026-11-18, https://docs.firecrawl.dev/features/scrape
  31. Search, Firecrawl documentation, read 2026-11-18, https://docs.firecrawl.dev/features/search
  32. MCP Server, Firecrawl documentation, read 2026-11-18, https://docs.firecrawl.dev/mcp-server
  33. firecrawl-mcp-server repository, GitHub, read 2026-11-18, https://github.com/firecrawl/firecrawl-mcp-server
  34. Firecrawl changelog, read 2026-11-18, https://www.firecrawl.dev/changelog
  35. Firecrawl Brings Its Library for the World's Knowledge to Toronto, Business Wire, 2026-11-17, https://www.businesswire.com/news/home/20261117386615/en/Firecrawl-Brings-Its-Library-for-the-Worlds-Knowledge-to-Toronto
  36. Apify pricing, read 2026-11-18, https://apify.com/pricing
  37. Actors in Store, Apify documentation, read 2026-11-18, https://docs.apify.com/platform/actors/running/actors-in-store
  38. Apify MCP server, Apify documentation, read 2026-11-18, https://docs.apify.com/platform/integrations/mcp
  39. apify-mcp-server repository, GitHub, read 2026-11-18, https://github.com/apify/apify-mcp-server
  40. Amazon Product Scraper, Apify Store, read 2026-11-18, https://apify.com/junglee/amazon-crawler
  41. Google Search Results Scraper, Apify Store, read 2026-11-18, https://apify.com/apify/google-search-scraper
  42. TikTok Scraper, Apify Store, read 2026-11-18, https://apify.com/clockworks/tiktok-scraper
  43. Instagram Post Scraper, Apify Store, read 2026-11-18, https://apify.com/apify/instagram-post-scraper
  44. What is the Model Context Protocol, MCP documentation, read 2026-11-18, https://modelcontextprotocol.io/docs/getting-started/intro
  45. EveryInfra capability catalog, read 2026-11-18 00:14, https://api.everyinfra.com/api/v1/social/catalog
  46. EveryInfra search tool catalog, read 2026-11-18, https://api.everyinfra.com/api/v1/search/tools
  47. Which is the best web scraping API for e-commerce sites?, Reddit r/WebScrapingInsider, read 2026-11-18, https://www.reddit.com/r/WebScrapingInsider/comments/1vsd1ot/which_is_the_best_web_scraping_api_for_ecommerce/
  48. I'm looking for ScrapingBee Alternatives in 2026, Reddit r/scrapingtheweb, read 2026-11-18, https://www.reddit.com/r/scrapingtheweb/comments/1v85plc/im_looking_for_scrapingbee_alternatives_in_2026/
  49. ScraperAPI Alternative Same Pages Lower Cost 2026 Benchmark, YouTube, 2026-10-26, https://www.youtube.com/watch?v=PkaI1bDWhAw
  50. Scraper API Review: Best Web Scraper Tool in 2026?, YouTube, 2026-06-02, https://www.youtube.com/watch?v=niOu3F7fVlw
  51. Best Web Scraping API: five-provider comparison, YouTube, 2026-10-19, https://www.youtube.com/watch?v=hvmfHAYxgLQ
  52. Regulation (EU) 2016/679 (GDPR), EUR-Lex, https://eur-lex.europa.eu/eli/reg/2016/679/oj

Reference BL-183

Google Analytics needs consent. Privacy