Agentic Commerce for WooCommerce
| 开发者 | xpaysh |
|---|---|
| 更新时间 | 2026年6月22日 21:33 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
Your next customer is asking ChatGPT, not Google. They're shopping by typing "find me a cordless drill under $80 that ships in 2 days" into a chat box — and quietly walking away from any store the AI can't see. Right now, that's most WooCommerce stores.
Agentic Commerce for WooCommerce (by xpay) makes your store visible to ChatGPT, Claude, Gemini and Perplexity in five minutes flat — no theme changes, no replatforming, no new payment processor. Your existing checkout stays exactly as it is; xpay just makes sure you're the answer the AI gives.
📘 Full setup guide with screenshots: docs.xpay.sh/merchants/woocommerce
🌐 Plugin home: www.xpay.sh/merchants/woocommerce/
🔓 Source on GitHub: github.com/xpaysh/agentic-commerce-for-woocommerce
What it does
- Publishes a public, agent-readable product feed — your full catalog with live prices and stock, hosted on xpay's CDN (no extra load on your origin).
- Adds AI-shopping JSON-LD —
Product,Offer,AggregateOffer,BuyActionandItemListschemas on product pages, shop archive and home page. Detects existing schema from Yoast / Rank Math / WooCommerce core and only fills the gaps. - Serves the real AI shopping standards on your own domain —
/llms.txt(llmstxt.org),schema.orgProduct/Offer/BuyActionJSON-LD on every product page, and an explicitrobots.txtallowlist for AI user-agents. Optional watchlist emitters for/.well-known/oauth-protected-resource(RFC 9728, when UCP OAuth identity linking is on) and/.well-known/agent-card.json(A2A 1.0, off by default). The discovery layer is registry-based so new standards plug in cleanly. - Allows the right bots — GPTBot, ChatGPT-User, OAI-SearchBot, ClaudeBot, Claude-User, Claude-SearchBot, PerplexityBot, Perplexity-User, Google-Extended, Applebot-Extended and CCBot. Never overrides your existing robots.txt rules.
- Cart deep-link — AI agents create a one-click "Buy" link that pre-fills your existing WooCommerce cart and lands the buyer on your existing checkout. Orders are tagged with
_xpay_agent_attributionso you can attribute AI-driven revenue in your existing reporting. - Live inventory — webhook-driven catalog refresh on every product / stock change (debounced 30s), plus an hourly safety-net poll.
- It doesn't touch your checkout. Stripe / WooPayments / PayPal / Square / whatever you already use — payment runs through them, unchanged. Your payout schedule is unchanged.
- It doesn't see your customers. No buyer names, emails, addresses, IPs, payment cards, order line items, refunds, or PII of any kind passes through xpay. Ever. The plugin is non-custodial.
- It doesn't require a new account or contract to start. Free to install and get going — paid plans available as you grow. See pricing.
- It doesn't slow down your site. The JSON-LD block is tiny and cached; the catalog feed is served from xpay's CDN, not your origin.
- Install the plugin from this directory or upload the zip. (detailed walk-through)
- Activate. You'll be taken to Settings → xpay.
- Click Connect store. You're redirected to app.xpay.sh, where you grant a read-only WooCommerce REST API key. (how to generate one)
- Your catalog goes live on AI surfaces within about 10 minutes. The plugin's built-in audit-readiness checklist (what each row means) turns green as each piece confirms.
- WooCommerce 7.0+ on WordPress 6.2+ and PHP 7.4+.
- Declares compatibility with WooCommerce High-Performance Order Storage (HPOS) and Cart/Checkout Blocks.
- Works alongside Yoast SEO, Rank Math, WooCommerce Blocks, WooPayments, Stripe for WooCommerce, and the standard Storefront / Astra / Divi / Elementor themes.
- Anonymous lifecycle telemetry is off by default. On first activation a single admin notice asks once. Pick "No thanks" and the plugin never contacts our backend for analytics. Pick "Enable" and you can change your mind any time under Settings → xpay → Privacy. System-wide opt-out via
define( 'XPAY_WC_TELEMETRY', false );inwp-config.php. - Full data disclosure at install.xpay.sh/woocommerce/privacy.html — every byte the plugin sends, when it sends it, how to opt out, how to request deletion. Plain-English version: docs.xpay.sh/merchants/woocommerce/privacy-telemetry.
安装:
From the WordPress.org plugin directory
- In your WordPress admin, go to Plugins → Add New.
- Search for "Agentic Commerce for WooCommerce".
- Click Install Now, then Activate.
- You'll be redirected to Settings → xpay. Click Connect store.
- Approve the WooCommerce REST API permissions on app.xpay.sh, then you'll be redirected back to your store.
- WordPress 6.2 or higher
- WooCommerce 7.0 or higher
- PHP 7.4 or higher
- SSL (
https://) on the store domain — required for the agent discovery files to be honored by AI surfaces
屏幕截图:
常见问题:
Does this slow down my site?
No. The plugin emits a small <script type="application/ld+json"> block in <head> on product pages, shop and home (only when no other plugin has already emitted equivalent schema). The discovery files (/llms.txt, /.well-known/ucp, /.well-known/oauth-protected-resource, /.well-known/agent.json) are served through WordPress rewrite rules with no database query. The catalog feed itself is hosted on xpay's CDN, not your origin — so AI shoppers reading it never load your origin.
Does xpay see my customers' payment info?
No. Payment runs through your existing WooCommerce gateway (Stripe / WooPayments / PayPal / Square / etc.). xpay never touches your checkout, your cards, your buyer PII, or your refund flow.
What if I already have Yoast SEO / Rank Math emitting Product schema?
xpay detects the existing schema at runtime and only adds the bits it's missing — typically BuyAction on product pages and ItemList on the homepage. No duplicate schema is emitted.
What does the plugin send to xpay's servers, and when?
Two data paths:
- Catalog sync (required after Connect) — your public product fields (name, description, price, currency, stock state, image URLs, categories, SKU). No customer or order data. Used to publish your catalog at
agent-feed.xpay.sh/catalog/{your-slug}.jsonso AI shoppers can read it. - Anonymous lifecycle telemetry (opt-in, off by default) — lifecycle event names (
plugin_activated,settings_viewed,resync_error, etc.) tagged with your site URL and plugin/WP/WC/PHP versions. No customer data, no order data, no PII.
How do I uninstall cleanly?
Plugins → Deactivate → Delete. The bundled uninstall.php removes every option the plugin wrote. To also delete the catalog feed from xpay's CDN, email privacy@xpay.sh from your admin email with your merchant slug.
How do I opt out of anonymous telemetry after I already enabled it?
Settings → xpay → Privacy → Turn off. Or define XPAY_WC_TELEMETRY to false in wp-config.php for a system-wide hard disable.
My host blocks /.well-known/ — can the discovery file still work?
Yes. The plugin also serves the discovery file at https://yoursite.com/?xpay_route=acp. AI shoppers that respect the Link header find this fallback automatically. If your host is interfering, contact them — many hosts (especially those that handle ACME challenges themselves) intercept /.well-known/* before WordPress sees it.
I have multiple WooCommerce stores. Do I install xpay on each?
Yes. Each store gets its own merchant slug and its own catalog feed. Pricing applies per store.
Is the source code available?
Yes. GPLv2-or-later, public repo at github.com/xpaysh/agentic-commerce-for-woocommerce.
How much does this cost?
Free to install and get started. Paid plans are available as you scale — see www.xpay.sh/pricing/.
Does xpay work with WooCommerce Subscriptions / WooCommerce Bookings / WooCommerce Memberships?
The plugin publishes simple, variable, and grouped products in v0.1. Subscriptions, bookings, and memberships are on the roadmap — track progress in the GitHub repo.
I have a question that isn't answered here.
Email merchants@xpay.sh or open an issue at github.com/xpaysh/agentic-commerce-for-woocommerce/issues.
更新日志:
The full machine-readable changelog lives at install.xpay.sh/woocommerce/CHANGELOG.md (Keep-a-Changelog format). The summary below is the WP.org-required mirror.
0.3.7
- Maintenance and reliability polish.
- Optional agency/referral attribution: a store set up by a partner can carry that partner's referral code — captured automatically from a referral link, entered on the Connect screen, or pinned by the installer. Counts only — no product, customer or order data is shared.
- New:
/agents.mdagent skill. A dedicated, machine-readable skill served atyourstore.com/agents.mdthat tells AI shopping agents (and skill-using assistants) exactly how to connect to your store: browse the live catalog over MCP or REST, look products up, and build a cart that hands the shopper off to your existing checkout. This is purpose-written connect-and-transact instructions — not a copy of/llms.txt. Served only once your store is connected; like our other discovery files it skips quietly if you already publish your own/agents.md. - Safer
/llms.txtmerge (bug fix). When appending to an existing/llms.txt, the plugin now ignores non-text responses. Hybrid/headless storefronts and single-page themes that answer every URL with an HTML page no longer get that page pulled in as bogus "existing content" above our agent-shopping sections. - Catalog link points at your branded agent surface. The
/llms.txtcatalog link now uses your store's own agent-commerce surface instead of the shared feed host (same data, your brand). - Optional AI shopping-bot routing. Realtime AI shopping assistants can be transparently routed to your structured catalog surface for cleaner, faster product data, while search/indexing crawlers stay on your store for citations. Centrally controlled and off by default — nothing changes for your site until xpay enables it for your store; it never affects humans, logged-in users, your cart, or checkout.
- Friendlier Connect screen. The pre-connect panel now leads with what you get — your products discoverable to ChatGPT, Claude, Gemini and Perplexity, with no code and no payment change — instead of a wall of acronyms. The technical detail (llms.txt, schema.org, ACP/UCP/AP2/MCP) is still there, moved to a small footnote.
- Upfront safety promise. The Connect screen now states plainly what this update verified end-to-end: the plugin never writes files to your site, doesn't touch your theme or payments, appends to any existing
/llms.txtrather than replacing it, and fully reverts the moment you deactivate. - New transparency panel. Once connected, the General tab lists every external service the plugin contacts (
agent-feed.xpay.sh,agent-commerce.xpay.sh,app.xpay.sh) and what each receives, alongside the Terms and Privacy links. - Clearer telemetry opt-in. The anonymous-diagnostics prompt now explains the benefit to you — we can catch a silently broken AI connection (failed sync, blocked endpoint) before your products drop out of ChatGPT, Claude and Perplexity. Still off by default, still no customer or order data, still changeable any time.
- New: Run site diagnostics (Tools tab). One click loopback-checks the three things that silently block a connection at the web-server layer before WordPress even runs: the WordPress REST API (Pretty Permalinks), the plugin's own REST routes, and the
/.well-known/discovery files. Each check shows a pass/fail with the HTTP status, and a failure gives you the exact fix — e.g. switch Permalinks off "Plain", or (on Apache/ACME hosts that reserve/.well-known/) the query-arg fallback URL that agents can still use. - No behaviour change to the connect flow itself. Diagnostics are network-only on the explicit button click; the Settings page still makes zero outbound calls on render.
- Good neighbour with other AI/SEO plugins. If your site already publishes its own
llms.txt(for example via Yoast SEO AI, RankMath AI, AIOSEO, or your own setup), we now add our agent-shopping sections at the end of your file instead of replacing it. Everything you wrote is preserved exactly as you wrote it. - Automatic detection. The plugin checks once a day whether another tool has started publishing one of the same discovery files we do. When it sees one, we step aside or append cleanly — no merchant action needed.
- Smoother connect experience. A handful of polish items in the Connect flow so the handshake is quicker and any stray retry doesn't show up as a misleading error.
- Live updates from xpay. Once you're connected, xpay can fine-tune small parts of your discovery setup (like an extra section of seasonal promotions on your
llms.txt) without you needing to install another plugin update. Fully optional and reversible — nothing changes unless you tell us to or we both agree.
- REST endpoints constructed via
rest_url(). The fallback UCP manifest now callsrest_url('xpay/ucp/v1')/rest_url('xpay/mcp')instead of hardcodinghome_url('/wp-json/...'), so the plugin respects sites that customize the REST prefix. Per the WP.org Determining Locations guideline. - Tested against WordPress 7.0 + WooCommerce 10.8.1 on a clean sandbox with
WP_DEBUG=true.
- Privacy: no outbound calls on Settings page load. The Connect panel no longer pre-registers a nonce with the xpay backend when the page renders. The nonce is generated, the attempt is stamped, and the merchant is redirected to the xpay onboarding flow only after the Connect store button is clicked. Matches WordPress.org's no-phoning-home guideline.
Requires Plugins: woocommerceheader. Declares the WooCommerce dependency via the WP 6.5 plugin-dependencies mechanism so the plugin won't activate without WooCommerce present. Existing manual activation check remains as defence-in-depth for pre-6.5 sites.- Inline admin script removed. The Connect button no longer emits an inline
<script>tag; click-time telemetry is recorded server-side in the redirect handler instead.
- Tabbed Settings → xpay UI. Five tabs replace the single-screen layout: General (status + slug + last sync + disconnect + telemetry opt-in), Capabilities (per-UCP-capability toggles), Payments (map enabled WC gateways to UCP
payment_handlers[]), Links (auto-detect privacy/TOS/about/contact/shipping with per-row override), Tools (view UCP profile, view full audit, test connection, refresh catalog now, telemetry debug log toggle). URL is bookmarkable via?tab=. - Capability toggles wired into
/.well-known/ucp. Switching off any ofcheckout/fulfillment/discount/orderremoves the entry from the emitted UCP manifest. Default (no option set) = all enabled, so existing installs don't regress on upgrade. payment_handlers[]now populated from the Payments tab. Each enabled gateway emits as{id, label, type:"merchant_gateway"}so UCP-aware agents can negotiate payment surfaces against the methods you actually accept.ucp.linksarray. Privacy, TOS, About, Contact, Shipping URLs are auto-detected (WordPress privacy_policy_url + common page slugs) and overridable on the Links tab; emitted in the manifest as{rel, href}pairs.
- MCP transport advertised in
/.well-known/ucp. Native MCP-speaking agents (Claude, ChatGPT Operator, Shopify AI Toolkit) discover the endpoint atagent-commerce.xpay.sh/mcp/{slug}without further configuration. Three tools available:search_catalog(BM25-ranked over title + description),get_product(lookup by SKU or numeric product ID),create_cart(returns a signed deeplink that pre-populates checkout on your store). - One-click connect via WooCommerce's
/wc-auth/v1/authorizeOAuth. When you click Connect store, the xpay onboarding page opens WooCommerce's built-in approval popup. You approve there once and WordPress hands xpay read-only API credentials directly — no Settings → Advanced → REST API trip, no copy-paste. The manual paste flow remains available as a fallback. - Disconnect notifies the backend. Clicking Disconnect now fires a non-blocking
DELETE /v1/merchants/{slug}so your account is marked disconnected and the cached agent-feed catalog is archived. Local cleanup happens regardless of whether the backend acks. - UCP manifest fixes for strict-validator compliance:
extendsis now an array (["dev.ucp.shopping.checkout"]) rather than a string per the 2026-04-08 spec; capabilityspecURLs are uniformly date-prefixed;payment_handlers: []placeholder added for parity with the ecosystem. - Clear apology + guidance when a Connect attempt fails. If you start a Connect flow but the handshake doesn't complete, the Settings → xpay page now shows an explicit apology and a clear "click Connect again" CTA, and our ops team is notified automatically so we can recover if anything weird happens.
- Fixed onboarding-finalize 500/timeout that left merchants in a half-provisioned state. The Lambda now has a 15-second timeout and an 8s
AbortSignalon the callback fetch into your WordPress site. The nonce is no longer burned until the plugin acknowledges receipt, so a re-click is always safe within the 30-minute TTL. The plugin-siderest_finalizeis now idempotent on(slug, api_key)replay. Initial catalog resync moved towp_schedule_single_event+ non-blockingwp_remote_postso the REST response returns in under a second on hosts whose outbound HTTPS to xpay is slow.
/llms.txt## Commerce protocolssection is now gated on thexpay_wc_protocol_endpointswp_option (backend-pushed during Connect). Agents that follow a URL from/llms.txtreach a working service or a structured 501 — never a bare 404.- Companion: backend stubs at
agent-commerce.xpay.sh/{ucp,acp,ap2,mcp}/...now return a 501 Not Implemented envelope withprotocol,spec,merchant_slug,status,retry_after_seconds, and adocslink. - Filter
xpay_wc_protocol_endpointslets a mu-plugin override.
- Aligned with the open commerce standards. Per-protocol surfaces (ACP, UCP, AP2, MCP) are now advertised in
/llms.txtand hosted on xpay infrastructure. The plugin keeps the merchant's domain to what genuinely belongs there: discovery files, JSON-LD, robots.txt allowlist. - NEW:
/.well-known/ucp(UCP business profile, spec 2026-04-08). This is the file Google, Shopify, Etsy, Wayfair, Target and Walmart fetch to negotiate capabilities with your store. The plugin generates a sensible default profile pointing at xpay-hosted UCP service endpoints; commercial-tier merchants can override the body + inject JWK signing keys via thexpay_wc_ucp_profileandxpay_wc_ucp_signing_keysoptions. - Discovery layer is an extensible emitter registry. Each standard (
/llms.txt,/.well-known/ucp, RFC 9728 OAuth metadata, A2A agent-card) is a registered emitter with a default-on/default-off flag and per-merchant override. Adding a new standard means adding a new emitter — no changes elsewhere in the plugin. - Added watchlist emitters (off by default):
/.well-known/oauth-protected-resource(RFC 9728) — turns on automatically when UCP OAuth Identity Linking is enabled for the merchant on the xpay side./.well-known/agent-card.json(A2A 1.0, IANA-registered 2025-08-01) — opt-in via thexpay_wc_emit_agent_cardoption once A2A adoption matures in commerce./llms.txtcontent refresh. Now links the agent-readable catalog, the per-protocol endpoints (ACP / UCP / AP2 / MCP), the cart-deeplink template, and top product categories. Markdown structure follows the llmstxt.org convention.- Admin readiness checklist updated to reflect the standards-based architecture — the "AI assistants know where to send a buyer" row now points at the per-protocol endpoints listed in
/llms.txt, not at a single discovery file. - No breaking changes for merchants. Cart deeplink, catalog feed, JSON-LD injection, robots.txt allowlist, telemetry pipe and the WC REST onboarding flow are unchanged. The audit-readiness pills continue to all turn green after Connect.
- Plugin renamed to "Agentic Commerce for WooCommerce" (slug
agentic-commerce-for-woocommerce). - Why: the previous name "xpay for WooCommerce" was rejected at WordPress.org submission as too similar to Nexi XPay (an established Italian payment-gateway plugin for WC by Nexi Payments, ~6,000 installs since 2017). WordPress.org's similarity check matches on the brand string regardless of category, and Nexi has prior art.
- What changed: Plugin Name header, Text Domain (
agentic-commerce-for-woocommerce), main file name (agentic-commerce-for-woocommerce.php),/languages/agentic-commerce-for-woocommerce.pot, admin page slug, plugin folder name inside the zip. User-Agent header for outbound HTTP. Settings page H1. - What didn't change: the product, the architecture, the xpay brand identity (still the author + still in admin nav as "xpay"), backend services (
agent-feed.xpay.sh,agent-commerce.xpay.sh, etc.), or anything else functional.
- Cleared 4 PCP
PrefixAllGlobalswarnings: uninstall.phpnow runs in an anonymous-closure IIFE — no top-level$option_keys/$keyglobals.class-xpay-schema.php :: render_product()uses a local$xpay_productand skips theglobal $productdeclaration entirely. Directwc_get_product(get_the_ID())works on PDPs without WC's template-loop side effect.class-xpay-plugin.php :: woocommerce_active()uses rawget_option('active_plugins')+ multisite merge +class_exists('WooCommerce')instead of filtering WP core'sactive_pluginshook. Same behavior, no false-positive.
- Tested up to WordPress 6.9 (PCP flagged 6.7 as below current). No code changes — verified compatibility on a real WC 9.x install.
- Short description trimmed to 141 chars (PCP cap is 150).
- Removed
load_plugin_textdomain()call. Discouraged since WP 4.6 — WordPress.org-hosted plugins get translations loaded automatically by core via the plugin slug. - Excluded non-canonical markdown files (
INSTAWP_TEST_WALKTHROUGH.md,README.md) from the release zip. The plugin zip should only contain files needed at runtime; READMEs and walkthroughs are repo-only.
- Documentation URLs migrated
docs.xpay.sh/products/woocommerce/*→docs.xpay.sh/merchants/woocommerce/*. Merchants is the bucket; WooCommerce is one (of many future) integrations inside it. Future Shopify / BigCommerce docs will live as siblings. - No plugin functionality changed — readme + admin-UI links updated.
- Punchier Description hero — leads with the buyer-side framing ("Your next customer is asking ChatGPT, not Google") instead of an abstract claim.
- Pricing link updated everywhere to
https://www.xpay.sh/pricing/?tab=agentic-commerce. - New documentation site at docs.xpay.sh/merchants/woocommerce — multi-page walkthrough covering install, WC REST API key generation, connect flow, privacy & telemetry, audit readiness checklist, and a troubleshooting guide. readme backlinks the docs at the right moments.
- GitHub backlinks throughout the readme + FAQ (issue tracker, source browse).
xpaysh/xpay-for-woocommerceGitHub repo flipped public. Restored repo link references in readme.txt FAQ and "Source code" section so reviewers and merchants can browse the unminified source directly. GPLv2-or-later unchanged.
- Removed GitHub repo link references from readme.txt to avoid a broken-link impression for reviewers (the source repo was private). Plugin is still GPLv2-or-later — the zip is the canonical, unminified source.
- Query-arg fallback for the discovery file: hosts that intercept
/.well-known/(some shared hosts, CDN edges, ACME setups) can now serve the discovery file at/?xpay_route=acp. Discoverable via theLinkheader on the home page. - Post-activation redirect to Settings → xpay now fires on any activation when the store hasn't connected yet, not only on the very first activation. Skipped on bulk-activate.
- WC HPOS + Cart/Checkout Blocks compatibility declared.
- First-activation redirect to Settings → xpay.
- Privacy + Terms pages at install.xpay.sh/woocommerce/{privacy,terms}.html.
- Plugin URI: xpay.sh/sellers/woocommerce → www.xpay.sh/merchants/woocommerce/.
- PHPCS WordPress-standard clean: 0 errors / 1 cosmetic warning.
phpcs.xml.distruleset added.languages/xpay-for-woocommerce.potgenerated.- WP.org listing assets (banner / icon / 5 screenshots).
- Slug renamed
xpay-woocommerce→xpay-for-woocommerce(Guideline 17). - Telemetry now opt-in via first-activation admin notice; default OFF (Guideline 7).
- Settings → xpay → Privacy toggle.
- readme.txt External services and Privacy sections added.
- Fire-and-forget lifecycle telemetry pipe (was always-opt-out; reworked to opt-in in 0.1.2).
- Initial release. WP plugin scaffold; /llms.txt and /.well-known/agentic-commerce.json; JSON-LD on PDP / shop / home; robots.txt allowlist; cart-deeplink handler; webhook-driven resync; admin page with connect flow and audit-readiness checklist.