nexscope-ai/nexscope-ecommerce-skills / ecommerce-amazon-market-statistics
ecommerce.amazon-market-statistics
VerifiedUse Nexscope market statistics capability to output a market statistics dashboard by category node, including top listing average rating, average price, BSR, sales, seller count, and new product related metrics, suitable for quickly assessing the market quality and competitive landscape of a category. Trigger when the user mentions category market statistics, market selection dashboard, market fundamentals assessment, node market quality, top product statistics, Nexscope market statistics, category statistics. Even if the user does not explicitly mention "Nexscope", if the need is to view aggregated statistical results by category node, this skill should also be triggered.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 4.7 KB |
| manifest.json | config | 228 B |
| references/api.md | markdown | 7.6 KB |
| scripts/amazon_market_statistics.py | script | 6.6 KB |
references/api.md
View on GitHub# Nexscope - Market Statistics API Reference
This document aligns with the `inputSchema` / `outputSchema` of the tool `_sellersprite_market_statistics` (see `temp/tools20260430.txt`).
## API Specification
- **Endpoint**: `${NEXSCOPE_PROXY_BASE}/api/v1/tools/research/sellersprite/market/statistics`
- **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
| Parameter | Type | Required | Constraints | Description |
|------|------|------|------|------|
| marketplace | string | Yes | maxLength 1000, default `US` | Site code, see [marketplace](#marketplace-options) |
| nodeIdPath | string | Yes | maxLength 1000 | Node ID path string, e.g. `1064954:1069242:1069784:1069820:1069838:1069828` |
| month | string | No | See [month](#month) | Filter date: `nearly` or `yyyyMM` |
| topN | integer | No | Default `10` | Top Listing count (used for top-related metric definitions) |
| newProduct | integer | No | Default `6` | New product definition (months) |
### marketplace Options
| Value | Meaning |
|------|------|
| US | US marketplace USD($) |
| JP | Japan marketplace JPY(¥) |
| UK | UK marketplace GBP(£) |
| DE | Germany marketplace EUR(€) |
| FR | France marketplace EUR(€) |
| IT | Italy marketplace EUR(€) |
| ES | Spain marketplace EUR(€) |
| CA | Canada marketplace C$($) |
| IN | India marketplace INR(₹) |
### month
- **Format**: Regex `^(nearly|(19|20)\d{2}(0[1-9]|1[0-2]))$`
- **`nearly`**: Last 30 days
- **`yyyyMM`**: Specific month (e.g. `202507`); supports up to **24 months** of historical months from the current month
## 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 record count |
| marketplace | string | Site code |
| data | array | Statistics result list (corresponds to third-party `data`) |
| columns | array | Render columns |
| costToken | integer | Tokens consumed |
| type | string | Render style |
### data[] Element (Single Node Statistics)
In the tool schema, `hl*` denotes **Top N Top Listings** (where N is determined by the request parameter `topN`).
#### Node and Site
| Field | Type | Description |
|------|------|------|
| nodeIdPath | string | Node ID path |
| nodeLabelPath | string | Node name path |
| nodeLabelLocale | string | Node name translation |
| nodeLabelPathLocale | string | Node name path translation |
| marketplace | string | Market identifier |
| countryCode | string | Two-letter country code |
| currency | string | Currency type for this market |
#### Scale and Sample
| Field | Type | Description |
|------|------|------|
| totalProducts | integer | Total product count |
| products | integer | Sample product count |
| sellers | integer | Seller count |
| brands | integer | Brand count |
| avgSellers | number | Average seller count |
| hlProducts | integer | Top N Listing sample product count |
#### Overall Market Metrics
| Field | Type | Description |
|------|------|------|
| avgUnits | integer | Average monthly sales volume |
| avgRevenue | number | Average monthly sales revenue |
| avgPrice | number | Average price |
| avgRating | number | Average star rating |
| avgRatings | integer | Average review count |
| avgRatingsCv | integer | Average monthly review growth count |
| avgBsr | integer | Average BSR |
| avgProfit | number | Average profit margin |
| avgWeight | number | Average weight (pound) |
| baseAvgWeight | number | Average weight (g) |
| avgVolume | number | Average volume (in³) |
| baseAvgVolume | number | Average volume (cm³) |
#### Top Listings (Top N, N = topN)
| Field | Type | Description |
|------|------|------|
| hlAvgUnits | integer | Top N Listing average monthly sales volume |
| hlAvgRevenue | number | Top N Listing average monthly sales revenue |
| hlAvgPrice | number | Top N Listing average price |
| hlAvgRating | number | Top N Listing average star rating |
| hlAvgRatings | integer | Top N Listing average review count |
| hlAvgRatingsCv | integer | Top N Listing average monthly review growth count |
| hlAvgBsr | integer | Top N Listing average BSR |
#### New Products (definition determined by newProduct)
| Field | Type | Description |
|------|------|------|
| newProducts | integer | New product count |
| newProductProportion | number | New product share |
| newAvgUnits | integer | New product average monthly sales volume |
| newAvgRevenue | number | New product average monthly sales revenue |
| newAvgPrice | number | New product average price |
| newAvgRating | number | New product average star rating |
| newAvgRatings | integer | New product average review count |
| minNewRatings | integer | Minimum new product review count |
| maxNewRatings | integer | Maximum new product review count |
#### Listing Time
| Field | Type | Description |
|------|------|------|
| firstShelfDate | string | Product first listing date |
| lastShelfDate | string | Product latest listing date |
## curl Example
```bash
curl -X POST ${NEXSCOPE_PROXY_BASE}/api/v1/tools/research/sellersprite/market/statistics -H "Authorization: Bearer ${NEXSCOPE_API_KEY}" -H "Content-Type: application/json" -d '{
"marketplace": "US",
"nodeIdPath": "172282:281407",
"month": "nearly",
"topN": 10,
"newProduct": 6
}'
```
---
## 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 |