ecommerce.geekbi-temu-search-by-image

Nexscope Temu Image Search

Scope

Image-based public product discovery with product, price, sales, reviews, inventory, supply-price, store, and category fields.

Temu public-market image search only. It does not identify products on other marketplaces or mutate seller data.

Read references/api.md for the authoritative source-derived request and response contract.

Operations

Script	Nexscope route
geekbi_temu_goods_image_search.py	POST /api/v1/tools/research/geekbi/temu/goodsImageSearch
upload_image.py	POST /api/v1/tools/research/oss/file/presignedPut → signed PUT → remove URL query parameters

Response handling

For the research HTTP response, require a numeric outer code equal to 0 before using data. Nonzero codes are platform failures; display outer msg without interpreting its wording as a retry instruction. Nexscope preserves upstream messages and translates Chinese to English; successful responses may have msg: null. HTTP 200 alone and nested business code / status do not replace the platform check. See references/api.md for response paths and task-specific states.

Package scripts that unwrap the response keep the platform code and msg under _nexscope; their remaining fields are the business payload. _nexscope.cost is elapsed time, not credits.

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

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_goods_image_search.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.
• 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.

Legacy local cache: a still-valid cache created before this response contract remains usable without a new paid request. The scripts mark its copied metadata as _nexscope.responseContract = "legacy-cache", with _nexscope.code and _nexscope.msg set to null because the original platform status/message is unavailable. Do not infer platform success from business errcode, code, or status. Existing business data, billing metadata, cache contents and expiration are preserved; the marker is added only to the in-memory output.