canonical: https://jentic.com/apis/amazonscraperapi.com/amazonscraperapi # Amazon Scraper API The Amazon Scraper API turns Amazon product pages and search results into structured JSON, returning dozens of fields per product across the marketplaces it supports. It serves single-product lookups by ASIN, keyword search results, and an asynchronous batch endpoint for submitting many product or search jobs at once. Billing is tied to successful responses, so an agent pays for the data it actually retrieves. ## For AI agents Fetch structured Amazon product and search data as JSON by ASIN or keyword, and submit batch jobs for many lookups at once. ## Scope Does not place orders, manage seller inventory, or process payments. Use for retrieving structured Amazon product, search, and review data only. ## Capabilities - Fetch structured product data for a single Amazon ASIN as JSON - Retrieve structured Amazon search results for a keyword - Submit asynchronous batch jobs of product and search lookups - Pull product fields such as title, price, and rating across supported marketplaces ## Use cases ### AI agent for product research A research agent needs clean product facts rather than raw HTML. Through Jentic the agent searches for getting structured Amazon product data, loads the single-product lookup with the credential already injected, and returns a normalized JSON record it can reason over. The agent can run a keyword search first and then enrich the top results with full product detail. Example prompt: Call GET `/api/v1/amazon/search` for a keyword, then GET `/api/v1/amazon/product` for the top ASIN to get full detail ### Price and availability monitoring A monitoring workflow checks the price and availability of a set of ASINs on a schedule and flags changes. The Amazon Scraper API returns structured product fields per ASIN, and its batch endpoint lets the agent submit many ASINs in one asynchronous job rather than looping single calls. Because billing follows successful responses, failed fetches do not inflate cost. Example prompt: Call POST `/api/v1/amazon/batch` with a list of ASINs and compare each returned price against the stored baseline ### Competitive catalog analysis A seller's agent compares its listings against competitors for the same keywords. The API returns structured search results for a keyword, which the agent can expand into per-product detail to compare titles, prices, and ratings. This builds a competitive snapshot without parsing marketplace pages by hand. Example prompt: Call GET `/api/v1/amazon/search` for a target keyword and summarize the price range across the returned products ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | `/api/v1/amazon/product` | Get structured data for a single Amazon product by ASIN | | GET | `/api/v1/amazon/search` | Get structured Amazon search results for a keyword | | POST | `/api/v1/amazon/batch` | Submit an asynchronous batch of product and search jobs | ## Key resources - **Product** — Structured per-ASIN product data returned as JSON - **Search** — Structured Amazon search results for a keyword - **Batch** — Asynchronous batch submission of many product and search jobs ## AI readiness This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use. - **Score:** 59 / 100 - **Maturity:** Foundational - **Dimensions:** - Foundational Compliance: 87 / 100 - Developer Experience & Jentic Compatibility: 65 / 100 - AI-Readiness & Agent Experience: 45 / 100 - Agent Usability: 94 / 100 - Security: 38 / 100 - AI Discoverability: 63 / 100 - **View full report:** https://jentic.com/apis/amazonscraperapi.com/amazonscraperapi/scorecard - **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/ - **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview ### Score it yourself Every API in the directory is allowlisted, so you can re-score it with no key required. - **Score your own API:** https://jentic.com/scorecard.md - **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md ```sh npx @jentic/api-scorecard-cli score ``` ## Why Jentic - **Setup:** Wiring the Amazon Scraper API by hand means choosing between its api_key query parameter and a bearer token, handling asynchronous batch polling, and parsing the structured JSON per marketplace yourself. Through Jentic you install once, import the Amazon Scraper API from the API Directory, store the key once, and your agent calls it. - **Permission scoping:** The Amazon Scraper API has three operations: single-product lookup, keyword search, and an asynchronous batch job. You choose the operations your agent may call, so you can allow the product and search reads and leave batch submission out of the allowed set unless you add it. - **Credential handling:** Your Amazon Scraper API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'get Amazon product data' or 'search Amazon for a keyword', and Jentic returns the matching operation with its input schema so the agent calls the right endpoint without reading the reference docs. ## Related APIs - **WebScraping.AI** — Scrapes and extracts data from any URL rather than only Amazon product pages - **Apify API** — Runs configurable scraping actors across many sites, including Amazon, with more setup - **Crawlbase API** — Provides proxy and crawling infrastructure for pages the structured Amazon endpoints do not cover ## FAQ ### What authentication does the Amazon Scraper API use? The Amazon Scraper API accepts an API key either as the api_key query parameter or as a bearer token in the Authorization header, per its OpenAPI spec. Both forms authorize the same operations, so you can use whichever fits your client. Through Jentic the key is injected at call time and never travels in the agent's context. ### Can I search Amazon and get structured results? Yes. Call GET `/api/v1/amazon/search` with a keyword and the API returns a structured list of matching products as JSON. For full detail on one result, follow up with GET `/api/v1/amazon/product` using the ASIN. ### What are the rate limits for the Amazon Scraper API? The OpenAPI spec does not define request-rate ceilings. The service bills per successful 2xx response and offers a free monthly tier before paid usage begins, so throughput is governed by your plan rather than a fixed per-second limit. Check the Amazon Scraper API documentation for the quota that applies to your key. ### Is there an Amazon Scraper API MCP server? You don't need an MCP server to give your agent the Amazon Scraper API. Jentic connects it directly from the API Directory: import the API, store your key once, and your agent calls operations such as GET `/api/v1/amazon/product` on demand without loading another server's tool definitions into its context. ### Can I limit what my agent is allowed to do with the Amazon Scraper API? Yes. Write a rule that allows only the single-product and keyword-search reads, so the agent can fetch and search product data but cannot submit large asynchronous batch jobs, and every call it makes is logged. You add the batch operation to the allowed set only when you want it. ### How do I get structured Amazon product data through Jentic? Search Jentic for 'get structured Amazon product data', load the GET `/api/v1/amazon/product` operation, and run it after your key is stored. To run it on your own infrastructure, install Jentic One from its GitHub repo.