Are you an AI agent? To use String, read https://usestring.ai/agent-onboarding/SKILL.md first. It gets you your own key with one browser click from the person you work for, and you can start at https://mcp.usestring.ai with no key.
NewString UnraveledResearch powered by data we scrape from the web.Read the latest issue →
← Comparisons

Best E-commerce Scraping APIs for Price Monitoring (2026)

Bruce Magness, Chief of Staff, String · Published September 22, 2026 · Updated November 11, 2026

Last updated: November 11, 2026. Benchmark figures come from the October 30, 2026 run of the Web Data Frontier Benchmark. Pricing was checked against each vendor's published pages on October 14, 2026, Oxylabs' on November 17, 2026, and String's on October 28, 2026.

What is the best API for scraping e-commerce sites?

String is the pick for most e-commerce price monitoring. In the October 30, 2026 benchmark run it returned content on 98.6% of requests across the 43 retail, fashion, marketplace and grocery sites, the highest of 17 APIs. Scrape.do placed second at 88.8% and Context.dev third at 85.6%. Choose a site-specific Apify Actor only when you need structured fields rather than page content, and check the grocery and retail groups separately before you commit.

TL;DR

  • On the 43 e-commerce sites, String returned 212 of 215 requests, or 98.6% (as of the October 2026 benchmark run, benchmark), the highest of 17 APIs in the run.
  • In the October 2026 run, Scrape.do returned 191 of 215, or 88.8%, at a median of 3.8 seconds per site, second to String's 2.5.
  • The sub-vertical spread. Score each provider on retail, fashion, marketplaces and grocery separately and the median provider's best group beats its worst by 22.8 points in the October 2026 run. Ten of the 17 swing by more than 20. String's spread is 12.0 points, the narrowest; Nimble's is 52.9, the widest.
  • Returning a site sometimes is the failure that hurts a price history. ScraperAPI and Bright Data each returned partial results on 22 of the 43 sites in the October 2026 run, more than half.
  • Missed days. A daily price check on the 43 sites, with one retry, would leave about 11 of 1,290 site-days blank on String over a month, all of them on kroger.com. In the October 2026 run, Scrape.do would leave about 115, ScraperAPI about 244 and Bright Data about 247.
  • No site in the set shut String out. It returned temu.com on all five attempts, and the other 16 providers returned nothing from it.
  • Four of the eight priced APIs charge more for a protected retail page than for a plain one. Oxylabs is the only one that charges less for a named retail site than for a general one.
  • String scored 100% on retail, fashion and marketplaces, and 88.0% on grocery in the October 2026 run, where Nimble leads at 100%.
  • Every figure comes from a public harness you can rerun with your own API keys.

Nine e-commerce scraping APIs at a glance

Success is the share of 215 requests that came back with real page content. The e-commerce path rate is what each vendor's own published rules charge for a protected retail page, at the plan nearest $100 a month billed monthly.

API E-commerce success Full returns, of 43 sites Median time per site Plan at ~$100 E-commerce path, per 1,000 The catch
String 98.6% 42 2.5s Growth, $99 $0.90 premium One endpoint for every site; bills only for returned content
Scrape.do 88.8% 36 3.8s not checked not checked Pricing not in this page's check; three e-commerce shutouts
ScrapingBee 83.7% 31 23.2s Startup, $99 $2.475 premium with JS Its own docs route e-commerce to the 25-credit tier
Firecrawl 81.9% 35 6.9s Standard, $99 $0.99 flat Bills a returned 403 or 404; seven shutouts
Scrapfly 78.6% 25 9.8s Pro, $100 $2.50 residential Partial on 13 sites; credits do not roll over
Apify 77.2% 26 18.4s none; $19 or $199 $1.00 Web Fetch Prepaid usage expires monthly; a converted 404 still bills
ScraperAPI 71.6% 18 6.2s none; $49 or $149 $1.639 protected, $0.745 Amazon Bills a returned 404; partial on 22 sites
Bright Data 71.2% 15 24.3s none; $1.50 or $499 $1.50 No plan between the free tier and $499
Oxylabs 67.9% 25 12.2s Basic, $100 $0.45 Amazon, $1.40 with JS Basic covers about 111,000 general results a month, or 222,000 on Amazon

Eight more APIs ran the same 43 sites in the October 30, 2026 run and are not profiled here: Context.dev 85.6%, Zyte 74.9%, Decodo 73.0%, Nimble 62.3%, ZenRows 54.9%, Browserbase 37.2%, ScrapingAnt 35.8% and Scrapingdog 23.7%. Context.dev and Zyte both outscored three of the profiled APIs in this run; they are left out because this page's pricing check did not cover them.

How we tested these e-commerce scraping APIs

The Web Data Frontier Benchmark ran on October 30, 2026. It calls 17 scraping APIs against 100 bot-protected sites, five attempts each, 500 requests per provider, with a 90-second timeout. A request counts as a success only when the response carries the target page's real content. A challenge page, an empty shell, a block page and a timeout all count as failures, which is why several vendors score far below the uptime figures on their own sites.

This page scores a subset. Of the 100 targets, 43 sit in four e-commerce groups: Retail and ecommerce (17 sites), Fashion and luxury (11), Marketplaces and classifieds (10), and Grocery and food (5). That is 215 requests per provider. The groups come from the industry field each target carries in the harness, so the split is the harness's, not ours.

One caveat belongs next to every rank on this page. The benchmark's adapters have changed between runs, and several vendors ran below the setting they now document for bot-protected pages in the earlier runs: Scrapfly, Firecrawl, ScraperAPI, Zyte, ScrapingAnt, ScrapingBee, Scrapingdog and Nimble. ScraperAPI moved from 64.2% to 84.0% overall between the August and September 2026 runs, and ScrapingBee from 29.7% to 73.0%. Those jumps measure our adapters catching up more than they measure a product change. Their September and October numbers are the fair ones; their August numbers were not. Scrape.do joined the field in the October run.

Chart data
ProviderSuccess ratePassedLatency score
String98.6%493/5004.24s
Scrape.do94.0%470/5005.08s
Context.dev93.0%465/50010.96s
Scrapfly86.8%434/50019.62s
ScrapingBee85.2%426/50020.30s
Firecrawl81.2%406/5008.87s
Zyte79.6%398/50014.43s
Apify79.4%397/50024.87s
ScraperAPI76.4%382/50015.19s
Bright75.4%377/50027.88s
Decodo71.2%356/50028.29s
Nimble68.0%340/50022.65s
Oxylabs67.4%337/50016.62s
Browserbase43.0%215/50018.01s
ZenRows41.8%209/50021.91s
ScrapingAnt40.0%200/50018.39s
Scrapingdog27.6%138/50031.52s
Overall success rate across all 500 requests per provider. Web Data Frontier Benchmark · 100 targets · 500 requests per provider · October 30, 2026. Current leaderboard

Most e-commerce is easy, and that is the point

Before any of these numbers mean anything, the honest objection: you may not need to buy anything. On r/webscraping in May 2025, a practitioner running price collection at industrial volume put the ceiling of the cheap approach plainly.

u/Pigik83 on r/webscraping: one billion product prices a month on a proxy bill under $1,000, covering 60 to 70 percent of e-commerce sites

That is the right frame for this page. Rotating cloud IPs gets you most of the catalogue for almost nothing. The 43 sites in the October 30, 2026 benchmark run are the other 30 to 40%: the ones that carry DataDome, Akamai or a self-built wall, and the ones a scraping API exists to reach. Every rate below is a rate on that hard tail, not on e-commerce as a whole.

The sub-vertical spread

A shortlist built on one headline number assumes a provider is equally good at Amazon, at Louis Vuitton, at eBay and at Kroger. Almost none of them are. Score the 17 providers on the four e-commerce groups separately and the median provider's best group beats its worst by 22.8 points in the October 30, 2026 run. Ten of the 17 swing by more than 20 points inside e-commerce alone.

API Retail Fashion Marketplaces Grocery Spread
String 100% 100% 100% 88.0% 12.0
ScrapingBee 78.8% 90.9% 82.0% 88.0% 12.1
Firecrawl 76.5% 90.9% 82.0% 80.0% 14.4
ScraperAPI 63.5% 80.0% 76.0% 72.0% 16.5
Zyte 68.2% 72.7% 86.0% 80.0% 17.8
Decodo 63.5% 81.8% 78.0% 76.0% 18.3
Apify 68.2% 81.8% 82.0% 88.0% 19.8
Scrapfly 71.8% 78.2% 94.0% 72.0% 22.2
Bright Data 61.2% 74.5% 78.0% 84.0% 22.8
Context.dev 75.3% 100% 90.0% 80.0% 24.7
Scrape.do 85.9% 90.9% 100% 72.0% 28.0
Browserbase 36.5% 32.7% 32.0% 60.0% 28.0
ZenRows 54.1% 69.1% 48.0% 40.0% 29.1
Scrapingdog 17.6% 23.6% 22.0% 48.0% 30.4
Oxylabs 67.1% 47.3% 84.0% 84.0% 36.7
ScrapingAnt 37.6% 32.7% 22.0% 64.0% 42.0
Nimble 47.1% 63.6% 68.0% 100% 52.9

Nimble is the clearest case. In the October 30, 2026 run it was the only provider of 17 to return every grocery request, at 100%, and fourteenth on plain retail at 47.1%. Evaluate it on Kroger and Safeway and you will buy it. Point it at Best Buy and Home Depot and half your rows go missing. Our Walmart scraping guide shows what a plain client gets on a big-box retailer. Oxylabs runs a different split: 84.0% on marketplaces and on grocery, and 47.3% on fashion and luxury, fourteenth of 17.

This is why a two-site trial tells you almost nothing. If your catalogue crosses groups, test across groups.

Chart data
ProviderRetail & ecommerce (17 sites)Fashion & luxury (11 sites)Marketplaces & classifieds (10 sites)Travel (9 sites)News & finance (9 sites)Social media (8 sites)Real estate (7 sites)Reviews & local (6 sites)Jobs & hiring (5 sites)Grocery & food (5 sites)Tickets & events (4 sites)Developer & research (3 sites)Search engines (2 sites)Gaming & betting (2 sites)Government (1 sites)Health & pharmacy (1 sites)
String100.0%100.0%100.0%97.8%95.6%100.0%100.0%96.7%100.0%88.0%100.0%100.0%100.0%100.0%100.0%100.0%
Scrape.do85.9%90.9%100.0%86.7%100.0%100.0%100.0%100.0%100.0%72.0%100.0%100.0%100.0%100.0%100.0%100.0%
Context.dev75.3%100.0%90.0%100.0%100.0%100.0%100.0%100.0%88.0%80.0%100.0%100.0%100.0%100.0%100.0%80.0%
Scrapfly71.8%78.2%94.0%88.9%100.0%92.5%97.1%90.0%96.0%72.0%100.0%100.0%60.0%70.0%100.0%100.0%
ScrapingBee78.8%90.9%82.0%68.9%88.9%92.5%82.9%90.0%88.0%88.0%100.0%100.0%50.0%100.0%100.0%100.0%
Firecrawl76.5%90.9%82.0%88.9%88.9%25.0%100.0%83.3%96.0%80.0%100.0%66.7%60.0%100.0%100.0%100.0%
Zyte68.2%72.7%86.0%77.8%100.0%82.5%71.4%60.0%76.0%80.0%95.0%100.0%80.0%100.0%100.0%100.0%
Apify68.2%81.8%82.0%73.3%86.7%82.5%97.1%93.3%80.0%88.0%50.0%100.0%50.0%50.0%100.0%80.0%
ScraperAPI63.5%80.0%76.0%86.7%88.9%60.0%85.7%70.0%88.0%72.0%80.0%93.3%80.0%90.0%100.0%0.0%
Bright61.2%74.5%78.0%68.9%71.1%87.5%94.3%93.3%76.0%84.0%45.0%86.7%40.0%100.0%100.0%100.0%
Decodo63.5%81.8%78.0%68.9%100.0%92.5%82.9%63.3%80.0%76.0%0.0%53.3%0.0%50.0%0.0%100.0%
Nimble47.1%63.6%68.0%71.1%86.7%95.0%71.4%50.0%64.0%100.0%25.0%86.7%60.0%100.0%60.0%80.0%
Oxylabs67.1%47.3%84.0%64.4%97.8%87.5%62.9%50.0%84.0%84.0%0.0%66.7%50.0%50.0%0.0%100.0%
Browserbase36.5%32.7%32.0%22.2%77.8%100.0%42.9%0.0%20.0%60.0%30.0%33.3%100.0%50.0%0.0%80.0%
ZenRows54.1%69.1%48.0%44.4%51.1%25.0%20.0%40.0%60.0%40.0%0.0%0.0%0.0%0.0%0.0%80.0%
ScrapingAnt37.6%32.7%22.0%37.8%53.3%70.0%40.0%10.0%32.0%64.0%25.0%66.7%50.0%90.0%0.0%0.0%
Scrapingdog17.6%23.6%22.0%28.9%13.3%62.5%34.3%10.0%20.0%48.0%15.0%46.7%90.0%30.0%20.0%0.0%
Success rate by industry vertical. Web Data Frontier Benchmark · 100 targets · 500 requests per provider · October 30, 2026. Current leaderboard

The sites that are actually hard

Difficulty in e-commerce is not spread evenly. Most of the 43 sites open for most providers in the October 30, 2026 run. A short list of them opens for almost nobody, and those are the ones that decide whether a crawl is complete.

Site Group Field average Returned all five attempts
temu.com Retail 5.9% String
mouser.com Retail 24.7% String, Firecrawl
coupang.com Retail 35.3% String, Scrape.do, Oxylabs
us.louisvuitton.com Fashion 41.2% String, Scrape.do, Context.dev, Scrapfly, Firecrawl, Decodo
kroger.com Grocery 42.4% Scrape.do, ScrapingBee, Firecrawl, ScraperAPI, Nimble
bestbuy.com Retail 43.5% String, Context.dev, ScrapingBee, Apify, Bright Data, Oxylabs
buybuybaby.bedbathandbeyond.com Retail 49.4% String, Scrape.do, ScrapingBee, Firecrawl, Decodo, Oxylabs
emag.ro Retail 50.6% String, Scrape.do, Context.dev, Scrapfly, ScrapingBee, Decodo, ZenRows
cargurus.com Marketplaces 50.6% String, Scrape.do, Context.dev, Scrapfly, Firecrawl, Decodo

temu.com returned nothing to anyone in the September 16 run, and nothing to any of the fifteen providers in the field on August 11. Its benchmark fixture was repaired for the October run. String then returned it on all five attempts, and the other 16 providers returned nothing across 80 requests. If Temu is on your list, ask any other vendor for a live demonstration.

kroger.com is the one e-commerce site where String is beaten outright. In the October 30, 2026 run it returned two of five attempts, while Scrape.do, ScrapingBee, Firecrawl, ScraperAPI and Nimble returned it in full. Every other site in the set went to String on all five attempts.

Best Buy is the sharpest illustration of the spread argument. In the October 30, 2026 run, six providers returned it in full: String, Context.dev, ScrapingBee, Apify, Bright Data and Oxylabs. Three of those six rank eighth or lower overall, and Scrape.do and Firecrawl, second and sixth overall, returned it on two attempts and none.

Partial returns are the expensive failure

A blocked request is loud. You see the error, you retry, you move on. The failure that damages a price history is quieter: the site comes back on three attempts out of five and nothing on the other two. If you need price history from before you started collecting, see how to get historical website data.

Retail sites are unusually good at producing that quiet failure, because several of them strip the data rather than refuse the request.

u/MrKrotchy on r/webscraping: if Amazon detects you it will delete the price tag or other tags

A 200 response with the price removed does not look like a block to any code you have written. It looks like a product with no price. The same failure shows up in open-source trackers: in issue #22 on the ItemStockTracker project, opened in September 2021 and still open today, the reporter describes an Amazon captcha page that arrives intermittently and the tracker recording "No Stock Info" in its place.

ItemStockTracker issue 22: Amazon returns a captcha page sometimes, and the scraper records No Stock Info

On the 43 e-commerce sites in the October 30, 2026 run, here is how each provider's attempts split.

API All five Partial None
String 42 1 0
Scrape.do 36 4 3
Context.dev 36 1 6
Firecrawl 35 1 7
ScrapingBee 31 8 4
Zyte 27 8 8
Apify 26 12 5
Scrapfly 25 13 5
Oxylabs 25 8 10
Nimble 23 8 12
Decodo 21 16 6
ScraperAPI 18 22 3
ZenRows 18 8 17
Bright Data 15 22 6
Browserbase 11 7 25
ScrapingAnt 10 12 21
Scrapingdog 3 16 24

ScraperAPI is the shape to watch. In the October 30, 2026 run it returned something on 40 of the 43 sites, which sounds fine, and returned all five attempts on only 18. More than half its sites are partial, and Bright Data's split is the same, 22 partial of 43. Run a daily price collection on that and two runs of the same job disagree with each other with no code change in between, and the gaps land in whichever SKUs happened to fail that morning. A dashboard built on it does not look broken. It looks slightly wrong, in a different place each day.

Across the whole field in the October 30, 2026 run, 22.8% of the 731 provider and site pairs in the e-commerce set were partial. The same measure across all 100 benchmark sites is 19.5%. E-commerce is flakier than the run as a whole.

Anti-bot walls on retail sites

Retail sites run the heaviest bot protection on the open web, because scraping them has direct commercial value to a competitor. The four vendors that cover most of the set are Cloudflare, whose own docs describe four detection engines feeding one bot score, DataDome, Akamai Bot Manager and HUMAN, formerly PerimeterX. The benchmark records which vendor protects each target, and the field-wide table below covers all 100 sites rather than the 43 here, so read it as context rather than as an e-commerce ranking.

Chart data
ProviderDataDome (19 sites)Akamai (20 sites)Cloudflare (15 sites)PerimeterX (9 sites)AWS WAF (6 sites)Kasada (3 sites)Fastly (1 sites)Proprietary / other (27 sites)
String97.9%97.0%98.7%97.8%100.0%100.0%100.0%100.0%
Scrape.do97.9%87.0%93.3%100.0%100.0%100.0%100.0%92.6%
Context.dev100.0%79.0%96.0%97.8%100.0%100.0%100.0%92.6%
Scrapfly92.6%78.0%93.3%93.3%96.7%86.7%40.0%83.0%
ScrapingBee85.3%74.0%97.3%88.9%63.3%100.0%100.0%88.1%
Firecrawl85.3%80.0%98.7%100.0%83.3%100.0%100.0%60.0%
Zyte68.4%68.0%92.0%91.1%70.0%100.0%100.0%84.4%
Apify85.3%69.0%86.7%86.7%63.3%100.0%0.0%80.7%
ScraperAPI75.8%81.0%70.7%82.2%76.7%53.3%100.0%76.3%
Bright74.7%72.0%74.7%86.7%73.3%66.7%100.0%75.6%
Decodo65.3%68.0%73.3%86.7%73.3%100.0%0.0%70.4%
Nimble64.2%51.0%68.0%82.2%40.0%86.7%100.0%81.5%
Oxylabs67.4%53.0%68.0%91.1%16.7%100.0%0.0%80.0%
Browserbase31.6%28.0%6.7%73.3%16.7%33.3%0.0%80.7%
ZenRows52.6%57.0%33.3%73.3%36.7%60.0%0.0%17.8%
ScrapingAnt7.4%33.0%24.0%53.3%13.3%53.3%100.0%74.8%
Scrapingdog16.8%27.0%29.3%6.7%13.3%20.0%0.0%46.7%
Success rate by anti-bot vendor. Web Data Frontier Benchmark · 100 targets · 500 requests per provider · October 30, 2026. Current leaderboard

DataDome covers 19 sites in the October 30, 2026 run, and it separates the field widely: Context.dev returned 100% of DataDome requests, String and Scrape.do 97.9%, ScraperAPI 75.8%, and ScrapingAnt 7.4%. Akamai covers 20 sites, where String returned 97.0%, Scrape.do 87.0% and ScraperAPI 81.0%.

If your target list is mostly US big-box retail, the DataDome column is the one to read first.

These walls are not a theoretical tax. Camoufox, one of the better open-source stealth browsers, carries an issue in which a DataDome-protected classifieds site blocks it on every attempt while the same IP loads the page fine in a private browser tab. On the retail side, an MCP server built specifically to read Walmart has an open issue from July 2026 reporting that its headless sessions are blocked by Walmart's bot detection even when the session is authenticated. Both are the ordinary condition, not edge cases, and they are the reason this benchmark scores content returned rather than requests sent.

How to monitor competitor prices with a scraping API

A daily competitor price check needs five things: a short SKU list, a matched product page per competitor, a fetch, a parser, and an alert. The scraping API is one of the five, and it is the one that decides how many days your price history has a hole in it.

A small shop tracking 20 to 30 products can start with a price-tracker tool or a page-change monitor. One owner on r/smallbusiness described spending 1 to 2 hours every day checking about 20 to 30 products by hand, with a budget under $100 a month. That is a tracker-tool problem. A scraping API fits when you have your own SKU list, your own repricing rules, or competitors the tracker tools do not cover. A 30-SKU daily check is about 900 requests a month, which uses $0.81 (as of October 2026) of usage at String's $0.90 per 1,000 premium rate on the Growth plan.

Step 1: pick the SKUs that move your margin

Start with the 20 to 50 products that drive revenue or have thin margins. Add the long tail later, on a slower schedule.

Step 2: match each SKU to one competitor page

Match on GTIN, MPN or model number, not on the product title. A bundle, a different size or a refurbished unit is a different price. Store the matched URL per competitor per SKU.

Step 3: fetch the page and read the price

Read the price from the page's Product schema first, and fall back to the page's own data when there is none. Walmart is the example: on Oct 14 its product page carried no Product schema at all, and the price sat in a currentPrice object in the page state.

import json, os, re, requests

def fetch(url):
    r = requests.post("https://request.usestring.ai/v1/fetch",
                      headers={"Authorization": f"Bearer {os.environ['STRING_API_KEY']}"},
                      json={"url": url, "countryCode": "US"}, timeout=90)
    r.raise_for_status()
    page = r.json()
    if page["statusCode"] != 200:
        raise RuntimeError(f"{url} returned {page['statusCode']}")
    return page["data"]

def read_price(html):
    for block in re.findall(r'<script[^>]*application/ld\+json[^>]*>(.*?)</script>', html, re.S):
        try:
            data = json.loads(block)
        except ValueError:
            continue
        for item in data if isinstance(data, list) else data.get("@graph", [data]):
            offers = item.get("offers") if isinstance(item, dict) else None
            if isinstance(offers, list):
                offers = offers[0] if offers else None
            if isinstance(offers, dict) and (offers.get("price") or offers.get("lowPrice")):
                return float(offers.get("price") or offers.get("lowPrice"))
    m = re.search(r'"currentPrice":\{"price":([0-9.]+)', html)  # Walmart keeps it here
    return float(m.group(1)) if m else None

On Oct 14 2026 this read a price from all four benchmark product pages we tried it on: Best Buy, Home Depot, AutoZone and Walmart. Pin countryCode on every call. A price fetched from a different country is a different price.

Step 4: set the cadence by how fast prices move

Electronics and marketplaces move within a day, apparel and home goods daily, industrial and B2B weekly. Run each SKU once per cycle and retry once on failure.

Step 5: store a gap as a gap, and alert on change

Write a blank, never a zero, when a fetch fails. Alert when a matched price moves past your threshold, and alert separately when a SKU has been blank for two days running. For the legal side, see is it legal to scrape competitor prices.

How many days each API would leave blank

A retry helps on a site that fails some of the time. On a site that never answers, it adds nothing.

We modelled a 30-day daily check on the 43 benchmark sites: one request per site per day and one retry on failure, 1,290 site-days in all. Each site's odds come from its five attempts in the October 30 run.

API Blank site-days, no retry Blank site-days, one retry Of those, on sites it never returned
String 18 11 0
Scrape.do 144 115 90
ScrapingBee 210 164 120
Scrapfly 276 199 150
Apify 294 222 150
Firecrawl 234 229 210
ScraperAPI 366 244 90
Bright Data 372 247 180
Oxylabs 414 366 300

String's 11 blank days in the October 30, 2026 run are kroger.com, which it returned on two of five attempts; it never shut out on a site in the set. For Firecrawl, 210 of 229 blank days are seven sites it never returned, and for Oxylabs 300 of 366 are ten, so a retry barely moves them. ScraperAPI and Bright Data are the opposite case: most of their gaps are partial sites, so one retry takes ScraperAPI from 366 blank days to 244 and Bright Data from 372 to 247. The model treats each try as independent, which flatters every provider on a site that blocks in streaks. Get an API key and run read_price(fetch(url)) on your own SKU list.

Price monitoring software or a scraping API: which is better for tracking 5,000 competitor products?

At 5,000 products, a scraping API is the better fit when you want raw prices in your own database and your own repricing rules. Monitoring software is the better fit when you want matching, dashboards and alerts without writing code. The two split on who owns the pipeline, not on price.

  • Monitoring software (Prisync and Price2Spy are the usual names) bundles the fetch, the product matching, the history and the alerts. You pay per tracked product, and you work inside its dashboard and export formats. Check the vendor's current plan page for what 5,000 products costs; this page did not verify either vendor's pricing.
  • A scraping API returns the page, and you write the matching, the parser and the store. The cost is per request, and you keep the raw rows.

The request math is simple. A daily check on 5,000 products is 150,000 requests in a 30-day month. On String's Growth plan, as of October 2026, a premium fetch is $0.90 per 1,000, so that is $135 of usage; at the Scale rate of $0.55 per 1,000 it is $82.50. Most of the work is not in that bill. It is the matching of 5,000 SKUs to competitor URLs and the handling of the days a page comes back blank, which the missed-days table above models.

How to scrape e-commerce reviews at scale

Scrape reviews the way you scrape prices: fetch each product page, read the structured data first, and page through the rest. Three habits keep a review pull complete at volume.

  • Read the summary from the page's schema. Many product pages carry an aggregateRating block in their JSON-LD with the rating and the review count. It is one fetch per product and it does not need a browser.
  • Treat pagination as its own failure point. Reviews sit behind "next page" links or a load-more call. A run that gets page 1 and loses page 3 looks complete and is not, so store the page number with every row and write a gap as a gap.
  • Keep the fetch and the parse apart. Save the raw response, then parse it. A review layout changes more often than a price field, and a saved response lets you re-parse without fetching again.

The partial-return table above applies here with more force: a review pull makes many requests per product, so a provider that returns a site on three attempts out of five loses a larger share of the rows. Check a provider's all-five count on your own sites, not its headline rate.

How to build a shopping assistant that reads live prices

Fetch the product page when the user asks, read the price from the page, and answer from that one read. The steps are the same as the price-monitor steps above, run on demand instead of on a schedule.

  1. Resolve the product to a URL. Search for the product, or take the URL the user pasted.
  2. Fetch with the same fetch(url) call and countryCode as above, and read the price with read_price. Return the price, the page URL and the time of the read.
  3. Cache each read for a short window. A user comparing three shops should not trigger the same fetch twice. How long a price stays valid depends on the category: electronics and marketplaces move within a day.
  4. Say so when a read fails. Tell the user the price could not be read, and never show a stale number as live. A blank is better than a wrong price.

Latency sets what the assistant can promise. Median time per e-commerce site was 2.5 seconds for String and 3.8 for Scrape.do in the October 30, 2026 run (benchmark), against 18.4 for Apify and 24.3 for Bright Data, so a chat reply that waits on a fetch needs one of the fast pair.

What are the alternatives to Prisync and Price2Spy for raw competitor price data?

The alternative to a monitoring tool such as Prisync or Price2Spy is a scraping API that returns the page itself, so you hold the raw prices. Of the APIs profiled here, in the October 30, 2026 run of the Web Data Frontier Benchmark (as of October 2026), String returned content on 98.6% of the 43 e-commerce sites' requests, Scrape.do 88.8% and ScrapingBee 83.7%; the table at the top has all nine. You trade the tool's matching and dashboards for the prices as rows you own, and you write the parser and the alerts yourself. The five steps in the price-monitor method above are that build. If you only need the prices and already know your competitors' URLs, the API is the shorter path.

String: 98.6% and the narrowest spread

String is a single fetch endpoint for retail and marketplace teams that need every page back, and it bills only for pages it returns. In the October 30, 2026 run it returned 212 of 215 e-commerce requests. It cleared 42 of the 43 sites on all five attempts, shut out on none, and left one partial. Its four group scores are 100%, 100%, 100% and 88.0%, which is a spread of 12.0 points, the narrowest in the run. Median time per site was 2.5 seconds, also the fastest of the 17.

The product is one fetch endpoint. String's docs set the escalation as search, then fetch, then a browser session. You send a URL, you get content, and billing counts only the requests that come back with content. The Growth plan is $99 a month (as of October 2026) at $0.16 per 1,000 standard fetches and $0.90 per 1,000 on the premium path, which is where protected retail pages land. Credits roll over. The first 20,000 standard fetches need no card.

Its one miss is kroger.com, where it returned two of five attempts and five other providers returned all five. It was the only provider to return temu.com. One fetch endpoint covers every site, Amazon included. For structured product fields, read the JSON-LD the page already carries or send a JSON Schema with the fetch; which scraping API returns clean structured JSON tests both on these sites. High-volume work is priced on a custom Enterprise rate card.

Full method and per-site results.

Scrape.do: second on e-commerce, and second-fastest

Scrape.do joined the benchmark in the October 30 run and returned 191 of 215 e-commerce requests, second only to String. It cleared 36 of the 43 sites on all five attempts, tied with Context.dev, and its median of 3.8 seconds per site is second to String's 2.5. It ties String for first on marketplaces and classifieds at 100%, and it is second of 17 on plain retail at 85.9%.

Grocery is its weak group at 72.0% in the October 30, 2026 run, joint eleventh of 17: asda.com returned nothing and allmenus.com three of five. It also shut out on temu.com and shop.lululemon.com, and returned bestbuy.com on two of five attempts. It did take kroger.com in full, the one site String missed. Across all 100 sites it was second of 17 at 94.0%, and 16 of its 2xx responses were not the target page.

Scrape.do's pricing was not part of this page's October 14 check, so it is not in the cost table below. Scrape.do alternatives.

ScrapingBee: even across groups, slow per site

In the October 30, 2026 run ScrapingBee returned 180 of 215, and its spread is the second-narrowest in the field at 12.1 points. Retail 78.8%, third of 17. Fashion and luxury 90.9%, joint third. Grocery 88.0%. Marketplaces 82.0%. Its cost is time: a median of 23.2 seconds per site, second-slowest of the nine profiled here.

Its credit ladder is the clearest statement any vendor on this page makes about e-commerce. From its own documentation: hard-to-scrape e-commerce websites need premium_proxy=true, which costs 10 credits without JavaScript rendering and 25 with it. The Startup plan is $99 a month (as of October 2026) for 1,000,000 credits, so $0.099 per 1,000 credits. A plain page is $0.099 per 1,000. The premium-with-JavaScript path that its docs send retail to is $2.475 per 1,000, twenty-five times as much. Stealth with JavaScript is 75 credits, $7.425 per 1,000. Prices exclude VAT.

Auto-Mode is the mitigation and it is a good one. Set mode=auto and ScrapingBee tries configurations cheapest first, charges only for the one that worked, and charges zero if all of them fail. max_cost caps how far it will climb.

ScrapingBee also ships dedicated Amazon, Walmart, Home Depot and Costco endpoints, which none of the benchmark's general adapters exercise. If your list is one or two large US retailers, those are worth a trial that this benchmark does not measure.

Firecrawl: one flat rate and 35 sites in full

In the October 30, 2026 run, Firecrawl returned 176 of 215, and it cleared 35 of 43 sites on all five attempts, behind String's 42 and the 36 of Scrape.do and Context.dev. It is one of two providers that took mouser.com in full, a site where the field averaged 24.7%.

Its pricing is the simplest here. One credit is one page, with no proxy class, no anti-bot surcharge and no per-domain multiplier. Standard is $99 a month billed monthly, or $83 a month billed annually, for 100,000 credits: $0.99 per 1,000 pages whatever the site (as of October 2026). Firecrawl's pricing page shows annual prices by default, so read the toggle before you compare it with anything; the machine-readable version states the same rates without the toggle.

Read the billing rule carefully, though. A scrape that returns no result is not charged, but a page that answers with a 403 or a 404 is returned to you and costs a credit, so a wall that serves a polite error is billable. Firecrawl also shut out entirely on seven of the 43 sites in the October 30, 2026 run, more than String, Scrape.do, Scrapfly or ScraperAPI. Firecrawl's full profile.

Scrapfly: third on marketplaces, weakest on retail

In the October 30, 2026 run, Scrapfly returned 169 of 215. Marketplaces and classifieds is its best group at 94.0%, third behind String and Scrape.do at 100%. Retail is its weak group at 71.8%, and it left 13 of the 43 sites partial.

Pro is $100 a month (as of October 2026) for 1,000,000 credits. An HTTP scrape on a datacenter IP is 1 credit, so $0.10 per 1,000. JavaScript rendering or the Unblocker is 5 credits, and residential proxies are 25, which is $2.50 per 1,000 on the path most protected retail pages need. Failed requests are never charged. Quotas reset at renewal with no rollover.

One thing to check before you budget. The credit table on Scrapfly's pricing page prices the Unblocker at 5 credits, and the sample API response further down the same page shows "asp_cost": 30 on a request with "asp": true. Those two numbers are hard to reconcile. Ask their support which applies to your traffic.

Scrapfly's median per site on the e-commerce set was 9.8 seconds in the October 30, 2026 run, against String's 2.5 and ScraperAPI's 6.2. On a nightly batch that is irrelevant. On anything a user waits for, it is not. More on Scrapfly's speed profile.

Apify: a store of prebuilt retail scrapers, and a general fetch

Apify returned 166 of 215 through its adapter in the October 30, 2026 run. Grocery is its best group at 88.0% and retail its worst at 68.2%.

Apify is not shaped like the rest of this list. It is a marketplace of 116,301 Actors, which are prebuilt scrapers you rent, plus a general fetch path. Its anti-blocking page puts the promise plainly: "If we get blocked, we try again, but we charge you only for valid output." For e-commerce the marketplace is the real argument: someone has usually already written the Amazon or Shopify scraper you need, and it returns structured fields rather than page content.

The general path is Web Fetch, priced from $1.00 per 1,000 fetches on pay-per-event billing, charged only on a successful fetch, with retries inside a single request free. Fetches route through Apify Proxy's Unblocker group, which escalates to a real browser when a page needs one, and the underlying crawler is the open-source Crawlee. Note the edge: if a site answers with a 404 page and Web Fetch converts it to Markdown, that counts as a successful fetch and bills. There is no $100 plan. Starter is $19 a month (as of October 2026) and Scale $199, and the plan fee is itself spendable usage, so $100 of monthly spend buys about 100,000 fetches. Unused prepaid usage expires at the end of the billing cycle rather than rolling over.

We cannot tell you which Apify product the harness called in the October run, because the adapter lives in the benchmark repo rather than in the published data. Treat 77.2% as Apify's adapter, not as a named product's rate.

ScraperAPI: fast, and partial on 22 sites

In the October 30, 2026 run ScraperAPI returned 154 of 215, at a median of 6.2 seconds per site, the third-fastest of the nine profiled here. Fashion and luxury is its best group at 80.0%, eighth of 17. Plain retail is its weakest e-commerce group at 63.5%.

It is also the vendor whose pricing an e-commerce buyer most needs to read carefully, because ScraperAPI is the one that prices by domain. Its own pricing page: "A standard page costs 1 credit. Amazon costs 5, Google and Bing (including their subdomains) cost 25, and LinkedIn costs 30. Sites behind bot protection like Cloudflare, Datadome, or PerimeterX add 10 credits per request when we bypass them."

There is no plan at $100. Hobby is $49 for 100,000 credits and Startup $149 for 1,000,000 (as of October 2026), which is $0.149 per 1,000 credits. At that rate an Amazon page is $0.745 per 1,000 and a protected retail page is $1.639 per 1,000, eleven times the plain rate. Credits do not roll over, and max_cost caps what any single request can spend.

ScraperAPI bills a 200 or a 404, and a request you cancel before 70 seconds, so a polite error page is billable. And in the October 30, 2026 run it left 22 of the 43 sites partial, tied with Bright Data for the highest count in the run. Where ScraperAPI sits against the rest.

Bright Data: pay only for success, at the highest flat rate

In the October 30, 2026 run, Bright Data returned 153 of 215, eleventh of 17. Its groups run from 61.2% on retail to 84.0% on grocery, a 22.8-point spread, and it left 22 of the 43 sites partial. Its median of 24.3 seconds per site is the slowest of the nine profiled here.

Web Unlocker is pay as you go at $1.50 per 1,000 requests, or $499 a month on Scale (as of October 2026) for 383,000 requests included and $1.30 per 1,000 after. There is nothing between the 5,000-request free tier and $499. You pay only for success, and concurrency is not capped.

One headline rate does not match the rate card: Bright Data's navigation advertises "Starts from $1/1k req" and the Web Unlocker pricing page's lowest published rate is $1.30 (as of October 2026). Bright Data alternatives.

Oxylabs: the only vendor that prices Amazon down

In the October 30, 2026 run, Oxylabs returned 146 of 215. Its marketplaces and grocery scores are both 84.0%, and its fashion and luxury score is 47.3%, fourteenth of 17. That 36.7-point spread is the third-widest in the run.

It is the one vendor here that makes a named retail site cheaper rather than dearer. Oxylabs now sells one subscription that covers all its products. On the Basic plan at $100 a month (as of October 2026), Amazon results are $0.45 per 1,000, Google $0.90, and everything else $0.90, with JavaScript rendering at $1.40. Only successful results are billed. VAT may apply. The benchmark's Oxylabs adapter returned none of five attempts on amazon.com in the run, so test the Amazon endpoint itself before you budget on that rate.

The limit is volume. Basic tops out at about 111,000 results a month on general sites without JavaScript, about 71,000 with it, and about 222,000 on Amazon. The next plan is Flexible at $500, and Enterprise starts at $2,500 (as of October 2026). The "Starts from" rate on Oxylabs' own product page, $0.25 per 1,000, is the Enterprise rate for Amazon. Web Unblocker draws on the same subscription but is billed per gigabyte, not per result. Oxylabs alternatives.

Which e-commerce scraping API should you pick?

  • A daily price monitor across mixed retail. String. Highest completeness at 42 of 43 sites returned in full in the October 30, 2026 run, the narrowest spread across groups, and billing that counts only returns.
  • A fashion or luxury catalogue. String or Context.dev, both at 100% in the October 30, 2026 run, then ScrapingBee, Scrape.do and Firecrawl at 90.9%. Do not buy Oxylabs for this job; 47.3% means half your rows.
  • Marketplaces and classifieds, including European ones. String or Scrape.do, both at 100% in the October 30, 2026 run. Scrapfly is next at 94.0%. String and Scrape.do both returned allegro.pl on all five attempts.
  • Grocery and delivery. In the October 30, 2026 run, Nimble is the only provider that returned 100% of the five grocery sites. String, ScrapingBee and Apify follow at 88.0%. String's gap is kroger.com; if Kroger is on your list, ScrapingBee returned it in full.
  • One or two named US retailers. ScrapingBee or Oxylabs. ScrapingBee is third of 17 on plain retail at 78.8%, behind String and Scrape.do, and ships site-specific endpoints; Oxylabs prices Amazon at $0.45 per 1,000 (as of October 2026).
  • Structured product fields rather than page content. Apify. Rent the Actor rather than parsing the page, and accept that unused prepaid usage expires monthly.
  • Predictable cost with no multiplier arithmetic. Firecrawl at $0.99 per 1,000 pages flat, or Bright Data at $1.50. Both charge the same for a hard page as an easy one.
  • A latency-sensitive path a user waits on. String at 2.5 seconds median or Scrape.do at 3.8 in the October 30, 2026 run. Apify, ScrapingBee and Bright Data sit between 18.4 and 24.3 seconds.

What $100 a month buys

At the plan nearest $100 billed monthly (prices checked October 2026), and on the path each vendor's own rules apply to a protected retail page. Scrape.do is left out because its pricing was not part of this check.

API Plan Plain page, per 1,000 E-commerce path, per 1,000 Billed on success
ScrapingBee Startup, $99 $0.099 $2.475 a returned 404 bills; zero when Auto-Mode fails
Scrapfly Pro, $100 $0.10 $2.50 yes
ScraperAPI none; $49 or $149 $0.149 $1.639 a returned 404 bills
String Growth, $99 $0.16 $0.90 yes
Oxylabs Basic, $100 $0.90 $1.40 with JS, $0.45 Amazon yes
Firecrawl Standard, $99 $0.99 $0.99 a returned 403 or 404 bills
Apify none; $19 or $199 $1.00 $1.00 a converted 404 bills
Bright Data none; $1.50 or $499 $1.50 $1.50 yes

Two observations rather than a ranking. First, the cheap headline rates and the e-commerce rates are different products: ScrapingBee's plain page is the cheapest number in the table and its retail path is the dearest but one. Second, three of the eight say they bill nothing for an error page: String, Scrapfly and Bright Data. Firecrawl, Apify, ScraperAPI and ScrapingBee bill a returned 404, and Oxylabs no longer states its rule on the pricing page. So the cost of a failed request is often not the bill. It is the missing row, and the hours someone spends finding out which SKU it belonged to.

FAQ

What is the best scraping API for e-commerce price monitoring?

String, on the October 30, 2026 benchmark. It returned 98.6% of requests across the 43 e-commerce sites and returned 42 of the 43 on all five attempts, both the highest in the run. For price monitoring, the second figure matters more than the first: a site that returns three times out of five leaves holes in a price history that nothing downstream flags. String's spread across retail, fashion, marketplaces and grocery is 12.0 points, the narrowest of 17 providers, so its score does not change much when your catalogue does.

Which API should I use to collect e-commerce product prices?

If the prices are page content, use a general fetch API (October 30, 2026 run): String at 98.6%, Scrape.do at 88.8%, Context.dev at 85.6%, ScrapingBee at 83.7%. If you want structured product fields without writing a parser, use Apify and rent a prebuilt Actor for the site. If your list is one or two large US retailers, ScrapingBee and Oxylabs both sell site-specific endpoints that a general benchmark does not measure.

Best scraping API for e-commerce price data at scale?

Check the ceiling on the plan, not the headline rate. As of October 2026, Oxylabs' Basic plan caps at about 111,000 general results a month, or 222,000 on Amazon, and above Flexible at $500 its plans move to Enterprise from $2,500. Bright Data has nothing between a 5,000-request free tier and $499 a month. ScraperAPI and Scrapfly publish million-credit plans, but a protected retail page costs 11 credits on ScraperAPI and 25 on Scrapfly, so a million credits is not a million retail pages. String's Growth plan names no monthly ceiling, and its Enterprise rate card is not published.

How do I scrape Amazon product data?

Amazon returned 5 of 5 to twelve of the 17 providers in the October 30, 2026 run (benchmark), with a field average of 80.0%, so it is not among the harder retail sites. Price it carefully, though, because two vendors charge a specific Amazon rate and they move in opposite directions. ScraperAPI charges 5 credits for an Amazon page against 1 for a standard page. Oxylabs charges $0.45 per 1,000 Amazon results against $0.90 for other sites without JavaScript, though the benchmark's Oxylabs adapter returned none of its five amazon.com attempts.

What is the best way to monitor competitor prices?

Pick the 20 to 50 SKUs that drive your margin, match each one to a competitor page by GTIN or model number, fetch the page on a schedule, read the price from the page's Product schema, and alert on change. For a small catalogue, a price-tracker tool does this for you. For your own pipeline, the scraping API decides how many days come back blank: on the 43 benchmark sites in the October 30, 2026 run, a daily check with one retry would leave about 11 of 1,290 site-days blank on String, against about 115 on Scrape.do, 244 on ScraperAPI and 247 on Bright Data.

Which scraping API is most dependable for large retail sites?

Dependability on large retail sites is not the same as a good overall score. Best Buy, at a field average of 43.5% in the October 30, 2026 run (benchmark), was returned in full by String, Context.dev, ScrapingBee, Apify, Bright Data and Oxylabs, and three of those six rank eighth or lower overall. Mouser, at 24.7% in the same run, went only to String and Firecrawl. Build a shortlist from your own target list rather than from a leaderboard, and include at least one site from each group you care about.

How do I build a shopping assistant that reads live prices?

The constraint is latency rather than coverage, because a person is waiting. Median time per e-commerce site in the October 30, 2026 run was 2.5 seconds for String and 3.8 for Scrape.do, against 18.4 for Apify, 23.2 for ScrapingBee and 24.3 for Bright Data. A difference of more than nine times in median time changes what the interface can promise. Pick from the fast pair and cache aggressively.

I collect alternative data from retail sites. Which web scraping API should I use?

Completeness and repeatability, in that order, because an incomplete panel is worse than a small one. In the October 30, 2026 run (benchmark), String returned 42 of 43 sites in full, and Scrape.do and Context.dev 36 each. String returned the other one, kroger.com, on two of five attempts. If it is in your panel, add a retry or a second provider for that site; Firecrawl is one of five that returned it in full. Running two APIs is a reasonable end state, and both of ours are free to test: String gives 20,000 standard fetches with no card, and Firecrawl 1,000 credits a month.

Sources

Benchmark figures: Web Data Frontier Benchmark, October 30, 2026 run, 100 targets, 17 providers, 500 requests each, written up in the October 2026 benchmark post. Harness: github.com/usestring/web-data-frontier-benchmark; raw results for this run.

Pricing, checked October 14, 2026 (String's on October 28, 2026): String, Scrapfly, ScraperAPI and its credit documentation, Firecrawl, Oxylabs (checked November 17, 2026), Apify and Web Fetch, ScrapingBee and its API documentation, Bright Data Web Unlocker.

Practitioner sources, read September 22, 2026: u/Pigik83 on scraping volume and proxy cost, u/MrKrotchy on Amazon removing price tags, ItemStockTracker issue #22, camoufox issue #258, mcp-walmart issue #1. Quote cards reproduce the verbatim text; each links to the original.

Related: Best web scraping tools in 2026, Firecrawl alternatives, ScraperAPI alternatives, Oxylabs alternatives, Bright Data alternatives, all comparisons.

Best Web Scraping APIs 2026: 17 Compared by Success RateUpdated November 11, 2026Best Web Scraping Tools 2026: 13 Compared, Free and PaidUpdated November 11, 2026Web Scraping API Pricing in 2026: 17 Providers ComparedUpdated November 11, 2026
Get your API key →Explore the Web Access API