Agents started buying. What your site has to say about itself now
Most discussion of AI agents stops at the demo: something books a flight, something fills a form. The interesting part started in January, when the plumbing got standardised — and standards are what turn a demo into a channel.
TechCrunch reported the announcement on 11 January 2026:
The standard lets agents work across different parts of customer buying processes, including discovery and post-purchase support.
Ivan Mehta, Google announces a new protocol to facilitate commerce using AI agents, TechCrunch
The Universal Commerce Protocol was, in TechCrunch’s words, “developed with companies like Shopify, Etsy, Wayfair, Target, and Walmart” — which is the detail that separates it from the usual protocol announcement. The buyers signed up before the launch.
The stated problem it solves is integration sprawl: rather than a merchant wiring up a connection per agent, one standard “could facilitate these various parts of the process instead of requiring connections with different agents”.
Why this concerns B2B, and not only retail
The launch partners are retailers, so the easy conclusion is that this is an e-commerce story. It is not, for one structural reason: the protocol does not describe shopping. It describes how a machine discovers what you offer, on what terms, and how it proceeds.
Every B2B company already has that information. It is scattered across a services page written for humans, a PDF rate card, an email thread, and someone’s head. None of it is addressable by a machine.
UCP sits alongside the other agent protocols — MCP, A2A, agent payments — and together they describe a stack whose assumption is that the counterparty is software. The question that follows is not “will we sell through an agent”, which for most B2B services is no. It is “can a machine acting for a buyer find out what we do, what it costs, and how to start” — because that machine is increasingly the thing doing the shortlisting.
What that means in practice
Your catalogue has to exist as data. Not as a page describing your services warmly. As structured, unambiguous statements: what the service is, what it includes, what it costs or how the price is formed, what the delivery time is, who it is for. If your pricing is “contact us”, you are not on the shortlist a machine assembles — you are the option it cannot evaluate.
Ambiguity is now a cost, not a negotiating position. “Every project is unique” has always been true and has always been a way of avoiding a number. A model reading your site has no way to represent it, so it represents the competitor who published a range.
The integration work is the moat, and it is unglamorous. Catalogues, identifiers, availability, terms — the same tedious data hygiene that made e-commerce work, arriving for services. Whoever does it early is legible to agents while everyone else is still writing hero copy.
What we would actually do first
- Write the catalogue down as data, even before anything consumes it. One row per service: name, scope, price or price mechanism, lead time, prerequisites.
- Mark it up. Structured data for services and offers, so the machine reading the page does not have to infer it from prose.
- Decide the price question honestly. If you will not publish a number, publish a mechanism — a range, a starting point, a formula. Something that survives being quoted.
- Leave the protocol itself alone for now. UCP is aimed at merchants with checkouts. The preparation that pays off is the data underneath it, which is useful regardless of which protocol wins.
The honest position
Nobody is buying consulting through an agent today, and it is not obvious that they will. Protocols announced with a roster of launch partners still fail. What is not speculative is the direction: the entity reading your website is more often a machine that must summarise you accurately, and every step toward being machine-legible is a step you would want anyway.
That is the recurring shape of this whole period. The defensive move and the useful move happen to be the same one.
Source: Ivan Mehta, “Google announces a new protocol to facilitate commerce using AI agents”, TechCrunch, 11 January 2026.
