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

Choose an integration method

Amazon ABA & Business Insights

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 dataSnapshotMonth, page, pageItemCount, pageSize, sourceTool, sourceType, stdout, title.

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 dataSnapshotMonth, page, pageItemCount 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 dataSnapshotMonth, page, pageItemCount 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 dataSnapshotMonth, page, pageItemCount, pageSize, sourceTool, sourceType, stdout, title. 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 credits Connect 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"
}'

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

Code	Description
200	Default HTTP response for both success and many business errors. Only outer JSON code 0 indicates success or asynchronous acceptance; inspect data for the result.
429	Execution admission rate limit; honor Retry-After when present.
503	Execution admission is temporarily unavailable; honor Retry-After when present.
Opt-in	X-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.

View parameters & response Try online

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.

Open tester

Endpoint

Method	`POST`
Path	`https://api.nexscope.ai/amazon/opportunity/reportByKeyword`
Auth	`Bearer API key`
Content-Type	`application/json`

Request parameters

Name	Type	Required	Description
`site`	`string`	required	Amazon site code, currently only supports `US`. Example: US
`keyword`	`string`	required	The search keyword to query the insight report.

Code example

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

Response example

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

{
  "code": 0,
  "cost": "-1",
  "data": {},
  "msg": null,
  "time": "2026-01-01 00:00:00",
  "traceId": null,
  "ts": "0"
}

Response fields

Name	Type	Required	Description
`code`	`integer`	required	0 means accepted or successful; nonzero is a platform error.
`cost`	`string`	required	Elapsed milliseconds, never credits; -1 outside web requests.
`data`	`any`	required	Data value used by this API operation.
`msg`	`string \| null`	required	Msg value used by this API operation.
`time`	`string`	required	Server local time: yyyy-MM-dd HH:mm:ss.
`traceId`	`string \| null`	required	Trace id value used by this API operation.
`ts`	`string`	required	Epoch milliseconds.

Any of option 1

Name	Type	Required	Description
`data`	`object`	required	Data value used by this API operation.
`data.costTime`	`any`	optional	Cost time value used by this API operation.
`data.costToken`	`any`	optional	Cost token value used by this API operation.
`data.dataSnapshotMonth`	`any`	optional	Data snapshot month value used by this API operation.
`data.page`	`any`	optional	Page value used by this API operation.
`data.pageItemCount`	`any`	optional	Page item count value used by this API operation.
`data.pageSize`	`any`	optional	Page size value used by this API operation.
`data.sourceTool`	`any`	optional	Source tool value used by this API operation.
`data.sourceType`	`any`	optional	Source type value used by this API operation.
`data.stdout`	`any`	optional	Stdout value used by this API operation.
`data.title`	`any`	optional	Title value used by this API operation.
`data.totalPage`	`any`	optional	Total page value used by this API operation.
`data.type`	`any`	optional	Type value used by this API operation.

Any of option 1

Name	Type	Required	Description
`data.costTime`	`integer`	optional	The total processing time, in milliseconds. Example: null

Any of option 2

Name	Type	Required	Description
`data.costTime`	`null`	optional	Cost time value used by this API operation.

Any of option 1

Name	Type	Required	Description
`data.costToken`	`integer`	optional	Token consumption. Example: null

Any of option 2

Name	Type	Required	Description
`data.costToken`	`null`	optional	Cost token value used by this API operation.

Any of option 1

Name	Type	Required	Description
`data.dataSnapshotMonth`	`string`	optional	Data snapshot month returned by the upstream provider. Example: null

Any of option 2

Name	Type	Required	Description
`data.dataSnapshotMonth`	`null`	optional	Data snapshot month value used by this API operation.

Any of option 1

Name	Type	Required	Description
`data.page`	`integer`	optional	Current page returned by the upstream provider. Example: null

Any of option 2

Name	Type	Required	Description
`data.page`	`null`	optional	Page value used by this API operation.

Any of option 1

Name	Type	Required	Description
`data.pageItemCount`	`integer`	optional	Item count on the current page returned by the upstream provider. Example: null

Any of option 2

Name	Type	Required	Description
`data.pageItemCount`	`null`	optional	Page item count value used by this API operation.

Any of option 1

Name	Type	Required	Description
`data.pageSize`	`integer`	optional	Page size returned by the upstream provider. Example: null

Any of option 2

Name	Type	Required	Description
`data.pageSize`	`null`	optional	Page size value used by this API operation.

Any of option 1

Name	Type	Required	Description
`data.sourceTool`	`string`	optional	Provider-specific source tool name. Example: null

Any of option 2

Name	Type	Required	Description
`data.sourceTool`	`null`	optional	Source tool value used by this API operation.

Any of option 1

Name	Type	Required	Description
`data.sourceType`	`string`	optional	Provider-specific source platform type. Example: null

Any of option 2

Name	Type	Required	Description
`data.sourceType`	`null`	optional	Source type value used by this API operation.

Any of option 1

Name	Type	Required	Description
`data.stdout`	`string`	optional	Comprehensive business insight report content (Markdown format), including six dimensions: market potential, product features, user reviews, customer portraits, search trends, and pricing analysis. Example: null

Any of option 2

Name	Type	Required	Description
`data.stdout`	`null`	optional	Stdout value used by this API operation.

Any of option 1

Name	Type	Required	Description
`data.title`	`string`	optional	Provider-specific response title. Example: null

Any of option 2

Name	Type	Required	Description
`data.title`	`null`	optional	Title value used by this API operation.

Any of option 1

Name	Type	Required	Description
`data.totalPage`	`integer`	optional	Total page count returned by the upstream provider. Example: null

Any of option 2

Name	Type	Required	Description
`data.totalPage`	`null`	optional	Total page value used by this API operation.

Any of option 1

Name	Type	Required	Description
`data.type`	`string`	optional	Response type. Example: null

Any of option 2

Name	Type	Required	Description
`data.type`	`null`	optional	Type value used by this API operation.

Any of option 2

Name	Type	Required	Description
`data`	`null`	required	Data value used by this API operation.

Responses

Code	Description
200	Default HTTP response for both success and many business errors. Only outer JSON code 0 indicates success or asynchronous acceptance; inspect data for the result.
429	Execution admission rate limit; honor Retry-After when present.
503	Execution admission is temporarily unavailable; honor Retry-After when present.
Opt-in	X-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

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.

32 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

API key*

JSON payload*

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

Amazon Keyword Intelligence

Explore weekly Amazon Brand Analytics search-term data.

Amazon Opportunity Search By Metrics

Filter Amazon niches and keywords using 30+ business metrics covering market size, growth, competition, pricing, demographics.

Amazon Policy Feed

Browse Amazon policy updates by marketplace and date, with AI-generated Chinese summaries.

Amazon Policy Update Details

Read the details of a selected Amazon policy update to understand the announcement and assess its relevance to your business.