Nexscope

Amazon Policy Update Details

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

CostRecent 32 credits / call
Try online
POST · https://api.nexscope.ai/amazon/policyFeedDetailMCP · nexscope_data_amazon_policy_feed_detail

Choose an integration method

Amazon ABA & Business Insights

What this API does

Read the details of a selected Amazon policy update to understand the announcement and assess its relevance to your business. The request accepts id. Its documented result includes errcode, errmsg, stdout, title, summaryZh.

Amazon Policy Update Details API use cases

Inspect a candidate product

To inspect a candidate product, a marketplace analyst submits id to Amazon Policy Update Details. The returned errcode, errmsg, stdout help inspect the documented attributes of the candidate product.

Compare listing details

A marketplace analyst uses Amazon Policy Update Details with id to compare listing details. The returned errcode, errmsg, stdout help compare product details with another shortlisted listing.

Prepare product evidence for a sourcing review

For this workflow, a marketplace analyst calls Amazon Policy Update Details with id to prepare product evidence for a sourcing review. The result helps record product facts before a sourcing discussion.

Amazon Policy Update Details API FAQ

What does the Amazon Policy Update Details API return?

Read the details of a selected Amazon policy update to understand the announcement and assess its relevance to your business. The documented output includes errcode, errmsg, stdout, title, summaryZh. It corresponds to the supplied id. 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 Policy Update Details API cost?

The current documented cost is Recent 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 Policy Update Details API from my app or an MCP client?

Send a POST request to https://api.nexscope.ai/amazon/policyFeedDetail 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_amazon_policy_feed_detail. 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/policyFeedDetail
MCP method
nexscope_data_amazon_policy_feed_detail

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

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/policyFeedDetail' \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "id": "a1b2c3d4e5f6a1b2c3d4e5f6a1b2c3d4"
}'

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 ABA & Business Insights
POSThttps://api.nexscope.ai/amazon/policyFeedDetail

Run this API

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

Endpoint

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

Request parameters

NameTypeRequiredDescription
idstringrequired
Information record ID (32-bit string), `data[].id` from list interface response.

Code example

{
  "id": "a1b2c3d4e5f6a1b2c3d4e5f6a1b2c3d4"
}

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

NameTypeRequiredDescription
errcodeintegeroptional
Gateway response code, `200` indicates success.
errmsgstringoptional
Prompt message or error message.
typestringoptional
The response type is fixed to `stdoutWorkbenches`, and the front-end renders `stdout` according to Markdown.
stdoutstringoptional
The complete text of the information, in Markdown format.
titlestringoptional
Information title.
summaryZhstringoptional
AI-generated Chinese summary, summarizing 1-3 sentences.
costTimeintegeroptional
The total processing time, in milliseconds.
costTokenintegeroptional
Token consumption.

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_amazon_policy_feed_detail",
    "arguments": {
      "id": "a1b2c3d4e5f6a1b2c3d4e5f6a1b2c3d4"
    }
  }
}

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/policyFeedDetail
MCP method
nexscope_data_amazon_policy_feed_detail
cURL
curl -X POST \
  https://api.nexscope.ai/amazon/policyFeedDetail \
  -H "Authorization: Bearer nk-..." \
  -H "Content-Type: application/json" \
  -d '{ "id": "a1b2c3d4e5f6a1b2c3d4e5f6a1b2c3d4" }'
Response
No response yet. Run the request to see the response here.

Related APIs