/vendor/jd/AgentRouting.json or
/vendor/jd/AgentContext.json directly.
jd.com
Overview
Does jd.com support MCP?
Yes. jd.com has a confirmed MCP implementation. MCP client consumer within JoyAgent-JDGenie (open-source multi-agent framework by JD.com that accepts external MCP server URLs over SSE transport for tool invocation); separately, micro-app-mcp is an MCP server published by JD's open-source team providing tool access to JD's micro-app micro-frontend framework — neither exposes JD.com's commerce/retail APIs via MCP.
What agentic protocols does jd.com support?
As of 2026-06-30, jd.com has confirmed support for MCP and proprietary.
Is jd.com's API publicly accessible or partner-gated?
Access varies by protocol: open, partner only.
Does jd.com explicitly prohibit automated access?
Yes. jd.com's terms of service explicitly prohibit automated or scraper access to the public website without prior written permission.
Is jd.com agent-ready?
Partial. jd.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 JD.com (Jingdong/京东) participates in the A2A (Agent2Agent) protocol as a launch partner, adopter, or implementer. Named launch partners at the April 2025 Google Cloud announcement include Atlassian, Box, Cohere, Intuit, Langchain, MongoDB, PayPal, Salesforce, SAP, ServiceNow, UKG, and Workday — JD.com does not appear in any list. A Medium article by a person named 'Jingdong Sun' discussing A2A is unrelated to the JD.com e-commerce platform.
No evidence found that JD.com (the Chinese e-commerce platform) has any involvement with the Agentic Commerce Protocol (OpenAI/Stripe). One search result referenced a JD.com–Mastercard partnership exploring Mastercard Agent Pay, a distinct protocol unrelated to ACP. A separate mention of 'JD Sports Fashion' deploying Stripe's Agentic Commerce Suite refers to a different UK retailer, not jd.com. Named ACP launch partners include Shopify merchants, Target, PayPal, and Meta — JD.com is not among them.
No evidence that jd.com (JD.com) appears among AP2 launch partners or adopters. Google's original announcement lists 60+ initial partners including Mastercard, Adyen, PayPal, Coinbase, and major merchants — none identified as JD.com. No JD.com-specific AP2 documentation, announcement, or integration was found. Not confirmed absent via any vendor-specific statement; absence here reflects no evidence found, not a confirmed opt-out.
MCP client consumer within JoyAgent-JDGenie (open-source multi-agent framework by JD.com that accepts external MCP server URLs over SSE transport for tool invocation); separately, micro-app-mcp is an MCP server published by JD's open-source team providing tool access to JD's micro-app micro-frontend framework — neither exposes JD.com's commerce/retail APIs via MCP
JD.com's open-source GitHub org (jd-opensource) has two distinct MCP surfaces: (1) JoyAgent-JDGenie (github.com/jd-opensource/joyagent-jdgenie) acts as an MCP client that connects to any user-supplied MCP server via SSE endpoints; (2) micro-app-mcp (listed in jd-opensource repositories) is an MCP server designed for integration with JD's micro-app micro-frontend framework. Neither surface exposes JD.com's core e-commerce or retail APIs — the retail API developer platform (JOS/Zeus) at jos.jd.com uses its own proprietary REST protocol.
No evidence that jd.com (JD.com, the Chinese e-commerce retailer) has adopted, announced, or been listed as a partner or pilot participant in the Machine Payments Protocol. Known MPP launch partners include Anthropic, OpenAI, DoorDash, Shopify, Ramp, Revolut, Nubank, Visa, Mastercard, and Cloudflare — none of the sources name JD.com. MPP was co-authored by Stripe and Tempo and launched March 18, 2026; no JD.com-specific integration announcement was found in any search result. Distinction from confirmed_absent: no JD.com-specific statement or deprecation notice exists; absence is based on non-appearance in launch partner lists, not a vendor-side rejection.
NLWeb's confirmed early adopters are Chicago Public Media, Hearst, Shopify, Tripadvisor, and Yoast — jd.com does not appear in any published launch partner list or press coverage. No evidence of jd.com implementing /ask or /mcp endpoints under the NLWeb framework was found. not_found rather than confirmed_absent because jd.com has made no vendor-specific statement deprecating or rejecting NLWeb.
No evidence found of JD.com (Jingdong, the Chinese e-commerce platform) adopting or implementing UCP. The UCP announcement names adopters including Shopify, Etsy, Wayfair, Target, Walmart, Zalando, Mastercard, and Stripe — JD.com is absent from all published lists. Note: search results frequently surface 'JD Sports Fashion' (a distinct UK/US sportswear retailer) in UCP-related coverage, but that company explicitly chose the commercetools Agentic Commerce Suite over UCP; neither company is JD.com.
No evidence found that jd.com has implemented or announced WebMCP support. WebMCP is a nascent browser-native protocol developed by Google and Microsoft under the W3C Web Machine Learning community group, with early adoption concentrated among Western developer-tooling and platform vendors (e.g., Cloudflare, Thumbtack cited in search results). Neither search surfaced any jd.com-specific WebMCP documentation, launch partnership, or implementation. Given jd.com's focus on the Chinese market and Chrome Canary's early-preview status, absence is expected rather than surprising.
No evidence that jd.com (Jingdong, the Chinese e-commerce company) has adopted or is a launch partner for the x402 protocol. JD.com does have stablecoin activity via its subsidiary JINGDONG Coinlink Technology in Hong Kong's regulatory sandbox, but this is an independently developed HKD/USD-pegged stablecoin initiative unrelated to Coinbase's x402/HTTP-402 standard. The 'JD Supra' result in searches is jdsupra.com, a legal news site, not jd.com. Known x402 launch partners include Cloudflare, per public announcements.
No evidence found of JD.com (jd.com) having an app or integration built on OpenAI's ChatGPT Apps SDK platform. OpenAI's launch partners for the Apps SDK were Booking.com, Canva, Coursera, Figma, Expedia, Spotify, and Zillow, with additional partners (AllTrails, Peloton, OpenTable, Target, theFork) announced for later availability — JD.com is absent from all lists. JD.com's AI activity has been directed toward their own proprietary ChatGPT-style product (ChatJD), not toward integration into OpenAI's platform.
Seller/merchant-facing REST API (JD Open Platform, branded 'Zeus Developer Center') covering product catalog management, order lifecycle, marketing promotions, and store management for merchants operating on JD.com. API methods follow a dot-notation naming convention (e.g. jingdong.seller.promotion.activitymode.add). Supply/logistics and cross-border seller capabilities also documented.
The JD Open Platform (jos.jd.com) is JD.com's proprietary merchant API surface, internally named 'Zeus Developer Center' (宙斯开发者中心). Platform migration notices visible on the homepage indicate ongoing consolidation of application types, suggesting active platform evolution. Documentation is primarily in Chinese and gated behind app registration; direct content fetch was not possible, but API structure and method names are confirmed via third-party SDK code (github.com/one-coder/jdsdk) and a JD.ID seller guide circulating publicly.
Direct fetch attempts to jd.com for /llms.txt, /AGENTS.md, /.well-known/agent, and /.well-known/ai-plugin.json all timed out with no response (HTTP 000), indicating the domain blocks external connections rather than returning 404s. Web searches found no evidence that JD.com (jingdong) has published any self-declaration discovery files. JD.com does have active AI/LLM research (JoyAgent-JDGenie, JoyIndustrial), but no publicly surfaced llms.txt, AGENTS.md, or well-known agent manifest. Status is not_found rather than unable_to_verify because the absence of any web-indexed evidence is itself meaningful alongside the blocked direct checks.
Summary
Has agent interface: partial
Pursue formal merchant/partner enrollment via jos.jd.com (Zeus Developer Center) to obtain app_key credentials and access token for the proprietary REST API; separately evaluate JoyAgent-JDGenie (github.com/jd-opensource/joyagent-jdgenie) as an MCP client framework if the use case involves orchestrating external MCP servers rather than accessing JD.com's own commerce data.
AgentContext
Verified discrepancies
Vendor claim: JD.com advertised '10 billion yuan subsidy' promotional programs to consumers, implying broad, straightforward price reductions during major shopping campaigns such as the 618 festival.
What actually happens: Beijing regulators found that JD.com (alongside Alibaba, Pinduoduo, Douyin, and Xiaohongshu) advertised these subsidy programs without transparent disclosure of terms and funding sources, constituting deceptive promotional pricing. The Beijing Municipal Administration for Market Regulation summoned platform executives and issued mandatory correction orders, finding the advertised discounts did not match the actual conditions consumers would encounter.
Agent guidance: When completing purchases on jd.com during promotional or subsidy campaign periods, do not treat the advertised subsidy or discount price as the confirmed final price. Before finalising any transaction, explicitly verify the full checkout total including all applicable conditions, as advertised 'subsidy' prices may carry undisclosed eligibility terms that alter the real price at checkout.
Human handoff required for
Verify the actual checkout total before confirming any purchase made during a JD.com promotional or subsidy campaign (e.g., '618' or '11.11' festivals), specifically when the displayed price references a 'billion-yuan subsidy' or similar discount program — Beijing regulators found these advertised prices carry undisclosed eligibility conditions that can produce a higher real price at checkout than the price shown on the product listing.
Five categories were checked for JD.com (jd.com): (1) Pricing discrepancies — a confirmed finding was surfaced: Beijing regulators issued correction orders against JD.com for deceptively advertised subsidy promotions without disclosed eligibility terms. (2) Availability — no evidence of ghost inventory or bait-and-switch availability was found; search results touched on counterfeit product concerns unrelated to availability at checkout. (3) Identity/merchant-of-record — no documented regulatory action or verified finding of systematic liability deflection to third-party sellers was found; search results were partially diluted by results for an unrelated UK retailer also named 'JD.' (4) Policy discrepancies — no verified gap between stated and enforced refund or cancellation policy was found; a 2024 'refund-only' policy change was noted but represents a publicly announced policy, not a hidden discrepancy. (5) Undisclosed constraints — no independently verified hidden transactional constraints for agents or foreign users were found, though JD.com's domestic payment instrument requirements are widely noted contextually without meeting the inclusion bar for a specific discrepancy finding.