Agentic Commerce Readiness: What Changes When an AI Agent Builds the Shortlist
Assistants now retrieve, compare, and eliminate options before a buyer sees a single result. The five-layer Agent Readiness Score, where ACP and AP2 actually fit, and the sequencing error that has most teams building the last layer first.
TL;DR
- Agentic commerce is a shortlisting problem before it is a checkout problem. The agent eliminates options before the human sees them, so the commercially decisive event happens upstream of your site.
- The Agent Readiness Score grades five layers — Retrieval, Representation, Verification, Transaction, Attribution — 0 to 3 each, 15 maximum. Under 6, agent-mediated demand cannot reach you at all.
- Two protocols matter and they solve different problems: ACP (OpenAI and Stripe) standardises agent checkout; AP2 (Google, 60+ launch partners) standardises payment authorisation and liability.
- The sequencing error is universal: teams start at the Transaction layer. Protocol support is worthless if you were never shortlisted, and it is the layer most likely to change underneath you.
- This is not only a retail problem. In B2B SaaS and professional services the agent rarely buys, but it decides who gets evaluated — the more valuable position.
- Expect measurement distortion. Agent-mediated demand lands as direct or branded search, so existing channel reports will understate it and misattribute the credit.
The Shortlist Moved Upstream
For twenty years the contested ground in digital acquisition was a results page. A buyer typed a query, saw ten options plus ads, and chose which to click. Every discipline that grew up around that moment — SEO, paid search, conversion rate optimisation, landing page testing — assumed the buyer would personally see a set of candidates and personally narrow it.
Agent-mediated buying removes that assumption. When someone asks an assistant to find a project management tool under a certain seat price with SOC 2 compliance and a Slack integration, the assistant retrieves candidates, checks each against the stated constraints, discards the ones that fail, and returns three. The buyer never sees the twelve that were discarded, and never learns why. There is no impression to optimise, no click-through rate to improve, and no landing page to test, because elimination happened before any of those existed.
This is a different failure mode from ranking poorly. A brand that ranks tenth is still visible to a determined buyer. A brand whose price is rendered client-side, whose availability is stale, or whose compliance posture is stated only in a PDF is not ranked low — it is absent from the comparison entirely, because the agent could not verify it against the constraint and dropped it rather than guess.
The scale estimates vary widely and should be treated as directional, but the direction is consistent. McKinsey has projected that agent-coordinated purchasing could touch roughly $900 billion to $1 trillion in US retail revenue by 2030, and several trillion globally. What matters operationally is not the number but its implication: a meaningful and growing share of purchase consideration is now filtered by software that reads your data rather than your marketing.
The Agent Purchase Path
Before scoring readiness it helps to name the stages, because most teams optimise one of them and assume they have covered the rest. An agent-mediated purchase moves through five distinct steps, and a business can fail independently at each.
1. Retrieval
The agent gathers candidates — from its index, from a live search call, from a partner feed, or from a merchant API. If your content is not fetchable by the specific crawler the assistant uses at answer time, you are not in the candidate pool. This is a robots and rendering question, not a content-quality question.
2. Representation
The agent parses what you are and what you cost. Prices, tiers, availability, specifications, and eligibility criteria must be present as structured, machine-readable facts. Prose that a human would find perfectly clear ("flexible pricing to suit your needs") is a null value to a filter.
3. Verification
The agent checks your claims against the user's constraints and against corroborating sources. Inconsistency between your site, your marketplace listings, and third-party directories reads as unreliability, and unreliable candidates get dropped in favour of ones the agent can confirm.
4. Transaction
The agent either completes a purchase, assembles a cart, or hands off to a human with a deep link. This is where checkout and payment protocols live. It is the most discussed layer and, for most businesses today, the least urgent.
5. Attribution
The resulting revenue is recorded — or, far more commonly, is not. Without deliberate instrumentation, agent-mediated demand appears as direct traffic or branded search, and the channel that actually produced it never receives credit or budget.
Stages one through three are recognisably an extension of the work covered in our guide to generative engine optimization. The difference is that GEO optimises for being cited in an answer, while agentic commerce optimises for surviving a filter. Citation rewards authority and quotability; survival rewards completeness and verifiability. A brand can be highly citable and still fail every constraint check.
The Agent Readiness Score
Score each of the five layers from 0 to 3 for a maximum of 15. The scoring is deliberately coarse — the purpose is to locate the binding constraint, not to produce a precise number.
| Layer | Score 0–1 | Score 2–3 |
|---|---|---|
| Retrieval | Client-side rendered; retrieval bots blocked or unreviewed | Server-rendered HTML; deliberate per-bot access policy |
| Representation | Price and availability in prose or images only | Valid Product/Offer JSON-LD with current price, currency, availability, identifiers |
| Verification | Claims differ across site, listings, and directories | One source of truth propagated everywhere; specifics dated and citable |
| Transaction | No path an agent can complete or hand off cleanly | Deep-linkable cart or booking; platform-level protocol support in place |
| Attribution | Agent demand indistinguishable from direct traffic | Referrer grouping, log detection, and self-reported capture in place |
Read the total as three bands. Below 6, agent-mediated demand cannot reach the business at all and no amount of downstream work changes that. Between 6 and 10, the business is findable and occasionally shortlisted but loses on verification or on transaction friction — this is where most competent mid-market teams sit today. Above 10, the constraint has moved back to conventional territory: positioning, pricing, and whether the offer is actually competitive when compared honestly against three alternatives.
That last point deserves emphasis. Agent readiness is a qualification requirement, not an advantage. Getting to 12 does not win the comparison — it earns the right to be in it. If the underlying offer loses on the merits, cleaner data simply causes you to lose faster and more often.
Where ACP, AP2, and the Rest Actually Fit
The transaction layer has attracted the most attention and the most confusion, largely because several standards launched close together and are frequently described as competitors when they mostly operate at different points in the flow.
| Standard | Backers | Problem It Solves |
|---|---|---|
| ACP — Agentic Commerce Protocol | OpenAI, Stripe | How an agent constructs, prices, and submits a cart to a merchant |
| AP2 — Agent Payments Protocol | Google + 60 launch partners | Proving a specific human authorised a specific amount; liability and consent |
| x402 / MPP and adjacent efforts | Various, incl. crypto-native rails | Machine-to-machine settlement, often for micro-value or API-metered spend |
AP2 was announced in September 2025 with more than sixty launch partners spanning card networks, wallets, and enterprise software, and uses cryptographically signed mandates so a merchant can verify that a real user consented to a specific transaction. ACP arrived through OpenAI and Stripe and reached production first via in-chat purchasing with a subset of marketplace sellers. That deployment was subsequently narrowed in early 2026 as OpenAI shifted toward an app-based model — which is the single most useful data point in this entire section.
The lesson is not that the transaction layer does not matter. It is that the transaction layer is being actively rewritten by parties who can change it unilaterally, while the layers beneath it — server-rendered facts, valid structured data, consistent claims — are stable, useful regardless of which protocol wins, and already valuable for conventional search. Build the durable layers first. For most merchants, protocol support will arrive as a platform update from Shopify, Stripe, or an equivalent, not as an engineering project.
This Is Not Only a Retail Problem
Physical-goods retail got the protocols first, so the discourse is dominated by product feeds and carts. The shortlisting mechanic, though, applies to any purchase an assistant can research — which is nearly all of them.
B2B SaaS
Buyers ask assistants to compare tools by seat price, integration coverage, data residency, and compliance certification. Pricing pages that say "contact sales" return null against every one of those filters. The tool with a published tier table gets compared; the one without gets omitted.
DTC
The closest to the retail case. Feed completeness, GTIN and identifier hygiene, real-time availability, and return-policy clarity determine whether the agent can confirm a match. Stale availability is worse than a higher price — one loses a comparison, the other loses trust.
Professional services
Assistants shortlist firms by specialism, region, and demonstrated outcomes. Service pages that describe capability without scope, sector, or engagement model cannot be matched to a constraint, so the firm is dropped in favour of one that published specifics.
Across all three, the same pattern holds: vagueness that reads as flexibility to a human reads as a missing field to a filter. Published constraints win comparisons against unpublished ones, even when the unpublished offer is better. This is genuinely uncomfortable for businesses whose pricing strategy depends on discretion, and there is no clean way around it — the choice is between being comparable and being absent.
Retrieval Access Is a Policy Decision, Not a Default
A recurring and expensive mistake: a team blocks AI crawlers wholesale to protect content from training use, and in doing so removes itself from the retrieval pool that feeds agent shortlists. These are separate bots serving separate purposes, and they deserve opposite policies.
Training crawlers ingest content to improve a model with no attribution and no traffic returned. Retrieval and agent crawlers fetch a page at answer time specifically to cite it, compare it, or transact against it. Blocking the first is a defensible commercial position. Blocking the second removes you from consideration at the exact moment a buyer is choosing. Our guide to which AI bots to allow, block, or charge covers the per-bot audit in detail, and it is worth completing before any structured-data work, since clean data behind a closed door achieves nothing.
The rendering check is equally unglamorous and equally decisive. Fetch your key commercial pages with JavaScript disabled. If the price, the availability, the tier structure, or the specification table is not in the server-rendered HTML, assume a large share of retrieval systems cannot see it — regardless of how well it renders in a browser.
Measuring It Without Fooling Yourself
Agent-mediated demand is systematically under-reported by default analytics. A buyer who was shortlisted inside an assistant, decided there, and then navigated directly or searched your brand name appears in reporting as direct traffic or branded search. The channel that produced the decision gets nothing; the channel that caught the last click gets everything.
The consequence is a budget error in both directions. Teams cut investment in the work that is actually generating consideration, and over-fund branded search that is merely harvesting it. The four-layer approach in our guide to AI search attribution — citation monitoring, server log detection, referrer grouping, and self-reported capture — transfers directly to this problem, with one addition specific to commerce: track shortlist appearance rate for your priority constraint queries, sampled on a fixed schedule, as a leading indicator that moves months before revenue does.
On economics, treat this as an infrastructure investment with a content-like payback curve. Fixed cost is concentrated up front, marginal cost per additional transaction is near zero, and the benefit compounds as more assistants index the same clean data. Judge it on twelve-month channel-level payback using the same discipline as any other acquisition channel — the reference ranges in our 2026 CAC benchmarks and the ceiling logic in the LTV:CAC framework both apply unchanged.
A 90-Day Readiness Sequence
The ordering matters more than the speed. Each phase is cheap and useful on its own terms even if agentic channels grow more slowly than expected — which is the correct way to invest under this much uncertainty.
Days 1–30 — Access and rendering
Complete a per-bot crawler audit and separate training policy from retrieval policy. Verify server-side rendering of price, availability, tier structure, and specifications on every commercial page. Score the Retrieval layer honestly.
Days 31–60 — Representation and consistency
Ship valid Product, Offer, and Service JSON-LD with current price, currency, availability, and identifiers. Reconcile every claim across your site, marketplace listings, and third-party directories to one source of truth. Publish the specifics you have been keeping vague.
Days 61–90 — Instrumentation and handoff
Stand up referrer grouping, log detection, and a self-reported capture field. Begin sampling shortlist appearance rate for priority queries. Confirm an agent can reach a completable action — a deep-linkable cart, a bookable slot, a self-serve signup — without a human intermediary.
Protocol implementation is deliberately absent from all three phases. For the large majority of businesses it belongs in a fifth month at the earliest, after the readiness score clears 10 and after the platform vendors have shipped their own support. Teams that want to automate parts of this sequence should read our guide to AI agents for B2B marketing — data reconciliation and structured-data validation are among the few workflows where agent deployment reliably pays for itself. The broader operating model sits in the Kres Labs Growth Playbook, and regional considerations for GCC businesses — multilingual product data and Arabic-language specification coverage in particular — are covered in our Dubai growth marketing engagement notes.
Frequently Asked Questions
What is agentic commerce?
Agentic commerce is any purchase where an AI assistant does part or all of the buying work on the user's behalf — retrieving candidates, comparing specifications and prices, assembling a cart, and in some implementations completing checkout. It differs from AI-assisted search in one respect that matters commercially: the agent applies filters and eliminates options before a human ever sees them. The buyer is still a person, but the shortlist is machine-made.
Is agentic commerce only relevant to ecommerce and DTC brands?
No. Physical-goods retail is where the transaction protocols landed first, but the shortlist mechanic applies to any purchase an assistant can research. B2B SaaS buyers ask assistants to compare tools on pricing tiers, integrations, and compliance posture. Professional-services buyers ask for shortlists of agencies or firms by specialism and region. In those categories the agent rarely completes a transaction, but it decides who gets evaluated — which is the more valuable position in the funnel anyway.
What is the difference between ACP and AP2?
They solve adjacent problems. ACP (Agentic Commerce Protocol), co-developed by OpenAI and Stripe, standardises the checkout flow between an agent and a merchant — how a cart is constructed, priced, and submitted. AP2 (Agent Payments Protocol), led by Google and announced in September 2025 with more than sixty launch partners including Mastercard, PayPal, American Express and Coinbase, standardises the trust and authorisation layer using cryptographically signed mandates that prove a specific human approved a specific purchase. ACP answers "how does the order get placed"; AP2 answers "who authorised it and who is liable". Merchants will likely need both, and neither has consolidated into a single winner yet.
Do I need to implement a payment protocol right now?
For most businesses, no — and this is the most common way teams waste money on agentic commerce. Protocol support is the last layer of the stack, it is the layer most likely to change underneath you, and it is worthless if the agent never shortlisted you in the first place. The sequence that holds is structured data first, machine-readable pricing and availability second, feed and API exposure third, transaction protocols fourth. Merchants on Shopify, Stripe, or a major commerce platform will mostly receive protocol support as a platform update rather than a build.
How do I know if AI agents can currently read my product or pricing data?
Run three checks. First, fetch your product or pricing page with JavaScript disabled — if the price, availability, and specifications are not in the server-rendered HTML, a large share of retrieval systems cannot see them. Second, validate your JSON-LD against schema.org Product and Offer types and confirm price, priceCurrency, availability, and identifiers are present and current. Third, confirm your robots policy does not block the retrieval and agent crawlers you actually want, which is a separate decision from your training-data policy.
What is the Agent Readiness Score?
It is a five-layer diagnostic Kres Labs uses to score how legible a business is to AI buying agents: Retrieval, Representation, Verification, Transaction, and Attribution. Each layer scores 0 to 3, for a maximum of 15. Below 6 the business is effectively invisible to agent-mediated demand; 6 to 10 means it can be found and shortlisted but loses on verification or friction; above 10 means the constraint has moved back to conventional positioning and pricing. Because the protocols and channels move quarterly, the score should be re-run quarterly rather than treated as a one-time project.
Does agentic commerce cannibalise my existing paid and organic channels?
It reallocates rather than adds. Demand that previously ran through a search results page and a landing page now runs through an assistant that may never send a session at all. The practical consequence is measurement: agent-mediated demand tends to surface as direct traffic, branded search, or an unattributed conversion, so channel reporting understates it and overstates whichever channel gets the last click. Instrument for it before you conclude that a channel has declined.
How should I measure return on agentic commerce work?
Treat it as an infrastructure investment with a content-like payback profile: high fixed cost, near-zero marginal cost per additional transaction, and a benefit that compounds as more assistants index the same clean data. Track share of shortlist appearances for your priority queries, the ratio of agent-referred sessions to conversions, and the resulting channel-level CAC. Judge it on a twelve-month payback the same way you would any compounding channel — not on the first quarter, when most of the cost lands and almost none of the benefit does.
Score Your Agent Readiness
We run the five-layer audit against your commercial pages, product data, and analytics setup — then identify the one binding constraint keeping you out of agent shortlists, and what it costs to fix.
Request Your Growth Audit