Amazon Trends API

Amazon's Product Advertising API is built for listings and affiliate cards. It does not return keyword-level product search demand over time. Trends MCP does: Amazon search volume as a 0-100 series, about 5 years of weekly history, growth percentages, and a keyword-free bestseller feed. The keyword is a shopper phrase such as air fryer, not an ASIN. REST and MCP share the same payload. One connection covers 25+ sources, including the narrative on Amazon search trends. The free plan includes 100 requests per month. Starter is $19/month.

Product search demand, not catalog JSON

A time series of Amazon search interest answers whether shoppers still type a phrase into Amazon. That is purchase-adjacent demand. It is not Buy Box, not inventory, not review stars. Those objects stay on Selling Partner and Product Advertising APIs.

Seasonal goods (air fryer, christmas lights) show calendar peaks that a 5-year weekly chart makes obvious. Consumables (protein powder) show slower compounding. Gadget fads show a spike and a multi-year fade. Assistants should not treat a December peak as a permanent TAM.

get_trends returns the history. get_growth returns 6M, 1Y, and other presets. get_top_trends with Amazon Best Sellers Top Rated is the live ranking call and needs no keyword.

Keyword format for product search

Short shopper language wins. standing desk beats ergonomic office furniture solution. Brand plus product (dyson v15) is valid when people search that way. Category phrases aggregate competing listings, which is useful for aisle-level research and weak for SKU-level rank.

ASINs, dp/B0... URLs, and associate tags belong in Amazon product data or PA-API lookups. They are not the demand-series keyword. Seller display names are also the wrong type unless shoppers actually search that name.

US spelling is the default assumption for a global-style index. Marketplace-specific curves (.co.uk, .de) are not selected with a TLD in the keyword; the keyword stays the product phrase. Ecommerce product research covers how teams combine Amazon demand with Google and TikTok.

Bundles and "with" phrases (air fryer with accessories) often have thinner history than the head term. Start with the head term, then add a modifier only when shoppers clearly type it. Gift-intent modifiers (for mom, for men) are real Amazon queries and should be tracked as their own series when a listing is built around that intent, not treated as interchangeable with the generic category.

Product Advertising API versus Trends MCP

PA-API requires an Associates (or equivalent) account, signed requests, and creative-use rules. Responses are item attributes: title, price, image, rating. Rebuilding a five-year search-demand curve from item APIs is not a supported PA-API job.

Selling Partner search-term reports exist for advertisers who already spend. They are account-scoped and not a public research API. Ads Console is not something an assistant can call with only a Trends MCP key.

Keepa, Jungle Scout, and Helium 10 expose operator UIs for rank, fees, and product databases. Teams should check current vendor pricing for those suites. Trends MCP is the JSON demand series plus live bestsellers for agents, not an FBA profit calculator.

REST surface (same data as MCP tools)

POST https://api.trendsmcp.ai/api
Authorization: Bearer YOUR_API_KEY
Content-Type: application/json

Weekly demand:

{
  "source": "amazon",
  "keyword": "air fryer"
}

Points include date, value (0-100), optional volume, keyword, and source. "data_mode": "daily" returns about 30 days at daily resolution.

Growth:

{
  "source": "amazon",
  "keyword": "protein powder",
  "percent_growth": ["3M", "1Y", "3Y"]
}

The same preset list as other sources applies (7D through 5Y, plus MTD QTD YTD). Custom pairs use recent and baseline dates.

Live bestsellers:

{
  "mode": "top_trends",
  "type": "Amazon Best Sellers Top Rated",
  "limit": 50
}

MCP maps these bodies to get_trends, get_growth, and get_top_trends. Python and JavaScript callers POST with a Bearer token the same way they would for YouTube or Google Search.

Who uses an Amazon demand API

Private-label teams screen category phrases before ordering inventory. Brand analysts compare Amazon growth with Google Search to see if awareness became shopping. Funds that hold retailer or brand equity watch a handful of category keywords around Prime events. Content studios check whether a buying-guide topic still has Amazon search before filming another roundup.

The API is a poor fit for repricers, listing crawlers, and review-request automations. Those need PA-API or SP-API.

Holiday and Prime-adjacent windows need daily mode on a short list of phrases, not a full catalog crawl. A kitchen gadget that only exists in November should be judged on year-over-year November weeks, not on a 3M window that includes a dead summer. Assistants that ignore the calendar will kill good seasonal keywords and keep bad all-year ones.

Comparison: Amazon search-demand APIs

Trends MCP is one REST and MCP connection covering 25+ sources. Amazon product search sits on the 0-100 index with about 5 years of weekly history, growth presets, and a keyword-free bestseller feed. Sparse phrases miss. The index is relative to that keyword's peak, so volume (when present) is the field for rough size. Recalls and viral safety searches can look like demand; news sentiment is the check. Quota is 100 requests per month free, Starter $19/month. Nightly scans of thousands of keywords belong in a seller-suite crawler.

Product Advertising API remains the path for live listing cards and affiliate links.

Seller intelligence vendors remain the path for rank, fees, and SKU databases. Teams should check current vendor pricing. Trends MCP is the demand API for assistants, not a replacement for Seller Central.