AMZScout sells two public price lists. The AI Bundle on amzscout.net is $59.99 for one month, $169.99 for three months (struck $179.97), or $399.99 for twelve months (struck $719.88), with a 10-day money-back line on the cart and an unlimited-time trial that does not ask for a card. Skill + MCP is a separate catalog: $39 for 1 million tokens, $99 for 5 million (struck $195), and $199 for 20 million (struck $780), each with a 30-day usage period, fetched 30 August 2026. Those MCP pages still disagree on whether a pack covers 50 product analyses or 100+ in-depth sessions, and one page now prints "/month" next to copy that also says there are no subscriptions. Trends MCP is not an Amazon seller suite. It is the MCP plus REST path for Amazon search volume and live Best Sellers boards when an agent needs ranked demand, not FBA operations.

What does the AMZScout AI Bundle cost on the public cart?

The public cart on amzscout.net and the Amazon sellers bundle page both printed the same three AI Bundle SKUs on 30 August 2026. One month is $59.99. Three months is $169.99 against a struck $179.97, with cart copy that says "Save $10 vs monthly." Twelve months is $399.99 against a struck $719.88. A lifetime SKU was not on this homepage fetch; third-party roundups that still quote one should be treated as stale until AMZScout puts that number on the cart again.

Two booster packs sit under the bundle, each $29.99 per three months: Pack for Private Label (listing builder, review analyzer, private-label checklist, a 10-product report, supplier list) and Pack for Reselling (arbitrage / wholesale / dropshipping extension, arbitrage guide, ungated-category list, wholesale supplier list). The comparison grid marks those extensions as add-ons on every term, not as bundle defaults.

The cart states a 10-day money-back guarantee. Homepage trial copy still says unlimited-time trial and no credit card. Those two clocks are not the same product. A trial that never asks for a card is not a 10-day refund on a paid invoice.

Coverage claims on the same fetch do not collapse to one number. Homepage copy lists 14 Amazon markets (United States, United Kingdom, Germany, France, Italy, Spain, Canada, Mexico, India, Japan, UAE, Saudi Arabia, Australia, Brazil) and a Product Database of 550 million items. The bundle page, on the same day, says 600 million products in the weekly-ideas section, 600M+ items in the product-selection headline, and 500 million products in the Product Database how-to block. Trust lines also split: homepage 500K+ sellers, 100+ Amazon coaches, 5M+ profitable products found, and over 1,000 Chrome Store reviews; the bundle page adds a Chrome Store rating line of 500,000 users. Cite the page that printed the figure. Do not flatten 500 million, 550 million, and 600 million into one database size.

The Skill & MCP Connector row on the bundle comparison grid lists 500 research sessions in a single cell, with a link out to separate MCP pricing. That 500 is a bundle marketing line, not the token-pack catalog.

TermPublic price (30 Aug 2026)Struck / save copyRefund / trial on that surface
AI Bundle, 1 month$59.99none printed10-day money-back on cart; unlimited-time trial, no card, on homepage
AI Bundle, 3 months$169.99struck $179.97; save $10 vs monthlysame cart / homepage split
AI Bundle, 12 months$399.99struck $719.88same cart / homepage split
Private Label booster$29.99 / 3 monthsnone printednot a standalone trial on this fetch
Reselling booster$29.99 / 3 monthsnone printednot a standalone trial on this fetch

Why do Skill + MCP token packs disagree across AMZScout pages?

AMZScout sells Claude / ChatGPT / Cursor access to Amazon research data as a second catalog, not as a line item with a monthly seat on the AI Bundle. The dedicated pricing page at learn.amzscout.net/amazon-product-api-for-ai-agents-pricing (30 August 2026) prints three packs and the sentence "Only pay for what you use. No subscriptions. No seat limits."

PackPriceStruckMeter on the pricing URLMeter on the product URLUsage window
1M tokens$39noneup to 50 product analysestypically enough for 100+ in-depth research sessions; also prints "/month"30-day usage period on both
5M tokens$99$195up to 250 product analysestypically enough for 500+ in-depth research sessions; also prints "/month"30-day usage period on both
20M tokens$199$780up to 1,000 product analysestypically enough for 2,000+ in-depth research sessions; also prints "/month"30-day usage period on both

The product page at learn.amzscout.net/amazon-product-api-for-ai-agents is the one that adds "/month" under each dollar figure while keeping the 30-day usage period. A 30-day prepaid pack is not a subscription. A page that prints both should not be summarized as "monthly MCP." Treat $39 / $99 / $199 as the verified dollars. Treat 50 / 250 / 1,000 analyses, 100+ / 500+ / 2,000+ sessions, and the bundle grid's 500 research sessions as three marketing meters that have not been reconciled on the public site.

Neither MCP page publishes a Cursor mcp.json on the pricing cards. Install lives on a third URL.

Which Cursor JSON does AMZScout actually publish?

How to Install the AMZScout Skill + MCP in Cursor (30 August 2026) is the paste-ready block. The server key is amzscout. The transport field is type: streamable-http. The URL is https://chatbot.amzscout.net/mcp. Auth is an Authorization Bearer header. The page says the Skill ships with the connector, that a paid Skill + MCP plan and a personal API key from the purchase email are required, and that a working check is to ask the agent how many AMZScout tokens remain. Support is [email protected].

"amzscout": {
  "type": "streamable-http",
  "url": "https://chatbot.amzscout.net/mcp",
  "headers": {
    "Authorization": "Bearer YOUR_AMZSCOUT_API_KEY"
  }
}

Trends MCP uses a different Cursor shape. docs.md and the MCP server for Cursor page (same day) put the server on https://api.trendsmcp.ai/mcp with transport: http and the same Bearer header pattern. There is no type: streamable-http key in that snippet. Claude.ai Connectors are a second host: OAuth against the www /mcp path, not the api host, and no Bearer key in that connector config.

"trends-mcp": {
  "url": "https://api.trendsmcp.ai/mcp",
  "transport": "http",
  "headers": { "Authorization": "Bearer YOUR_API_KEY" }
}

Pasting the AMZScout block into a Trends MCP slot, or the reverse, will not "just work." The field names are the durable difference: type plus streamable-http versus transport plus http, and chatbot.amzscout.net versus api.trendsmcp.ai.

No. AMZScout's paid surfaces are product research inside Amazon: Chrome PRO AI, Product Database, keyword lookup, stock stats, listing tools, and (on the MCP packs) agent questions about ASINs, niches, and PPC. Trends MCP does not score private-label competition, estimate FBA fees, or return supplier lists. It wins the narrower job: live multi-source trend data, including Amazon, over MCP and REST, with a public request grid instead of a 30-day token pack.

HTML pricing on 30 August 2026 listed Free at $0 / 100 requests a month, Starter $19 / 1,000, Pro $49 / 5,000, Business $199 / 25,000, all in USD. The yearly toggle billed Starter $16 a month ($192 a year), Pro $39 ($468), Business $159 ($1,910), with "2 months free" on the annual switch and "Annual billing saves 20%" on the markdown mirror. Free is capped to top 10 trends, 12 months of history, and 24-hour delayed data. Paid cards say all trends, full history, and real-time. Keyword alerts sit on Pro (50) and Business (250). Failed calls do not count. A 429 pauses the key until reset; there is no overage line. HTML FAQ says the paid-plan card is collected at checkout and not charged until day 8. The plan-card fine print on the same HTML says "Card charged after day 7." Cite both. Do not pick one.

Source counts still do not match across first-party files on that date. HTML markets 35+ data sources. docs.md lists 15 keyword sources (no python row) and 24 named live feeds, including Amazon Best Sellers by Category and the other three by Category boards. data-sources.md lists the same 15 keyword sources and only 20 live feeds; it omits all four by Category boards. llms.txt still opens with "plus 21 live feeds" while its own live-feed table includes those four boards (24 rows). MCP get_growth still accepts python as a source even though the docs table does not. Do not flatten any of those to a single "N sources" claim.

For Amazon specifically, keyword source amazon is product search volume. The live board that filters by category is Amazon Best Sellers by Category, with 26 official category strings in docs.md (Toys Games, Pet Supplies, Home Kitchen, and the rest of that list). docs.md still says official category names live on /data-sources. On this fetch, data-sources.md did not document that feed at all. Default get_top_trends limit is 25, max 200, counted per feed type and per page. A climber pull uses sort: rank_change and a window such as 7d. That is the call an agent should use when the job is "which toys climbed this week," not "what is this ASIN's FBA margin."

{"mode": "get_top_trends", "type": "Amazon Best Sellers by Category", "category": "Toys Games", "sort": "rank_change", "window": "7d", "limit": 10}

Sellers who want Chrome overlays, Product Database filters, and token-metered Amazon Q&A stay on AMZScout (or Helium 10 / Jungle Scout / SmartScout for those suites). Agents that need Amazon search volume next to TikTok, Google, and Reddit, plus a paste-ready Cursor url + transport: http block, use Amazon trends in Cursor and the Amazon Best Sellers by Category API. Mixing both is coherent. Swapping one price list for the other is not.

FAQ

Is AMZScout cheaper as a yearly bundle or as MCP token packs?

The AI Bundle yearly cart price is $399.99 for twelve months of the seller toolkit. Skill + MCP is $39 / $99 / $199 per 30-day token pack on the pricing URL, with no seat limit printed there. Those are not interchangeable units: one is a Chrome-plus-database suite, the other is agent tokens. A seller who only needs Cursor on Amazon data can stay on the token catalog. A seller who needs the extension and Product Database still pays the bundle, then follows the MCP link if the agent connector is required on top.

Does the AI Bundle include Skill + MCP?

The bundle comparison row advertises a Skill & MCP Connector and prints 500 research sessions, with a link to the separate MCP price list. The MCP pricing page still sells 1M / 5M / 20M token packs as their own SKUs. Until AMZScout publishes one matrix that maps bundle term to token allowance, treat MCP dollars as a second checkout.

How is AMZScout MCP different from Trends MCP in Cursor?

AMZScout's published Cursor block uses type: streamable-http and https://chatbot.amzscout.net/mcp. Trends MCP's published Cursor block uses url plus transport: http and https://api.trendsmcp.ai/mcp. Both use Bearer headers. AMZScout meters 30-day token packs aimed at ASIN and keyword research. Trends MCP meters monthly API/MCP requests (100 / 1,000 / 5,000 / 25,000) across keyword sources and live boards, including Amazon Best Sellers by Category with a default limit of 25.

Can Trends MCP estimate Amazon sales the way AMZScout does?

Not on the public docs. Trends MCP returns Amazon search-volume series, growth windows, and ranked Best Sellers boards. It does not claim monthly unit sales, FBA fee math, or supplier matching. AMZScout's Chrome and MCP copy is built around those seller metrics. Use each for the job it actually meters.

Where were these prices checked?

AMZScout homepage, Amazon sellers bundle, Skill + MCP pricing, Skill + MCP product page, and Cursor install page, plus Trends MCP HTML pricing, pricing.md, docs.md, data-sources.md, and llms.txt, all on 30 August 2026. HTML pricing showed 9,581,225 API calls served; the homepage counter on the same session still read 9,543,071. Re-check the live cart before buying; AMZScout's MCP meters already disagree with each other on this date.

Sources