canonical: https://jentic.com/apis/ecommercedataapi.com/main # Ecommerce Data API The Ecommerce Data API returns Amazon marketplace intelligence: product research and ASIN detail, review data, and price, BSR, and sales-estimate history for a listing. It covers keyword research with reverse-ASIN lookups and search-volume trends, market research with concentration and price and demand distributions, and global trademark lookups, plus a tool that reads text from a product image. It is a read-oriented data source for sellers and analysts studying the Amazon market. ## For AI agents Query Amazon product, review, keyword, and market data, pull ASIN sales and price history, search global trademarks, and extract text from product images. ## Scope Does not place orders, manage listings, or process payments. Use for reading Amazon product, keyword, market, and trademark data only. ## Capabilities - Search and research Amazon products by keyword or ASIN - Pull an ASIN's price, BSR, and sales-estimate history - Run keyword research with reverse-ASIN lookups and search-volume trends - Analyze market concentration, demand, and price distributions for a category - Look up global trademark registrations by brand - Extract text from a product image ## Use cases ### Agent-driven product research An AI agent evaluates whether a product is worth selling by pulling its ASIN detail, review counts, and sales-estimate and price history in one research pass. Because the API returns BSR-based sales estimates and historical trends, the agent can judge demand and pricing pressure before a human spends time on the listing. Example prompt: Fetch an ASIN's detail, review data, and sales-estimate history, then summarize its demand and price trend ### Keyword and traffic intelligence Sellers optimizing listings need the keywords that drive traffic and the products that already rank for them. The API runs keyword research, reverse-ASIN lookups, and search-volume trends, so an agent can build a keyword set for a listing and see the competing ASINs behind each term. Example prompt: Run keyword research for a seed term and a reverse-ASIN lookup to list the products ranking for it ### Market structure analysis Deciding whether to enter a category needs a view of how concentrated and how priced it is. The market endpoints return seller and brand concentration, demand trends, and price distribution for a category, so an agent can assess competition and typical price points before a go or no-go call. Example prompt: Pull brand concentration and price distribution for a category and report whether it is crowded ## Key endpoints | Method | Path | Description | | --- | --- | --- | | POST | `/v1/amazon/product/research` | Research Amazon products | | POST | `/v1/amazon/asin/detail` | Get Amazon product details by ASIN | | POST | `/v1/amazon/asin/history` | Get a product's history | | POST | `/v1/amazon/review` | Get Amazon product reviews | | POST | `/v1/amazon/keyword-research` | Run Amazon keyword research | | POST | `/v1/amazon/market/research` | Run Amazon market research | | POST | `/v1/global/brand/list` | Search global trademarks | | POST | `/v1/tools/image-text` | Extract text from an image | ## Key resources - **Products** — Amazon product search, ASIN detail, reviews, and price and sales history - **Keywords and traffic** — Keyword research, reverse-ASIN lookups, and search-volume trends - **Markets** — Category concentration, demand, and price distribution data - **Trademarks and tools** — Global trademark lookups and image text recognition ## 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:** 73 / 100 - **Maturity:** AI-Aware - **Dimensions:** - Foundational Compliance: 99 / 100 - Developer Experience & Jentic Compatibility: 88 / 100 - AI-Readiness & Agent Experience: 59 / 100 - Agent Usability: 94 / 100 - Security: 55 / 100 - AI Discoverability: 64 / 100 - **View full report:** https://jentic.com/apis/ecommercedataapi.com/main/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 Ecommerce Data API by hand means choosing between the X-API-Key header and bearer token and shaping a JSON body for each of its product, keyword, and market endpoints. Through Jentic you install once, import it from the API Directory, store the key once, and your agent calls it. - **Permission scoping:** The ASIN and keyword travel in the request body, so a rule bounds which operations your agent may call, such as the product and market research reads. You choose the operations it may call, so the trademark and image tools are not included unless you add them. - **Credential handling:** Your Ecommerce Data 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 'research an Amazon product' or 'find keywords for a listing', and Jentic returns the matching operation with its input schema so the agent calls the right endpoint without reading the reference docs. ## Related APIs - **Semrush** — Semrush offers keyword and market intelligence for web search rather than the Amazon marketplace. - **Scrapingdog** — Scrapingdog scrapes arbitrary pages when the packaged Amazon datasets do not cover a source. - **Domo** — Domo builds dashboards and reports over the market data this API returns. ## FAQ ### What authentication does the Ecommerce Data API use? The Ecommerce Data API authenticates with an API key, supplied either in the X-API-Key header or as an Authorization bearer token, as declared in its OpenAPI spec. Through Jentic the key is stored encrypted by your own Jentic One instance and injected when a call runs, so it never reaches the agent's prompt or logs. ### Can I get an ASIN's sales estimate and price history with this API? Yes. The API returns BSR-based sales estimates for an ASIN and a history endpoint for its price and rank over time, so an agent can judge demand and pricing pressure for a listing. ### What are the rate limits for the Ecommerce Data API? The OpenAPI spec does not specify rate limits. Check the vendor documentation at ecommercedataapi.com for the current plan limits before running large research batches. ### Is there an Ecommerce Data API MCP server? You do not need an MCP server to give your agent the Ecommerce Data API. Jentic connects it directly from the API Directory: import it, store your API key once, and your agent queries Amazon product and market data on demand. ### Can I limit what my agent is allowed to do with the Ecommerce Data API? Yes. The ASIN and keyword travel in the request body, so a rule bounds which operations your agent may call, such as the product and keyword research reads, rather than naming a product, and every call it makes is logged. ### How do I research an Amazon product with this API through Jentic? Search Jentic for an intent like 'research an Amazon product' and it returns the matching operation with its input schema, then your agent calls it with the API key Jentic injects at runtime. To run it on your own infrastructure, install Jentic One from its GitHub repo.