Nexscope

Amazon Opportunity Report By Keyword

Generate an Amazon opportunity report by keyword across market potential, product traits, reviews, customer profiles, trends. Available via REST API or MCP.

CostRecent Avg. 49 · Range 45–56 credits / call
Try online
POST · https://api.nexscope.ai/amazon/opportunity/reportByKeywordMCP · nexscope_amazon_opportunity_report_by_keyword

What this API does

Generate an Amazon opportunity report by keyword across market potential, product traits, reviews, customer profiles, trends. The request accepts site, keyword. Its documented result includes stdout.

Amazon Opportunity Report By Keyword API use cases

Build a keyword shortlist

To build a keyword shortlist, a marketplace analyst submits site and keyword to Amazon Opportunity Report By Keyword. The returned stdout help choose candidate search terms for further investigation.

Compare search demand signals

A marketplace analyst uses Amazon Opportunity Report By Keyword with site and keyword to compare search demand signals. The returned stdout help compare keyword demand within the requested market scope.

Plan a content or advertising test

For this workflow, a marketplace analyst calls Amazon Opportunity Report By Keyword with site and keyword to plan a content or advertising test. The result helps select terms for a content or advertising experiment.

Amazon Opportunity Report By Keyword API FAQ

What does the Amazon Opportunity Report By Keyword API return?

Generate an Amazon opportunity report by keyword across market potential, product traits, reviews, customer profiles, trends. The documented output includes stdout. It corresponds to the supplied site, keyword. Optional fields can be absent; a missing value should not be interpreted as a measured zero. Example values illustrate the response shape, rather than live account results.

How many credits does the Amazon Opportunity Report By Keyword API cost?

The current documented cost is Recent Avg. 49 · Range 45–56 credits / call. This is the same cost shown at the top of this page. If a range or estimate is displayed, the final charge depends on the request. Review your available credits and the pricing page before calling the API, and check API usage records for the actual charge.

How do I call the Amazon Opportunity Report By Keyword API from my app or an MCP client?

Send a POST request to https://api.nexscope.ai/amazon/opportunity/reportByKeyword with your API key as a Bearer token and the JSON inputs shown in API integration. In a compatible MCP client such as Claude or Cursor, connect Nexscope and call nexscope_amazon_opportunity_report_by_keyword. Use the MCP arguments shown in the MCP guide, or switch Online test to MCP to review its request before adding it to your app.

View plans and creditsConnect this API with MCP

Try this API
Endpoint
https://api.nexscope.ai/amazon/opportunity/reportByKeyword
MCP method
nexscope_amazon_opportunity_report_by_keyword

Step 1 of 3 · Authenticate

Authentication

All run endpoints require a user API key. Send it as a bearer token in the Authorization header.

Authorization: Bearer nk-xxxxxxxxxxxxxxxxx
Missing or invalid API keys return an authentication error. Manage keys from .

Step 2 of 3 · Send a request

POSThttps://api.nexscope.ai/amazon/opportunity/reportByKeyword

Run an API

Send a JSON request body using the parameters described below.

Example request

Replace YOUR_API_KEY, then run this command in your terminal.

curl -X POST 'https://api.nexscope.ai/amazon/opportunity/reportByKeyword' \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "keyword": "ice bricks",
  "site": "US"
}'

Code example

{
  "keyword": "ice bricks",
  "site": "US"
}

Step 3 of 3 · Inspect the result

Check the response

Read code for the request status and data for the result. Open the parameter and response reference for the full field definitions.

HTTP status codes

CodeDescription
200Default HTTP response for both success and many business errors. Only outer JSON code 0 indicates success or asynchronous acceptance; inspect data for the result.
429Execution admission rate limit; honor Retry-After when present.
503Execution admission is temporarily unavailable; honor Retry-After when present.
Opt-inX-Nexscope-Http-Status: semantic maps controller-handled business errors to HTTP status on run and task routes. Pre-authentication failures, such as a missing API key (code 11209), may still return HTTP 200 before this mapping. Always check the outer JSON code; malformed requests and infrastructure failures may also return non-200 HTTP responses.
All categories/ Amazon ABA & Business Insights
POSThttps://api.nexscope.ai/amazon/opportunity/reportByKeyword

Run this API

Send a JSON request to execute this API and receive the documented response payload.

Endpoint

MethodPOST
Pathhttps://api.nexscope.ai/amazon/opportunity/reportByKeyword
AuthBearer API key
Content-Typeapplication/json

Request parameters

NameTypeRequiredDescription
sitestringrequired
Amazon site code, currently only supports `US`.
Example: US
keywordstringrequired
The search keyword to query the insight report.

Response example

Platform response envelope. code 0 indicates success or acceptance; data contains the business result.

No response example is published for this API. Refer to the response fields below.

Response fields

Response field reference (6 fields)

NameTypeRequiredDescription
codestringoptional
Response code.
msgstringoptional
Prompt message or error message.
stdoutstringoptional
Comprehensive business insight report content (Markdown format), including six dimensions: market potential, product features, user reviews, customer portraits, search trends, and pricing analysis.
costTimeintegeroptional
The total processing time, in milliseconds.
costTokenintegeroptional
Token consumption.
typestringoptional
Response type.

Responses

CodeDescription
200Default HTTP response for both success and many business errors. Only outer JSON code 0 indicates success or asynchronous acceptance; inspect data for the result.
429Execution admission rate limit; honor Retry-After when present.
503Execution admission is temporarily unavailable; honor Retry-After when present.
Opt-inX-Nexscope-Http-Status: semantic maps controller-handled business errors to HTTP status on run and task routes. Pre-authentication failures, such as a missing API key (code 11209), may still return HTTP 200 before this mapping. Always check the outer JSON code; malformed requests and infrastructure failures may also return non-200 HTTP responses.

Data source, freshness, and limitations

Source, freshness, coverage, rate limits, and estimation notes are not specified in this API definition unless they appear in the request or response field documentation above. Do not assume official marketplace data or real-time freshness when it is not explicitly documented.

Step 1 of 2 · Connect your MCP client

MCP

V2 recommended

Connect remote agents through the standard MCP 2025-11-25 Streamable HTTP endpoint. Use OAuth 2.1 Authorization Code with PKCE, or an API key for compatibility.

POST https://api.nexscope.ai/mcp
MCP-Protocol-Version: 2025-11-25
Content-Type: application/json
Authentication

OAuth clients request the mcp:tools scope. The endpoint's 401 response advertises protected-resource metadata for authorization discovery.

Step 2 of 2 · Call the tool

Call a tool

{
  "jsonrpc": "2.0",
  "id": "tool-call-1",
  "method": "tools/call",
  "params": {
    "name": "nexscope_amazon_opportunity_report_by_keyword",
    "arguments": {
      "keyword": "phone case",
      "site": "US"
    }
  }
}

Legacy MCP v1

Existing API-key clients can continue using the compatibility endpoint. New integrations should use MCP v2.

GET / POST /mcp/legacy

Data Example

Request parameters

{
  "site": "US",
  "keyword": "cordless table lamp"
}

Response

{
  "code": 0,
  "msg": null,
  "data": {
    "stdout": "# Cordless Table Lamp 市场综合分析报告\n**市场:美国 Amazon | 关键词:cordless table lamp**\n\n---\n\n## 总览与市场判断\n\n这是一个**值得进入但需精准切入**的市场。台灯品类整体搜索量庞大(核心词 \"desk lamp\" 年搜索量达 6,974k+),而 \"cordless table lamp\" 细分赛道 YoY 增速高达 351%+,\"rechargeable table lamp\" 更达 1,287%+(搜索词分析),显示无线便携需求正从边缘走向主流。**主要机会**在于:现有产品普遍存在电池续航差(41.2%+ 差评)和质量不可靠(47.2%+ 差评)的双重痛点,而消费者愿意为解决这两个问题付费,市场存在明显的质量供给缺口。**最大风险**是:品类竞争激烈(96.7%+ 产品投放 Sponsored 广告),新品评论壁垒高(老品均值 11,000+ 条评论),且整体价格带集中在 $9.99–$32.50,溢价空间受限。\n\n### 核心指标汇总\n\n| 维度 | 核心指标 |\n|------|---------|\n| 市场潜力 | 年销售额 $14.1M–$18.8M;YoY 搜索增长 258.7%+;近 180 天回落 13.3%;活跃产品 85 个 / 65 个品牌 |\n| 产品特征 | 最热门属性:触控调光 + USB 充电 + 无线设计;头部品牌:Fenmzee、Dicoool、Airlonv |\n| 评价分析 | 正面:整体质量(78.9%+)、性价比(46.4%+);负面:不能使用(47.2%+)、电池续航差(41.2%+)|\n| 客户画像 | 主力年龄 22–45 岁;中等收入($40k–$75k);学生 + 远程办公者 + 年轻房主 |\n| 搜索词 | \"cordless lamp\" 1,355k+ 搜索;\"rechargeable table lamp\" 959k+;非品牌词占比 95%+ |\n| 价格分析 | 入门段($9.99–$32.50)占 71.4% 产品 / 78.6% Click Share;最优价格带 $16–$22 |\n\n---\n\n## 市场机会与竞争格局\n\n### 市场阶段与增长方向\n\n台灯品类整体处于**成熟期**,但无线/可充电细分赛道正处于**高速成长期**。核心矛盾在于:\n\n- **整体品类降温**:近 180 天搜索量下滑 13.3%(市场潜力),说明传统有线台灯需求趋于饱和。\n- **无线细分爆发**:同期 \"rechargeable table lamp\" YoY +1,287%、\"cordless table lamp\" YoY +351%、\"battery operated lamp\" 搜索量达 919k+(搜索词分析),三个无线相关词合计搜索量超 4,100k+,占品类总搜索量约 12.7%,且仍在快速扩张。\n\n**季节性特征**:需求峰值出现在 7 月(搜索量 1,212k+),低谷在 4 月(448k+),峰谷差约 63%(市场潜力)。这一规律与暑期居家布置/开学备货周期吻合,建议在 5–6 月完成库存备货。\n\n### 竞争集中度与进入难度\n\n**【交叉分析:搜索增长 vs. 产品数量增长】**\n\n- 品类搜索量 YoY 增长 258.7%,但品牌数量 YoY 仅变化 1.5%(65 个品牌,市场潜力)。\n- 这意味着**需求增速远超供给扩张速度**,尤其在无线细分赛道,供给缺口更为显著——Top 10 产品中仅 4 款具备可充电功能(产品特征),而无线相关搜索词已占总搜索量约 12.7%。\n\n**【交叉分析:品牌词占比 vs. 搜索行为】**\n\n- 非品牌词占搜索量 95%+(搜索词分析),说明消费者品牌忠诚度极低,购买决策以功能和价格为主导。\n- Top 5 产品仅占 24.2% Click Share(市场潜力),品牌集中度低,新卖家凭借差异化功能可快速切入。\n\n**竞争壁垒量化**:\n\n| 壁垒类型 | 数据支撑 | 评估 |\n|---------|---------|------|\n| 广告竞争 | 96.7%+ 产品投放 Sponsored 广告(市场潜力) | 高——广告成本不可忽视 |\n| 评论壁垒 | 新品均值 500+ 条;老品均值 11,000+ 条(产品特征) | 中——新品有基准,但差距悬殊 |\n| 价格竞争 | 78.6% Click Share 集中在 $9.99–$32.50(价格分析) | 中——入门价格带拥挤但有功能溢价空间 |\n| 品牌壁垒 | 非品牌搜索占 95%+(搜索词分析) | 低——品牌忠诚度弱,功能驱动决策 |\n\n---\n\n## 产品与消费者需求\n\n### 制胜产品属性\n\nTop 10 产品中,8 款具备触控三档调光,7 款具备 USB-C/USB-A 充电,4 款具备可充电设计(产品特征)。消费者最认可的功能组合为:\n\n1. **触控调光 + USB 充电 + 交流插座**:满足多设备充电需求,适合床头/书桌场景\n2. **无线 + 无级调光 + 三色温**:可充电台灯的溢价功能组合,适合餐桌/户外/灵活摆放场景\n\n正面评价中,78.9%+ 提及整体质量,46.4%+ 提及性价比,34.0%+ 提及亮度表现(评价分析)——说明消费者的基础期望是\"好用、亮、值\",而非品牌或外观。\n\n### 消费者痛点与需求缺口\n\n**【交叉分析:差评痛点 vs. 搜索词增长 → 需求已显性化】**\n\n| 痛点(评价分析) | 对应搜索行为(搜索词分析) | 结论 |\n|---------------|------------------------|------|\n| 电池续航差(41.2%+ 差评) | \"rechargeable table lamp\" YoY +1,287% | 消费者正在主动搜索\"更好的充电方案\",需求已显性化 |\n| 产品不能使用(47.2%+ 差评) | 非品牌词占 95%+,无品牌忠诚度 | 质量失信导致消费者持续换品,新品机会窗口持续存在 |\n| 廉价塑料材质(16.6%+ 差评) | \"cordless table lamp\" YoY +351% | 无线产品溢价预期更高,材质升级有定价支撑 |\n\n**【交叉分析:目标客群收入 vs. 价格带 → 溢价空间评估】**\n\n- 主力消费群体年收入 $40k–$75k(客户画像),属中等收入群体。\n- 当前最优价格带为 $16–$22(价格分析),对应年收入 $40k–$75k 的消费者,这一价格仅占月收入的 0.3%–0.5%,属于低决策门槛消费。\n- 关键推论:**若产品能解决电池续航和质量可靠性问题,定价 $28–$38 仍在该收入群体的可接受范围内**,且中端价格带($32.50–$55.02)目前 Click Share(17.0%)低于产品占比(22.6%),说明现有中端产品未能有效传递价值,而非消费者不愿付费。\n\n### 次级客群:科技便利型消费者(25–40 岁)\n\n该群体(客户画像)对无线、无线充电、智能家居集成有明确偏好,与 \"cordless lamp\" 1,355k+ 搜索量高度吻合(搜索词分析)。目前智能家居连接、RGB 模式、定时功能均属\"稀缺功能\"(产品特征),是差异化切入点,但需评估开发成本与定价承接能力。\n\n---\n\n## 流量与关键词机会\n\n### 搜索流量分布\n\n| 关键词类别 | 代表词 | 搜索量 | YoY 增长 | 竞争强度 |\n|-----------|-------|--------|---------|---------|\n| 核心大词 | \"desk lamp\" | 6,974k+ | 高基数 | 极高 |\n| 无线细分 | \"cordless lamp\" | 1,355k+ | 351%+ | 中(供给不足) |\n| 可充电细分 | \"rechargeable table lamp\" | 959k+ | 1,287%+ | 中(快速增长) |\n| 床头场景 | \"bedside lamps\" | 1,707k+ | 稳定 | 高 |\n| 电池操作 | \"battery operated lamp\" | 919k+ | 高增长 | 中 |\n| 高转化词 | \"desk lamps for home office\" | — | — | 转化率 2.59%(最高)|\n\n(数据来源:搜索词分析)\n\n### 长尾机会词\n\n以下词与消费者痛点直接对应,搜索意图明确,广告竞争相对较低:\n\n- **\"cordless table lamp rechargeable\"**:同时覆盖 351%+ 和 1,287%+ 增长赛道\n- **\"battery operated table lamp long lasting\"**:直接对应 41.2%+ 差评中的续航痛点\n- **\"touch lamp cordless\"**:结合最高频正面功能(触控)与最快增长趋势(无线)\n- **\"rechargeable lamp for nightstand\"**:结合床头场景(1,707k+ 搜索)与无线需求\n\n### 新卖家流量获取难度综合判断\n\n**难度:中等偏高**。理由:96.7%+ 产品投放广告(市场潜力),广告竞价激烈;但非品牌词占 95%+(搜索词分析),意味着消费者不锁定品牌,优质新品有机会通过广告快速获得曝光。无线细分赛道搜索量增速远超现有供给,是新卖家相对低竞争的流量入口。\n\n---\n\n## 行动建议\n\n### 建议一:以\"长续航可充电台灯\"为核心差异化切入无线细分赛道\n\n**做什么**:开发一款定价 $28–$35 的可充电台灯,核心卖点为大容量电池(6,000mAh+,超越现有主流 4,000–5,000mAh)+ 触控无级调光 + 三色温,外壳采用哑光金属或陶瓷质感材料替代塑料。\n\n**为什么**:\n- 无线细分搜索量合计 4,100k+,YoY 增速 351%–1,287%(搜索词分析),需求爆发但供给不足(Top 10 中仅 4 款可充电产品,产品特征)。\n- 41.2%+ 差评直接指向电池续航差,35.3%+ 正面评价称赞长续航(评价分析)——这是消费者愿意为之付费的明确信号。\n- 16.6%+ 差评提及廉价塑料(评价分析),而中端价格带($32.50–$55.02)Click Share 低于产品占比(价格分析),说明现有中端产品未能传递质量价值,新品有机会以真实材质升级填补这一空白。\n\n**风险提示**:大容量电池(6,000mAh+)会增加产品重量和成本,需在产品开发阶段验证重量是否影响便携体验;同时 $28–$35 价格带需要至少 200–300 条真实评论才能在广告竞争中获得足够转化率,冷启动期广告预算需充足规划。\n\n---\n\n### 建议二:首批广告聚焦无线细分长尾词,规避核心大词竞争\n\n**做什么**:广告策略分两层——第一层精准投放 \"cordless table lamp rechargeable\"、\"battery operated table lamp\"、\"rechargeable lamp for nightstand\" 等长尾词;第二层以 \"desk lamps for home office\"(转化率 2.59%,搜索词分析)作为高转化补充词,暂不竞争 \"desk lamp\"、\"table lamp\" 等核心大词。\n\n**为什么**:\n- \"desk lamp\" 等核心词竞争极度激烈(96.7%+ 产品投放广告,市场潜力),新品 ASIN 权重低,广告成本高且转化率难以保证。\n- 无线细分词(\"cordless lamp\" 1,355k+、\"rechargeable table lamp\" 959k+)搜索量大、增速快,但现有供给中专门针对这些词优化的产品数量有限,广告竞价相对较低。\n- 非品牌词占 95%+(搜索词分析),消费者以功能词搜索为主,长尾功能词的购买意图更精准,有助于提升新品初期 Conversion Rate。\n\n**风险提示**:无线细分词增速虽快,但绝对搜索量仍低于核心词(\"desk lamp\" 6,974k+ vs. \"cordless lamp\" 1,355k+),单纯依赖细分词流量天花板有限。建议在积累 300+ 评论、评分稳定在 4.5+ 后,逐步扩展至核心大词竞价。\n\n---\n\n### 建议三:将\"质量可靠性\"作为 Listing 核心信任背书,而非功能堆砌\n\n**做什么**:在产品 Listing 的 Bullet Points 和 A+ 内容中,将质量保障信息(如 18 个月质保、严格 QC 测试、电池循环寿命 500 次+)置于功能参数之前;主图和视频中展示电池续航测试场景(如\"单次充电使用 8 小时\"的实测画面)。\n\n**为什么**:\n- 47.2%+ 差评来自\"产品不能使用\",耐用性差评从 2026 年 1 月的 9.5%+ 上升至 5 月的 15.8%+(评价分析),说明消费者对品类整体质量信任度持续下降——这是新品建立信任差异化的窗口期。\n- 78.9%+ 正面评价提及整体质量(评价分析),说明消费者一旦收到质量过关的产品,给出好评的概率极高,有助于快速积累评分。\n- 主力消费群体(22–45 岁,中等收入,客户画像)在购买决策中高度依赖评论数量和评分,而当前新品均值仅 500+ 条评论(产品特征),质量口碑是突破评论壁垒最高效的路径。\n\n**风险提示**:质量承诺需要供应链端的真实支撑。若工厂 QC 能力不足,强调质量保障反而会加速差评积累,建议在首批备货前完成至少 50 件样品的压力测试,重点验证电池续航和触控模块的稳定性。",
    "costTime": 52590,
    "type": "stdoutWorkbenches"
  }
}

Online test

Execute the current API with your API key and JSON payload. Online tests use this site's configured API environment; the Endpoint and copyable examples use the public integration address.

Recent Avg. 49 · Range 45–56 credits / callAPI usage records

Try it

Send a real request with the same contract shown in the reference.

Endpoint
/amazon/opportunity/reportByKeyword
MCP method
nexscope_amazon_opportunity_report_by_keyword
cURL
curl -X POST \
  https://api.nexscope.ai/amazon/opportunity/reportByKeyword \
  -H "Authorization: Bearer nk-..." \
  -H "Content-Type: application/json" \
  -d '{ "keyword": "ice bricks", "site": "US" }'
Response
No response yet. Run the request to see the response here.

Related APIs