What problem does it solve? Temu Partner EU sellers need to handle buyer-initiated cancellation requests and submit seller-side cancellations (appeals or out-of-stock) through authenticated OpenAPI calls, which requires managing LinkFox gateway credentials, Temu access tokens, and per-interface request schemas. ## Core Features & Use Cases - Buyer cancellation handling: Query pending buyer cancellation after-sales requests with bg.aftersales.cancel.list.get and approve them with bg.aftersales.cancel.agree. - Seller cancellation workflows: Submit cancellation appeals (temu.order.cancel.appeal.apply), out-of-stock cancellations (temu.order.cancel.outofstock.apply), and poll their review results. - Credential management: Save, list, and retrieve Temu access tokens locally by storeKey, site, and tokenPurpose, with an authorization guide for each shop type. - Use Case: A seller lists pending buyer cancellations with afterSalesStatusGroup=8, agrees to them, then submits an out-of-stock cancellation for another order and polls the review status. ## Quick Start Set the LINKFOXAGENT_API_KEY environment variable and ask the agent to list pending Temu EU buyer cancellation requests using the eu_cancel_aftersales_cancel_list_get script with your Temu access token.