git:20260908.ef1f05b to git:20260914.fe7ea5b
5 added, 5 removed. Audit A to A.
---
name: ecommerce-geekbi-temu-market-research
- description: Analyze public Temu category opportunities and keyword demand through GeekBI and NexScope.
+ description: Analyze public Temu category opportunities and keyword demand through GeekBI and Nexscope.
---
# GeekBI Temu Market Research
## Scope
Category opportunity discovery, keyword-demand research, site lookup, category trees, filters, and daily, weekly, or monthly trends.
Public-market research only. It does not access a Temu seller account or perform product, order, advertising, or fulfillment mutations.
Read [references/api.md](references/api.md) for the authoritative source-derived request and response contract.
## Operations
- | Script | NexScope route |
+ | Script | Nexscope route |
|---|---|
| `geekbi_temu_category_list.py` | `POST /api/v1/tools/research/geekbi/temu/categoryList` |
| `geekbi_temu_category_search.py` | `POST /api/v1/tools/research/geekbi/temu/categorySearch` |
| `geekbi_temu_keyword_search.py` | `POST /api/v1/tools/research/geekbi/temu/keywordSearch` |
| `geekbi_temu_site_list.py` | `POST /api/v1/tools/research/geekbi/temu/siteList` |
## Authentication and safety
- - Set `NEXSCOPE_PROXY_BASE` and `NEXSCOPE_API_KEY`. Send the NexScope key as `Authorization: Bearer <key>`.
+ - Set `NEXSCOPE_PROXY_BASE` and `NEXSCOPE_API_KEY`. Send the Nexscope key as `Authorization: Bearer <key>`.
- No marketplace account authorization is required; these operations read public-market data.
- Provider credentials and upstream tokens remain backend-owned. Never accept, print, or persist them.
- - Treat HTTP 401 as NexScope authentication failure and HTTP 402 as insufficient NexScope credits.
+ - Treat HTTP 401 as Nexscope authentication failure and HTTP 402 as insufficient Nexscope credits.
- Do not substitute another account, market, region, creator, product, or operation after an authorization or ambiguous network failure.
- This operation consumes credits. Preserve `X-Cost-Token` and `X-Cost-Credit` from response headers as server-reported billing metadata.
## Workflow
1. Identify the exact operation, market/account context, filters, dates, pagination, and requested output.
2. Validate required fields, types, enums, ranges, and operation-specific limits against `references/api.md` before any request.
3. Explain that additional pages, markets, or operations may consume more credits and obtain approval before a paid call.
4. Run only the selected entry script, for example: `python scripts/geekbi_temu_category_list.py '<JSON parameters>' --no-cache` when the script supports that flag.
5. Preserve the full response under `nexscope/<date>/<session>/data`; return a concise summary and the saved path.
6. On an ambiguous timeout or upstream failure, do not retry automatically. Report the trace ID and reconcile state first.
## Output rules
- - Distinguish the NexScope transport envelope from the nested business response.
+ - Distinguish the Nexscope transport envelope from the nested business response.
- Report only returned facts. Preserve absent values as unknown and keep provider-specific metric definitions intact.
- Never expose API keys, provider tokens, presigned URL query strings, internal account records, or raw secrets.
- Do not submit feedback or make any unrelated external mutation unless the user explicitly requests it.
## Authentication
Set the `NEXSCOPE_API_KEY` environment variable. If credentials are missing or expire, visit [https://www.nexscope.ai/help/skills-external-access?co-from=skillNS](https://www.nexscope.ai/help/skills-external-access?co-from=skillNS) to top up credits.