Agent Readiness
Your site has a new kind of visitor
Software now arrives on websites with a job to do. It reads your pages, fills your forms, and on a growing number of surfaces it completes a purchase. When it cannot, nothing tells you. There is no error in your logs and no drop in your dashboards, because from your server's point of view nothing went wrong. Someone just left.
The shift is already priced in
This is not a forecast. Two protocols shipped, and the companies that run the surfaces your customers use are building on them right now.
Commerce got a protocol
The Universal Commerce Protocol launched on 11 January 2026 with eleven co-developers, including Google, Shopify, Amazon, Microsoft, Meta, Salesforce, Stripe, Walmart and Target. Version 2026-04-08 is current. Fifty partners are listed as endorsing it, up from the twenty named at launch.
What UCP isCheckout moved onto the agent's surface
Google announced its Universal Cart on 19 May 2026, naming Nike, Sephora, Target, Ulta Beauty, Walmart and Wayfair, plus Shopify merchants. It is a limited release: as of Google's developer documentation, last updated 16 June 2026, merchants join a waitlist and integrations must be approved before going live.
The browser is growing an interface for agents
WebMCP lets a site declare typed tools an agent can call, rather than leaving it to guess from your markup. It is co-authored by Microsoft and Google, incubated in a W3C community group, and running as a public Chrome origin trial from Chrome 149 through 156, with shipping targeted at Chrome 157.
What WebMCP isThree ways this breaks quietly
Each of these produces a working website and a failing agent. That combination is what makes them hard to notice.
1. Access
Bot rules were written for crawlers. Agents are not crawlers: a person is waiting on the other end. A rule that keeps scrapers out will also turn away a customer's agent, and the block looks like ordinary bot mitigation working correctly. Meanwhile the ground is moving. From 15 September 2026, new domains onboarding to Cloudflare get defaults that block traffic classified as Agent on pages that display ads.
2. Protocol
An integration that is present is not the same as an integration that works. A profile served behind a redirect is invisible, because agents are told not to follow redirects on it. A missing cache header, a required registry left out, a capability pointing at a schema on someone else's domain: each is a small thing that produces a silent failure rather than an error page.
3. Drift
These specifications are young and they move. WebMCP already renamed its entry point once, and tutorials published earlier this year still show the old one. UCP marks breaking changes by date. Your integration was correct when you shipped it. Nothing in your build tells you the day it stops being correct.
What you can check right now
UCP checker
Reads your profile the way an agent would and reports what breaks, against the specification's own requirements rather than a presence check.
WebMCP checker
Finds tool registration, including the markup form a script scanner misses, and enumerates the tools an agent would actually receive.
Agents directory
Which agents visit, what they publish, and which ones you can actually verify. Most publish nothing.
Spec changelog
Every UCP release in plain English, with what actually changed and whether you need to do anything about it.
Run it in your own pipeline
The same checks belong in CI, so a deploy that breaks your integration fails the build instead of failing quietly in production.
View the CLI on GitHub