Skip to content

nexscope-ai/nexscope-ecommerce-skills / ecommerce-amazon-market-product-detail

ecommerce-amazon-market-product-detail

Verified

Query Amazon product detail and historical trends by ASIN using Nexscope data, covering 14 marketplaces. Trigger when the user mentions Nexscope product detail, ASIN detail query, sales trends, price curves, price history, BSR ranking history, BSR trends, profit analysis, FBA fee analysis, gross margin, product trend analysis, daily/monthly sales, revenue trends, Deal promotion history, product detail, sales trend, price history, BSR ranking, profit analysis, FBA fees. Even if the user does not explicitly mention "Nexscope", if their need involves querying Amazon product detail or historical trend data by ASIN, this skill should also be triggered.

FileKindSize
SKILL.mdskill md10.6 KB
manifest.jsonconfig268 B
references/api.mdmarkdown10.8 KB
scripts/amazon_market_product_detail.pyscript6.6 KB

references/api.md

View on GitHub
# Nexscope Product Detail (with Trends) API Reference

## API Specification

- **Endpoint**: `${NEXSCOPE_PROXY_BASE}/api/v1/tools/research/sorftime/amazon/productDetail`
- **HTTP Method**: POST, Content-Type: application/json
- **Authentication**: Header `Authorization: <api_key>`, api_key is read from environment variable `NEXSCOPE_API_KEY` or `NEXSCOPE_API_KEY` (if not configured, follow the **## Resolving Authentication and Credits Issues** section in SKILL.md)

## Request Parameters

POST Body (JSON):

| Parameter | Type | Required | Description |
|------|------|------|------|
| asin | string | Yes | Amazon Standard Identification Number (ASIN), supports multiple (max 10), comma-separated. Example: `B0088PUEPK` or `B0088PUEPK,B00U26V4VQ` |
| marketplace | string | Yes | Amazon site code: us, gb, de, fr, in, ca, jp, es, it, mx, ae, au, br, sa |
| includeTrend | integer | No | Whether to include trend data. `1`: include (default); `2`: exclude |
| queryTrendStartDate | string | No | Trend start date, format `yyyy-MM-dd`. Default returns only the last 15 days; querying more than 15 days doubles the cost |
| queryTrendEndDate | string | No | Trend end date, format `yyyy-MM-dd` |

## Listing date and age

Read `products[].availableDate` only when present and nonempty. 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.

ASIN date lookup example:

```json
{"asin":"B085S2CD7Y","marketplace":"us","includeTrend":2}
```

## 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

### Top-Level Fields

| Field | Type | Description |
|------|------|------|
| total | integer | Total result count |
| costTime | integer | Latency (ms) |
| costToken | integer | Tokens consumed |
| requestConsumed | integer | Requests consumed |
| sourceType | string | Source type: Nexscope |
| type | string | Render style |
| columns | array | Render columns |
| products | array | Product detail list (see below) |

### Product Object Fields (products Array Elements)

Trend arrays use an interleaved format: even indices are dates (yyyyMMdd), odd indices are corresponding values.

| Field | Type | Description |
|------|------|------|
| asin | string | ASIN |
| title | string | Product title |
| brand | string | Brand |
| asinUrl | string | Product link, Amazon Listing detail page URL |
| imageUrl | string | Main image URL |
| productImageUrls | array | Main image list (all product image URLs) |
| ebcPhoto | array | A+ image list |
| storeName | string | Store name |
| description | string | Five bullet points |
| productBadge | array | Product badges, e.g. Amazon Choice, Best Seller, New Release, etc. |
| lastUpdate | string | Update time, most recent ASIN data collection time (format yyyy-MM-dd) |
| offSale | boolean | Whether delisted. true = unavailable, false = available |
| productType | string | Category, Amazon product category node name |
| weight | string | Weight, unit g |
| size | array | Dimensions, outer packaging [longest side, second longest side, shortest side], unit cm |
| parentAsin | string | Parent ASIN, the parent ASIN if variants exist, null if no variants |
| variationNum | integer | Number of variations |
| variationASIN | array | Child ASIN list, empty if no variants |
| attribute | array | Product attributes, variant attributes if variants exist. Each entry contains asin (child ASIN), name (attribute name), value (attribute value) |
| price | number | Selling price, actual price after coupon deduction, in local currency (e.g. USD) |
| coupon | integer | Coupon policy. Value >= 0 = deduction amount (e.g. 500 = $5), value < 0 = discount percentage (e.g. -10 = 10% discount) |
| platformFee | number | Platform commission, in local currency (e.g. USD) |
| fbaFees | number | FBA fees, in local currency (e.g. USD) |
| fbaDetail | array | FBA detail. First item is delivery fee, subsequent items are month:storage fee, e.g. [475,"1-9:5","10-12:15"] |
| shipCost | number | FBM shipping cost, in local currency (e.g. USD) |
| shipsFrom | string | Ship-from location |
| profitAmount | number | Profit, final price - FBA fee - commission, in local currency (e.g. USD) |
| profitRate | number | Profit margin, e.g. 25.83 means 25.83% |
| monthlySalesUnits | integer | Official monthly sales volume, Amazon published ASIN monthly sales, latest value from the last 7 calendar days, 0 if unavailable |
| salesRank | integer | BSR rank, main category rank |
| category | array | Main category, [category name, NodeId] |
| bsrCategory | array | Subcategory rank list, each entry containing nodeId (node ID), name (category name), rank (rank), date (date, format yyyyMMdd) |
| availableDate | string | Optional listing/first-available date (yyyy-MM-dd); may be absent or empty; not a verified launch date |
| onlineDays | integer | Days since listing |
| rating | number | Current rating (0.0-5.0, e.g. 4.70) |
| ratings | integer | Number of ratings |
| fiveStarRatings | number | 5-star percentage, e.g. 57.7 means 57.7% |
| fourStarRatings | number | 4-star percentage |
| threeStarRatings | number | 3-star percentage |
| twoStarRatings | number | 2-star percentage |
| oneStarRatings | number | 1-star percentage |
| buyboxSeller | string | Buybox seller name |
| buyBoxSellerId | string | Buybox seller ID |
| buyboxSellerAddress | string | Seller location, Buybox seller nationality (two-letter code e.g. CN, US), null if Amazon's own |
| isFBA | boolean | Whether FBA, whether Buybox seller uses FBA logistics |
| sellerNum | integer | Number of sellers |
| aPlus | boolean | Has A+ |
| hasVideo | boolean | Has video |
| hasBrandStore | boolean | Has brand store |
| feature | object | Product feature ratings, features and star ratings collected by Amazon for this product, e.g. {"Battery life":4.0} |
| productInfo | object | Product information, structured data from the Product Information section in the Listing |
| property | object | Attribute list, including variant attributes and Bullet Points header descriptions |
| brandPromotion | string | Brand promotion |
| dealType | string | Deal label |
| extraSavings | array | Associated promotions, e.g. [{Asin:xxx, Text:"Save 5%..."}] |
| rankTrend | array | BSR trend, main category rank change history, interleaved format [date, rank, ...] |
| bsrRankTrend | array | Subcategory rank trend, JSON format [{NodeId:xxx, Rank:[date, rank, ...]}] |
| listingSalesVolumeOfDailyTrend | array | Daily sales volume trend, value -1 means unable to estimate |
| listingSalesOfDailyTrend | array | Daily sales revenue trend, in local currency smallest unit (e.g. cents), value -1 means unable to estimate |
| listingSalesVolumeOfMonthTrend | array | Monthly sales volume trend (last 30 days), value -1 means unable to estimate |
| listingSalesOfMonthTrend | array | Monthly sales revenue trend, in local currency smallest unit (e.g. cents) |
| priceTrend | array | Selling price trend, before coupon, in local currency smallest unit, -1 means no price available for that day |
| listPriceTrend | array | Original price trend (strikethrough price history), in local currency smallest unit, -1 means no price available for that day |
| dealTrend | array | Deal trend, value 1 = has deal, 0 = no deal |

## 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 the **## Resolving Authentication and Credits Issues** section in SKILL.md. |
| Insufficient balance | HTTP 402: follow the **## Resolving Authentication and Credits Issues** section in SKILL.md. |

## curl Example

```bash
curl -X POST ${NEXSCOPE_PROXY_BASE}/api/v1/tools/research/sorftime/amazon/productDetail \
  -H "Authorization: Bearer ${NEXSCOPE_API_KEY}" \
  -H "Content-Type: application/json" \
  -d '{"asin": "B00FLYWNYQ", "marketplace": "us"}'
```

```bash
curl -X POST ${NEXSCOPE_PROXY_BASE}/api/v1/tools/research/sorftime/amazon/productDetail \
  -H "Authorization: Bearer ${NEXSCOPE_API_KEY}" \
  -H "Content-Type: application/json" \
  -d '{"asin": "B00FLYWNYQ", "marketplace": "us", "includeTrend": 1, "queryTrendStartDate": "2025-01-01", "queryTrendEndDate": "2025-03-01"}'
```

---

## 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.
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: 472kUpdated Claude CodeCodexVerifiedInstall
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: 323kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 323kUpdated Claude CodeCodexVerifiedInstall
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 availableStars: 323kUpdated Claude CodeCodexVerifiedInstall