Cost to scrape Amazon at 10K, 100K, and 1M

Access fact, checked 2026-07-26: Amazon’s Conditions of Use prohibit data mining, robots, and similar extraction tools unless Amazon gives express written consent (Source).

Cost to scrape Amazon at 10K, 100K, and 1M table

The comparison uses 10,000, 100,000, and 1,000,000 billable target calls or delivered results per month, calculated on 2026-07-26. It does not claim those calls all become useful rows. Credit, request, result, and search meters are passed through the dataset quote model, which selects the least expensive published self-service offer that covers each volume. A starting USD rate is shown as a lower bound because an unpublished minimum, tier, or contract can raise the invoice. Retries, pagination, duplicate outputs, taxes, and data licensing are outside these figures.

The published price answer

The record contains 5 published target-rate lines across 4 vendors. Those are the only rows allowed to produce a target-specific dollar result. Different light, normal, HTML, rendered, protected, or dedicated modes stay separate because collapsing them would hide the unit change that drives the bill. A plan name in a cell is the offer selected from that vendor record, not a recommendation.

Amazon requests cost 5 credits. docs.scraperapi.com. The Amazon API light request costs 5 credits; normal costs 15 credits. help.scrapingbee.com. The Amazon API normal request costs 15 credits; light costs 5 credits. help.scrapingbee.com. Amazon domains cost 1 credit and are routed through the Amazon Scraper API. scrape.do. Oxylabs publishes an Amazon Web Scraper API rate starting at $0.0005 per result. oxylabs.io.

The page is simple; the access path is not

This record classifies Amazon as hard and records rate limiting, CAPTCHA, bot detection and fingerprinting, IP reputation checks, geographic variation or restriction. JavaScript rendering is not required in the recorded profile, so the table does not add a rendering multiplier unless a published target mode already includes one. Residential routing is recorded as needed, but no generic proxy multiplier is silently added: the table applies only a vendor’s explicit target meter.

Product, offer, seller, search, and availability data are different outputs, so a vendor endpoint must be checked against the exact fields the job needs.

The official route is a separate product decision

Amazon Creators API is recorded as available. Requires an Amazon Associates account, completed identity verification, and qualifying sales. No separate API price is published; eligibility and usage limits are tied to the Associates account. Creators API can cover qualifying product use cases, but eligibility and supported data differ from unrestricted page extraction. Source and access status checked 2026-07-26.

Endpoint evidence and the remaining unknown

The dataset confirms 6 dedicated endpoints or templates. This proves named target support in the cited product documentation. It does not prove that each endpoint has a public target-specific price.

• Amazon targets in Web Scraper API is paired with a published target meter in the cost table.
• Amazon Scraping API is paired with a published target meter in the cost table.
• Amazon Scraper API is paired with a published target meter in the cost table.
• Amazon scrapers is documented, while its target-specific price remains unpublished in this record.
• Amazon target templates is documented, while its target-specific price remains unpublished in this record.
• Amazon Scraper API is documented, while its target-specific price remains unpublished in this record.

What volume means for Amazon

One useful unit is one ASIN observation at the required depth, such as catalog fields, current offers, seller data, reviews, or a rendered product page. When ASINs are not already known, the workload is search or category pages + product calls + any separate offer, seller, or review calls. The documented commercial endpoints split those objects into separate search, product, pricing, seller, bestseller, offer, and review routes, so a search request is not a bundle of every downstream product observation. (Oxylabs Amazon targets, Crawlbase scraper catalog, and Scrape.do Amazon API, retrieved 2026-07-27.)

Amazon Creators API makes its own pagination boundary explicit: SearchItems returns up to 10 items per request, ItemCount is between 1 and 10, and ItemPage is between 1 and 10. It can answer a catalog search or known-item question when its supported resources contain the required fields. It does not turn arbitrary retail pages, seller pages, or review collection into the same API operation. Commercial scraper routes can return structured output for those other objects, but their request, result, or record meter must be applied to the exact endpoint selected in the table. (Amazon Creators API SearchItems and Amazon Creators API introduction, retrieved 2026-07-27.)

Evidence to check before buying

• ScraperAPI prices Amazon at 5 credits versus 1 credit for a normal request docs.scraperapi.com.
• ScrapingBee prices its Amazon API at 5 credits in light mode and 15 in normal mode help.scrapingbee.com.
• Oxylabs publishes an Amazon rate starting at $0.0005 per result oxylabs.io.
• Oxylabs maintains separate Amazon product, search, pricing, seller, and bestseller targets developers.oxylabs.io.
• Confirm the exact entity and output unit, whether a page, search, result, record, or API object. Then multiply by pagination and refresh frequency before selecting a plan.
• Fix the required country or market before pricing. The recorded geographic variation means one nominal URL can represent different jobs.