Cloudflare and Commerce.com turned on WebMCP for a large set of storefronts. Merchants can opt out.
Cloudflare says Commerce.com turned on WebMCP across nearly 100,000 storefronts on October 21. A merchant can opt out. The browser standard is still an early preview.
The short version
Cloudflare's October 21 post says Commerce.com enabled WebMCP, a browser tool surface for shopping agents, across nearly 100,000 storefronts, with a per-store opt-out. GlobeNewswire carried the companies' release the same morning. The standard is still an early preview.
A tool list instead of a guessed click
Cloudflare's October 21 post says websites were built for people, and that a shopping agent which only reads the page has to guess which control does what. WebMCP, which the post attributes to Google as a proposed browser standard, lets a page offer named tools. The agent calls the tool instead of hunting for a button. Cloudflare says the standard is still an early preview. The news is that Commerce.com asked to turn the preview on across the stores it already runs on Cloudflare.sites closing doors to agents.
Nearly 100,000 domains, as the post counts them
The post says Commerce.com uses Cloudflare for almost 100,000 domains and asked whether the preview could be enabled for all of those stores at once. GlobeNewswire's October 21 release is the companies' announcement of that switch. StartupHub's item the same hour repeats the scale. The figure is a platform count, not a count of completed purchases. Asked directly, Does the agent leave the merchant's site? The post says the tools run in the shopper's browser session on the storefront's domain, that prices and the cart stay that session's, and that checkout remains the merchant's. It does not say a third party takes the order.llm-d 1.0 routes a fleet.
The opt-out is the control the post names
Cloudflare says it built the opt-out at the edge so each merchant can refuse. A store that opts out does not receive the script. The post quotes a Commerce.com product director on the reason merchants asked: they want to be in an agent's answer, keep the shopper on the store, and avoid editing the theme by hand. That is the company's reason. It is not evidence that shoppers preferred it. The document named in the sources is the record this page will keep. The document named in the sources is the record this page will keep.what a session cannot be.
What the agent is allowed to call
The post says the tools cover product search, product details, a cart, and a checkout link, and that the same tools exist on a server-side endpoint for agents that are not in the browser. WebMCP, in this account, is the in-browser path. The server path is a separate door. Merchants are not described as choosing one and losing the other. Asked directly, Does GlobeNewswire add a measurement? It is the companies' release, retold the same morning. It is not a second store's independent test of whether an agent bought anything.Clairic returns typed values.
The session stays on the storefront
Cloudflare says the tools execute in the shopper's browser on the store's own domain, so the agent sees that session's prices and cart. Credentials are not described as leaving for a third party. Cloudflare's role, in the post, is to deliver the tool list from Commerce.com's backend. The merchant keeps the tool logic. A reader should not treat the edge script as a new place the order is charged. The document named in the sources is the record this page will keep. The document named in the sources is the record this page will keep.the distributed-cloud desk.
A preview flag is not general availability
The post lists where WebMCP can be seen today: experimental Chrome flags, an origin trial, some agent browsers, and developer tools. A storefront that exposes tools still depends on the agent understanding them. Enabling the script does not put the standard in every browser, and it does not require a shopper to use an agent. Asked directly, Can a merchant refuse? Cloudflare says the integration has an edge opt-out, so a store that opts out does not get the injected script. The post presents that switch as the merchant's control.what on-device inference keeps.
What this page will not treat as a result
No conversion rate, no error rate, and no count of agents that finished checkout appears in the three sources as a measured outcome. The record is a switch, a domain count, an opt-out, and a standard that is still preview. StartupHub is a retelling of that record. Asked directly, Is WebMCP a finished browser standard? Cloudflare calls it an experimental proposed browser standard in early preview, available behind experimental Chrome flags, in an origin trial, and in some agent browsers. Turning it on for stores does not make the standard final.an evaluation a second lab can run.
Who is in scope
Commerce.com merchants on Cloudflare, and the agents that already speak the preview. Shoppers who never use an agent are outside the change, except that an opted-in store now offers a tool surface those agents can see. A merchant who opts out is outside it by the switch the post describes. Asked directly, How many stores does Cloudflare name? The post says Commerce.com already runs almost 100,000 domains on Cloudflare, and that the companies turned the preview on for those storefronts. StartupHub repeats the figure. It is the companies' count.Futureweb.
What stays on the record
October 21, 2026. Cloudflare and Commerce.com. Nearly 100,000 domains, as they count them. WebMCP tools for search, detail, cart, and a checkout link. A per-store opt-out. The browser standard still in early preview. No purchase tally on this page. The short answer this page will stand on is this: Cloudflare's October 21 post says Commerce.com enabled WebMCP, a browser tool surface for shopping agents, across nearly 100,000 storefronts, with a per-store opt-out. GlobeNewswire carried the companies' release the same morning. The standard is still an early preview.what a license obligates.
Sources
The reports this brief is filing. Futureweb did not republish them.
Questions
Is WebMCP a finished browser standard?
Cloudflare calls it an experimental proposed browser standard in early preview, available behind experimental Chrome flags, in an origin trial, and in some agent browsers. Turning it on for stores does not make the standard final.
How many stores does Cloudflare name?
The post says Commerce.com already runs almost 100,000 domains on Cloudflare, and that the companies turned the preview on for those storefronts. StartupHub repeats the figure. It is the companies' count.
Can a merchant refuse?
Cloudflare says the integration has an edge opt-out, so a store that opts out does not get the injected script. The post presents that switch as the merchant's control.
Does the agent leave the merchant's site?
The post says the tools run in the shopper's browser session on the storefront's domain, that prices and the cart stay that session's, and that checkout remains the merchant's. It does not say a third party takes the order.
Does GlobeNewswire add a measurement?
It is the companies' release, retold the same morning. It is not a second store's independent test of whether an agent bought anything.