nexscope-ai/nexscope-ecommerce-skills / ecommerce-amazon-search
ecommerce-amazon-search
VerifiedSimulates a real user searching on Amazon's storefront to get real-time keyword ranking and search results page data. Use when the user mentions Amazon product search, search result scraping, keyword ranking on search pages, ASIN ranking position check, competitor discovery, search page price comparison, sponsored product analysis, new product monitoring, or storefront search simulation. Even if the user does not explicitly mention "search simulation", trigger this skill whenever their need involves real-time Amazon search results, product ranking data, or storefront SERP analysis.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 12.3 KB |
| manifest.json | config | 268 B |
| references/api.md | markdown | 10.7 KB |
| scripts/amazon_search.py | script | 6.5 KB |
references/api.md
View on GitHub# Amazon Frontend Search Simulation API Reference
## API Specification
- **Endpoint**: `${NEXSCOPE_PROXY_BASE}/api/v1/tools/research/amazon/search`
- **HTTP Method**: POST, Content-Type: application/json
- **Authentication**: Header `Authorization: <api_key>`, read api_key from environment variable `NEXSCOPE_API_KEY` or `NEXSCOPE_API_KEY` (if not configured, follow **## Resolving Authentication and Credit Issues** in SKILL.md)
## Request Parameters
POST Body (JSON):
| Parameter | Type | Required | Description |
|------|------|------|------|
| keyword | string | No | Keyword; please translate to the language of the target country whenever possible, e.g., use English keywords for the US, German keywords for Germany, etc. (max length 1024) |
| amazonDomain | string | No | Amazon country site, default `amazon.com` |
| node | string | No | Amazon category node (max length 1000) |
| language | string | No | Language/region code, e.g., en_US, de_DE, ja_JP, fr_FR (max length 1000) |
| sort | string | No | Sort order: `relevanceblender` (Featured, default), `price-asc-rank` (Price low to high), `price-desc-rank` (Price high to low), `review-rank` (Avg. customer review), `date-desc-rank` (Newest arrivals), `exact-aware-popularity-rank` (Best sellers) |
| page | integer | No | Page number (starting from 1, ~20 items per page), default `1` |
| deliveryZip | string | No | Delivery zip code, used to simulate Amazon frontend address. It is recommended to use commonly used zip codes for major cities in the target country, e.g., New York zip code 10001 for the US site (max length 1000) |
| device | string | No | Device type: `desktop`, `mobile`, `tablet`, default `desktop` (max length 1000) |
| includeSellerSpriteData | boolean | No | Default `false`; enabling enrichment incurs additional dynamic charges. Date coverage is optional, not guaranteed. |
### Optional enrichment and listing date
`includeSellerSpriteData` is an optional JSON boolean, default `false`. Enable it only when the user authorizes the additional dynamic charges. It can populate `products[].availableDate` and other enrichment fields when covered; it does not guarantee a date for every ASIN. Monthly sales fields alone do not prove that enrichment was enabled.
`sellerSpriteEnriched` is an optional response flag describing whether enrichment was requested. It may be absent and is not a subscription/plan indicator or proof of complete data for each product. Do not synthesize it when omitted.
The date is a data-source listing/first-available date, not a verified brand launch date. It is optional and may be absent or empty. The source timezone is unspecified; use a consistent calendar-date basis for age calculations and leave missing dates unknown. Do not automatically make additional paid calls when a date is missing.
For an ASIN-based date lookup, use `ecommerce-amazon-product-history` with `{"asin":"B085S2CD7Y","domain":"1","history":0}` or `ecommerce-amazon-market-product-detail` with `{"asin":"B085S2CD7Y","marketplace":"us","includeTrend":2}`. Both document optional `products[].availableDate`; check the actual value before calculating age. These are separate credit-consuming queries and require user authorization before an additional call.
Example after the user authorizes enrichment:
```json
{"keyword":"coffee canister","amazonDomain":"amazon.com","page":1,"includeSellerSpriteData":true}
```
Keep ordinary search examples unchanged so enrichment remains disabled by default. Do not silently enable it or automatically retry with it.
### Supported amazonDomain Values
| Domain | Country |
|------|------|
| amazon.com | United States |
| amazon.co.uk | United Kingdom |
| amazon.de | Germany |
| amazon.fr | France |
| amazon.it | Italy |
| amazon.es | Spain |
| amazon.co.jp | Japan |
| amazon.ca | Canada |
| amazon.com.au | Australia |
| amazon.com.br | Brazil |
| amazon.in | India |
| amazon.nl | Netherlands |
| amazon.se | Sweden |
| amazon.pl | Poland |
| amazon.sg | Singapore |
| amazon.sa | Saudi Arabia |
| amazon.ae | UAE |
| amazon.com.mx | Mexico |
| amazon.com.tr | Turkey |
| amazon.com.be | Belgium |
| amazon.cn | China |
| amazon.eg | Egypt |
### Common language Values
| Region Code | Description |
|----------|------|
| en_US | US English |
| en_GB | UK English |
| de_DE | Germany German |
| fr_FR | France French |
| it_IT | Italy Italian |
| es_ES | Spain Spanish |
| ja_JP | Japan Japanese |
| en_CA | Canada English |
| fr_CA | Canada French |
| en_AU | Australia English |
| pt_BR | Brazil Portuguese |
| en_IN | India English |
| hi_IN | India Hindi |
| nl_NL | Netherlands Dutch |
| sv_SE | Sweden Swedish |
| pl_PL | Poland Polish |
| en_SG | Singapore English |
| ar_AE | UAE/Saudi Arabia/Egypt Arabic |
| en_AE | UAE/Saudi Arabia/Egypt English |
| tr_TR | Turkey Turkish |
| nl_BE | Belgium Dutch |
| fr_BE | Belgium French |
| zh_CN | China Chinese |
| pt_MX | Mexico Spanish |
### Common deliveryZip Values
| Country | City | Zip Code |
|------|------|------|
| United States | New York | 10001 |
| United Kingdom | London | EC1A 1BB |
| Germany | Berlin | 10115 |
| France | Paris | 75001 |
| Italy | Rome | 00100 |
| Spain | Madrid | 28001 |
| Japan | Tokyo | 100-0001 |
| Canada | Toronto | M5A 1A1 |
| Australia | Sydney | 2000 |
| Brazil | Sao Paulo | 01000-000 |
| India | New Delhi | 110001 |
| Netherlands | Amsterdam | 1012 |
| Sweden | Stockholm | 111 22 |
| Poland | Warsaw | 00-001 |
| Singapore | Singapore | 018989 |
| Saudi Arabia | Riyadh | 11564 |
| UAE | Abu Dhabi | 00000 |
| Mexico | Mexico City | 01000 |
| Turkey | Istanbul | 34349 |
| Belgium | Brussels | 1000 |
| China | Beijing | 100000 |
| Egypt | Cairo | 11511 |
## Nexscope response envelope
These research endpoints return a platform object with numeric `code`, nullable `msg`, and business `data`. Only outer `code: 0` means success; `200`, string codes, missing codes, and HTTP 200 alone do not. A nonzero code is a platform error: show `msg` and do not interpret the payload as a successful result.
`msg` preserves the upstream message when available; Chinese messages are translated to English by Nexscope. A successful response without a message has `msg: null`. Do not infer success or retry behavior from the message text. On both success and failure, the direct fields `code`, `errcode`, `errorCode`, `msg`, `errmsg`, `message`, and `errorMsg` are removed from public `data`. Read the message only from outer `msg`; deeper business fields are preserved, including nested `code` and `status`.
Business field tables and abbreviated business examples below describe `data`, unless explicitly labeled as a complete platform response. For example, a business `products` field is at HTTP `data.products`, and a business `data` array is at HTTP `data.data`. The research endpoints already had this outer envelope; no additional wrapper is added.
```json
{"code":0,"msg":null,"data":{}}
```
Metadata includes string `ts` (epoch milliseconds), string `cost` (elapsed milliseconds, not credits), `time`, and nullable `traceId`. Handle network/HTTP failures before the platform code; gateway failures may not be platform JSON. Keep the existing billing-header guidance separate from elapsed time.
## Response Structure
| Field | Type | Description |
|------|------|------|
| total | integer | Total rows |
| keyword | string | Search keyword |
| type | string | Render style |
| columns | array | Rendered column definitions |
| costToken | integer | Token consumption |
| products | array | Search result list (see below) |
| sellerSpriteEnriched | boolean | Optional; whether enrichment was requested. May be absent; not a plan indicator or per-ASIN coverage guarantee. |
### Product Object Fields in products
| Field | Type | Description |
|------|------|------|
| asin | string | ASIN |
| title | string | Title |
| brand | string | Brand |
| price | number | Price |
| extractedPrice | number | Parsed price |
| oldPrice | number | Strikethrough price |
| extractedOldPrice | number | Parsed strikethrough price |
| currency | string | Currency |
| priceUnit | string | Price unit |
| extractedPriceUnit | number | Parsed price unit |
| rating | number | Rating |
| ratings | integer | Number of ratings |
| position | integer | Position |
| sponsored | boolean | Whether sponsored |
| imageUrl | string | Thumbnail |
| asinUrl | string | Link |
| delivery | string | Delivery information |
| fulfillment | string | Fulfillment information (e.g., FBA) |
| availableDate | string | Optional data-source listing/first-available date; may be missing or empty, especially without enrichment. Timezone unspecified; not a verified launch date. |
| monthlySalesUnits | integer | Monthly sales units |
| monthlySalesRevenue | string | Monthly sales revenue |
| sellerNation | string | Seller nationality |
| dimension | string | Dimensions |
| weight | string | Weight |
| options | string | Options |
| offers | string | Offer information |
| badges | string | Amazon frontend search badges |
| tags | string | Tags |
| snapEbtEligible | boolean | SNAP/EBT eligibility |
| sourceType | string | Source type: amazon |
| sourceTool | string | Source tool |
| keyword | string | Keyword |
## Error Codes
HTTP 200 does not prove business success. Read only the numeric outer platform `code`: `0` succeeds and any other value fails. Show outer `msg`; never test removed provider codes or nested business `code` as the platform status. Authentication, permissions, balance, and validation failures may be platform errors even with HTTP 200; also handle non-2xx HTTP and non-JSON responses.
### Recovery guidance
| Condition | Action |
|---|---|
| Authentication failed | HTTP 401 or authorized error: follow **## Resolving Authentication and Credit Issues** in SKILL.md. |
| Insufficient credits | HTTP 402: follow **## Resolving Authentication and Credit Issues** in SKILL.md. |
## curl Example
```bash
curl -X POST ${NEXSCOPE_PROXY_BASE}/api/v1/tools/research/amazon/search \
-H "Authorization: Bearer ${NEXSCOPE_API_KEY}" \
-H "Content-Type: application/json" \
-d '{"keyword": "wireless earbuds", "amazonDomain": "amazon.com", "page": 1}'
```
---
## API Key request rate and retries
All API Keys of one Nexscope user share the public API execution request-rate allowance, measured in any rolling 1-second window. The allowed RPS depends on that user's entitlements; it is not a universal 1 RPS. One Skill operation may issue multiple public API requests, each of which uses the allowance.
HTTP 429 with Nexscope outer code `13012` means request-rate exhaustion: honor the response's `Retry-After`. Outer code `13013` means concurrent-request exhaustion, not rate exhaustion; honor `Retry-After` when supplied. Check the HTTP status and outer JSON code separately. Do not automatically replay writes or requests with uncertain outcomes; first reconcile the operation's state.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |