The Agent Checks Out Now: What the Agentic Commerce Protocol Does to Your Feed

The Agent Stopped Recommending and Started Buying

For two years we optimized to be the answer. That was the wrong finish line. The Agentic Commerce Protocol, the open standard OpenAI and Stripe put into the wild, moved the finish line from the recommendation to the receipt. An agent now reads a buyer's constraints, checks them against your catalog, builds a cart, and completes payment without a human ever loading your product page. If you are not eligible at the feed layer, you are not in that transaction. Being the best answer no longer matters if the agent cannot buy what you sell.

This is the shift I have been telling clients to prepare for, and it happened faster than the pretty roadmaps suggested. Let me be specific about what changed, why your feed is now the product, and what to do about it this quarter.

Three Standards, One Reality

You do not need to memorize the alphabet soup, but you should know the shape of it. Three protocols are fighting to own how agents transact:

• ACP, the Agentic Commerce Protocol from OpenAI and Stripe, powers Instant Checkout inside ChatGPT. Its first live surface let sellers complete a purchase without the buyer leaving the chat.
• UCP, Google's universal approach, added cart, real time catalog queries, and identity, turning a static feed into something an agent can interrogate live.
• Agent Pay and agentic tokens from the card networks handle the money. A scoped token carries the buyer's limits: max spend per session, allowed merchants, session lifetime. The card number never touches the agent or, in the tokenized flow, you.

The plumbing differs. The demand on you is the same. Every one of these standards reads structured commerce data and decides, in milliseconds, whether your product qualifies. This is the natural extension of what I covered in when search books the job for agentic local search, except the job is now a checkout and the stakes are a completed sale.

Your Feed Is Not Marketing Anymore. It Is Inventory the Agent Can Underwrite

Here is the mental model that matters. In classic SEO, your feed helped a human find and evaluate a product. In agentic commerce, your feed is the interface the agent shops. It is not a billboard. It is an API the machine reads to answer a purchase question that already has hard rules attached.

Buyers are handing agents constraints, not keywords. "Under 80 dollars, ships to a locker, returnable within 30 days, in stock today." The agent matches those constraints against your feed fields and eliminates anything that cannot prove compliance. Miss a field and you do not rank lower. You are simply removed from consideration before the comparison starts.

That is a different failure mode than we are used to. There is no page two. There is a shortlist of merchants who answered the machine's questions and a silence for everyone who did not. I made this argument in general terms when I wrote about what happens when agentic search completes the task instead of sending the click. Commerce is where that argument stops being theoretical and starts touching revenue.

The FEED Standard: A Four-Part Eligibility Audit

Use this checklist to grade your catalog. I call it the FEED standard because that is exactly where the work lives now.

F is for Fields. Can an agent retrieve a full, deep record per SKU? Not a title and a price, the whole thing: product ID, title, description, canonical URL, price, sale price, live inventory, primary and secondary images, variants, and the attributes that describe the actual thing. If a human comparison shopper would ask it, the agent will expect it as a field. Sparse feeds get filtered.

E is for Eligibility signals. These are the compliance facts the agent uses to qualify you: returns window, return method, warranty, shipping cost, delivery windows, cutoff times, pickup and locker options, and any location constraints. This is the newest and most neglected layer. Merchants who treated returns and delivery as fine print are discovering those are now ranking factors for whether the sale is even offered.

E is for Endpoints. Discovery gets you recommended. Transaction gets you paid. To capture the full experience you need the checkout and payment components the protocol expects, not just a product feed for browsing. Decide deliberately whether you want to be a source the agent cites and links, or a merchant the agent can complete a purchase with. Those are different integrations with different revenue.

D is for Data freshness. Agents assume real time. A price or stock level that is a day stale is not a minor error, it is a broken promise that gets your feed distrusted or dropped. Stale inventory that triggers a failed agentic checkout is the fastest way to lose eligibility, because the protocol is built to punish merchants who cannot fulfill what they advertised.

Grade each SKU across those four. The products that pass all four are the only ones truly in the game. Everything else is visible to humans and invisible to the buyers who never open a browser.

What This Does Not Change

I promised numbers over noise, so here is the honest boundary. Agentic commerce does not repeal the fundamentals. Structured data still does the translating, and if you have not internalized why schema markup is the translation layer for machines, the feed work will feel harder than it is, because it is the same discipline applied to a new consumer. Reviews, ratings, and returns still shape trust, they just get read by an agent instead of a shopper. Clean catalog architecture, accurate pricing, and honest fulfillment promises were always the job. Agents simply automated the punishment for getting them wrong.

The teams that already run disciplined product data are not scrambling. The teams that treated the feed as an afterthought owned by whoever had spare time are the ones exposed. This is the same story I told in generative search optimization for ecommerce: the merchants who win the machine layer are usually the ones who never let their fundamentals rot.

What To Do This Quarter

You do not need a task force. You need a sequence.

1. Inventory your feed against the FEED standard. Pull a random sample of SKUs and ask, for each, whether an agent could retrieve 30-plus meaningful attributes and prove your eligibility signals. Where you go silent, so does the agent.
2. Fix the eligibility layer first. Returns, shipping, delivery windows, and stock accuracy are the fields most likely to be missing and most likely to disqualify you. This is the cheapest, highest-leverage repair available.
3. Make a build-or-cite decision. Choose whether you are integrating for full checkout or feeding for discovery, and staff accordingly. Half a decision here gets you the cost of both and the benefit of neither.
4. Instrument the new channel. Traffic and clicks will undercount agent-driven sales by design. Decide now how you will attribute a purchase that never touched your site, or you will argue about a channel you cannot see.

The Honest Bottom Line

The recommendation was the old prize. The transaction is the new one, and the Agentic Commerce Protocol handed the keys to whoever keeps the cleanest, deepest, most honest feed. That is not a technology problem you buy your way out of. It is operational discipline, and it rewards the teams who never mistook their product data for someone else's job.

If your catalog is throwing off more questions than answers, the channel here is open by introduction. Bring me your feed and a hard question, and we will find the SKUs that are quietly getting filtered out before the buyer ever decides.