Skip to content

nexscope-ai/nexscope-ecommerce-skills / ecommerce-walmart-search

ecommerce.walmart-search

Verified

Search and browse Walmart product listings by keyword, category, price range, and other conditions. Trigger when users mention Walmart product search, Walmart product listing, Walmart price comparison, Walmart competitor analysis, Walmart product research, Walmart market data, find products on Walmart, Walmart search, Walmart products, Walmart product selection, Walmart pricing, Walmart competitors, Walmart market. Even if the user does not explicitly mention "Walmart search", trigger this skill whenever their need involves searching for products on Walmart, checking product availability, comparing Walmart prices, or analyzing Walmart product listings.

FileKindSize
SKILL.mdskill md8.4 KB
manifest.jsonconfig199 B
references/api.mdmarkdown6.7 KB
scripts/walmart_search.pyscript6.5 KB

references/api.md

View on GitHub
# Walmart Frontend Product List API Reference

## API Specification

- **Endpoint**: `${NEXSCOPE_PROXY_BASE}/api/v1/tools/research/walmart/search`
- **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 |
|------|------|------|------|
| keyword | string | No* | Search keyword, max length 1024 characters. *At least one of keyword and categoryId must be provided |
| categoryId | string | No* | Category ID. *At least one of keyword and categoryId must be provided. `0` means all departments. For example: `976759_976787` means "Cookies" |
| sort | string | No | Sort method. Options: `price_low` (price low to high), `price_high` (price high to low), `best_seller` (best seller), `best_match` (best match) |
| page | integer | No | Page number for pagination, default 1, max 100 |
| minPrice | number | No | Minimum price |
| maxPrice | number | No | Maximum price |
| spelling | boolean | No | Enable spelling correction, default `true`. `true` includes spelling correction, `false` excludes it |
| softSort | boolean | No | Sort by relevance, default `true`. Set to `false` to disable relevance sorting |
| storeId | string | No | Store ID, used to filter products by a specific store |
| device | string | No | Device type, default `desktop`. Options: `desktop`, `tablet`, `mobile` |
| facet | string | No | Filter conditions, format as key:value pairs separated by `\|\|` |
| nextDayEnabled | boolean | No | Only show NextDay delivery results, default `false`. `true` to enable, `false` to disable |
| jsonRestrictor | string | No | JSON field restrictor |


## 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 | Record count |
| products | array | Product list (see product object below) |
| columns | array | Rendered columns |
| type | string | Render style |
| costToken | integer | Token cost |

### Product Object

| Field | Type | Description |
|------|------|------|
| productId | string | Product ID |
| usItemId | string | US item ID |
| title | string | Title |
| description | string | Description |
| price | number | Price |
| wasPrice | number | Original price (was_price) |
| currency | string | Currency unit |
| minPrice | number | Minimum price |
| pricePerUnitAmount | string | Price per unit amount |
| pricePerUnit | string | Price per unit |
| rating | number | Rating |
| reviews | integer | Review count |
| sellerName | string | Seller name |
| sellerId | string | Seller ID |
| imageUrl | string | Thumbnail |
| productPageUrl | string | Product page URL |
| sponsored | boolean | Whether a sponsored product |
| outOfStock | boolean | Whether out of stock |
| freeShipping | boolean | Whether free shipping |
| twoDayShipping | boolean | Whether two-day shipping supported |
| freeShippingWithWalmartPlus | boolean | Free shipping for Walmart Plus members |
| shippingPrice | number | Shipping cost |
| multipleOptionsAvailable | boolean | Whether multiple options available |
| variantSwatches | array | Variant swatch list (each item contains `name` variant name, `imageUrl` variant image URL, `productPageUrl` variant product page URL, `variantFieldId` variant field ID) |
| sourceTool | string | Source tool |
| sourceType | string | Source type: walmart |

## 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/walmart/search \
  -H "Authorization: Bearer ${NEXSCOPE_API_KEY}" \
  -H "Content-Type: application/json" \
  -d '{"keyword": "wireless earbuds", "sort": "best_seller", "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.
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: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated 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: 322kUpdated Claude CodeCodexVerifiedInstall