[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fcfbODM_kfb3UdXBAEX-DbY2ZgIpwnDtLUZePN7HoghU":3,"$fEIkUFyy81vVXO2qjacvRaeWB4x0Rg4Ef8fWlbNkkvUk":116,"$f6TleW_AsnvyuPEdX0uMWKGWHmuiCWqa-8GJIIdTrPR0":121},{"slug":4,"name":5,"version":6,"author":7,"author_profile":8,"description":9,"short_description":10,"active_installs":11,"downloaded":12,"rating":11,"num_ratings":11,"last_updated":13,"tested_up_to":14,"requires_at_least":15,"requires_php":16,"tags":17,"homepage":23,"download_link":24,"security_score":25,"vuln_count":11,"unpatched_count":11,"last_vuln_date":26,"fetched_at":27,"discovery_status":28,"vulnerabilities":29,"developer":30,"crawl_stats":26,"alternatives":35,"analysis":26,"fingerprints":26},"ecentic-for-woocommerce","écentic for WooCommerce","1.0.0","ecentic","https:\u002F\u002Fprofiles.wordpress.org\u002Fecentic\u002F","\u003Cp>écentic for WooCommerce connects your store to the \u003Ca href=\"https:\u002F\u002Fucp.dev\" rel=\"nofollow ugc\">Universal Commerce Protocol\u003C\u002Fa> so AI shopping assistants (Google Gemini AI Mode, ChatGPT Shopping, and any UCP-compatible agent) can discover, browse, and purchase from your store — no screen-scraping, no custom integrations.\u003C\u002Fp>\n\u003Cp>The heavy UCP protocol surface — capability negotiation, catalog search, cart and checkout sessions, payment handling, idempotency, RFC 9421 request\u002Fresponse signing, and order webhooks — is served by \u003Cstrong>\u003Ca href=\"https:\u002F\u002Fecentic.ai\" rel=\"nofollow ugc\">écentic\u003C\u002Fa>\u003C\u002Fstrong> on your store’s behalf. This plugin is the store-side half:\u003C\u002Fp>\n\u003Cp>\u003Cstrong>On your domain:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ccode>\u002F.well-known\u002Fucp\u003C\u002Fcode> — the UCP discovery profile (cached proxy of your hosted profile, so agents always discover you at your own URL)\u003C\u002Fli>\n\u003Cli>\u003Ccode>\u002F.well-known\u002Foauth-authorization-server\u003C\u002Fcode> — OAuth 2.0 metadata (RFC 8414) for UCP identity linking\u003C\u002Fli>\n\u003Cli>\u003Ccode>\u002Fucp-oauth\u002Fauthorize|token|revoke\u003C\u002Fcode> — the identity-linking authorization server: your customers log in and grant consent on \u003Cem>your\u003C\u002Fem> site, never on a third party\u003C\u002Fli>\n\u003Cli>\u003Ccode>\u002Fucp-connect\u002F*\u003C\u002Fcode> — the one-click écentic connection (OAuth 2.0 + PKCE; the API secret never travels through a browser)\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>For the écentic backend (private, key-authenticated bridge):\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Live cart math — quotes run on a real WooCommerce cart, so your tax tables, shipping zones, coupons, and any third-party pricing plugins all apply\u003C\u002Fli>\n\u003Cli>Order creation through the native WooCommerce checkout internals\u003C\u002Fli>\n\u003Cli>Optional server-side payment processing via the WooCommerce Stripe Gateway (your Stripe secret key never leaves this site)\u003C\u002Fli>\n\u003Cli>Order entity snapshots, user-token introspection, and store policy (legal pages, page URLs, payment handlers, access rules)\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>Merchant controls (WooCommerce \u003Cspan aria-hidden=\"true\" class=\"wp-exclude-emoji\">→\u003C\u002Fspan> UCP (AI Agents)):\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Enable\u002Fdisable the whole UCP surface\u003C\u002Fli>\n\u003Cli>Require RFC 9421 signed requests\u003C\u002Fli>\n\u003Cli>Store-level API key (\u003Ccode>X-UCP-Key\u003C\u002Fcode>)\u003C\u002Fli>\n\u003Cli>Allow-list of agent platforms permitted to transact (identity binding)\u003C\u002Fli>\n\u003Cli>Per-agent rate limit\u003C\u002Fli>\n\u003Cli>Include\u002Fexclude out-of-stock products from the agent catalog\u003C\u002Fli>\n\u003Cli>Google Pay payment handler declaration (merchant ID + PSP gateway)\u003C\u002Fli>\n\u003Cli>Server-side Stripe charging (off by default; payment otherwise defers to your trusted checkout)\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Settings apply to the hosted endpoints immediately on save.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Also included:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Order lifecycle webhooks to agent platforms (\u003Ccode>order.created\u003C\u002Fcode>, \u003Ccode>order.updated\u003C\u002Fcode>) with Standard Webhooks headers and RFC 9421 signatures, relayed through écentic\u003C\u002Fli>\n\u003Cli>Full support for variable products, coupon codes (with per-line discount allocations), and live shipping options\u003C\u002Fli>\n\u003Cli>HPOS (custom order tables) and cart\u002Fcheckout blocks compatible\u003C\u002Fli>\n\u003Cli>Extensible: \u003Ccode>ecentic_ucp_process_instrument\u003C\u002Fcode> (custom payment processors), \u003Ccode>ecentic_ucp_payment_handlers\u003C\u002Fcode>, \u003Ccode>ecentic_ucp_identity_scopes\u003C\u002Fcode>, \u003Ccode>ecentic_ucp_stripe_secret_key\u003C\u002Fcode>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>External services\u003C\u002Fh3>\n\u003Cp>This plugin relies on the following third-party services. No data is transmitted to any of them until you explicitly connect the store (see Installation) or explicitly enable the feature described.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>écentic (ecentic.ai) — required\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>écentic is the hosted backend that serves this store’s UCP protocol surface: capability negotiation, catalog search, cart and checkout sessions, payment handling, RFC 9421 request signing, and order webhooks to AI agent platforms. The plugin is the store-side half of that service; the store cannot be served to AI agents without it.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>What is sent, and when.\u003C\u002Fstrong> Nothing is sent on installation or activation. When you click \u003Cstrong>Connect to ecentic.ai\u003C\u002Fstrong> on the settings screen, your store URL, REST API URL, and site name are sent to start the OAuth 2.0 connection. If you approve it, écentic receives a WooCommerce REST API key that you issued, and from then on it reads your product catalog and store policy (currency, shipping options, legal page URLs, payment handler declarations, and your UCP settings) as agents request them, and receives the orders that AI agents place through it (line items, totals, and the buyer’s shipping and contact details needed to fulfil the order). Your store also serves écentic’s copy of your discovery profile at \u003Ccode>\u002F.well-known\u002Fucp\u003C\u002Fcode>, refreshing it about every 5 minutes.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>What is never sent.\u003C\u002Fstrong> Payment secrets (such as your Stripe secret key), customer passwords, and the WooCommerce database itself stay on your site.\u003C\u002Fli>\n\u003Cli>Service provided by écentic: \u003Ca href=\"https:\u002F\u002Fecentic.ai\u002Fterms\" rel=\"nofollow ugc\">Terms of Service\u003C\u002Fa>, \u003Ca href=\"https:\u002F\u002Fecentic.ai\u002Fprivacy-policy\" rel=\"nofollow ugc\">Privacy Policy\u003C\u002Fa>.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>Stripe (api.stripe.com) — optional, off by default\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>Only used if you tick \u003Cstrong>Server-side Payments (Stripe)\u003C\u002Fstrong> on the settings screen \u003Cem>and\u003C\u002Fem> have the WooCommerce Stripe Gateway configured. When an AI agent completes a checkout, the plugin calls Stripe’s PaymentIntents API from your server to charge the payment method the buyer authorised, sending the payment token, the order amount and currency, and the order number. The call is made with the Stripe secret key already configured on your own site — the key never leaves your server, and no request is made to Stripe while the setting is off.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Service provided by Stripe: \u003Ca href=\"https:\u002F\u002Fstripe.com\u002Flegal\u002Fssa\" rel=\"nofollow ugc\">Terms of Service\u003C\u002Fa>, \u003Ca href=\"https:\u002F\u002Fstripe.com\u002Fprivacy\" rel=\"nofollow ugc\">Privacy Policy\u003C\u002Fa>.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>Google Pay — optional, declaration only\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>If you enter a Google Pay merchant ID in the settings, the store advertises a Google Pay payment handler in its UCP profile, referencing Google’s published handler schema URL. The plugin itself makes no request to Google and sends Google no data; any Google Pay interaction happens between the buyer’s AI agent and Google.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Service provided by Google: \u003Ca href=\"https:\u002F\u002Fpayments.developers.google.com\u002Fterms\u002Fsellertos\" rel=\"nofollow ugc\">Terms of Service\u003C\u002Fa>, \u003Ca href=\"https:\u002F\u002Fpolicies.google.com\u002Fprivacy\" rel=\"nofollow ugc\">Privacy Policy\u003C\u002Fa>.\u003C\u002Fli>\n\u003C\u002Ful>\n","Make your store discoverable and transactable by AI shopping agents via the Universal Commerce Protocol (UCP 2026-04-08), powered by écentic.",0,59,"2026-07-13T21:21:00.000Z","7.0.2","6.0","8.0",[18,19,20,21,22],"agentic-commerce","ai","ai-commerce","ucp","woocommerce","https:\u002F\u002Fecentic.ai\u002Fplatforms\u002Fwoocommerce","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fecentic-for-woocommerce.1.0.0.zip",100,null,"2026-07-22T17:31:50.256Z","no_bundle",[],{"slug":7,"display_name":7,"profile_url":8,"plugin_count":31,"total_installs":11,"avg_security_score":25,"avg_patch_time_days":32,"trust_score":33,"computed_at":34},1,30,94,"2026-08-28T19:51:34.570Z",[36,52,69,87,102],{"slug":37,"name":38,"version":39,"author":40,"author_profile":41,"description":42,"short_description":43,"active_installs":11,"downloaded":44,"rating":11,"num_ratings":11,"last_updated":45,"tested_up_to":14,"requires_at_least":15,"requires_php":46,"tags":47,"homepage":50,"download_link":51,"security_score":25,"vuln_count":11,"unpatched_count":11,"last_vuln_date":26,"fetched_at":27},"wt-ucp-enabler-for-woocommerce","WebToffee Universal Commerce Protocol Enabler for Woocommerce","1.0.1","WebToffee","https:\u002F\u002Fprofiles.wordpress.org\u002Fwebtoffee\u002F","\u003Cp>\u003Cstrong>WebToffee Universal Commerce Protocol Enabler for Woocommerce\u003C\u002Fstrong> integrates your store with the \u003Ca href=\"https:\u002F\u002Fucp.dev\" rel=\"nofollow ugc\">Universal Commerce Protocol\u003C\u002Fa> — the open standard that lets AI assistants (Google AI Mode, Gemini, ChatGPT, and others) discover, browse, and purchase from your store without custom builds for each platform.\u003C\u002Fp>\n\u003Cp>Once activated, two things happen automatically:\u003C\u002Fp>\n\u003Col>\n\u003Cli>\u003Cstrong>A discovery profile is published at \u003Ccode>\u002F.well-known\u002Fucp\u003C\u002Fcode>\u003C\u002Fstrong> — the standard entry point that AI platforms fetch to learn what your store supports.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>REST endpoints go live at \u003Ccode>\u002Fwp-json\u002Fwt-ucp\u002Fv1\u002F\u003C\u002Fcode>\u003C\u002Fstrong> — implementing the five standard UCP capabilities.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Ch4>Capabilities\u003C\u002Fh4>\n\u003Cp>\u003Cstrong>Checkout\u003C\u002Fstrong> (\u003Ccode>dev.ucp.shopping.checkout\u003C\u002Fcode>)\u003Cbr \u002F>\nCreate, update, and complete checkout sessions. An AI agent calls \u003Ccode>POST \u002Fcheckout-sessions\u003C\u002Fcode> with a list of items and buyer details, updates it with shipping info via \u003Ccode>PUT\u003C\u002Fcode>, then finalises payment via \u003Ccode>POST ...\u002Fcomplete\u003C\u002Fcode>. Sessions map directly to WooCommerce pending orders.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Cart\u003C\u002Fstrong> (\u003Ccode>dev.ucp.shopping.cart\u003C\u002Fcode>)\u003Cbr \u002F>\nSession-based basket building before a purchase is ready to commit. The agent creates a cart with \u003Ccode>POST \u002Fcarts\u003C\u002Fcode>, then optionally hands it off to the human buyer via a \u003Ccode>continue_url\u003C\u002Fcode> that loads items into the WooCommerce frontend cart and redirects to the cart page.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Order\u003C\u002Fstrong> (\u003Ccode>dev.ucp.shopping.order\u003C\u002Fcode>)\u003Cbr \u002F>\nLets agents check the status of any order using \u003Ccode>GET \u002Forders\u002F{id}\u003C\u002Fcode>, covering the full WooCommerce order lifecycle from pending to fulfilled.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Catalog\u003C\u002Fstrong> (\u003Ccode>dev.ucp.shopping.catalog\u003C\u002Fcode>)\u003Cbr \u002F>\nProduct search via \u003Ccode>GET \u002Fcatalog\u002Fsearch\u003C\u002Fcode> and individual item lookup via \u003Ccode>GET \u002Fcatalog\u002Fitems\u002F{id}\u003C\u002Fcode>. Returns prices in minor currency units as required by the spec.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Discount\u003C\u002Fstrong> (\u003Ccode>dev.ucp.shopping.discount\u003C\u002Fcode>)\u003Cbr \u002F>\nExtends the Cart and\u002For Checkout capabilities with coupon code support. An agent submits \u003Ccode>discounts.codes\u003C\u002Fcode> inside any Cart or Checkout create\u002Fupdate request. The plugin validates each code against WooCommerce coupons, applies the discount, and returns the structured \u003Ccode>discounts.applied\u003C\u002Fcode> array alongside updated line-item and order-level totals. Coupons applied automatically by WooCommerce hooks are surfaced as \u003Ccode>automatic: true\u003C\u002Fcode> entries. Supports \u003Ccode>percent\u003C\u002Fcode>, \u003Ccode>fixed_cart\u003C\u002Fcode>, and \u003Ccode>fixed_product\u003C\u002Fcode> WooCommerce coupon types. Rejected codes are returned as typed \u003Ccode>messages\u003C\u002Fcode> entries (e.g. \u003Ccode>discount_code_expired\u003C\u002Fcode>, \u003Ccode>discount_code_combination_disallowed\u003C\u002Fcode>).\u003C\u002Fp>\n\u003Ch4>Discount Behaviour\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>\u003Cstrong>Replacement semantics\u003C\u002Fstrong> — each Cart or Checkout PUT replaces the full set of applied codes. Send an empty \u003Ccode>discounts.codes\u003C\u002Fcode> array to clear all discounts.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Cart sessions\u003C\u002Fstrong> — discounts are computed entirely in PHP against \u003Ccode>WC_Coupon\u003C\u002Fcode> without requiring a live WooCommerce cart session. Per-line \u003Ccode>items_discount\u003C\u002Fcode> totals are injected into \u003Ccode>line_items[].totals\u003C\u002Fcode> and the cart-level \u003Ccode>totals\u003C\u002Fcode> array.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Checkout sessions\u003C\u002Fstrong> — discounts are applied directly to the WooCommerce order via \u003Ccode>$order->apply_coupon()\u003C\u002Fcode>. \u003Ccode>$order->calculate_totals()\u003C\u002Fcode> is called automatically; the response reflects WooCommerce’s authoritative totals.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Total types\u003C\u002Fstrong> — line-item-level discounts appear as \u003Ccode>items_discount\u003C\u002Fcode> entries; order-level discounts appear as \u003Ccode>discount\u003C\u002Fcode> entries, matching the UCP spec distinction.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Automatic coupons\u003C\u002Fstrong> — coupons applied by a WooCommerce hook (not in the submitted codes) are returned in \u003Ccode>discounts.applied\u003C\u002Fcode> with \u003Ccode>\"automatic\": true\u003C\u002Fcode> and no \u003Ccode>code\u003C\u002Fcode> field.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>REST Endpoints\u003C\u002Fh4>\n\u003Cp>  Method\u003Cbr \u002F>\n  Path\u003Cbr \u002F>\n  Capability\u003C\u002Fp>\n\u003Cp>  GET\u003Cbr \u002F>\n  \u003Ccode>\u002Fwp-json\u002Fwt-ucp\u002Fv1\u002Fcatalog\u002Fsearch\u003C\u002Fcode>\u003Cbr \u002F>\n  Catalog\u003C\u002Fp>\n\u003Cp>  GET\u003Cbr \u002F>\n  \u003Ccode>\u002Fwp-json\u002Fwt-ucp\u002Fv1\u002Fcatalog\u002Fitems\u002F{id}\u003C\u002Fcode>\u003Cbr \u002F>\n  Catalog\u003C\u002Fp>\n\u003Cp>  POST\u003Cbr \u002F>\n  \u003Ccode>\u002Fwp-json\u002Fwt-ucp\u002Fv1\u002Fcarts\u003C\u002Fcode>\u003Cbr \u002F>\n  Cart\u003C\u002Fp>\n\u003Cp>  GET\u003Cbr \u002F>\n  \u003Ccode>\u002Fwp-json\u002Fwt-ucp\u002Fv1\u002Fcarts\u002F{id}\u003C\u002Fcode>\u003Cbr \u002F>\n  Cart\u003C\u002Fp>\n\u003Cp>  PUT\u003Cbr \u002F>\n  \u003Ccode>\u002Fwp-json\u002Fwt-ucp\u002Fv1\u002Fcarts\u002F{id}\u003C\u002Fcode>\u003Cbr \u002F>\n  Cart\u003C\u002Fp>\n\u003Cp>  POST\u003Cbr \u002F>\n  \u003Ccode>\u002Fwp-json\u002Fwt-ucp\u002Fv1\u002Fcheckout-sessions\u003C\u002Fcode>\u003Cbr \u002F>\n  Checkout\u003C\u002Fp>\n\u003Cp>  GET\u003Cbr \u002F>\n  \u003Ccode>\u002Fwp-json\u002Fwt-ucp\u002Fv1\u002Fcheckout-sessions\u002F{id}\u003C\u002Fcode>\u003Cbr \u002F>\n  Checkout\u003C\u002Fp>\n\u003Cp>  PUT\u003Cbr \u002F>\n  \u003Ccode>\u002Fwp-json\u002Fwt-ucp\u002Fv1\u002Fcheckout-sessions\u002F{id}\u003C\u002Fcode>\u003Cbr \u002F>\n  Checkout\u003C\u002Fp>\n\u003Cp>  POST\u003Cbr \u002F>\n  \u003Ccode>\u002Fwp-json\u002Fwt-ucp\u002Fv1\u002Fcheckout-sessions\u002F{id}\u002Fcomplete\u003C\u002Fcode>\u003Cbr \u002F>\n  Checkout\u003C\u002Fp>\n\u003Cp>  POST\u003Cbr \u002F>\n  \u003Ccode>\u002Fwp-json\u002Fwt-ucp\u002Fv1\u002Fcheckout-sessions\u002F{id}\u002Fcancel\u003C\u002Fcode>\u003Cbr \u002F>\n  Checkout\u003C\u002Fp>\n\u003Cp>  GET\u003Cbr \u002F>\n  \u003Ccode>\u002Fwp-json\u002Fwt-ucp\u002Fv1\u002Forders\u002F{id}\u003C\u002Fcode>\u003Cbr \u002F>\n  Order\u003C\u002Fp>\n\u003Cp>Discount codes are submitted as \u003Ccode>discounts.codes\u003C\u002Fcode> inside the Cart and Checkout create\u002Fupdate request bodies — no separate endpoint is needed.\u003C\u002Fp>\n\u003Ch4>Settings\u003C\u002Fh4>\n\u003Cp>Go to \u003Cstrong>WooCommerce \u003Cspan aria-hidden=\"true\" class=\"wp-exclude-emoji\">→\u003C\u002Fspan> UCP Enabler\u003C\u002Fstrong> to configure:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>General\u003C\u002Fstrong> — UCP protocol version, API base endpoint (for proxied setups), profile cache TTL.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Capabilities\u003C\u002Fstrong> — Toggle individual capabilities on or off using the switch controls. The Discount toggle is only effective when Cart or Checkout (or both) are also enabled.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Payment Handler\u003C\u002Fstrong> — Configure a PSP tokenizer: token retrieval URL, public key, and accepted card brands.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Payment Processing\u003C\u002Fh4>\n\u003Cp>The plugin handles the UCP protocol layer and stores the payment token in WooCommerce order meta (\u003Ccode>_ucp_payment_token\u003C\u002Fcode>). The actual charge against your PSP is delegated via a WordPress filter, giving you full control:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>php\nadd_filter( 'wbte_ucp_enabler_process_payment', function( $result, $order, $instrument, $credential ) {\n    \u002F\u002F $credential['token'] is the PSP token sent by the agent.\n    \u002F\u002F Call your payment gateway SDK here.\n    \u002F\u002F On success: return null (or call $order->payment_complete($tx_id) first).\n    \u002F\u002F On failure: return a WP_Error.\n    return null;\n}, 10, 4 );\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch4>Cart Handoff\u003C\u002Fh4>\n\u003Cp>When an agent builds a cart for a human buyer to finish, the \u003Ccode>continue_url\u003C\u002Fcode> in the cart response is a one-time link that loads all items into the WooCommerce session and redirects to the WooCommerce cart page. The token is consumed on first use. Any discounts applied to the cart are preserved in the transient and will be visible in the response on subsequent GETs.\u003C\u002Fp>\n\u003Ch4>Item ID Convention\u003C\u002Fh4>\n\u003Cp>UCP uses a single string \u003Ccode>item.id\u003C\u002Fcode> to identify products. The plugin maps:\u003Cbr \u002F>\n* \u003Ccode>\"123\"\u003C\u002Fcode> \u003Cspan aria-hidden=\"true\" class=\"wp-exclude-emoji\">→\u003C\u002Fspan> WooCommerce product ID 123\u003Cbr \u002F>\n* \u003Ccode>\"123-456\"\u003C\u002Fcode> \u003Cspan aria-hidden=\"true\" class=\"wp-exclude-emoji\">→\u003C\u002Fspan> WooCommerce product 123, variation 456\u003C\u002Fp>\n\u003Cp>The catalog endpoint returns variation IDs in \u003Ccode>\"{product_id}-{variation_id}\"\u003C\u002Fcode> format so agents can reference them directly. Override with the \u003Ccode>wbte_ucp_enabler_resolve_item_id\u003C\u002Fcode> filter for custom slug-based IDs.\u003C\u002Fp>\n\u003Ch4>Extend the Profile\u003C\u002Fh4>\n\u003Cpre>\u003Ccode>php\nadd_filter( 'wbte_ucp_enabler_profile', function( $profile, $settings ) {\n    \u002F\u002F Add signing_keys, custom extensions, etc.\n    return $profile;\n}, 10, 2 );\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch3>External services\u003C\u002Fh3>\n\u003Cp>This plugin does not send any data to WebToffee or to any third party by itself. However, its entire purpose is to let external AI shopping agents (Google AI Mode, Gemini, ChatGPT, and others that implement the Universal Commerce Protocol) call your own store’s REST API to browse your catalog and place orders — this section documents that data flow.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Universal Commerce Protocol (ucp.dev) schema references.\u003C\u002Fstrong> The \u003Ccode>\u002F.well-known\u002Fucp\u003C\u002Fcode> profile and the plugin’s REST responses embed several fixed URLs like \u003Ccode>https:\u002F\u002Fucp.dev\u002F{version}\u002Fschemas\u002Fshopping\u002Fcheckout.json\u003C\u002Fcode> and \u003Ccode>https:\u002F\u002Fucp.dev\u002F{version}\u002Fspecification\u002Foverview\u003C\u002Fcode>. These are static links to the public UCP specification\u002Fschema documentation, included so that any AI agent reading your profile knows which version of the protocol and JSON schema your store implements. Your server does not call these URLs at runtime and no store or customer data is ever sent to ucp.dev; the links are descriptive metadata only, and only the requesting agent (not this plugin) may choose to resolve them. ucp.dev is an open specification site (not a paid service) published under the Apache License 2.0.\u003Cbr \u002F>\nService: Universal Commerce Protocol specification (ucp.dev), an open standard maintained by the UCP Authors (Google, Shopify, and other industry partners) on GitHub.\u003Cbr \u002F>\nSpecification & source: https:\u002F\u002Fgithub.com\u002FUniversal-Commerce-Protocol\u002Fucp\u003Cbr \u002F>\nLicense: https:\u002F\u002Fgithub.com\u002FUniversal-Commerce-Protocol\u002Fucp\u002Fblob\u002Fmain\u002FLICENSE\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Inbound requests from AI shopping agents.\u003C\u002Fstrong> Once activated, this plugin exposes REST endpoints (catalog, cart, checkout, order) under \u003Ccode>\u002Fwp-json\u002Fwt-ucp\u002Fv1\u002F\u003C\u002Fcode>. Any AI platform or agent that supports UCP can call these endpoints directly to search your catalog, build a cart, and complete checkout — this is the plugin’s core function, not an optional integration. Catalog search\u002Flookup is open to any caller. Checkout-session and order operations beyond creation require the caller to present the session token issued at checkout creation (delivered via an \u003Ccode>X-UCP-Session-Token\u003C\u002Fcode> response header, and presented back as a standard \u003Ccode>Authorization: Bearer \u003Ctoken>\u003C\u002Fcode> header, per the UCP REST binding’s own guidance on authenticating individual operations) — so an agent can only read or modify a session it created itself. No background or scheduled data transmission occurs; every exchange is a direct response to a request initiated by the agent. Which AI platforms can reach your store depends entirely on which agents or vendors you choose to make your \u003Ccode>\u002F.well-known\u002Fucp\u003C\u002Fcode> profile known to; this plugin does not register your store with, or transmit data to, any specific AI vendor on its own.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Optional payment handler \u002F tokenizer.\u003C\u002Fstrong> If you configure a Payment Handler under Settings, card\u002Fpayment data is tokenized by the handler you choose to configure. Consult that provider’s own terms of service and privacy policy, as it is not bundled with or endorsed by this plugin.\u003C\u002Fp>\n","Make your WooCommerce store discoverable and purchasable by AI shopping agents through the Universal Commerce Protocol (UCP).",52,"2026-07-22T12:30:00.000Z","7.4",[20,48,49,21,22],"checkout","rest-api","https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fwt-ucp-enabler-for-woocommerce\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fwt-ucp-enabler-for-woocommerce.1.0.1.zip",{"slug":53,"name":54,"version":6,"author":55,"author_profile":56,"description":57,"short_description":58,"active_installs":59,"downloaded":60,"rating":25,"num_ratings":31,"last_updated":61,"tested_up_to":62,"requires_at_least":63,"requires_php":46,"tags":64,"homepage":67,"download_link":68,"security_score":25,"vuln_count":11,"unpatched_count":11,"last_vuln_date":26,"fetched_at":27},"agentic-commerce-protocol-chatgpt-product-feed-ovena-acp-for-woocommerce","Agentic Commerce Protocol & ChatGPT Product Feed for WooCommerce","ovenaai","https:\u002F\u002Fprofiles.wordpress.org\u002Fovenaai\u002F","\u003Cp>\u003Cstrong>ChatGPT Product Feed for WooCommerce\u003C\u002Fstrong> enables your store to work seamlessly with \u003Cstrong>ChatGPT\u003C\u002Fstrong>, \u003Cstrong>Claude\u003C\u002Fstrong>, and other AI assistants through the Agentic Commerce Protocol (ACP). Transform your WooCommerce shop into an AI-ready platform for next-generation conversational shopping experiences.\u003C\u002Fp>\n\u003Ch4>What is Agentic Commerce Protocol (ACP)?\u003C\u002Fh4>\n\u003Cp>Agentic Commerce Protocol is a revolutionary standard that enables AI assistants like ChatGPT to understand, browse, and interact with your e-commerce store. Transform your WooCommerce shop into an AI-ready platform for intelligent shopping experiences.\u003C\u002Fp>\n\u003Ch4>Power of AI Shopping Assistants\u003C\u002Fh4>\n\u003Cp>Your customers can now shop through natural conversations with ChatGPT and other AI assistants. The plugin automatically syncs your product catalog, enabling AI-powered product discovery, recommendations, and seamless purchasing experiences.\u003C\u002Fp>\n\u003Ch4>Key Features\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>\u003Cstrong>ChatGPT Integration\u003C\u002Fstrong>: Enable shopping through ChatGPT conversations\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Agentic Commerce Protocol\u003C\u002Fstrong>: Full ACP compliance for AI assistant compatibility\u003C\u002Fli>\n\u003Cli>\u003Cstrong>AI Assistant Support\u003C\u002Fstrong>: Works with ChatGPT, Claude, and other LLM-powered assistants\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Conversational Commerce\u003C\u002Fstrong>: Natural language shopping experiences for customers\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Automatic Product Sync\u003C\u002Fstrong>: Real-time synchronization with AI platforms every 15 minutes\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Smart Product Discovery\u003C\u002Fstrong>: AI-powered product recommendations and search\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Intelligent Catalog Management\u003C\u002Fstrong>: Automatic product data formatting for AI consumption\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Secure API Integration\u003C\u002Fstrong>: Enterprise-grade security with encrypted communication\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Performance Optimized\u003C\u002Fstrong>: Efficient batch processing for large product catalogs\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Real-time Monitoring\u003C\u002Fstrong>: Admin dashboard with sync statistics and AI activity logs\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Multi-language Support\u003C\u002Fstrong>: Available in English, Turkish, and Danish\u003C\u002Fli>\n\u003Cli>\u003Cstrong>HPOS Compatible\u003C\u002Fstrong>: Full support for WooCommerce High-Performance Order Storage\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Developer Friendly\u003C\u002Fstrong>: Clean code following WordPress and WooCommerce standards\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Perfect For\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>\u003Cstrong>AI-First Stores\u003C\u002Fstrong>: Businesses embracing conversational commerce\u003C\u002Fli>\n\u003Cli>\u003Cstrong>ChatGPT Shopping\u003C\u002Fstrong>: Enable customers to shop via ChatGPT\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Voice Commerce\u003C\u002Fstrong>: Prepare for voice-activated AI shopping\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Future-Ready E-commerce\u003C\u002Fstrong>: Stay ahead with Agentic Commerce Protocol\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Enhanced Customer Experience\u003C\u002Fstrong>: Offer AI-powered shopping assistance\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Requirements\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>WordPress 5.8 or higher\u003C\u002Fli>\n\u003Cli>WooCommerce 5.0 or higher\u003C\u002Fli>\n\u003Cli>PHP 7.4 or higher\u003C\u002Fli>\n\u003Cli>Ovena ACP account and API key\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Support & Documentation\u003C\u002Fh4>\n\u003Cp>For support, documentation, and API keys, visit \u003Ca href=\"https:\u002F\u002Fovena.ai\" rel=\"nofollow ugc\">Ovena AI\u003C\u002Fa> or contact our team at support@ovena.ai.\u003C\u002Fp>\n\u003Ch3>Privacy Policy\u003C\u002Fh3>\n\u003Cp>This plugin connects to the Ovena Agentic Commerce Protocol (ACP) platform to synchronize your WooCommerce product data with AI assistants like ChatGPT. Product information is transmitted securely via encrypted API to enable conversational commerce experiences. No customer personal data is shared with AI assistants. Review our privacy policy at https:\u002F\u002Fovena.ai\u002Fprivacy for detailed information.\u003C\u002Fp>\n\u003Ch3>Third-party Services\u003C\u002Fh3>\n\u003Cp>This plugin communicates with the Ovena AI platform (https:\u002F\u002Fovena.ai\u002Fapi\u002F) to synchronize product data. By using this plugin, you agree to Ovena’s terms of service and privacy policy.\u003C\u002Fp>\n","Connect your WooCommerce store to ChatGPT and AI assistants. Enable conversational AI-powered shopping with Agentic Commerce Protocol.",20,545,"2025-11-08T22:39:00.000Z","6.8.6","5.8",[18,19,65,66,22],"chatgpt","product-feed","https:\u002F\u002Fovena.ai","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fagentic-commerce-protocol-chatgpt-product-feed-ovena-acp-for-woocommerce.1.0.0.zip",{"slug":70,"name":71,"version":72,"author":73,"author_profile":74,"description":75,"short_description":76,"active_installs":77,"downloaded":78,"rating":79,"num_ratings":80,"last_updated":81,"tested_up_to":14,"requires_at_least":82,"requires_php":46,"tags":83,"homepage":85,"download_link":86,"security_score":25,"vuln_count":11,"unpatched_count":11,"last_vuln_date":26,"fetched_at":27},"agentic-commerce-for-woocommerce","Agentic Commerce for WooCommerce","0.6.3","xpay✦","https:\u002F\u002Fprofiles.wordpress.org\u002Fxpaysh\u002F","\u003Cp>\u003Cstrong>Your next customer is asking ChatGPT, not Google.\u003C\u002Fstrong> 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.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Agentic Commerce for WooCommerce (by xpay) makes your store visible to ChatGPT, Claude, Gemini and Perplexity\u003C\u002Fstrong> 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.\u003C\u002Fp>\n\u003Cp>📘 \u003Cstrong>Full setup guide with screenshots:\u003C\u002Fstrong> \u003Ca href=\"https:\u002F\u002Fdocs.xpay.sh\u002Fmerchants\u002Fwoocommerce\" rel=\"nofollow ugc\">docs.xpay.sh\u002Fmerchants\u002Fwoocommerce\u003C\u002Fa>\u003Cbr \u002F>\n🌐 \u003Cstrong>Plugin home:\u003C\u002Fstrong> \u003Ca href=\"https:\u002F\u002Fwww.xpay.sh\u002Fmerchants\u002Fwoocommerce\u002F\" rel=\"nofollow ugc\">www.xpay.sh\u002Fmerchants\u002Fwoocommerce\u002F\u003C\u002Fa>\u003Cbr \u002F>\n🔓 \u003Cstrong>Source on GitHub:\u003C\u002Fstrong> \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fxpaysh\u002Fagentic-commerce-for-woocommerce\" rel=\"nofollow ugc\">github.com\u002Fxpaysh\u002Fagentic-commerce-for-woocommerce\u003C\u002Fa>\u003C\u002Fp>\n\u003Ch4>What it does\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>\u003Cstrong>Publishes a public, agent-readable product feed\u003C\u002Fstrong> — your full catalog with live prices and stock, hosted on xpay’s CDN (no extra load on your origin).\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Adds AI-shopping JSON-LD\u003C\u002Fstrong> — \u003Ccode>Product\u003C\u002Fcode>, \u003Ccode>Offer\u003C\u002Fcode>, \u003Ccode>AggregateOffer\u003C\u002Fcode>, \u003Ccode>BuyAction\u003C\u002Fcode> and \u003Ccode>ItemList\u003C\u002Fcode> schemas on product pages, shop archive and home page. Detects existing schema from Yoast \u002F Rank Math \u002F WooCommerce core and only fills the gaps.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Serves the real AI shopping standards on your own domain\u003C\u002Fstrong> — \u003Ccode>\u002Fllms.txt\u003C\u002Fcode> (\u003Ca href=\"https:\u002F\u002Fllmstxt.org\" rel=\"nofollow ugc\">llmstxt.org\u003C\u002Fa>), \u003Ccode>schema.org\u003C\u002Fcode> \u003Ccode>Product\u003C\u002Fcode>\u002F\u003Ccode>Offer\u003C\u002Fcode>\u002F\u003Ccode>BuyAction\u003C\u002Fcode> JSON-LD on every product page, and an explicit \u003Ccode>robots.txt\u003C\u002Fcode> allowlist for AI user-agents. Optional watchlist emitters for \u003Ccode>\u002F.well-known\u002Foauth-protected-resource\u003C\u002Fcode> (RFC 9728, when UCP OAuth identity linking is on) and \u003Ccode>\u002F.well-known\u002Fagent-card.json\u003C\u002Fcode> (A2A 1.0, off by default). The discovery layer is registry-based so new standards plug in cleanly.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Allows the right bots\u003C\u002Fstrong> — 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.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Cart deep-link\u003C\u002Fstrong> — 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 \u003Ccode>_xpay_agent_attribution\u003C\u002Fcode> so you can attribute AI-driven revenue in your existing reporting.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Live inventory\u003C\u002Fstrong> — webhook-driven catalog refresh on every product \u002F stock change (debounced 30s), plus an hourly safety-net poll.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Product FAQs and return policy\u003C\u002Fstrong> — for products you approve in your xpay dashboard, the plugin publishes \u003Ccode>FAQPage\u003C\u002Fcode> and \u003Ccode>MerchantReturnPolicy\u003C\u002Fcode> JSON-LD answering the commerce questions AI shoppers ask (delivery, returns, variants). Optionally it can also show those answers to your shoppers as a block on the product page — \u003Cstrong>off on new installs\u003C\u002Fstrong>, enabled for your store from your xpay account on request. Placement is a WooCommerce product tab, the classic product-summary hook, or an \u003Ccode>[xpay-faq]\u003C\u002Fcode> shortcode you place yourself.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>What it doesn’t do\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>\u003Cstrong>It doesn’t touch your checkout.\u003C\u002Fstrong> Stripe \u002F WooPayments \u002F PayPal \u002F Square \u002F whatever you already use — payment runs through them, unchanged. Your payout schedule is unchanged.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>It doesn’t see your customers.\u003C\u002Fstrong> 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.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>It doesn’t require a new account or contract\u003C\u002Fstrong> to start. Free to install and get going — paid plans available as you grow. \u003Ca href=\"https:\u002F\u002Fwww.xpay.sh\u002Fpricing\u002F?tab=agentic-commerce\" rel=\"nofollow ugc\">See pricing\u003C\u002Fa>.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>It doesn’t slow down your site.\u003C\u002Fstrong> The JSON-LD block is tiny and cached; the catalog feed is served from xpay’s CDN, not your origin.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Five-minute install flow\u003C\u002Fh4>\n\u003Col>\n\u003Cli>Install the plugin from this directory or upload the zip. (\u003Ca href=\"https:\u002F\u002Fdocs.xpay.sh\u002Fmerchants\u002Fwoocommerce\u002Finstalling\" rel=\"nofollow ugc\">detailed walk-through\u003C\u002Fa>)\u003C\u002Fli>\n\u003Cli>Activate. You’ll be taken to \u003Cstrong>Settings \u003Cspan aria-hidden=\"true\" class=\"wp-exclude-emoji\">→\u003C\u002Fspan> xpay\u003C\u002Fstrong>.\u003C\u002Fli>\n\u003Cli>Click \u003Cstrong>Connect store\u003C\u002Fstrong>. You’re redirected to app.xpay.sh, where you grant a read-only WooCommerce REST API key. (\u003Ca href=\"https:\u002F\u002Fdocs.xpay.sh\u002Fmerchants\u002Fwoocommerce\u002Frest-api-keys\" rel=\"nofollow ugc\">how to generate one\u003C\u002Fa>)\u003C\u002Fli>\n\u003Cli>Your catalog goes live on AI surfaces within about 10 minutes. The plugin’s built-in audit-readiness checklist (\u003Ca href=\"https:\u002F\u002Fdocs.xpay.sh\u002Fmerchants\u002Fwoocommerce\u002Faudit-readiness\" rel=\"nofollow ugc\">what each row means\u003C\u002Fa>) turns green as each piece confirms.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>Stuck on any step? \u003Ca href=\"https:\u002F\u002Fdocs.xpay.sh\u002Fmerchants\u002Fwoocommerce\u002Ftroubleshooting\" rel=\"nofollow ugc\">Troubleshooting guide\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch4>Compatibility\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>WooCommerce 7.0+ on WordPress 6.2+ and PHP 7.4+.\u003C\u002Fli>\n\u003Cli>Declares compatibility with WooCommerce High-Performance Order Storage (HPOS) and Cart\u002FCheckout Blocks.\u003C\u002Fli>\n\u003Cli>Works alongside Yoast SEO, Rank Math, WooCommerce Blocks, WooPayments, Stripe for WooCommerce, and the standard Storefront \u002F Astra \u002F Divi \u002F Elementor themes.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Privacy and consent\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>\u003Cstrong>Anonymous lifecycle telemetry is off by default.\u003C\u002Fstrong> 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 \u003Cstrong>Settings \u003Cspan aria-hidden=\"true\" class=\"wp-exclude-emoji\">→\u003C\u002Fspan> xpay \u003Cspan aria-hidden=\"true\" class=\"wp-exclude-emoji\">→\u003C\u002Fspan> Privacy\u003C\u002Fstrong>. System-wide opt-out via \u003Ccode>define( 'XPAY_WC_TELEMETRY', false );\u003C\u002Fcode> in \u003Ccode>wp-config.php\u003C\u002Fcode>.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Full data disclosure\u003C\u002Fstrong> at \u003Ca href=\"https:\u002F\u002Finstall.xpay.sh\u002Fwoocommerce\u002Fprivacy.html\" rel=\"nofollow ugc\">install.xpay.sh\u002Fwoocommerce\u002Fprivacy.html\u003C\u002Fa> — every byte the plugin sends, when it sends it, how to opt out, how to request deletion. Plain-English version: \u003Ca href=\"https:\u002F\u002Fdocs.xpay.sh\u002Fmerchants\u002Fwoocommerce\u002Fprivacy-telemetry\" rel=\"nofollow ugc\">docs.xpay.sh\u002Fmerchants\u002Fwoocommerce\u002Fprivacy-telemetry\u003C\u002Fa>.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Source code and contributing\u003C\u002Fh4>\n\u003Cp>The plugin source is published under GPLv2-or-later. Public repo and issue tracker: \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fxpaysh\u002Fagentic-commerce-for-woocommerce\" rel=\"nofollow ugc\">github.com\u002Fxpaysh\u002Fagentic-commerce-for-woocommerce\u003C\u002Fa>. You can fork, modify, redistribute, and self-host without paying anything.\u003C\u002Fp>\n\u003Ch3>External services\u003C\u002Fh3>\n\u003Cp>This plugin connects to the following xpay-operated services to deliver its core function. Every endpoint and its purpose is documented; full payload disclosure is in the \u003Ca href=\"https:\u002F\u002Finstall.xpay.sh\u002Fwoocommerce\u002Fprivacy.html\" rel=\"nofollow ugc\">Privacy\u003C\u002Fa> section.\u003C\u002Fp>\n\u003Col>\n\u003Cli>\n\u003Cp>\u003Cstrong>agent-feed.xpay.sh\u003C\u002Fstrong> — Public CDN that hosts your AI-readable catalog feed at \u003Ccode>https:\u002F\u002Fagent-feed.xpay.sh\u002Fcatalog\u002F{your-slug}.json\u003C\u002Fcode>. The plugin does not contact this URL directly; the xpay backend writes it from your WooCommerce REST API after you click \u003Cstrong>Connect store\u003C\u002Fstrong>.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>agent-commerce.xpay.sh\u003C\u002Fstrong> — The agent-side API that AI shopping agents call to surface and buy from your products. The plugin contacts this host at the following paths: (a) \u003Ccode>POST \u002Fv1\u002Fonboard\u002Fwoocommerce\u002Fwc-auth-callback\u003C\u002Fcode> is the WooCommerce OAuth callback target (WordPress itself calls this on your behalf, server-to-server, after you approve the one-click connect prompt); (b) \u003Ccode>GET \u002Fv1\u002Fonboard\u002Fwoocommerce\u002Fstatus?nonce=…\u003C\u002Fcode> is polled by the xpay onboarding page while the handshake finishes; (c) \u003Ccode>POST \u002Fv1\u002Fmerchants\u002F{slug}\u002Fresync\u003C\u002Fcode> triggers a fresh catalog ingest after a product or stock change; (d) \u003Ccode>GET \u002Fv1\u002Fmerchants\u002F{slug}\u003C\u002Fcode> is called when \u003Cstrong>Settings \u003Cspan aria-hidden=\"true\" class=\"wp-exclude-emoji\">→\u003C\u002Fspan> xpay\u003C\u002Fstrong> verifies the current connection state; (e) \u003Ccode>PATCH \u002Fv1\u002Fmerchants\u002F{slug}\u002Fproducts\u002F{sku}\u003C\u002Fcode> pushes a single-product delta when a WooCommerce product\u002Fstock webhook fires; (f) \u003Ccode>DELETE \u002Fv1\u002Fmerchants\u002F{slug}\u003C\u002Fcode> is sent (non-blocking) when you click \u003Cstrong>Disconnect\u003C\u002Fstrong> so xpay marks your account as disconnected and archives the cached catalog. The hostname is also the publicly advertised target for \u003Ccode>POST \u002Fmcp\u002F{slug}\u003C\u002Fcode> (the JSON-RPC commerce MCP endpoint AI agents talk to) — the plugin itself does not call this URL but lists it in the \u003Ccode>\u002F.well-known\u002Fucp\u003C\u002Fcode> manifest.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>app.xpay.sh\u002Fonboard\u002Fwoocommerce\u003C\u002Fstrong> — The merchant-side onboarding page. When you click \u003Cstrong>Connect store\u003C\u002Fstrong>, the plugin redirects your browser here with three query-string parameters: your site URL, your administrator email address, and a one-time random nonce generated locally. No data is sent to xpay before you click the button. You sign in or sign up on xpay and grant the WooCommerce REST API permission there.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>agent-commerce.xpay.sh\u002Fv1\u002Fevents\u003C\u002Fstrong> — Optional anonymous lifecycle telemetry. Disabled by default; only contacted if you explicitly opt in via the first-activation admin notice or \u003Cstrong>Settings \u003Cspan aria-hidden=\"true\" class=\"wp-exclude-emoji\">→\u003C\u002Fspan> xpay \u003Cspan aria-hidden=\"true\" class=\"wp-exclude-emoji\">→\u003C\u002Fspan> Privacy\u003C\u002Fstrong>. Full payload disclosure in the Privacy section.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>agent-commerce.xpay.sh\u002Fv1\u002Fmerchants\u002F{slug}\u002Forders\u003C\u002Fstrong> — Agent-attributed order reporting for connected stores (non-PII order summary + attribution source; no customer, payment, or personal data). Off via the \u003Ccode>xpay_wc_order_events_enabled\u003C\u002Fcode> option. Full payload disclosure in the Privacy section.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>agent-commerce.xpay.sh\u002Fv1\u002Fagent-analytics\u003C\u002Fstrong> — Optional anonymous AI-bot crawl analytics. Disabled by default; shares the same opt-in as item 4 (and respects a separate \u003Ccode>define( 'XPAY_WC_AGENT_ANALYTICS', false )\u003C\u002Fcode> hard-off). When enabled, the plugin counts requests from \u003Cem>known AI bots only\u003C\u002Fem> (e.g. GPTBot, ChatGPT-User, ClaudeBot, PerplexityBot, Google-Extended) — recording the bot name, a coarse page type (home\u002Fproduct\u002Fcategory\u002Fdiscovery-file\u002Fsitemap\u002Fother), the HTTP status, and whether we routed the bot to your structured catalog. It also sends an aggregate daily count of human pageviews (a number only — no user-agent, no URLs, no per-visit data) as the AI-vs-human denominator. Since 0.5.3 a bot event also carries a salted, one-way hash of the connecting IP address (a bot’s — behind a proxy or CDN this is the connecting edge address), so two hits from the same crawler can be counted as one visitor. The salt is unique to your store and is regenerated every day, so the hash cannot be linked across days or across stores, and the address itself is never stored or transmitted. This applies to AI bots only — a human visitor’s IP is never read, hashed or sent. Events are buffered locally and sent in the background by WP-Cron, never on a page load. Cart, checkout, account, admin and REST paths are never recorded. No per-visit human data, no customer, order, or personal data.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>audit.xpay.sh\u003C\u002Fstrong> — Merchant-facing audit dashboard. The plugin emits a link to \u003Ccode>audit.xpay.sh\u002F{your-slug}\u003C\u002Fcode> on the Settings page so you can review the live agent-readiness score xpay computed from your catalog; the plugin itself does not fetch from this host. Opening the link from your browser sends standard browser headers to xpay.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\u003Cstrong>auth.xpay.sh\u003C\u002Fstrong> — Public OAuth-protected-resource discovery target. The plugin publishes \u003Ccode>auth.xpay.sh\u003C\u002Fcode> as the \u003Ccode>authorization_servers[0]\u003C\u002Fcode> entry in \u003Ccode>\u002F.well-known\u002Foauth-protected-resource\u003C\u002Fcode> (an RFC 9728 metadata document AI agents fetch to learn where to obtain a token). The plugin does not contact this host server-to-server; it is referenced for agent-side discovery only.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>install.xpay.sh\u002Fwoocommerce\u002F{terms,privacy}.html\u003C\u002Fstrong> — Static legal documents linked from this readme and from the Settings privacy panel. The plugin itself does not fetch these URLs; clicking the links opens them in your browser.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>Terms of use: \u003Ca href=\"https:\u002F\u002Finstall.xpay.sh\u002Fwoocommerce\u002Fterms.html\" rel=\"nofollow ugc\">install.xpay.sh\u002Fwoocommerce\u002Fterms.html\u003C\u002Fa>\u003Cbr \u002F>\nPrivacy policy: \u003Ca href=\"https:\u002F\u002Finstall.xpay.sh\u002Fwoocommerce\u002Fprivacy.html\" rel=\"nofollow ugc\">install.xpay.sh\u002Fwoocommerce\u002Fprivacy.html\u003C\u002Fa>\u003C\u002Fp>\n\u003Ch3>Privacy\u003C\u002Fh3>\n\u003Cp>xpay is built non-custodially: we never see your customers, your orders, or any payment data. Concretely:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\n\u003Cp>\u003Cstrong>Nothing leaves your site before you click Connect store.\u003C\u002Fstrong> The Settings \u003Cspan aria-hidden=\"true\" class=\"wp-exclude-emoji\">→\u003C\u002Fspan> xpay page is pure markup — no outbound HTTP, no analytics ping, no nonce pre-registration.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Sent only after you click Connect store\u003C\u002Fstrong> (required for the plugin to work): your site URL, your administrator email address, a one-time random nonce, your WooCommerce REST API consumer key\u002Fsecret (so xpay can read the product catalog), and your public product fields (name, description, price, stock, image URLs, categories). No customer data. No order data. No payment data.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Optionally sent if you opt in to anonymous telemetry\u003C\u002Fstrong> (default OFF): lifecycle event names tagged with your site URL, plugin version, WP version, WC version, PHP version, locale. No customer data, no order data, no customer PII.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Optionally sent if you opt in (default OFF), as part of the same telemetry consent — AI-bot crawl analytics\u003C\u002Fstrong>: for requests from \u003Cem>known AI bots only\u003C\u002Fem>, the bot name, a coarse page type (home\u002Fproduct\u002Fcategory\u002Fdiscovery-file\u002Fsitemap\u002Fother), the HTTP status, and whether the bot was routed to your structured catalog — tagged with your site URL. Also sent: an aggregate daily count of human pageviews (a number only — the AI-vs-human denominator). Also sent for \u003Cem>AI-bot\u003C\u002Fem> hits only: a salted one-way hash of the bot’s IP (per-store salt, rotated daily — not the address, and not linkable across days or stores). Never recorded: per-visit human data, human IP addresses, query strings, cart\u002Fcheckout\u002Faccount\u002Fadmin\u002FREST paths, or any customer, order, or personal data. Hard-disable just this (while keeping lifecycle telemetry) with \u003Ccode>define( 'XPAY_WC_AGENT_ANALYTICS', false );\u003C\u002Fcode>.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Opt out of anonymous telemetry\u003C\u002Fstrong>: \u003Cstrong>Settings \u003Cspan aria-hidden=\"true\" class=\"wp-exclude-emoji\">→\u003C\u002Fspan> xpay \u003Cspan aria-hidden=\"true\" class=\"wp-exclude-emoji\">→\u003C\u002Fspan> Privacy \u003Cspan aria-hidden=\"true\" class=\"wp-exclude-emoji\">→\u003C\u002Fspan> Turn off\u003C\u002Fstrong>. Or define \u003Ccode>XPAY_WC_TELEMETRY\u003C\u002Fcode> to \u003Ccode>false\u003C\u002Fcode> in \u003Ccode>wp-config.php\u003C\u002Fcode> for a system-wide hard disable that overrides any UI choice.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Request data deletion\u003C\u002Fstrong>: email privacy@xpay.sh from your admin email with your merchant slug. We process within 7 business days.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Full data-handling disclosure: \u003Ca href=\"https:\u002F\u002Finstall.xpay.sh\u002Fwoocommerce\u002Fprivacy.html\" rel=\"nofollow ugc\">install.xpay.sh\u002Fwoocommerce\u002Fprivacy.html\u003C\u002Fa>.\u003C\u002Fp>\n","Put your WooCommerce catalog inside ChatGPT, Claude, Gemini and Perplexity — buyers complete checkout on your existing WooCommerce gateway.",10,877,74,3,"2026-07-15T12:59:00.000Z","6.2",[18,19,65,84,22],"llms","https:\u002F\u002Fwww.xpay.sh\u002Fmerchants\u002Fwoocommerce\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fagentic-commerce-for-woocommerce.0.6.3.zip",{"slug":88,"name":89,"version":90,"author":91,"author_profile":92,"description":93,"short_description":94,"active_installs":11,"downloaded":95,"rating":25,"num_ratings":31,"last_updated":96,"tested_up_to":14,"requires_at_least":97,"requires_php":16,"tags":98,"homepage":100,"download_link":101,"security_score":25,"vuln_count":11,"unpatched_count":11,"last_vuln_date":26,"fetched_at":27},"clustova-commerce","Clustova Commerce – AI Product Feed for WooCommerce","1.1.2","Muhammad Afzal","https:\u002F\u002Fprofiles.wordpress.org\u002Fphpdocs\u002F","\u003Cp>Clustova Commerce is the free foundation for agentic commerce on WooCommerce. When AI agents like ChatGPT, Gemini, Copilot, and Perplexity search for products to recommend, your store shows up with rich, structured data they can understand and act on.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Free features:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>ACP product feed\u003C\u002Fstrong> — serve your catalog in the ACP (Agentic Commerce Protocol) format that ChatGPT and other OpenAI-powered agents consume natively.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>llms.txt\u003C\u002Fstrong> — generate and serve an AI-oriented \u003Ccode>llms.txt\u003C\u002Fcode> file describing your store and product catalog so agents can discover your entire range at a glance.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>AI-readable product schema\u003C\u002Fstrong> — emit structured product data that extends your existing schema, giving agents rich attributes, stock levels, and pricing without duplicating your SEO markup.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Basic AI-channel detection\u003C\u002Fstrong> — identify orders placed via the \u003Ccode>agentic_commerce\u003C\u002Fcode> gateway flag so you know which sales came through agents vs. direct browser traffic.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Rule-based GEO health score\u003C\u002Fstrong> — get a deterministic, no-AI health grade on every product (thin descriptions, missing attributes, no images) so you know what needs attention.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>Pro upgrade adds:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>Dual-protocol UCP feed\u003C\u002Fstrong> — serve a Universal Commerce Protocol feed alongside ACP plus MCP discovery, so your catalog reaches the widest range of AI shopping agents.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Ad-platform conversion tracking\u003C\u002Fstrong> — server-side reconciliation to GA4, Meta Conversions API, and Google Ads so agent-driven sales show up in your ad dashboards and Smart Bidding can optimise for them.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>AI-channel revenue dashboard\u003C\u002Fstrong> — track and reconcile revenue and orders driven by each AI agent surface, so you can prove the ROI of agentic commerce.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>AI product enrichment (bring your own key)\u003C\u002Fstrong> — use your own OpenAI, Anthropic, Gemini, or OpenRouter key to rewrite thin descriptions and auto-fix GEO issues in the background.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Agent-traffic hardening + AEO auth\u003C\u002Fstrong> — protect and authenticate agent traffic so only legitimate AI agents read your feeds.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Inventory sync\u003C\u002Fstrong> — keep stock levels accurate across agent surfaces.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>All Pro features fail gracefully — your store never breaks if a license lapses.\u003C\u002Fp>\n\u003Ch3>External services\u003C\u002Fh3>\n\u003Cp>This plugin connects to the Clustova licensing API (a service operated by Clustova) to verify a Clustova Commerce Pro license key.\u003C\u002Fp>\n\u003Cp>This connection is only made when you enter a license key and click “Save & verify license key” on the \u003Cstrong>Clustova \u003Cspan aria-hidden=\"true\" class=\"wp-exclude-emoji\">→\u003C\u002Fspan> Settings \u003Cspan aria-hidden=\"true\" class=\"wp-exclude-emoji\">→\u003C\u002Fspan> License\u003C\u002Fstrong> tab. The free plugin’s core features (ACP feed, llms.txt, product schema, GEO health scoring, channel detection) work fully without this service and make no external requests on their own.\u003C\u002Fp>\n\u003Cp>What is sent, and when:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>The license key you enter — sent only at the moment you save\u002Fverify the key, so the server can confirm whether it is valid, active, or expired.\u003C\u002Fli>\n\u003Cli>Your site URL (the result of \u003Ccode>home_url()\u003C\u002Fcode>) — sent with the same request so the license can be associated with this site.\u003C\u002Fli>\n\u003Cli>The product identifier (\u003Ccode>clustova-commerce-pro\u003C\u002Fcode>) — sent so the server knows which product the key belongs to.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>No personal data, customer data, or order data is ever sent to this service. The licensing endpoint is \u003Ccode>https:\u002F\u002Fapi.clustova.com\u002Fapi\u002Fv1\u002Flicensing\u002Fedd\u003C\u002Fcode>.\u003C\u002Fp>\n\u003Cp>If you also install the separate Clustova Commerce Pro add-on, it uses the same service to activate the license on install and to re-validate it periodically in the background.\u003C\u002Fp>\n\u003Cp>Service provider: Clustova. Terms of Service: https:\u002F\u002Fwww.clustova.com\u002Fterms-of-service — Privacy Policy: https:\u002F\u002Fwww.clustova.com\u002Fprivacy-policy\u003C\u002Fp>\n","Make your WooCommerce store discoverable and measurable for AI agents — ACP product feed, llms.txt, AI-readable schema, and channel detection.",64,"2026-07-17T15:21:00.000Z","6.5",[99,18,19,66,22],"acp","https:\u002F\u002Fclustova.com\u002Fcommerce","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fclustova-commerce.1.1.2.zip",{"slug":103,"name":104,"version":105,"author":106,"author_profile":107,"description":108,"short_description":109,"active_installs":11,"downloaded":110,"rating":11,"num_ratings":11,"last_updated":111,"tested_up_to":14,"requires_at_least":15,"requires_php":16,"tags":112,"homepage":114,"download_link":115,"security_score":25,"vuln_count":11,"unpatched_count":11,"last_vuln_date":26,"fetched_at":27},"kalicart-bridge","KaliCart Bridge – Product Feed for ChatGPT & AI Agents","1.0.123","Giuseppe Socci","https:\u002F\u002Fprofiles.wordpress.org\u002Fcarthub\u002F","\u003Cp>Make your WooCommerce catalog ready to be read and verified by AI shopping systems.\u003C\u002Fp>\n\u003Cp>KaliCart Bridge gives you an immediate catalog-readiness report inside WooCommerce: it identifies products with missing images, brand, usable description, category, price or SKU, and links you directly to the native Products screen to fix them. It then exposes your live catalog in a structured form for AI agents and can generate a validated product feed ready for ChatGPT merchant submission.\u003C\u002Fp>\n\u003Cp>No LLM runs on your site. No cloud service or customer data is sent anywhere by default. Prices, availability and product changes remain live on your WooCommerce store.\u003C\u002Fp>\n\u003Cp>The plugin does not promise traffic, ChatGPT placement or merchant approval. It prepares and exposes your catalog; OpenAI controls access to its own shopping surfaces and delivery channel.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>What you get after installation\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>A catalog-readiness report with actionable product fixes.\u003C\u002Fli>\n\u003Cli>A current, structured catalog API for agents that reach your store.\u003C\u002Fli>\n\u003Cli>An optional ChatGPT feed, validated before export.\u003C\u002Fli>\n\u003Cli>Optional inclusion in KaliCart’s federated catalog, only with explicit consent.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Documentation: https:\u002F\u002Fbridge.kalicart.com\u002Fdocs\u002F\u003C\u002Fp>\n\u003Cp>\u003Cstrong>For developers and AI integrations\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>\u003Cstrong>What it does:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Exposes a \u003Ccode>\u002Fdiscovery\u003C\u002Fcode> endpoint — the single entry point any agent needs to understand your catalog\u003C\u002Fli>\n\u003Cli>Provides \u003Ccode>\u002Fcatalog\u002Fsearch\u003C\u002Fcode>, \u003Ccode>\u002Fcatalog\u002Fproducts\u003C\u002Fcode>, \u003Ccode>\u002Fcatalog\u002Fproduct\u002F{id}\u003C\u002Fcode>, \u003Ccode>\u002Fcatalog\u002Fcategories\u003C\u002Fcode> endpoints\u003C\u002Fli>\n\u003Cli>Exposes a Model Context Protocol (MCP) server at \u003Ccode>\u002Fwp-json\u002Fkalicart\u002Fv1\u002Fmcp\u003C\u002Fcode> (JSON-RPC 2.0) so MCP-capable agents can call the catalog as tools — same data as the REST endpoints, no API key\u003C\u002Fli>\n\u003Cli>Gives AI chatbot and assistant builders a structured catalog source to ingest or call, instead of scraping product pages\u003C\u002Fli>\n\u003Cli>Computationally normalizes product data: prices (min\u002Fmax for variables, sale %, discount), stock, gender inference, color family mapping, size type detection\u003C\u002Fli>\n\u003Cli>Exposes WooCommerce shipping-zone policy for agent reasoning; checkout remains the final authority for exact destination\u002Fcart shipping cost\u003C\u002Fli>\n\u003Cli>Exposes active product\u002Fcategory-compatible coupons as conditional checkout savings; coupons never replace the catalog price\u003C\u002Fli>\n\u003Cli>Category tree nodes include direct \u003Ccode>products_url\u003C\u002Fcode> and \u003Ccode>search_url_template\u003C\u002Fcode> fields so agents can navigate without constructing URLs manually\u003C\u002Fli>\n\u003Cli>Dashboard issue cards and suggestions link to filtered product lists for direct remediation\u003C\u002Fli>\n\u003Cli>Uses \u003Cstrong>your merchant taxonomy\u003C\u002Fstrong> — no global remapping, products stay in your WooCommerce categories\u003C\u002Fli>\n\u003Cli>Injects a \u003Ccode>\u003Clink rel=\"kalicart-agent\">\u003C\u002Fcode> in your site \u003Ccode>\u003Chead>\u003C\u002Fcode> for agent auto-discovery\u003C\u002Fli>\n\u003Cli>Adds an “agent ready” badge in the footer\u003C\u002Fli>\n\u003Cli>Injects \u003Ccode>Allow: \u002Fwp-json\u002Fkalicart\u002F\u003C\u002Fcode> in \u003Ccode>robots.txt\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>Generates \u003Ccode>\u002Fkalicart-sitemap.xml\u003C\u002Fcode> linked from the WP sitemap index\u003C\u002Fli>\n\u003Cli>Shows a catalog health dashboard in wp-admin with quarantine tracking and improvement suggestions\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>What it does NOT do:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>No LLM calls\u003C\u002Fli>\n\u003Cli>No cloud dependency for core functionality\u003C\u002Fli>\n\u003Cli>No data sent anywhere outside your server by default — the only optional exception is the Federated Catalog feature (see “External services” below), which you turn on explicitly\u003C\u002Fli>\n\u003Cli>No API key required for public endpoints\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>Normalization engine:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Price: regular, sale, current, discount %, currency — variable products get min\u002Fmax ranges\u003C\u002Fli>\n\u003Cli>Stock: status, in_stock bool, quantity if managed, backorder policy\u003C\u002Fli>\n\u003Cli>Gender: inferred from \u003Ccode>pa_gender\u003C\u002Fcode> attribute, category paths, tags, product name (multilingual keywords: IT\u002FEN\u002FFR\u002FDE\u002FES)\u003C\u002Fli>\n\u003Cli>Color: mapped to 13 color families via keyword matching on \u003Ccode>pa_color\u003C\u002Fcode>\u002F\u003Ccode>pa_colore\u003C\u002Fcode> and product metadata\u003C\u002Fli>\n\u003Cli>Size: detected from \u003Ccode>pa_size\u003C\u002Fcode>\u002F\u003Ccode>pa_taglia\u003C\u002Fcode>, type auto-detected (clothing S\u002FM\u002FL, numeric EU, shoes EU half-sizes)\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>Catalog health \u002F quarantine:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>Products are scored 0–100 based on: title quality, description length, category assignment, price validity, image presence and SKU presence. Quarantine is reserved for blocking computability issues: ambiguous\u002Ftoo-short titles, missing or very short descriptions, missing real categories, and missing or zero prices. Missing images and SKUs remain clickable improvement suggestions but do not quarantine products.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Checkout sessions (optional):\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>When enabled in WP Admin \u003Cspan aria-hidden=\"true\" class=\"wp-exclude-emoji\">→\u003C\u002Fspan> KaliCart \u003Cspan aria-hidden=\"true\" class=\"wp-exclude-emoji\">→\u003C\u002Fspan> Settings, agents can create checkout sessions containing one or more products. Each session returns cart_url (lands on WooCommerce cart for review) and checkout_url (goes directly to checkout). Sessions expire after 30 minutes. No OAuth, no PII, no payment on the agent side.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Model Context Protocol (MCP) endpoint:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>The same read-only catalog is also exposed as an MCP server at \u003Ccode>\u002Fwp-json\u002Fkalicart\u002Fv1\u002Fmcp\u003C\u002Fcode> (JSON-RPC 2.0 over HTTP POST). MCP-capable agents and assistants connect to it and call the catalog as tools: \u003Ccode>search_products\u003C\u002Fcode>, \u003Ccode>list_products\u003C\u002Fcode>, \u003Ccode>get_product\u003C\u002Fcode>, \u003Ccode>list_categories\u003C\u002Fcode>, \u003Ccode>get_meta\u003C\u002Fcode>. It is read-only and needs no authentication, exactly like the public REST endpoints — it adds a second transport, not new data. No LLM, no external calls. Checkout and payment are never exposed over MCP.\u003C\u002Fp>\n\u003Ch3>ChatGPT Product Discovery Feed\u003C\u002Fh3>\n\u003Col>\n\u003Cli>\u003Cstrong>Configure and generate.\u003C\u002Fstrong> Set your return policy URL and target countries (derived from your WooCommerce selling locations); optionally set a brand fallback for own-label stores. The plugin validates every row against the OpenAI Product Feed specification: incomplete store configuration blocks generation entirely, products without image or brand are excluded and counted, and a failed run never destroys the last valid feed.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Apply at chatgpt.com\u002Fmerchants.\u003C\u002Fstrong> Application and approval are required and decided by OpenAI.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Deliver after approval.\u003C\u002Fstrong> Upload the generated file (stable filename, \u003Ccode>jsonl.gz\u003C\u002Fcode> supported) on the delivery channel OpenAI assigns. The plugin regenerates a full daily snapshot via WP-Cron.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>No acceptance or visibility is guaranteed by the plugin: approval, delivery access and final ranking are determined by OpenAI.\u003C\u002Fp>\n\u003Ch3>External services\u003C\u002Fh3>\n\u003Cp>This plugin works fully standalone. It connects to one external service \u003Cstrong>only if you explicitly opt in\u003C\u002Fstrong> by activating the optional Federated Catalog feature in WP Admin \u003Cspan aria-hidden=\"true\" class=\"wp-exclude-emoji\">→\u003C\u002Fspan> KaliCart Bridge.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Service:\u003C\u002Fstrong> KaliCart Global (https:\u002F\u002Fdashboard.kalicart.com)\u003C\u002Fp>\n\u003Cp>\u003Cstrong>When data is sent:\u003C\u002Fstrong> Only when an administrator clicks “Activate Federated Catalog” (and, symmetrically, “Revoke consent”). Nothing is sent automatically, on activation, or in the background. With the feature off, the plugin makes no external requests.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>What is sent:\u003C\u002Fstrong> A single value — your site’s public URL (e.g. https:\u002F\u002Fyourstore.com). On revoke, the same URL is sent to withdraw. No customer data, orders, personal data, credentials, or API keys are ever transmitted.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>What the service does:\u003C\u002Fstrong> The URL tells KaliCart Global your store wishes to be discovered. KaliCart Global then periodically reads your already-public catalog (the same data exposed by the Bridge’s public REST endpoints) and includes it in federated agent search. It only reads; it never writes to your store. Revoking stops this and parks your catalog.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Privacy notice:\u003C\u002Fstrong> https:\u002F\u002Fbridge.kalicart.com\u002Fprivacy\u002F\u003Cbr \u002F>\n\u003Cstrong>Terms \u002F documentation:\u003C\u002Fstrong> https:\u002F\u002Fbridge.kalicart.com\u002Fdocs\u002F\u003C\u002Fp>\n","Validated OpenAI-compatible product feed for ChatGPT product discovery (ACP), plus catalog API, MCP server and UCP discovery for AI agents.",741,"2026-07-22T07:06:00.000Z",[18,113,65,66,22],"ai-agents","https:\u002F\u002Fbridge.kalicart.com","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fkalicart-bridge.1.0.123.zip",{"error":117,"url":118,"statusCode":119,"statusMessage":120,"message":120},true,"http:\u002F\u002Flocalhost\u002Fapi\u002Fplugins\u002Fecentic-for-woocommerce\u002Fbundle",404,"no bundle for this plugin yet",{"slug":4,"current_version":6,"total_versions":31,"versions":122},[123],{"version":6,"download_url":24,"svn_tag_url":124,"released_at":26,"has_diff":125,"diff_files_changed":126,"diff_lines":26,"trac_diff_url":26,"vulnerabilities":127,"is_current":117},"https:\u002F\u002Fplugins.svn.wordpress.org\u002Fecentic-for-woocommerce\u002Ftags\u002F1.0.0\u002F",false,[],[]]