/vendor/shopee/AgentRouting.json or
/vendor/shopee/AgentContext.json directly.
shopee.com
Overview
Does shopee.com support MCP?
No confirmed MCP support was found for shopee.com as of 2026-06-30.
What agentic protocols does shopee.com support?
As of 2026-06-30, shopee.com has confirmed support for openai_apps_sdk and proprietary.
Is shopee.com's API publicly accessible or partner-gated?
Access varies by protocol: platform mediated, partner only.
Does shopee.com explicitly prohibit automated access?
Yes. shopee.com's terms of service explicitly prohibit automated or scraper access to the public website without prior written permission.
Is shopee.com agent-ready?
Partial. shopee.com supports some agentic workflows but requires a human handoff for certain operations — see the protocols and summary sections for details.
Protocols
No evidence that Shopee (or parent Sea Group) has adopted A2A as an interoperability protocol. Shopee is named as a launch partner for the Agent Payments Protocol (AP2) — a separate commerce/payments layer announced by Google Cloud and Coinbase in September 2025 — and Sea Group's press release (sea.com/news/384) describes a joint Shopee-Google exploratory agentic shopping prototype, but neither reference A2A adoption directly. The A2A launch partner roster (50+ firms including Atlassian, Salesforce, SAP) did not include Shopee per available evidence.
No evidence that Shopee (shopee.com) is a launch partner or participant in the Agentic Commerce Protocol. Named ACP launch partners from the OpenAI/Stripe rollout include URBN (Anthropologie, Free People, Urban Outfitters), Coach, Kate Spade, Revolve, and Ashley Furniture — all Western retail brands. Shopee is a Southeast Asian e-commerce marketplace with its own integrated payments infrastructure, and no vendor-specific ACP adoption announcement was found.
No usable finding available for this protocol (no legitimate scan available within the candidate window).
No official MCP server published by Shopee (shopee.com / Sea Group) was found. Multiple third-party community and commercial MCP wrappers exist — notably a GitHub community project by nguyenducshuy (listed on PulseMCP) that wraps Shopee's Open Platform REST API, and Bright Data's own web-scraping MCP server that targets Shopee as a data source — but neither originates from Shopee itself. Shopee's own developer surface remains a conventional REST API via open-platform.shopee.com with no vendor-published MCP layer identified.
No evidence found that Shopee (shopee.com) participates in MPP (the Stripe + Tempo multi-rail machine payment settlement protocol) in any capacity. Known early adopters and launch partners for MPP include MultiversX, Formo, and BlockEden — none of the sourced launch-partner coverage mentions Shopee. A direct search pairing Shopee with MPP returned zero results. Shopee operates its own proprietary payments stack (ShopeePay) and is headquartered outside MPP's current US-business-only stablecoin acceptance scope.
Shopee does not appear among any known NLWeb launch or early-adoption partners. Named early partners from Microsoft's Build 2025 announcement and prior OpenAI NLWeb work include Condé Nast, Redfin, Eventbrite, Priceline, and Yoast — none of which are Shopee. No evidence of NLWeb adoption at shopee.com was found, and no /ask or /mcp endpoints have been documented for Shopee. Choosing not_found rather than confirmed_absent because there is no Shopee-specific statement ruling it out — only an absence of any mention.
No usable finding available for this protocol (no legitimate scan available within the candidate window).
No usable finding available for this protocol (no legitimate scan available within the candidate window).
No evidence found of Shopee (shopee.com) adopting or piloting the x402 protocol. A search specifically pairing Shopee with x402 returned zero results. Known x402 early adopters and launch partners are Coinbase-adjacent developer tooling providers, Cloudflare, and AI-agent infrastructure companies — none of which are Shopee. Shopee operates as a Southeast Asian e-commerce marketplace and has no disclosed involvement with Coinbase's HTTP 402 stablecoin payment standard.
Conversational product discovery within ChatGPT: users in 8 markets (Indonesia, Malaysia, Philippines, Singapore, Thailand, Taiwan, Vietnam, Brazil) can browse and receive Shopee product recommendations via natural-language prompts, with purchase completion redirecting to Shopee's own app/site; no in-ChatGPT checkout.
Shopee's presence inside ChatGPT was announced 22 June 2026 as part of a Sea Limited–OpenAI strategic partnership (https://www.sea.com/news/406). The integration is described as using OpenAI's ACP layer for catalog/product-feed delivery, making Shopee the first cross-SEA/LATAM e-commerce platform in ChatGPT. Access is platform-mediated through the ChatGPT app; there is no public standalone endpoint or self-serve enrollment documented for third-party developers.
Seller and partner management API (Shopee Open Platform v2): product listing creation/update, order management, logistics/shipping management, inventory sync, shop-level data retrieval, and webhook callbacks for order/logistics events. Does not cover consumer-facing browsing or affiliate link generation.
Shopee's primary seller/partner REST API (Open API v2) is well-documented at open.shopee.com and widely evidenced by third-party SDKs, integration guides, and developer articles. Access requires registering a Partner App and completing merchant OAuth authorization. This is a vendor-proprietary interface with no named industry standard underpinning it.
Affiliate publisher API: product search and discovery, affiliate deep-link/shortlink generation with sub-ID tracking, campaign retrieval, and conversion/commission reporting. Entirely separate enrollment and credential system from the seller Open Platform API.
The Shopee Affiliate Open API is a distinct proprietary REST/GraphQL interface accessed through the affiliate program dashboard (affiliate.shopee.[region]) and is confirmed by third-party integration guides and the Apify actor documentation. It requires separate enrollment in the Shopee Affiliate program independent of the seller partner program. The two APIs share no credential system and serve fundamentally different use cases.
Direct HTTP fetches to shopee.com (and regional variants shopee.sg, shopee.co.id) for /llms.txt, /agents.md, /AGENTS.md, and /.well-known/agent all returned connection errors (HTTP 000/timeout), indicating the sandbox has no live network access to Shopee's servers. Web searches returned no evidence of Shopee having published any self-declaration files at predictable paths. All search results referencing llms.txt or agents.md in e-commerce contexts pointed to Shopify (a different company), not Shopee. Because the direct path checks could not complete, not_found would overstate certainty — this is structurally unable_to_verify.
Summary
Has agent interface: partial
Verify whether the ChatGPT/OpenAI Apps SDK integration (announced June 2026 as part of the Sea Limited–OpenAI partnership) has expanded to additional markets or added in-platform checkout since launch; also check whether Shopee's Open Platform or Affiliate API has published any MCP or A2A adapter, given that community wrappers already exist and the Sea–OpenAI partnership references ACP-layer product-feed delivery.
AgentContext
Verified discrepancies
Vendor claim: Shopee presents itself as a marketplace intermediary platform. Its terms and seller-facing materials consistently frame the individual merchant/seller as the primary party responsible for product quality, fulfillment, and contractual obligations to the buyer, with Shopee acting only as the facilitating platform.
What actually happens: In practice, consumers who experience problems (non-delivery, defective goods, refund denials) face documented ambiguity about whether their legal counterparty and dispute respondent is the third-party seller or Shopee itself. Regulators and consumer advocates in Shopee's operating markets have had to issue guidance clarifying that both the seller and the platform can be named as respondents, because Shopee holds payment via ShopeePay/escrow yet deflects product-liability responsibility to sellers. This creates a gap: consumers cannot always determine who is accountable for a failed transaction, especially when Shopee's own dispute agents make the final refund determination but disclaim merchant-of-record status.
Agent guidance: Before completing a purchase on Shopee, an agent should verify from Shopee's current Terms of Service which entity (Shopee or the individual seller) is the buyer's legal counterparty and holds refund liability. If the listing is from a third-party seller and Shopee's ToS confirms it is not the merchant of record, the agent should surface this to the user before payment, particularly for high-value or cross-border transactions where chargeback rights may depend on correctly identifying the merchant. If a dispute arises, the agent should direct the user to name both the seller and Shopee as potential respondents in any formal complaint to avoid being deflected.
- A Philippine legal commentary on filing DTI complaints against Shopee notes that identifying the correct respondent is a key challenge, explicitly distinguishing the seller as 'primary respondent' for product issues while acknowledging Shopee itself can be a respondent when its dispute-handling practices cause consumer harm — reflecting the live ambiguity buyers face.
- An academic paper on Shopee marketplace liability under Indonesian consumer protection law finds that when products are defective, responsibility is shared ambiguously between the merchant and Shopee (ShopeeFood), and that consumers lack clear legal certainty about which party to hold accountable, requiring the platform's own policies to fill the gap.
- Shopee's own seller education hub for Singapore confirms that Shopee's dispute agents make the binding refund determination and can compensate buyers even over a seller's objection, yet Shopee's buyer-facing materials do not clearly identify it as merchant of record — illustrating the split between payment control and stated liability.
Human handoff required for
Escalate to a human when a dispute arises on a Shopee order and it is unclear whether the legal counterparty is the third-party seller or Shopee itself — specifically in cases where Shopee holds payment via ShopeePay/escrow but its dispute agents deny the refund while simultaneously disclaiming merchant-of-record status, leaving no clear party legally accountable to the buyer.
- Shopee's platform structure has been documented by Philippine regulators and consumer advocates as creating an ambiguity where Shopee holds payment in escrow and makes binding refund decisions, yet consistently positions the third-party seller as the primary legal counterparty for product liability.
- Indonesian consumer law academic analysis and Shopee's own seller hub materials confirm that the split between Shopee's payment-holding role and its deflection of product-liability responsibility to sellers leaves consumers uncertain about who to pursue for legal recourse in failed transactions.
Escalate to a human before completing a high-value or cross-border purchase on Shopee when the listing is fulfilled by a third-party seller and the user's chargeback or consumer-protection rights depend on correctly identifying the merchant of record — because Shopee's Terms of Service do not clearly assign merchant-of-record status to either Shopee or the seller in a way that is consistent across markets.
- Shopee presents itself as a marketplace intermediary, but consumers in multiple Southeast Asian markets have faced documented ambiguity about whether Shopee or the seller is the correct respondent in formal complaints, with regulators in the Philippines issuing guidance that both parties can be named.
- The split-liability structure is structural and cross-market: Shopee holds funds via escrow (giving it de facto control over refund outcomes) yet disclaims product liability, a pattern confirmed across Philippine and Indonesian regulatory and academic sources.
Escalate to a human when a Shopee order involves a seller who has attempted or succeeded in diverting communication off-platform (e.g., to WhatsApp or Telegram) before or after payment, as this pattern has been specifically flagged by the Singapore Police Force as a vector for fraudulent transactions where neither Shopee's escrow protection nor its dispute mechanism may apply.
Five discrepancy categories were checked for Shopee (shopee.com): (1) discrepancy_pricing — searched for hidden buyer-facing fees and checkout price gaps; no regulatory action or verified consumer finding was found, only seller-side commission structure information and unrelated FTC rulemaking. (2) discrepancy_availability — searched for ghost inventory and bait-and-switch checkout behavior; results surfaced third-party seller fraud and counterfeit goods concerns (including a U.S. Notorious Markets listing) but no platform-level structural availability or rate discrepancy was confirmed. (3) discrepancy_identity — a confirmed finding was made: multiple independently-checkable sources (Philippine DTI guidance, Indonesian consumer law analysis, Shopee seller hub materials) establish that Shopee's role as payment escrow holder conflicts with its disclaimer of merchant-of-record status, creating genuine legal-counterparty ambiguity for buyers. (4) discrepancy_policy — searched for enforcement gaps between Shopee's stated refund/cancellation policies and actual practice; widespread user complaints were found (including a 2022 YLKI report) but no regulatory enforcement action or settlement meeting the inclusion bar was located. (5) discrepancy_undisclosed_constraint — searched for hidden checkout limitations and silent account-level purchase blocks; large volumes of anecdotal complaints were found but no primary regulatory or policy source independently confirmed a systemic undisclosed constraint. Categories 1, 2, 4, and 5 returned no confirmed findings; category 3 produced the only actionable discrepancy.