Nexscope
🇺🇸 English
Start free

Amazon Keyword Overview

Evaluate search demand and competition for an Amazon keyword. Call the Amazon Keyword Overview API via REST or MCP from 12 credits per call.

CostRecent Avg. 19 · Range 10–19 credits / call
Try online
POST · https://api.nexscope.ai/sf/keywordOverviewMCP · nexscope_amazon_keyword_overview

What this API does

Check search demand and competition for any Amazon keyword in 13 marketplaces. Get estimated weekly search volume, popularity rank, supply-demand ratio and how many products appear in organic and ad placements. Built for sellers, PPC managers and AI agents doing keyword and product research.

Amazon Keyword Overview API use cases

Validate a product idea

Before launching a new product, an Amazon seller checks the main keyword's weekly search volume and supply-demand ratio to see whether demand is large enough and competition low enough to enter.

Gauge ad competition

A PPC manager sees how many products run Sponsored Products, brand and video ads on a keyword, to judge how crowded the ad auction is before setting bids.

Choose the best marketplace

An agency or AI agent checks the same keyword across supported Amazon marketplaces and compares the balance of demand and competition before selecting a market to investigate.

Amazon Keyword Overview API FAQ

What does the Amazon Keyword Overview API return?

The API returns estimated weekly search volume, keyword popularity rank, supply-demand ratio and product counts for organic results, Sponsored Products, brand ads and video ads. The result also identifies the data period and keyword update time. These are keyword-level demand and competition signals, rather than a guarantee of future sales or advertising performance.

How many credits does the Amazon Keyword Overview API cost?

The current documented cost is Recent Avg. 19 · Range 10–19 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 Keyword Overview API from my app or an MCP client?

Send a POST request to https://api.nexscope.ai/sf/keywordOverview 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_keyword_overview. 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/sf/keywordOverview
MCP method
nexscope_amazon_keyword_overview

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/sf/keywordOverview

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/sf/keywordOverview' \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "country": "US",
  "keyword": "wireless charger"
}'

Code example

{
  "country": "US",
  "keyword": "wireless charger"
}

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 Search Intelligence SF
POSThttps://api.nexscope.ai/sf/keywordOverview

Run this API

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

Endpoint

MethodPOST
Pathhttps://api.nexscope.ai/sf/keywordOverview
AuthBearer API key
Content-Typeapplication/json

Request parameters

NameTypeRequiredDescription
keywordstringrequired
Keywords, maximum length 1000; try to use target site language
countrystringoptional
Site: `US`, `UK`, `DE`, `CA`, `JP`, `FR`, `ES`, `IT`, `MX`, `AU`, `AE`, `BR`, `SA`
Example: US
last7dbooleanoptional
Whether to take the last 7 days; when it is `false`, use the date range
Example: true
startDatestringoptional
`yyyy-MM-dd`; takes effect when `last7d=false`
endDatestringoptional
`yyyy-MM-dd`; works with `startDate`

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 (30 fields)

NameTypeRequiredDescription
msgstringoptional
news
totalintegeroptional
Total amount of data, usually 1
codestringoptional
sf business return code, `"1"` indicates success
dataarrayoptional
keyword overview array
costTimeintegeroptional
Time consuming (ms)
costTokenintegeroptional
Consume token
columnsarrayoptional
render column
typestringoptional
rendering style
titlestringoptional
Title
keywordstringoptional
keywords
keywordPopularityRankintegeroptional
Keyword popularity ranking. The smaller the value, the greater the search volume.
estimatedWeeklySearchVolumeintegeroptional
Estimated search volume per week
supplyDemandRationumberoptional
Supply and demand ratio (number of search results products / monthly search volume), the smaller the value, the smaller the competition and the greater the opportunity.
totalSearchResultProductCountintegeroptional
Total number of search results items
naturalSearchProductCountintegeroptional
Number of natural search items
sponsoredProductsCountintegeroptional
SP number of advertised items
brandAdProductCountintegeroptional
Number of brand advertising products
videoAdProductCountintegeroptional
Number of video advertising products
paidAdvertisingProductCountintegeroptional
Total number of PPC paid advertising products
amazonChoiceProductCountintegeroptional
Amazon's Choice item count
topRatedProductCountintegeroptional
Top Rated number of items
searchRecommendationProductCountintegeroptional
Search the number of recommended products
editorialRecommendationsProductCountintegeroptional
Number of items recommended by editors
recNonadProductCountintegeroptional
Number of recommended non-advertising products
recAdProductCountintegeroptional
Number of recommended advertising products
trackedAsinTotalCountintegeroptional
The total number of exposed ASIN deduplication tracked by sf; the upstream field is `totalAsinNum`
totalMarketplaceKeywordCountintegeroptional
Total number of site keywords
dataPeriodStartDatestringoptional
Data period start date
dataPeriodEndDatestringoptional
Data period end date
keywordDataUpdateTimestringoptional
Keyword data update time

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_keyword_overview",
    "arguments": {
      "country": "US",
      "keyword": "phone case",
      "last7d": true
    }
  }
}

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.

Recent Avg. 19 · Range 10–19 credits / callAPI usage records

Try it

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

Endpoint
/sf/keywordOverview
MCP method
nexscope_amazon_keyword_overview
cURL
curl -X POST \
  https://api.nexscope.ai/sf/keywordOverview \
  -H "Authorization: Bearer nk-..." \
  -H "Content-Type: application/json" \
  -d '{ "country": "US", "keyword": "wireless charger" }'
Response
No response yet. Run the request to see the response here.

Related APIs