Nexscope

Amazon Research JS: keywords/by keyword API

Use Amazon Research JS: keywords/by keyword API through Nexscope with documented parameters, structured results and API key authentication.

CostRecent Avg. 191 · Range 133–1328 credits / call
Try online
POST · https://api.nexscope.ai/js/keywords/by-keywordMCP · nexscope_data_js_keywords_by_keyword
Amazon Research JS

What this API does

Use Amazon Research JS: keywords/by keyword API through Nexscope with documented parameters, structured results and API key authentication. The request accepts marketplace, searchTerms, needCount, sort, minMonthlySearchVolumeExact. Its documented result includes keywordInfoList, name, country, monthlySearchVolumeExact, monthlySearchVolumeBroad, monthlyTrend, quarterlyTrend, dominantCategory.

Amazon Research JS: keywords/by keyword API API use cases

Build a keyword shortlist

To build a keyword shortlist, a marketplace analyst submits marketplace and searchTerms to Amazon Research JS: keywords/by keyword API. The returned keywordInfoList, name, country help choose candidate search terms for further investigation.

Compare search demand signals

A marketplace analyst uses Amazon Research JS: keywords/by keyword API with marketplace and searchTerms to compare search demand signals. The returned keywordInfoList, name, country help compare keyword demand within the requested market scope.

Plan a content or advertising test

For this workflow, a marketplace analyst calls Amazon Research JS: keywords/by keyword API with marketplace and searchTerms to plan a content or advertising test. The result helps select terms for a content or advertising experiment.

Amazon Research JS: keywords/by keyword API API FAQ

What does the Amazon Research JS: keywords/by keyword API API return?

Use Amazon Research JS: keywords/by keyword API through Nexscope with documented parameters, structured results and API key authentication. The documented output includes keywordInfoList, name, country, monthlySearchVolumeExact, monthlySearchVolumeBroad, monthlyTrend, quarterlyTrend, dominantCategory. It corresponds to the supplied marketplace, searchTerms, needCount, sort, minMonthlySearchVolumeExact. 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 Research JS: keywords/by keyword API API cost?

The current documented cost is Recent Avg. 191 · Range 133–1328 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 Research JS: keywords/by keyword API API from my app or an MCP client?

Send a POST request to https://api.nexscope.ai/js/keywords/by-keyword 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_data_js_keywords_by_keyword. The same documented request parameters apply; use Online test to review a request before adding it to your app.

View plans and creditsConnect this API with MCP

Try this API
Endpoint
https://api.nexscope.ai/js/keywords/by-keyword
MCP method
nexscope_data_js_keywords_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/js/keywords/by-keyword

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/js/keywords/by-keyword' \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "marketplace": "us",
  "needCount": 20,
  "searchTerms": "yoga mat"
}'

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
200HTTP request completed. Check JSON code; only 0 indicates business success or acceptance.
400Request JSON or required API parameters are invalid.
401API key is missing, invalid, or cannot be matched to a user.
5xxAPI execution or upstream service failed.
All categories/ Amazon Research JS
POSThttps://api.nexscope.ai/js/keywords/by-keyword

Run this API

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

Endpoint

MethodPOST
Pathhttps://api.nexscope.ai/js/keywords/by-keyword
AuthBearer API key
Content-Typeapplication/json

Request parameters

NameTypeRequiredDescription
marketplacestringrequired
Target market code. Optional values: `us`, `uk`, `de`, `in`, `ca`, `fr`, `it`, `es`, `mx`, `jp`
Example: us
searchTermsstringrequired
Seed keyword (single keyword string)
needCountintegeroptional
Return the total number of results
sortstringoptional
Sorting field, defaults to descending order by exact search volume
Example: -monthly_search_volume_exact
minMonthlySearchVolumeExactintegeroptional
Exact search volume minimum
maxMonthlySearchVolumeExactintegeroptional
Exact search volume cap
minMonthlySearchVolumeBroadintegeroptional
Broad search volume minimum
maxMonthlySearchVolumeBroadintegeroptional
Broad search volume cap
minWordCountintegeroptional
Minimum number of keywords (used to filter long-tail words)
maxWordCountintegeroptional
Key words maximum number of words
minOrganicProductCountintegeroptional
Minimum number of natural ranking products
maxOrganicProductCountintegeroptional
Maximum number of natural ranking products

Code example

{
  "marketplace": "us",
  "needCount": 20,
  "searchTerms": "yoga mat"
}

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

Response field reference (17 fields)

NameTypeRequiredDescription
costTokenintegeroptional
Number of tokens consumed
keywordInfoListarrayoptional
Keyword information list
namestringoptional
Keyword name
countrystringoptional
market code
monthlySearchVolumeExactintegeroptional
Average monthly exact match search volume
monthlySearchVolumeBroadintegeroptional
Average monthly broad match search volume
monthlyTrendnumberoptional
Monthly search volume percentage change
quarterlyTrendnumberoptional
Quarterly search volume percentage change
dominantCategorystringoptional
Category with the highest proportion in search results
relevancyScoreintegeroptional
Relevance score to seed word
easeOfRankingScoreintegeroptional
Ease of ranking score (the higher, the easier it is to rank)
organicProductCountintegeroptional
Number of naturally ranked products
sponsoredProductCountintegeroptional
Advertising product quantity
ppcBidExactnumberoptional
Exact match PPC recommended bid (USD)
ppcBidBroadnumberoptional
Broad match PPC recommended bid (USD)
spBrandAdBidnumberoptional
Sponsored Brand Ad Recommended Bid (USD)
recommendedPromotionsintegeroptional
Recommended promotional gift quantity

Responses

CodeDescription
200HTTP request completed. Check JSON code; only 0 indicates business success or acceptance.
400Request JSON or required API parameters are invalid.
401API key is missing, invalid, or cannot be matched to a user.
5xxAPI execution or upstream service failed.

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_data_js_keywords_by_keyword",
    "arguments": {
      "marketplace": "us",
      "needCount": 20,
      "searchTerms": "yoga mat"
    }
  }
}

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.

88 credits / callAPI usage records

Try it

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

Endpoint
/js/keywords/by-keyword
MCP method
nexscope_data_js_keywords_by_keyword
cURL
curl -X POST \
  https://api.nexscope.ai/js/keywords/by-keyword \
  -H "Authorization: Bearer nk-..." \
  -H "Content-Type: application/json" \
  -d '{ "marketplace": "us", "needCount": 20, "searchTerms": "yoga mat" }'
Response
No response yet. Run the request to see the response here.

Related APIs