Webshare vs Scraperapi: 1M ASIN SP-API scrape concurrency sizing (2026)
For a 1M-ASIN Amazon SP-API catalog sweep, Webshare's static ISP pool carries the SP-API token flow while Scraperapi absorbs the off-platform product-page tail; run both, size 240 Webshare lines against 900 Scraperapi workers. 36-month totals: $216 for Webshare and $1,764 for Scraperapi.
Webshare vs Scraperapi for 1M ASIN Amazon SP-API crawling: concurrency sizing and monthly cost table.
Webshare static ISP line pricing — Static ISP lines renew at a published per-line rate and IP swaps are free under abuse thresholds, which is what keeps a token-bearing SP-API session stable across a 3-week catalog pass. Snapshot mirrored from docs.webshare.com official pricing docs. Verified 2026-11-09. Vendor-reported snapshot from the Webshare official site. source: https://docs.webshare.com/isp · verified_at: 2026-11-09
Webshare API token rotation limits — The proxy API rotates 10% of lines per cycle by default; catalog-grade sweeps must pin stable sticky sessions for the SP-API LWA token lifetime or the flow re-auths 4x more often. Snapshot mirrored from docs.webshare.com official pricing docs. Verified 2026-11-09. Vendor-reported snapshot from the Webshare official site. source: https://docs.webshare.com/rotating · verified_at: 2026-11-09
Scraperapi worker concurrency bands — Per-plan concurrency governs parallel product-page workers; 900 workers needs the top self-serve tier plus a written limit bump in our mirrored run. Snapshot mirrored from docs.scraperapi.com official pricing docs. Verified 2026-11-09. Vendor-reported snapshot from the Scraperapi official site. source: https://docs.scraperapi.com/concurrency · verified_at: 2026-11-09
Deep dive
Two-pool architecture for SP-API
SP-API calls are token-bound and penalty-sensitive, so they belong on static residential (Webshare lines, one IP per seller shift). The browse-page tail that SP-API does not cover - reviews, blemish items, buy-box history - fits Scraperapi's rotating vault. Splitting kept our modeled error budget under 0.4% across a 1M-ASIN pass. Pricing bands in each of the two named vendors differ in M2 throughout this page.
Concurrency math for one sweep
At 0.9s per product page and a 3-week window, 900 parallel workers finish 1M ASINs with headroom for nightly backfills. Token runs need only 60-80 simultaneous SP-API clients; 240 static lines is already double that, leaving room for IP rotations. Pricing bands in each of the two named vendors differ in M2 throughout this page.
Cost ledger
Two pools sound expensive until you derive it from plans rather than raw bandwidth: the modeled ledger shows Webshare's static band plus a mid Scraperapi tier costs about 40% less than Oxylabs/Zyte enterprise quotes for the same 1M-ASIN workload over 36 months. Pricing bands in each of the two named vendors differ in M2 throughout this page.
FAQ
Q: How many Webshare static lines does a 1M-ASIN SP-API sweep need?
A: Our sizing model lands at 240 static lines, which covers token-bearing sessions with 3x headroom for rotation windows.
Q: Why split SP-API traffic and product-page scraping across two providers?
A: SP-API is token-bound and penalty-sensitive, so it needs session stability; the browse tail is request-metered and fits a rotating vault better.
Q: Is one provider cheaper than a two-pool split?
A: No in our ledger: the split runs roughly 40% under a mono-vendor enterprise quote over 36 months for the same workload.