Skip to main content
Temu merchandises through its homepage: the feed is where new arrivals, deep discounts and the products it wants to push appear first, and it changes constantly. There is no public API, and the site is built to be used in the app. Through AgentKey your agent reads that feed the same way it reads everything else — 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
Sites
  • The feed is fetched per site, so the same request can be repeated across Temu’s regional storefronts
Not covered today: keyword search, product detail by ID, reviews and shop pages for Temu. For a product you spot in the feed, search the same keyword on Amazon, AliExpress or 1688 to go deeper.

How to use it

Pass the request in plain language and let the router pick the tool:
Prices come back in the currency of the site you selected, not converted. Always 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

No. AgentKey holds the upstream access; your agent only needs your AgentKey subscription.
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.
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.