Five acronyms arrived in the last year and quietly started deciding which businesses AI agents are able to buy from.
ACP. UCP. AP2. Visa Trusted Agent. Mastercard Agent Pay.
You do not need to love them. You do need to know what they are, because merchants supporting more than one of these protocols are seeing roughly 40% more agentic traffic than merchants supporting a single one.
This is the plumbing layer of agentic commerce, and it is one of those rare moments where a boring technical decision has an obvious commercial consequence.
The problem all five are solving
An AI agent trying to buy something on your behalf hits three walls.
It cannot prove it is a legitimate agent acting for a real person rather than a bot scraping your inventory. It cannot reliably read your product data, because every site structures it differently. And it cannot pay, because payment systems were built on the assumption that a human is present with a card.
Each protocol is an attempt to solve one or more of those. Identity, data and payment.
The last twenty years of ecommerce assumed a human with a browser. The next ten assume a machine with a mandate. Almost none of the infrastructure transfers.
The five, in plain English
ACP, the Agentic Commerce Protocol. The most visible one, driven by OpenAI's shopping surfaces. Its current shape is discovery inside the assistant and checkout in the merchant's own environment. The agent finds the product, presents it, then hands the buyer to you to complete. Note that the earlier instant checkout model was retired in favour of this. Discovery happens in the assistant, the transaction happens on your site.
UCP, the Universal Commerce Protocol. A broader attempt at standardising how product, availability and pricing data are exposed to any agent, rather than to one platform's shopping surface.
AP2, the Agent Payments Protocol. Focused on the payment problem specifically. How does a merchant know an agent has genuine authority to spend a human's money, and who carries the liability when it goes wrong.
Visa Trusted Agent and Mastercard Agent Pay. The card networks answering the same question from their side. Both establish a way to verify that an agent is authorised, so a transaction initiated by software is not automatically treated as fraud.
The overlap is messy and the standards are still moving. That is normal for this stage and it is not a reason to wait.
Where the traffic is actually going
The share shift is worth understanding, because it tells you the game is not yet decided.
Amazon receives under 3% of ChatGPT referrals and that share has been falling. Walmart, Etsy, Target and eBay are each absorbing 10% to 20% and climbing. Over a million Shopify merchants are live on ChatGPT shopping, with Walmart and Target announced as partners.
Read that carefully. The dominant player in ecommerce search is not the dominant player in agentic commerce. When a discovery layer changes, the incumbents do not automatically carry their position across.
That is the whole opportunity for a smaller business. The shelf is being rebuilt and nobody has been given their old position back.
What to do, in the order that matters
Most businesses do not need to implement a protocol themselves. They need to be readable, then supported, then integrated. In that order.
- Fix your structured product data first. Clean schema markup on every product and service. Price, availability, specifications, shipping, returns, service area. This benefits every protocol and works today regardless of which standards win.
- Check what your platform already supports. If you are on Shopify or a major platform, a lot of this is a settings toggle and a feed, not a development project. Find out before you scope anything.
- Make sure agents can reach you. Aggressive bot blocking, interstitials, and login walls will exclude you from agentic traffic entirely. Review what your firewall and CDN are actually blocking. Plenty of businesses have quietly banned the exact traffic they are trying to attract.
- Write returns, warranty and shipping terms as plain readable text. Agents compare on these constantly and cannot read them out of a PDF or an image.
- Then support more than one protocol. That 40% traffic difference is the reason. Do not bet on a single standard this early.
If you do not sell products online
Most of this still applies, in a different shape. Service businesses are not exempt from agentic discovery, they are just at an earlier stage of it.
The agent is not completing a transaction. It is shortlisting, comparing and often booking. Which means your equivalent of product data is your service data. What you do, where, for whom, at what price range, with what availability and what guarantee.
Publish that in structured, machine readable form and you are doing the same work under a different name.
The three questions to ask your platform
You do not need to become an expert in any of this. You need three answers from whoever runs your website or store.
What structured data are we currently publishing about our products or services, and is it complete and accurate. Which agentic commerce integrations does our platform already support, and are they switched on. And are we accidentally blocking legitimate agent traffic at the firewall or CDN level.
If your developer cannot answer those quickly, that is the project. Everything else in this article can wait until those three are settled, because none of the protocols matter if agents cannot read you or reach you.
The timing question
Is this early? Yes. Standards are competing, shapes are changing, and some of these acronyms will not exist in two years.
But notice that everything on the practical list above is work you should do anyway. Clean structured data, readable terms, unblocked crawling and accurate service information all improve conventional search, AI answers and human conversion at the same time.
There is no version of the future where badly structured product data is an advantage. Do the boring layer now and whichever protocol wins, you are already legible to it.