內容簡介
SDX AI Readiness Toolkit for WooCommerce 是一款專為 WooCommerce 商店設計的外掛，能讓商店自動被 AI 購物代理發現、閱讀及購買，提升商店的可見性與銷售潛力。
【主要功能】
• 自動生成 UCP 商業檔案
• 提供 UCP 購物目錄功能
• 支援 OAuth 2.0 認證
• 兼容 WooCommerce 核心功能
• 提供 AI 準備度儀表板
• 自動生成 Google Merchant Center 產品供應
外掛標籤
開發者團隊
② 後台搜尋「SDX AI Readiness Toolkit for WooCommerce」→ 直接安裝（推薦）
原文外掛簡介
SDX AI Readiness Toolkit makes any WooCommerce store auto-discoverable, readable, and purchasable by AI shopping agents — ChatGPT plugins, Perplexity Shopping, Google’s commerce AI, custom Claude tools, and any agent that speaks the open protocols of the agentic commerce ecosystem.
Why this matters
In 2026 Google launched the Universal Commerce Protocol (UCP) with Shopify, Walmart, Target, Wayfair, and Etsy. WooCommerce was absent. This plugin closes that gap.
What this plugin does
UCP business profile at /.well-known/ucp — a spec-conformant UCP 2026-08-25 profile agents can negotiate against
UCP shopping catalog at /wp-json/agtc/v1/ucp/catalog/… — the dev.ucp.shopping.catalog.search and .lookup capabilities, served from your own products
MCP server at /wp-json/agtc/v1/mcp — JWT-authenticated tools for product listing, search, and order lookup, speaking every MCP revision from 2024-11-05 to 2026-07-28
ACP checkout at /wp-json/agtc/v1/acp/checkouts — agentic checkout sessions with Stripe payment_intent support
OAuth 2.0 server with discovery — dynamic client registration, client_credentials grant, and RFC 8414 / RFC 9728 metadata so MCP clients configure themselves
Coexistence with WooCommerce core — defers to WooCommerce’s native ACP checkout and to its canonical product/order Abilities instead of duplicating them
Web discovery — HTML tags, HTTP Link headers, robots.txt advisory, /llms.txt
Google Merchant Center feed at /merchant-feed/google.xml — a self-hosted, Google-spec product feed you register as a scheduled fetch
AI readiness dashboard — scores your store, shows what’s missing, offers one-click fixes
Production-grade engineering — 396 unit tests, integration-tested on live WordPress + WooCommerce, WordPress Coding Standards compliant, PHP 7.4+ compatible
How agents use your store
Agent fetches /.well-known/ucp and negotiates the capabilities you publish
Agent searches your catalog at /ucp/catalog/search (UCP) — no credentials needed for public product data
Agent discovers how to authenticate at /.well-known/oauth-authorization-server
Agent registers via /oauth/register → receives client ID + secret
Agent exchanges credentials for JWT at /oauth/token
Agent calls MCP tools under /mcp (search, list, order lookup)
Agent creates an ACP checkout session at /acp/checkouts
Agent completes the session → real WooCommerce order in your admin
All standard payment gateways work. UCP creates standard WC orders.
How this actually helps your store
AI shopping assistants — ChatGPT, Perplexity, Gemini, Claude — 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 on the domains it knows, reads which capabilities the store supports, and calls those endpoints. A store with no profile — or with a profile the platform cannot parse — simply is not part of that conversation.
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.
A few complementary moves we recommend alongside this plugin: register your products in Google Merchant Center 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.
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 — with ACP enabled — 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.
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 — so the practical path for most stores is discovery and catalog access first, agent-initiated orders second.
Google Merchant Center
The plugin publishes a Google-spec product feed at https://yourstore.com/merchant-feed/google.xml. It is fully self-hosted — the plugin contacts no external service. Instead, you register that URL in Google Merchant Center → Products → Feeds 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.
The feed is built from your published, catalog-visible WooCommerce products and includes each product’s title, description, price, availability, image, and — when set — brand and GTIN. Filling in brand and GTIN (Products → product → Inventory → 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.
Privacy & Data Handling
This plugin is built to be conservative about data:
The plugin only exposes publicly available product data — name, price, image, description — through its UCP and MCP discovery endpoints. Anything you already display on a public product page is fair game; nothing else is.
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 scope cannot read any orders at all, and read:orders is never granted by open client registration unless it is explicitly requested.
No customer personally identifiable information (PII) is collected, transmitted to third parties, or stored beyond standard WooCommerce order records that WooCommerce itself already manages.
All admin actions — including the audit dashboard and one-click auto-fix buttons — require the manage_woocommerce capability and a verified WordPress CSRF nonce.
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.
External Services
WordPress.org guideline #6 requires that we disclose any external services this plugin contacts. The list is short:
Stripe (optional, opt-in): Stripe is only contacted when the ACP module’s payment_intent flow is explicitly enabled by defining the AGTC_STRIPE_SECRET_KEY constant in wp-config.php. 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 to authorize the payment. No data is sent to Stripe unless this flow is activated. Stripe service terms: https://stripe.com/legal — Stripe privacy policy: https://stripe.com/privacy.
No other external services are contacted by default. UCP, MCP, and ACP discovery endpoints are served from your own WordPress installation. The agent pulls data from you; you do not push data to the agent or to any intermediary.
Disclaimer
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.
