canonical: https://jentic.com/apis/merchantwords.com/merchantwords # MerchantWords API The MerchantWords API returns Amazon search keyword data, ASIN analytics, and search results intelligence for sellers and agencies. It reports a keyword's search volume, depth, trend, seasonality, and monthly history, runs reverse ASIN searches that list every keyword a product ranks for with its position, and returns all products on page 1 of Amazon search results for a keyword. Related-keyword discovery finds terms that share product rankings with a seed even when they share no words, and bulk lookups handle up to 1000 keywords in one call, with a two-letter country code selecting the Amazon marketplace. ## For AI agents Look up Amazon keyword volume, trend, and seasonality, find every keyword an ASIN ranks for, read page-1 search results for a keyword, discover related keywords by search-results overlap, and run bulk keyword or ASIN lookups per marketplace. ## Scope Does not manage Amazon listings, place ads, or report a seller's own sales and orders. Use for Amazon keyword, ASIN ranking, and search results research only. ## Capabilities - Look up an Amazon keyword's search volume, depth, trend, seasonality, and monthly history for a marketplace - Run a reverse ASIN search listing every keyword a product ranks for, sorted by volume or position - Read all products on page 1 of Amazon search results for a keyword - Discover behaviourally related keywords that share product rankings with a seed, filtered by minVolume - Look up volume and depth for up to 1000 keywords, or product details for many ASINs, in one call - Fetch product details and top keywords for one ASIN - Check the current plan, live rate-limit usage, and bulk quota before a large job ## Use cases ### Agent-run Amazon keyword research through Jentic A seller's agent builds a keyword plan for a new listing. Through Jentic it searches keywords containing the product phrase, pulls volume and seasonality for the top results, and checks which keywords a leading competitor ASIN ranks for. The x-api-key stays in your own Jentic One instance, and the agent can read the account endpoint first to confirm quota before a bulk run. Example prompt: Call POST /keyword-search with keyword 'yoga mat', country 'us', and sort 'volume-desc', then POST /keyword with keyword 'yoga mat' and country 'us' to read its trend and seasonality ### Competitor reverse ASIN analysis To learn what traffic a rival listing captures, the ranked-keywords endpoint returns every keyword an ASIN ranks for with its position, volume, and trend, paginated and sortable by volume, position, or keyword. Pairing it with the ASIN lookup gives the product details and its top keywords in one view. Example prompt: Call POST /ranked-keywords with asin 'B0DGHMNQ5Z', country 'us', sort 'volume-desc', and page 1, then return the top 20 keywords with their positions ### Search results and related-keyword discovery The search results endpoint returns all products on page 1 of Amazon search results for a keyword, and related-keyword discovery finds terms whose results share product rankings with the seed, even with no words in common. Together they surface adjacent demand a listing could target that a plain phrase match would miss. Example prompt: Call POST /serp with keyword 'bluetooth speaker' and country 'us', then POST /related-keywords with the same keyword, minVolume 1000, and limit 25 ### Bulk keyword volume checks Agencies auditing many listings check volume at scale. The bulk keyword endpoint returns volume and depth for up to 1000 keywords in one call, and the bulk ASIN endpoint returns product details for many ASINs at once, both scoped to one marketplace by country code. Example prompt: Call POST /bulk-keywords with the agency's list of client keywords and country 'us', then return the keywords sorted by volume, highest first ## Key endpoints | Method | Path | Description | | --- | --- | --- | | POST | `/keyword` | Keyword volume lookup | | POST | `/ranked-keywords` | Reverse ASIN search | | POST | `/serp` | Page-1 search result products | | POST | `/keyword-search` | Keyword search by phrase | | POST | `/related-keywords` | Related keywords by SERP overlap | | POST | `/bulk-keywords` | Bulk keyword lookup | | POST | `/asin` | ASIN product lookup | | GET | `/account` | Account, usage, and plans | ## Key resources - **Keywords** — Amazon search terms with volume, depth, trend, seasonality, and monthly history - **ASINs** — Amazon products with details, top keywords, and ranked keywords - **Search results** — Page-1 Amazon search results for a keyword - **Markets** — Supported Amazon marketplaces with data coverage - **Account** — Plan, rate-limit usage, and bulk quota ## 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:** 61 / 100 - **Maturity:** AI-Aware - **Dimensions:** - Foundational Compliance: 73 / 100 - Developer Experience & Jentic Compatibility: 63 / 100 - AI-Readiness & Agent Experience: 43 / 100 - Agent Usability: 94 / 100 - Security: 50 / 100 - AI Discoverability: 88 / 100 - **View full report:** https://jentic.com/apis/merchantwords.com/merchantwords/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 MerchantWords by hand means sending an mw_live_ key in the x-api-key header, passing the right two-letter marketplace code on every POST, paging reverse ASIN results, and watching plan quota before bulk calls. Through Jentic you install once, import MerchantWords from the API Directory, store the key once, and your agent calls it. - **Permission scoping:** MerchantWords sends the keyword, ASIN, and country in the request body rather than the URL path, so rules bound which operations your agent may call, not which keyword or ASIN it looks up. You choose the operations it may call, so quota-heavy bulk keyword and bulk ASIN lookups are not included unless you add them. - **Credential handling:** Your MerchantWords 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 'find keywords an ASIN ranks for' or 'get Amazon search volume', and Jentic returns the matching MerchantWords operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **Jungle Scout API** — Amazon keyword research, sales estimates, and share-of-voice data - **Amazon Scraper API** — Structured Amazon product and search page data as JSON by ASIN or keyword - **Selling Partner APIs for Fulfillment Outbound** — Amazon seller fulfilment orders, tracking, and returns from FBA inventory ## FAQ ### What authentication does the MerchantWords API use? Per its OpenAPI spec, the MerchantWords API uses an API key starting with mw_live_ sent in the x-api-key header on every request. A public read-only sample key returns real data for a fixed set of demo keywords and ASINs, and a free signup gives a key that queries any keyword or ASIN. Through Jentic the key is stored encrypted by your own Jentic One instance and injected at call time. ### Can I find every keyword an ASIN ranks for with the MerchantWords API? Yes. POST /ranked-keywords with an asin and country returns all keywords the product ranks for with position, volume, and trend. Results are paginated with page, and sort accepts values such as volume-desc or position-asc. ### What are the rate limits for the MerchantWords API? The OpenAPI spec does not publish fixed numbers; limits depend on your plan. GET /account returns your current plan, live rate-limit and bulk-quota usage, and the full list of plans with their limits. See https://www.merchantwords.com/api for plan details. ### Is there a MerchantWords MCP server? You don't need an MCP server to give your agent MerchantWords. Jentic connects it directly from the API Directory: import it, store your API key once, and your agent calls the keyword and ASIN operations it needs on demand without loading another server's tool definitions into its context. ### How do I look up Amazon keyword volume through Jentic? Search Jentic for 'get Amazon search volume for a keyword', load the POST /keyword operation, and execute it with keyword and an optional two-letter country code. The response carries search volume, depth, trend, seasonality, and monthly history. To run it on your own infrastructure, install Jentic One from its GitHub repo. ### Can I limit what my agent is allowed to do with the MerchantWords API? Yes. Write a rule that allows only POST /keyword and POST /keyword-search, so the agent can research single keywords but cannot run bulk lookups that draw down your bulk quota. Every call it makes is logged, so you can see exactly which keywords it queried.