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 for the authoritative source-derived request and response contract.
Operations
| 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>.
- 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.
- 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
- Identify the exact operation, market/account context, filters, dates, pagination, and requested output.
- Validate required fields, types, enums, ranges, and operation-specific limits against
references/api.md before any request.
- Explain that additional pages, markets, or operations may consume more credits and obtain approval before a paid call.
- 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.
- Preserve the full response under
nexscope/<date>/<session>/data; return a concise summary and the saved path.
- 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.
- 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 to top up credits.
1---2name: ecommerce-geekbi-temu-market-research3description: Analyze public Temu category opportunities and keyword demand through GeekBI and NexScope.4---56# GeekBI Temu Market Research78## Scope910Category opportunity discovery, keyword-demand research, site lookup, category trees, filters, and daily, weekly, or monthly trends.1112Public-market research only. It does not access a Temu seller account or perform product, order, advertising, or fulfillment mutations.1314Read [references/api.md](references/api.md) for the authoritative source-derived request and response contract.1516## Operations1718| Script | NexScope route |19|---|---|20| `geekbi_temu_category_list.py` | `POST /api/v1/tools/research/geekbi/temu/categoryList` |21| `geekbi_temu_category_search.py` | `POST /api/v1/tools/research/geekbi/temu/categorySearch` |22| `geekbi_temu_keyword_search.py` | `POST /api/v1/tools/research/geekbi/temu/keywordSearch` |23| `geekbi_temu_site_list.py` | `POST /api/v1/tools/research/geekbi/temu/siteList` |2425## Authentication and safety2627- Set `NEXSCOPE_PROXY_BASE` and `NEXSCOPE_API_KEY`. Send the NexScope key as `Authorization: Bearer <key>`.28- No marketplace account authorization is required; these operations read public-market data.29- Provider credentials and upstream tokens remain backend-owned. Never accept, print, or persist them.30- Treat HTTP 401 as NexScope authentication failure and HTTP 402 as insufficient NexScope credits.31- Do not substitute another account, market, region, creator, product, or operation after an authorization or ambiguous network failure.32- This operation consumes credits. Preserve `X-Cost-Token` and `X-Cost-Credit` from response headers as server-reported billing metadata.3334## Workflow35361. Identify the exact operation, market/account context, filters, dates, pagination, and requested output.372. Validate required fields, types, enums, ranges, and operation-specific limits against `references/api.md` before any request.383. Explain that additional pages, markets, or operations may consume more credits and obtain approval before a paid call.394. 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.405. Preserve the full response under `nexscope/<date>/<session>/data`; return a concise summary and the saved path.416. On an ambiguous timeout or upstream failure, do not retry automatically. Report the trace ID and reconcile state first.4243## Output rules4445- Distinguish the NexScope transport envelope from the nested business response.46- Report only returned facts. Preserve absent values as unknown and keep provider-specific metric definitions intact.47- Never expose API keys, provider tokens, presigned URL query strings, internal account records, or raw secrets.48- Do not submit feedback or make any unrelated external mutation unless the user explicitly requests it.495051## Authentication5253Set 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.
nexscope-ai