Skip to content

nexscope-ai/nexscope-ecommerce-skills / ecommerce-temu-store-source-query

ecommerce.temu-store-source-query

Verified

Filter Temu stores by multiple dimensions (store name/ID, country site, backend category, fully-managed/semi-managed, total/weekly/monthly sales and revenue, rating, reviews, followers, product count, store opening time, etc.). Trigger when users mention Temu store, Temu store analysis, Temu seller, Temu store ranking, Temu semi-managed store, Temu revenue, temu stores, Temu store query. Even if the user does not mention the tool name, trigger this skill whenever they are looking for stores on Temu, filtering store data, or analyzing store performance.

FileKindSize
SKILL.mdskill md3.0 KB
manifest.jsonconfig233 B
references/api.mdmarkdown7.2 KB
scripts/temu_store_source_query.pyscript6.6 KB

references/api.md

View on GitHub
# Temu Store Query API Reference

## Calling Instructions

- **Gateway Route**: `POST ehunt/temu/storeQuery` (full: `${NEXSCOPE_PROXY_BASE}Query`).
- **MCP Display Name**: Temu Store Query (the exact tool name is subject to the tool metadata distributed by the current environment).
- **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).
- **Note**: Business fields depend on the operation. Only the outer numeric platform `code: 0` indicates success; a nested business `code` does not replace it.

## Request Parameters (JSON)

| Parameter | Type | Required | Description |
|------|------|------|------|
| searchKey | string, maxLen=500 | No | Store name or ID keyword |
| siteId | string | No | Country site ID, multiple separated by commas (e.g., 211=US, 76=UK) |
| category | string | No | Backend category ID, multiple separated by commas |
| isLocal | string | No | Whether semi-managed: 0=fully managed, 1=semi-managed |
| orderTotalMin | integer, >=0 | No | Total sales range (start) |
| orderTotalMax | integer, >=0 | No | Total sales range (end) |
| orderWeekMin | integer, >=0 | No | Weekly sales range (start) |
| orderWeekMax | integer, >=0 | No | Weekly sales range (end) |
| orderMonthMin | integer, >=0 | No | Monthly sales range (start) |
| orderMonthMax | integer, >=0 | No | Monthly sales range (end) |
| totalRevenueMin | number, >=0 | No | Total revenue range (USD, start) |
| totalRevenueMax | number, >=0 | No | Total revenue range (USD, end) |
| weekRevenueMin | number, >=0 | No | Weekly revenue range (USD, start) |
| weekRevenueMax | number, >=0 | No | Weekly revenue range (USD, end) |
| monthRevenueMin | number, >=0 | No | Monthly revenue range (USD, start) |
| monthRevenueMax | number, >=0 | No | Monthly revenue range (USD, end) |
| ratingMin | number (0~5) | No | Rating range (start) |
| ratingMax | number (0~5) | No | Rating range (end) |
| reviewNumMin | integer, >=0 | No | Review count range (start) |
| reviewNumMax | integer, >=0 | No | Review count range (end) |
| followerNumMin | integer, >=0 | No | Follower count range (start) |
| followerNumMax | integer, >=0 | No | Follower count range (end) |
| productNumMin | integer, >=0 | No | Product count range (start) |
| productNumMax | integer, >=0 | No | Product count range (end) |
| listedTimeBegin | string (YYYY-MM-DD) | No | Store opening date range (start) |
| listedTimeEnd | string (YYYY-MM-DD) | No | Store opening date range (end) |
| sortBy | string | No | Sort field+direction: `order_week_count-0` (weekly sales descending, default), `order_count-0`, `total_revenue-0`, `rating-0` |
| page | integer, >=1, default 1 | No | Page number (starting from 1) |
| pageSize | integer, 1~100, default 20 | No | Items per page, max 100 |

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

| Field | Type | Description |
|------|------|------|
| total | integer | Number of records on this page |
| storeNum | integer | Total number of stores matching criteria (upstream `store_num`) |
| stores | array | Temu store list |
| columns | array | Rendered columns |
| title | string | Title (`Temu Store Query`) |
| sourceType | string | Source type: temu |
| sourceTool | string | Tool type: ehunt |
| type | string | Render style: tableListWorkbenches |

### `stores[]` Elements

| Field | Upstream Alias | Description |
|------|----------|------|
| storeId | `store_id` | Store ID |
| siteId | `site_id` | Country site ID |
| storeName | `store_name` | Store name |
| logoUrl | `logo_url` | Store logo URL |
| orderTotal | `order_total` | Total sales |
| orderWeek | `order_week` | Weekly sales |
| orderMonth | `order_month` | Monthly sales |
| totalRevenue | `total_revenue` | Total revenue |
| weekRevenue | `week_revenue` | Weekly revenue |
| monthRevenue | `month_revenue` | Monthly revenue |
| rating | - | Rating |
| listedTime | `listed_time` | Store opening time |
| reviewNum | `review_num` | Review count |
| followerNum | `follower_num` | Follower count |
| productNum | `product_num` | Product count |
| categoriesCn | `categories_cn` | Chinese category list |
| categories | - | English category list |
| isLocal | `is_local` | Whether semi-managed: 0=fully managed, 1=semi-managed |

## Script Debugging (Optional)

The repository includes **`scripts/temu_store_query.py`** (Python 3, standard library only), which POSTs JSON consistent with MCP input parameters to the Nexscope tool gateway.

- **Gateway**: `${NEXSCOPE_PROXY_BASE}/api/v1/tools/research/ehunt/temu/storeQuery` (you can use `NEXSCOPE_PROXY_BASE_BASE` to override the root URL)
- **Authentication**: Environment variable `NEXSCOPE_API_KEY` (same as other `nexscope-*` skills; if not configured, follow the **## Resolving Authentication and Credit Issues** section in SKILL.md)

```bash
export NEXSCOPE_API_KEY="<your-key>"
python scripts/temu_store_query.py '{"searchKey": "home", "siteId": "211", "page": 1, "pageSize": 20}'
```

## 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: 471kUpdated 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