Nexscope

Amazon Search

Find Amazon products by keyword and marketplace. Results come back as structured JSON. Call the Amazon Search API via REST or MCP from 21 credits per call.

CostRecent Avg. 30 · Range 16–32 credits / call
Try online
POST · https://api.nexscope.ai/amazon/searchMCP · nexscope_amazon_search

Choose an integration method

Amazon Public Marketplace Data

What this API does

Find Amazon products by keyword and marketplace. Results come back as structured JSON. The request accepts keyword, amazonDomain, node, language, sort. Its documented result includes keyword, products, asin, title, brand, price, extractedPrice, oldPrice.

Amazon Search API use cases

Find products matching a sourcing brief

To find products matching a sourcing brief, a marketplace analyst submits keyword and amazonDomain to Amazon Search. The returned keyword, products, asin help identify products matching the requested search criteria.

Compare a product search shortlist

A marketplace analyst uses Amazon Search with keyword and amazonDomain to compare a product search shortlist. The returned keyword, products, asin help compare candidates before requesting individual product details.

Collect candidates for a market review

For this workflow, a marketplace analyst calls Amazon Search with keyword and amazonDomain to collect candidates for a market review. The result helps choose products for a supplier or competitor review.

Amazon Search API FAQ

What does the Amazon Search API return?

Find Amazon products by keyword and marketplace. Results come back as structured JSON. The documented output includes keyword, products, asin, title, brand, price, extractedPrice, oldPrice. It corresponds to the supplied keyword, amazonDomain, node, language, sort. 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 Search API cost?

The current documented cost is Recent Avg. 30 · Range 16–32 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 Search API from my app or an MCP client?

Send a POST request to https://api.nexscope.ai/amazon/search 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_search. 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/search
MCP method
nexscope_amazon_search

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/search

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/search' \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "amazonDomain": "amazon.com",
  "keyword": "wireless earbuds",
  "page": 1
}'

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 Public Marketplace Data

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_search",
    "arguments": {
      "keyword": "phone case",
      "page": 1
    }
  }
}

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.

21 credits / callAPI usage records

Try it

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

Endpoint
/amazon/search
MCP method
nexscope_amazon_search
cURL
curl -X POST \
  https://api.nexscope.ai/amazon/search \
  -H "Authorization: Bearer nk-..." \
  -H "Content-Type: application/json" \
  -d '{ "amazonDomain": "amazon.com", "keyword": "wireless earbuds", "page": 1 }'
Response
No response yet. Run the request to see the response here.

Related APIs