Shopify opened checkout on its merchants' stores, including Shop Pay, to any AI agent running inside a shopper's browser on Monday — removing the need for the kind of private partnership Meta's Muse agent signed a week earlier. The catch, buried in the developer documentation rather than the announcement, is that agent support for the underlying standard is currently limited to Chromium-based browsers.
Key takeaways
- Three new WebMCP tools — get_checkout, update_checkout and complete_checkout — let a browser agent read a checkout, change the address or delivery option, and place the order after the buyer approves.
- Shopify's own docs state that agent support for WebMCP is limited to Chromium-based browsers today.
- The move runs opposite to Amazon, which blocks third-party agents from buying on a shopper's behalf.
What the three new tools actually do
Browser agents using WebMCP could already search a Shopify catalogue and fill a cart. The new tools extend that to the transaction itself: get_checkout returns the state of a checkout session, update_checkout changes details such as the shipping address or delivery option, and complete_checkout submits payment and places the order — explicitly after buyer confirmation, not autonomously.
The point is to delete the screenshot-and-click layer. Without page-registered tools, an agent has to read a store's markup and simulate clicks, which Shopify's WebMCP documentation describes as slow and error-prone. Gil Greenberg, a staff product manager on agentic commerce, wrote on X that agents operating in the buyer's browser should use these structured tools instead of navigating HTML built for humans.
How WebMCP differs from Shopify's MCP server
Shopify now runs two agent surfaces. Its hosted Model Context Protocol server serves agents that connect server-to-server. WebMCP, a proposed web standard, serves agents that live in the shopper's browser: the storefront registers tools with the browser and the agent calls them with structured inputs. Both sit on Shopify's Universal Commerce Protocol, which standardises product discovery, cart building and checkout.
The browser-side surface is now fairly wide. On the storefront, agents get ten tools covering catalogue search, collection browsing, product and variant lookup, cart reads and edits, cart clearing, order-history navigation, a policies-and-FAQ lookup, and a jump to checkout. Checkout then swaps that set for its own, and a navigate_to_storefront call brings the shopper back.
One design detail matters for merchants. Cart tools call the same Shopify.actions storefront functions that apps use, so an agent's changes behave like the shopper's own and still trigger theme behaviour such as opening a cart drawer. Everything happens in the tab the shopper is looking at, and the tools are live on every Liquid storefront and on Hydrogen developer-preview storefronts with no setup.
The partnership moat just got smaller
A week before this rollout, Shopify struck a deal giving Meta's Muse agent Shop Pay checkout across every Shopify store; an Instinct partnership was announced the same day as the WebMCP change. Opening the same capability to any Chromium-based agent means a new entrant no longer needs a named deal to complete a purchase — a notable reversal of how agentic commerce access has been rationed so far.
There is a second, quieter implication in the documentation's promise of no installation or configuration. Because the tools ship enabled on every Liquid storefront, merchants receive agent traffic by default rather than by opting in. That is the mirror image of Amazon's posture, and it means the decision about whether agents may transact in a store has effectively been made at the platform layer rather than by each seller. Shopify's incentive is legible enough: it takes a cut of checkout through Shop Pay, so more completed agent purchases are more payment volume, whereas a retailer that owns its own funnel and ad inventory loses both when an agent skips the page.
It also puts Shopify on the opposite side of a widening split. As TechCrunch noted, Amazon blocks third-party agents from purchasing on shoppers' behalf, and Adidas appears to do the same. That divide will shape which stores agents can actually transact in, not merely which products assistants recommend.
What to watch next
The Chromium limitation is the near-term ceiling: until Safari and Firefox expose WebMCP to agents, this is a Chrome-and-friends capability, and the rollout reaches eligible merchants rather than all of them. Shopify's docs also require agents to refresh the browser's tool list when the shopper moves from storefront into checkout, and to hand the buyer off to the page if checkout tools are not registered — so a smooth agent purchase still depends on the agent handling that switch correctly.
FAQ
Can an AI agent buy something on Shopify without asking me?
No. The complete_checkout tool submits the order only after buyer confirmation, and Shopify documents it as requiring that authorization step. The agent can inspect and edit the checkout freely, but the final submission is gated on the shopper.
Do merchants need to install anything to support this?
No. Shopify provides WebMCP tools on every Liquid storefront and on Hydrogen developer-preview storefronts with no installation or configuration, and the checkout tools are rolling out to all eligible merchants. Checkout registers its own separate tool set, so the available tools change when a shopper leaves the storefront.
Which browsers support agentic checkout on Shopify?
Shopify's documentation states that agent support for WebMCP is currently limited to Chromium-based browsers, which covers Chrome and Edge but not Safari or Firefox. The tools themselves are live regardless; the constraint is on the agent side of the standard.
