WooCommerce 10.7 quietly added Agentic Commerce Protocol endpoints to core. The developer release notes never mention them. So this is what WooCommerce agentic commerce actually amounts to on a live store today: what is really in the code, the single gate that decides whether any of it does anything for you, and the five checks I ran on my own install before deciding whether it mattered.
The release notes didn’t mention it. The code did.
WooCommerce 10.7 shipped on 14 April 2026. I went looking through the developer release post for the agentic commerce work that had been on the roadmap since October 2025 — the post that promised the Store API and the WooCommerce MCP would be “a natural fit” for Stripe’s protocol.
What I found in the 10.7 release notes: performance work, order fulfilment API improvements, Store API enhancements, cart and checkout block refinements. Not one word about agents.
So I stopped reading about it and opened the plugin directory on my own server instead.
wp-content/plugins/woocommerce/src/StoreApi/Routes/V1/Agentic/
├── CheckoutSessions.php
├── CheckoutSessionsUpdate.php
└── CheckoutSessionsComplete.phpAnd in RoutesController.php, sitting directly above the three registrations, a single-line comment that answers the question:
// Agentic Commerce Protocol endpoints.
It shipped. It just didn’t make the announcement. That gap — between what is in the code and what anyone tells store owners — is the entire subject of this article.
What WooCommerce agentic commerce actually is in 10.7
Three endpoints, registered under a namespace of their own: wc/agentic/v1. Not the familiar wc/store/v1 that powers your cart and checkout blocks — a separate surface, deliberately.
The flow they describe is short. An agent opens a checkout session, updates it as the shopper changes their mind, then completes it. The completion step is the one worth sitting with: it books a real order in your store without the shopper’s browser ever loading your site. No product page. No cart. No checkout block. No theme, no popup, no banner, no exit-intent offer.
Two more pieces landed alongside the routes. src/Enums/PaymentGatewayFeature.php gained a new constant — AGENTIC_COMMERCE = 'agentic_commerce' — and src/StoreApi/Utilities/AgenticCheckoutUtils.php arrived to decide which of your gateways is allowed to handle an order that arrives this way.
That last file is where WooCommerce agentic commerce stops being an announcement and starts being a configuration question about your specific store.
The gate nobody mentions: your payment gateway decides
Inside AgenticCheckoutUtils there is a method called get_agentic_commerce_gateway(). It walks your available gateways and accepts one only if three things are true at once. The gateway has to declare support for the agentic_commerce feature, and it has to implement two methods by name: get_agentic_commerce_provider() and get_agentic_commerce_payment_methods().
All three. Any gateway that satisfies two of them is not eligible.
This is the part that gets lost in the headlines. “WooCommerce supports agentic commerce” is a true statement about WooCommerce core and a meaningless one about your store. Core built the socket. Your payment gateway has to bring the plug — and on the day 10.7 landed, almost none of them had.
Which turns the whole thing into one boring question you can actually answer this week: does my payment provider declare that feature yet? Not “should I care about agentic commerce.” That one you cannot act on. This one you can.
The MCP integration is in core too — experimental, and off by default
While I was in there I checked the feature registry, because the October 2025 roadmap had promised a WooCommerce MCP in version 10.3. It is registered in FeaturesController.php as mcp_integration, and two of its properties tell you exactly how much weight to put on it: enabled_by_default is false, and is_experimental is true.
It is worth understanding why both exist, because they solve opposite problems. The Agentic Commerce Protocol endpoints are for an agent that wants to buy — an outside shopper’s assistant, arriving with a basket. The MCP integration is for an assistant that wants to work — searching your products, adding and updating them, creating and managing orders, per that roadmap. One is a customer. The other is staff.
Store owners keep collapsing those two into “AI in my shop,” then get surprised when a tool that is good at one is useless at the other. They are separate doors with separate keys, and in 10.7 one of them ships switched off.
ACP, UCP, and why you don’t actually have to pick
There are two competing standards, and the coverage of them is more dramatic than the decision needs to be.
ACP — the Agentic Commerce Protocol — is open source, co-developed by Stripe and OpenAI, and it is the backbone of buying inside ChatGPT. It is optimised for the last ten percent of the funnel: the checkout itself. WooCommerce announced in December 2025 that it would be a launch partner for Stripe’s Agentic Commerce Suite, and the code above is that promise arriving.
UCP — the Universal Commerce Protocol — was announced by Shopify and Google in January 2026 and reaches wider, covering discovery through post-purchase rather than just the buy button.
Here is the detail that takes the pressure off: the agentic_commerce gateway feature is protocol-agnostic. Core did not pick a winner. It exposed a socket and left the protocol choice to whoever writes the gateway — which means the bet is your payment provider’s to make, and their incentive is to support whatever brings them volume.
So the honest answer to “which protocol should my store back” is: neither, yet. Back your data instead. Whichever standard wins, WooCommerce agentic commerce reads the same underlying thing — your catalog, your prices, your stock — and if that layer is wrong, both protocols will confidently sell something you cannot ship.
What changed in March 2026, a month before 10.7
There is a timing detail worth holding next to all of this. The endpoints landed in WooCommerce core in April. The most visible consumer implementation of that protocol had already changed shape in March.
OpenAI’s Instant Checkout — buying inside ChatGPT, built on ACP with Stripe — was the flagship demonstration that agent-initiated checkout was real. In early March 2026 OpenAI moved it. Digital Commerce 360 reported on 6 March, citing The Information and remarks by Shopify’s president three days earlier, that the feature was being deprioritised in its original form; an OpenAI spokesperson framed the change as “Instant Checkout is moving to Apps, where purchases can happen more seamlessly.” The reported reason was the operational weight of transacting on a merchant’s behalf — inventory, taxes and pricing that need constant maintenance to stay correct.
ACP itself did not go anywhere. The same spokesperson described it as “the infrastructure that connects users to merchants across the full shopping journey,” and the specification has kept moving — the stable version is dated 2026-04-17. What moved was the surface the shopper touches.
That is the strongest available argument for backing your data rather than a protocol. Inside a single quarter, the leading in-chat checkout experience was rebuilt around a different entry point, and the endpoints WooCommerce shipped in April were written against a target that had already shifted in March. A store that spent that quarter getting its catalog right lost nothing. A store that spent it integrating against a checkout surface would have rebuilt.
Worth noting alongside it: WooCommerce’s own agentic commerce page still lists both ACP and UCP as coming soon, and the concrete advice it gives merchants has not changed — structured product data, clean and accessible pages, the Stripe extension installed so the switch is quick, and the catalog synced to Google Merchant Center. Google’s Agent Payments Protocol (AP2), the rail that proves a human authorised a specific purchase within a spending limit, published 16 September 2025, sits in the same waiting room.
Five checks to run on your own store this week
None of these require a developer, a new plugin, or a decision about the future of retail. They take about twenty minutes.
1. Confirm what version you’re actually on
Not what you think you’re on. WooCommerce → Status, or wp plugin get woocommerce --field=version. Anything below 10.7 and the rest of this list is theoretical for you.
2. Ask your live store whether the endpoints are switched on
This one takes ten seconds and needs no server access. Open https://yourstore.com/wp-json/ and search the page for agentic.
If wc/agentic/v1 appears in the namespace list, an eligible gateway exists and your store can already be checked out by an agent. If it does not appear, the code is sitting there dormant — which is the far more likely result today, and is exactly what I got on my own store.
That single string is a better answer than any vendor roadmap, because it describes your store rather than the product category.
3. Ask your payment gateway one specific question
Not “do you support AI.” Ask: does your gateway declare the agentic_commerce feature, and implement get_agentic_commerce_provider() and get_agentic_commerce_payment_methods()? That question has a yes or no answer, and support teams cannot fog it. Everything downstream depends on it.
4. Read your own product data the way an agent will
An agent does not see your theme. It does not see the size chart you put in a tab, the shipping note in your footer, or the caveat you wrote in an image. It sees fields. Open three of your best-selling products and read only the structured data — title, price, stock status, attributes, short description. If a human could not decide from that alone, an agent cannot either.
5. Decide what an agent is allowed to do before one asks
Can it commit stock you do not have? Apply a coupon it inferred? Promise a delivery window? These stop being hypothetical the moment a completion endpoint can book an order without a browser. Write the answers down now, while it costs nothing.
What the data says about shoppers who arrive from AI
The reason to do the boring work is that the traffic stopped being a novelty.
Adobe Analytics has been tracking AI-referred retail traffic across more than a trillion visits to US retail sites, and the trajectory is the whole argument. In July 2024, visitors arriving from AI assistants converted 43% worse than other channels. By February 2025 the gap had closed to 9% worse. By May 2026 the same traffic converted 54% better than other channels, with volume up 138% year over year, 53% more time on site, and 23% more pages per visit.
Two years ago this was curiosity traffic. Now it is intent traffic that arrives pre-qualified, because something already did the comparison work before the click.
That is also the uncomfortable part. If an assistant is doing the comparison, then the quality of what it can read about your products is your storefront. The theme you spent three weeks on is not in the loop.
Where my own store landed
I run a WooCommerce shop, and I have spent the last stretch building an AI agent for stores like it, so I had every incentive to find something urgent in 10.7 and did not.
My store is on 10.7.0. I ran check two against it, and wc/agentic/v1 is not in the namespace list. The endpoint files are on disk; the routes are not registered; no gateway on my store qualifies. Nothing about my checkout changed on 14 April, and nothing about yours did either unless your payment provider has already done the work on its side.
But the same REST index gave up something more interesting. Sitting in it were three routes I had not gone looking for:
/wc/v3/wc_paypal/agentic-beta-banner/dismiss
/wc/v3/wc_paypal/agentic-beta-banner/remind
/wc/v3/wc_paypal/agentic-beta-banner/applyThat is PayPal’s WooCommerce plugin, already shipping the opt-in surface for an agentic beta — dismiss it, be reminded later, or apply — inside the plugin that runs my checkout. It is not the core feature declaration, and the namespace is still absent, so nothing is live on my store. But it answers the question the core code leaves open: the gateways are not waiting for the standards fight to settle. They are building the enrolment flow now.
What did change is the deadline. The plumbing is now in core, on four million stores, and the only remaining variable is when a payment provider flips the switch. When that happens, the stores whose catalogs are accurate will be sellable by agents and the stores whose catalogs are not will be confidently misrepresented by them. That work — the product data, the stock truth, the answers to questions nobody wrote down — takes months and cannot be bought in a hurry.
So the honest conclusion is unexciting and worth acting on: nothing is urgent today, and the thing that will be urgent takes a long time to fix.
Try this on us, and on everyone else
The five checks above are the useful part of this article, not the vendor writing it. Run them on your own store this week. Then, if you are evaluating any AI agent — ours or one of the alternatives — run check four against the demo: ask it something that is only answerable from live product data, and watch whether it looks it up or improvises.
We published the stock test we use ourselves for exactly that, and a comparison against Tidio and Intercom that includes where we lose. If you want the mechanics of how an agent connects to a WooCommerce store in the first place, that is written up here.
The tests are the useful part. Use them on whoever you end up choosing.
For another feature that shipped into WooCommerce core with a limitation the release notes skip, see our source-verified read of the built-in abandoned cart email in WooCommerce 11.
Sources
- WooCommerce 10.7.0 plugin source, read directly on 31 July 2026:
src/StoreApi/Routes/V1/Agentic/,src/StoreApi/RoutesController.php,src/Enums/PaymentGatewayFeature.php,src/StoreApi/Utilities/AgenticCheckoutUtils.php,src/Internal/Features/FeaturesController.php. - Live REST API index of my own WooCommerce 10.7.0 store, read 31 July 2026:
wc/agentic/v1absent from the registered namespaces; the threewc_paypal/agentic-beta-bannerroutes present. - WooCommerce Developer Blog, “AI & Agentic Commerce in WooCommerce” roadmap, 3 October 2025.
- Digital Commerce 360, “OpenAI shifts checkout plans in its agentic commerce strategy,” 6 March 2026 — reporting The Information and the Shopify president’s 3 March 2026 remarks; OpenAI spokesperson quotes on Instant Checkout moving to Apps and on ACP’s continuing role.
- WooCommerce, “Agentic Commerce” — protocol status page listing MCP as shipped and both ACP and UCP as coming soon, with the merchant preparation checklist. Read 16 August 2026.
- Google, Agent Payments Protocol (AP2) specification, published 16 September 2025.
- WooCommerce Developer Blog, “WooCommerce 10.7: What’s coming for developers,” 9 April 2026. Release date 14 April 2026.
- WooCommerce, “Stripe’s Agentic Commerce Suite launching with WooCommerce support from day one,” December 2025.
- Stripe, Agentic Commerce Suite announcement and the open-source Agentic Commerce Protocol, co-developed with OpenAI.
- Search Engine Journal, “WooCommerce Is Integrating Agentic AI Capabilities,” 15 December 2025.
- Adobe Analytics, AI-referred US retail traffic, based on more than one trillion visits: July 2024, February 2025 and May 2026 readings.
