Skip to content

nexscope-ai/nexscope-ecommerce-skills / ecommerce-walmart-product-detail

ecommerce.walmart-product-detail

Verified

Query Walmart product details via Nexscope, including pricing history and sales trends. Trigger when users mention Walmart product detail, Walmart product data, Nexscope, Walmart price trends, Walmart sales trends, Walmart product detail, Walmart price history, Walmart sales trend, Nexscope product. Even if the user does not explicitly mention "Nexscope", trigger this skill whenever their need involves viewing detailed information, historical price changes, or sales trends for a single Walmart product.

FileKindSize
SKILL.mdskill md6.2 KB
manifest.jsonconfig224 B
references/api.mdmarkdown7.6 KB
scripts/walmart_product_detail.pyscript6.6 KB

references/api.md

View on GitHub
# Nexscope Product Detail API Reference

## API Specification

- **Endpoint**: `${NEXSCOPE_PROXY_BASE}/api/v1/tools/research/wallysmarter/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 Credit Issues** section in SKILL.md)

## Request Parameters

POST Body (JSON):

| Parameter | Type | Required | Description |
|------|------|------|------|
| productId | integer | Yes | Product ID (ItemId), the numeric ID contained in the product detail link. For example: the `5169493923` in `https://www.walmart.com/ip/5169493923` |
| includeStats | boolean | No | Whether to include historical price/historical sales, default `true` |

## 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 | Number of products returned (typically 1 for this endpoint) |
| products | array | Product list (see product object below) |
| columns | array | Column definitions (metadata describing each field in products, including field, title, cellType, etc.) |
| type | string | Response render type (fixed value `"productWorkbenches"`) |
| costTime | integer | API elapsed time (milliseconds) |
| costToken | integer | Token cost |

### Product Object

| Field | Type | Description |
|------|------|------|
| usItemId | integer | Internal product ID (same as the requested productId) |
| productId | string | Walmart product unique identifier (alphanumeric, e.g., `"6YBM50F6ZXAE"`) |
| title | string | Product name |
| description | string | Product description |
| price | number | Current selling price (USD) |
| wasPrice | number | Striketrough price (USD), may be null when no discount |
| minPrice | number | Minimum price (USD) |
| brand | string | Brand name |
| rating | number | Product rating (0.0-5.0) |
| reviews | integer | Review count |
| salesEstimate | integer | Sales estimate (units, in recent period) |
| revenue | number | Revenue estimate (USD) |
| sellerName | string | Seller name |
| fulfillmentType | string | Fulfillment type: `"MARKETPLACE"` (third-party seller self-fulfilled) or `"WFS"` (Walmart Fulfillment Services) |
| productPageUrl | string | Product page URL |
| imageUrl | string | Product image URL (thumbnail) |
| departmentName | string | Department name (e.g., `"Cell Phones"`) |
| departmentId | integer | Department ID |
| listingScore | integer | Listing quality score |
| contentScore | integer | Content quality score |
| outOfStock | integer | Whether out of stock (`0`=in stock, `1`=out of stock) |
| sponsored | integer | Whether a sponsored product (`0`=no, `1`=yes) |
| isBranded | integer | Whether a branded product (`0`=no, `1`=yes) |
| multipleOptionsAvailable | integer | Whether there are variants (`0`=no, `1`=yes) |
| createdAt | string | First indexed time by Nexscope (format: `yyyy-MM-dd'T'HH:mm:ss.SSSSSS'Z'`) |
| updatedAt | string | Most recent data update time (same format as above) |
| stats | object/null | Historical statistics (only returned when `includeStats=true`, otherwise null. See structure below) |
| sourceTool | string | Source tool identifier |
| sourceType | string | Product source platform (fixed value `"walmart"`) |

### stats Object Structure

Returned when `includeStats=true` (default), aggregated by day and sorted by time ascending, timezone UTC. Contains two time series arrays:

| Field | Type | Description |
|------|------|------|
| stats.price | array | Historical selling price time series (sorted by date ascending). Each item is a single date-price mapping |
| stats.sales | array | Historical sales time series (sorted by date ascending). Each item is a single date-sales mapping |

**Array element structure:**

Each element is an object containing exactly one key-value pair. The key is a date string (format `yyyy-MM-dd`, UTC), and the value is the numeric amount for that day (price: in USD; sales: in units).

**Sample excerpt:**

```json
{
  "stats": {
    "price": [
      {"2025-08-18": 279.94},
      {"2025-09-29": 279.94}
    ],
    "sales": [
      {"2025-08-18": 62},
      {"2025-09-29": 79}
    ]
  }
}
```

> Data is aggregated by day (UTC timezone), sorted in ascending time order, covering the full history since the product was first indexed by Nexscope. When consuming, iterate the arrays and take each object's unique key as the date and its unique value as the numeric amount.

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

## curl Example

```bash
curl -X POST ${NEXSCOPE_PROXY_BASE}/api/v1/tools/research/wallysmarter/productDetail \
  -H "Authorization: Bearer ${NEXSCOPE_API_KEY}" \
  -H "Content-Type: application/json" \
  -d '{"productId": 5177343351, "includeStats": true}'
```

---

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