Temu Store Query
When the Nexscope "Third-Party Data Service" MCP is available, this maps to the gateway route ehunt/temu/storeQuery (MCP display name: Temu Store Query; exact tool name follows the tool metadata deployed in the current environment). Authentication and upstream routing are handled by the gateway; if the response contains a root-level code field, success is determined by the actual network response.
Key Points
- Pagination:
pagestarts at 1;pageSizedefaults to 20, max 100. - Range parameters:
*Min/*Maxcome in pairs (total/weekly/monthly sales, total/weekly/monthly revenue, rating, reviews, followers, product count), forming upstream ranges. - Site:
siteIdis the country site ID, multiple values comma-separated (e.g.,211=United States,76=United Kingdom). - Category:
categoryis the backend category ID, multiple values comma-separated. - Managed mode:
isLocal(0=fully-managed, 1=semi-managed, string type). - Store opening time:
listedTimeBegin/listedTimeEnd(YYYY-MM-DD). - Sorting:
sortByis a "field-direction" string, e.g.,order_week_count-0(weekly sales descending, default),order_count-0,total_revenue-0,rating-0.
Script (Optional)
Command-line debugging: python scripts/temu_store_source_query.py '<JSON>' (requires NEXSCOPE_API_KEY). See the end of references/api.md.
Reference
See references/api.md for input/output parameter tables.
Authentication
Set NEXSCOPE_API_KEY. Visit https://www.nexscope.ai/help/skills-external-access?co-from=skillNS to manage credits.
API Key request rate
All Nexscope API Keys belonging to the same user share one request-rate allowance for public API execution. The allowance is measured over any rolling 1-second window. Your RPS depends on your account entitlements; do not assume every user has a fixed 1 RPS. A single Skill operation may make multiple public API requests, and each request uses this allowance.
If an execution request returns HTTP 429 with outer code 13012, the request-rate allowance was exceeded. Honor the returned Retry-After before considering another request. Outer code 13013 means the concurrent-request limit was exceeded, not the rate limit; honor its Retry-After when supplied. Inspect the response and reconcile state before retrying. Never automatically replay a write operation or a request whose outcome is unclear.
