{"id":11784,"date":"2026-08-27T16:06:07","date_gmt":"2026-08-27T08:06:07","guid":{"rendered":"https:\/\/aeosub.com\/sdx-ai-readiness-toolkit\/"},"modified":"2026-08-27T16:06:07","modified_gmt":"2026-08-27T08:06:07","slug":"sdx-ai-readiness-toolkit","status":"publish","type":"post","link":"https:\/\/aeosub.com\/zh\/sdx-ai-readiness-toolkit\/","title":{"rendered":"SDX AI Readiness Toolkit for WooCommerce"},"content":{"rendered":"
\"SDX<\/div>\n
\n
LethaldiranMX Insight<\/div>\n
\n
\n

The SDX AI Readiness Toolkit addresses a critical structural gap in the WooCommerce ecosystem by implementing emerging agentic commerce standards like the Universal Commerce Protocol (UCP) and Model Context Protocol (MCP). By exposing standardized, machine-readable endpoints and a secure OAuth 2.0 framework, it allows self-hosted WooCommerce stores to participate in the rapidly growing AI-driven search and transactional economy alongside enterprise platforms. This toolkit serves as an essential infrastructure layer for forward-looking e-commerce brands aiming to capture traffic and direct checkouts from AI agents like ChatGPT, Claude, and Perplexity Shopping. The inclusion of a dedicated readiness dashboard and robust unit testing demonstrates a production-grade approach to what is typically a highly fragmented integration space.<\/p>\n

Best Fit & Operational Role:<\/strong> This plugin is best suited for established WooCommerce merchants and enterprise-level stores that target tech-forward demographics and want to secure early-mover advantages in AI-assisted search and shopping. Operationally, it functions as an API gateway extension, sitting alongside WooCommerce core to translate standard catalog and checkout logic into agent-friendly protocols without overriding native checkout flows. It solves the critical problem of platform exclusion, ensuring that self-hosted WordPress sites are not left behind as major search engines and AI assistants transition from traditional web scraping to structured, protocol-based agentic interactions.<\/p>\n

Potential Limitations & Pitfalls:<\/strong> While the plugin is engineered to defer to WooCommerce core and boasts high test coverage, exposing OAuth 2.0 endpoints, MCP tools, and dynamic client registration introduces a sophisticated API surface area that demands rigorous security monitoring. Site administrators must ensure their hosting environment can handle the additional REST API overhead from frequent agent polling and catalog queries, particularly if caching is not optimally configured for the `\/wp-json\/agtc\/` endpoints. Additionally, because agentic commerce protocols are still rapidly evolving, maintaining alignment with future revisions of the UCP and MCP specifications will require ongoing updates and active operational oversight.<\/p>\n<\/div>\n<\/div><\/div>\n

\n
\n \"SDX <\/p>\n
\n
Plugin Specification<\/div>\n

WordPress.org Official Data<\/small>\n <\/div>\n<\/p><\/div>\n\n\n\n\n\n\n\n
Developer<\/th>\nshan<\/a><\/td>\n<\/tr>\n
Version<\/th>\nv0.4.0<\/td>\n<\/tr>\n
Active Installs<\/th>\n0 +<\/td>\n<\/tr>\n
Requires \/ Tested<\/th>\n7.0 \/ 7.1<\/td>\n<\/tr>\n
Last Updated<\/th>\n2026-08-27 8:03am GMT<\/td>\n<\/tr>\n
Official Link<\/th>\nView Details -><\/a><\/td>\n<\/tr>\n<\/table><\/div>\n
Make your WooCommerce store first-class compatible with AI shopping agents: UCP discovery, MCP tools, OAuth 2.0, ACP checkout, audit dashboard.<\/div>\n

SDX AI Readiness Toolkit<\/strong> makes any WooCommerce store auto-discoverable, readable, and purchasable by AI shopping agents \u2014 ChatGPT plugins, Perplexity Shopping, Google’s commerce AI, custom Claude tools, and any agent that speaks the open protocols of the agentic commerce ecosystem.<\/p>\n

Why this matters<\/h4>\n

In 2026 Google launched the Universal Commerce Protocol (UCP)<\/strong> with Shopify, Walmart, Target, Wayfair, and Etsy. WooCommerce was absent. This plugin closes that gap.<\/p>\n

What this plugin does<\/h4>\n
    \n
  • UCP business profile<\/strong> at \/.well-known\/ucp<\/code> \u2014 a spec-conformant UCP 2026-08-25 profile agents can negotiate against<\/li>\n
  • UCP shopping catalog<\/strong> at \/wp-json\/agtc\/v1\/ucp\/catalog\/\u2026<\/code> \u2014 the dev.ucp.shopping.catalog.search<\/code> and .lookup<\/code> capabilities, served from your own products<\/li>\n
  • MCP server<\/strong> at \/wp-json\/agtc\/v1\/mcp<\/code> \u2014 JWT-authenticated tools for product listing, search, and order lookup, speaking every MCP revision from 2024-11-05 to 2026-07-28<\/li>\n
  • ACP checkout<\/strong> at \/wp-json\/agtc\/v1\/acp\/checkouts<\/code> \u2014 agentic checkout sessions with Stripe payment_intent<\/code> support<\/li>\n
  • OAuth 2.0 server with discovery<\/strong> \u2014 dynamic client registration, client_credentials<\/code> grant, and RFC 8414 \/ RFC 9728 metadata so MCP clients configure themselves<\/li>\n
  • Coexistence with WooCommerce core<\/strong> \u2014 defers to WooCommerce’s native ACP checkout and to its canonical product\/order Abilities instead of duplicating them<\/li>\n
  • Web discovery<\/strong> \u2014 HTML <link><\/code> tags, HTTP Link headers, robots.txt<\/code> advisory, \/llms.txt<\/code><\/li>\n
  • Google Merchant Center feed<\/strong> at \/merchant-feed\/google.xml<\/code> \u2014 a self-hosted, Google-spec product feed you register as a scheduled fetch<\/li>\n
  • AI readiness dashboard<\/strong> \u2014 scores your store, shows what’s missing, offers one-click fixes<\/li>\n
  • Production-grade engineering<\/strong> \u2014 396 unit tests, integration-tested on live WordPress + WooCommerce, WordPress Coding Standards compliant, PHP 7.4+ compatible<\/li>\n<\/ul>\n

    How agents use your store<\/h4>\n
      \n
    1. Agent fetches \/.well-known\/ucp<\/code> and negotiates the capabilities you publish<\/li>\n
    2. Agent searches your catalog at \/ucp\/catalog\/search<\/code> (UCP) \u2014 no credentials needed for public product data<\/li>\n
    3. Agent discovers how to authenticate at \/.well-known\/oauth-authorization-server<\/code><\/li>\n
    4. Agent registers via \/oauth\/register<\/code> \u2192<\/span> receives client ID + secret<\/li>\n
    5. Agent exchanges credentials for JWT at \/oauth\/token<\/code><\/li>\n
    6. Agent calls MCP tools under \/mcp<\/code> (search, list, order lookup)<\/li>\n
    7. Agent creates an ACP checkout session at \/acp\/checkouts<\/code><\/li>\n
    8. Agent completes the session \u2192<\/span> real WooCommerce order in your admin<\/li>\n<\/ol>\n

      All standard payment gateways work. UCP creates standard WC orders.<\/p>\n

      How this actually helps your store<\/h4>\n

      AI shopping assistants \u2014 ChatGPT, Perplexity, Gemini, Claude \u2014 now help millions of people find products every day. When a shopper asks “find me a waterproof backpack under $80”, the assistant increasingly queries machine-readable storefronts instead of crawling pages. A UCP platform starts by fetching \/.well-known\/ucp<\/code> on the domains it knows, reads which capabilities the store supports, and calls those endpoints. A store with no profile \u2014 or with a profile the platform cannot parse \u2014 simply is not part of that conversation.<\/p>\n

      This plugin publishes a conformant profile automatically, serves the UCP catalog capabilities behind it, and exposes the same catalog through MCP. You don’t have to write a single line of integration code; activating the plugin is enough to put your store on the map for agents that speak UCP, MCP, or ACP.<\/p>\n

      A few complementary moves we recommend alongside this plugin: register your products in Google Merchant Center<\/strong> so the Google Shopping feed picks them up, keep product titles and descriptions clear and well-structured (the same SEO discipline that helps humans also helps AI parsing), and make sure your site runs on HTTPS end-to-end so agents trust the responses.<\/p>\n

      Once your store is published, agents can do three things that previously required a human: discover that you exist, browse your catalog in real time, and \u2014 with ACP enabled \u2014 create a real WooCommerce order on behalf of their user, with the same checkout, tax, shipping, and fulfillment plumbing your human customers go through today.<\/p>\n

      A note on where the money moves: ChatGPT’s Instant Checkout was retired in March 2026, and the buyer now completes payment on the merchant’s own checkout. That is exactly the “Model B” flow described in the FAQ below, and it works with whatever gateway your store already uses \u2014 so the practical path for most stores is discovery and catalog access first, agent-initiated orders second.<\/p>\n

      Google Merchant Center<\/h4>\n

      The plugin publishes a Google-spec product feed at https:\/\/yourstore.com\/merchant-feed\/google.xml<\/code>. It is fully self-hosted \u2014 the plugin contacts no external service. Instead, you register that URL in Google Merchant Center \u2192<\/span> Products \u2192<\/span> Feeds<\/strong> as a scheduled fetch, and Google pulls the feed on its own schedule. Once Google has the feed, your products become eligible for Google Shopping and Google’s shopping AI.<\/p>\n

      The feed is built from your published, catalog-visible WooCommerce products and includes each product’s title, description, price, availability, image, and \u2014 when set \u2014 brand and GTIN. Filling in brand<\/strong> and GTIN<\/strong> (Products \u2192<\/span> product \u2192<\/span> Inventory \u2192<\/span> Global Unique ID, on WooCommerce 9.2+) materially improves listing quality and how often Google can match your products. Variable products are expanded to their purchasable variations. The generated XML is cached for one hour to keep the endpoint fast.<\/p>\n

      Privacy & Data Handling<\/h4>\n

      This plugin is built to be conservative about data:<\/p>\n

        \n
      • The plugin only exposes publicly available product data \u2014 name, price, image, description \u2014 through its UCP and MCP discovery endpoints. Anything you already display on a public product page is fair game; nothing else is.<\/li>\n
      • Order data is gated behind a valid OAuth 2.0 access token AND is scoped to the agent’s own orders. An agent (OAuth client) can only read orders it created itself through the ACP checkout flow; it can never read other agents’ orders or orders placed by human customers through normal checkout. An agent without the read:orders<\/code> scope cannot read any orders at all, and read:orders<\/code> is never granted by open client registration unless it is explicitly requested.<\/li>\n
      • No customer personally identifiable information (PII) is collected, transmitted to third parties, or stored beyond standard WooCommerce order records that WooCommerce itself already manages.<\/li>\n
      • All admin actions \u2014 including the audit dashboard and one-click auto-fix buttons \u2014 require the manage_woocommerce<\/code> capability and a verified WordPress CSRF nonce.<\/li>\n
      • No outbound telemetry. No analytics calls. No external “phone home” requests. The plugin does not contact the author, an analytics vendor, or any third party at install time, on activation, or during normal operation.<\/li>\n<\/ul>\n

        External Services<\/h4>\n

        WordPress.org guideline #6 requires that we disclose any external services this plugin contacts. The list is short:<\/p>\n

          \n
        • Stripe (optional, opt-in):<\/strong> Stripe is only contacted when the ACP module’s payment_intent<\/code> flow is explicitly enabled by defining the AGTC_STRIPE_SECRET_KEY<\/code> constant in wp-config.php<\/code>. When an agent completes a checkout session under that flow, the plugin makes a server-to-server POST to https:\/\/api.stripe.com\/v1\/payment_intents<\/code> to authorize the payment. No data is sent to Stripe unless this flow is activated. Stripe service terms: https:\/\/stripe.com\/legal \u2014 Stripe privacy policy: https:\/\/stripe.com\/privacy.<\/li>\n
        • No other external services are contacted by default.<\/strong> UCP, MCP, and ACP discovery endpoints are served from your own WordPress installation. The agent pulls data from<\/em> you; you do not push data to<\/em> the agent or to any intermediary.<\/li>\n<\/ul>\n

          Disclaimer<\/h4>\n

          This plugin is an independent, community-driven implementation of open commerce protocols. It is not affiliated with, endorsed by, or sponsored by Stripe, Inc., OpenAI, Google, Anthropic, Automattic, or the WooCommerce trademark holders. “WooCommerce” is a trademark of Automattic Inc. and is referenced solely for descriptive interoperability purposes.<\/p>\n

          Editorial note: This overview combines WordPress.org official plugin metadata with an AI-assisted LethaldiranMX editorial review. Plugin data should be verified on the official WordPress.org listing before installation.<\/div>","protected":false},"excerpt":{"rendered":"

          Make your WooCommerce store first-class compatible with AI shopping agents: UCP discovery, MCP tools, OAuth 2.0, ACP checkout, audit dashboard.<\/p>","protected":false},"author":1,"featured_media":11785,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"inline_featured_image":false,"footnotes":""},"categories":[252],"tags":[3019,550,930,3020,569,555],"class_list":["post-11784","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-trends","tag-acp","tag-ai","tag-mcp","tag-ucp","tag-woocommerce","tag-wordpress-plugin"],"_links":{"self":[{"href":"https:\/\/aeosub.com\/zh\/wp-json\/wp\/v2\/posts\/11784","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/aeosub.com\/zh\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/aeosub.com\/zh\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/aeosub.com\/zh\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/aeosub.com\/zh\/wp-json\/wp\/v2\/comments?post=11784"}],"version-history":[{"count":0,"href":"https:\/\/aeosub.com\/zh\/wp-json\/wp\/v2\/posts\/11784\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/aeosub.com\/zh\/wp-json\/wp\/v2\/media\/11785"}],"wp:attachment":[{"href":"https:\/\/aeosub.com\/zh\/wp-json\/wp\/v2\/media?parent=11784"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/aeosub.com\/zh\/wp-json\/wp\/v2\/categories?post=11784"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/aeosub.com\/zh\/wp-json\/wp\/v2\/tags?post=11784"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}