find_tools, describe_tool, execute_tool — choosing
the Temu site on each call.
What you can ask
- “What is on Temu’s US homepage right now? List the first 40 products with prices.”
- “Pull the Temu homepage feed for the UK site and tell me the price range and the most common product types.”
- “Fetch Temu’s homepage feed every morning and tell me which products are new since yesterday.”
What’s covered
Homepage feed- Product cards from the Temu homepage for a selected site, with offset pagination — the products Temu is actively pushing at that moment
- Suited to product sourcing, catalog monitoring and marketplace trend analysis
- The feed is fetched per site, so the same request can be repeated across Temu’s regional storefronts
How to use it
Pass the request in plain language and let the router pick the tool:describe_tool before executing: it shows the site field and its
accepted values, the offset parameter, and the per-call cost.
Building with code? The same capability is available as a fixed-contract
Scenario Method with automatic provider
failover:
ecommerce.temu.product.rank.FAQ
Do I need a Temu account?
Do I need a Temu account?
No. AgentKey holds the upstream access; your agent only needs your AgentKey
subscription.
Can I search Temu by keyword or open a single product?
Can I search Temu by keyword or open a single product?
Not today. The Temu coverage is the homepage feed; use it to see what the
platform is pushing, then continue the research on a marketplace with
search and detail lookups.
How fresh is the feed?
How fresh is the feed?
Every call goes to Temu at request time; nothing is served from a stale
archive. The cards are what the homepage shows for that site at that
moment, so two calls minutes apart can differ.