Research · Q3 2026
Declared is not payable.
Between 29 June and 31 August 2026, storefronts declaring themselves agent-ready grew 67%. Over the same nine weeks, the number declaring embedded checkout, the capability an agent needs to complete a purchase without a human, went from two to one.
This is the reading behind that, the spec migration that landed in the last week of it, and what happened when we tried to buy something.
Supply is arriving. Payability is not.
Verified storefronts went from 9,534 to 15,942 across ten weekly readings. Domains under monitoring went from 11,097 to 19,540. On any ordinary adoption chart this is a market forming quickly.
The capabilities that gate an actual autonomous purchase did not follow. Identity linking moved from 16 to 29. Buyer consent from 6 to 12. AP2 mandate from 5 to 9. Embedded checkout went from 2 to 1.
Two readings move backwards and we have left both in place: verified merchants fall from 13,100 to 13,012 between 27 July and 3 August, and AP2 mandate falls from 10 to 8 between 3 and 10 August. Both are upstream corrections in a dataset that is still being built.
Storefronts declaring agent-readiness
9,534 to 15,942 · +67%
max 20,000
Storefronts declaring embedded checkout
2 to 1 · -50%
max 3
| Week | Verified | Domains | Identity | Consent | AP2 | Embedded |
|---|---|---|---|---|---|---|
| 2026-06-29 | 9,534 | 11,097 | 16 | 6 | 5 | 2 |
| 2026-07-06 | 11,332 | 12,896 | 13 | 8 | 6 | 2 |
| 2026-07-13 | 11,959 | 13,761 | 15 | 8 | 7 | 1 |
| 2026-07-20 | 12,633 | 14,566 | 15 | 7 | 7 | 1 |
| 2026-07-27 | 13,100 | 15,865 | 14 | 7 | 9 | 1 |
| 2026-08-03 | 13,012 | 16,619 | 21 | 7 | 10 | 1 |
| 2026-08-10 | 14,260 | 17,280 | 25 | 9 | 8 | 1 |
| 2026-08-17 | 14,633 | 17,889 | 27 | 9 | 9 | 1 |
| 2026-08-24 | 14,881 | 18,355 | 28 | 12 | 9 | 1 |
| 2026-08-31 | 15,942 | 19,540 | 29 | 12 | 9 | 1 |
Ten thousand storefronts changed spec in one week
Spec version 2026-08-25 does not appear in the 24 August reading at all. Seven days later it carries 10,434 storefronts, while 2026-04-08 drops from 14,855 to 5,480.
Storefronts do not migrate a protocol version on their own initiative at that rate. Something pushed it. The cohort size is also within 200 of the group declaring cart, discount and order management (10,644 / 10,635 / 10,633), which has moved as a single block since June, and the capability labels themselves were renamed in the same reading.
This is a question, not a conclusion. We are probing across both spec versions to find out which platform moved and whether anything about payability changed with it. That result will be its own note.
24 August 2026
14,881 storefronts
- 2026-04-0814,855
- 2026-01-1113
- 2026-01-2311
- 2026-01-141
- 2025-01-011
31 August 2026
15,940 storefronts
- 2026-08-2510,434
- 2026-04-085,480
- 2026-01-1114
- 2026-01-2312
The cliff is between announcing and transacting
In the 31 August reading, capability adoption falls into three clear tiers, and the distance between the second and the third is the whole story: sixteen thousand storefronts declare checkout, ten thousand declare cart and order management, and twenty nine declare identity linking.
Read carefully, because this is easy to draw wrong. These counts come from a wider population than the verified set (checkout reads 16,095 against 15,942 verified merchants), so no tier is a subset of the tier above it. They are siblings to compare, not stages in a funnel.
Capability adoption, 31 August 2026
15,942 verified merchants
Declared by nearly every storefront
- Checkout16,095
- Fulfillment16,054
- Catalog search16,030
- Catalog lookup16,026
Declared by one large cohort
- Cart10,644
- Discount10,635
- Order management10,633
The primitives autonomous purchase actually needs
- Identity linking29
- Buyer consent12
- AP2 mandate9
- Embedded checkout1
Not a funnel. These counts are taken over a wider population than the verified set (Checkout reads 16,095 against 15,942 verified merchants), so no tier is a subset of the one above it. Compare tiers, not stages.
The second tier sits within 200 of the 10,434 storefronts that moved to spec 2026-08-25 in a single week. Same block, most likely one platform.
What happened when we tried to buy something
Declared capability and real capability are different things and the only way to know the difference is to try. Every finding below carries the date it was run. All of them predate the 25 August spec, which is exactly why we are re-probing.
Shopify gates autonomous checkout by design, not by rollout
probed 25 June 2026We built an agent client, authenticated at Shopify’s highest self-serve tier, and ran live checkout probes against third-party merchants and against our own store. Every path returned
checkout_completion_ineligible, including our own. The own-store control is the point: it separates "not rolled out yet" from "gated to Participating Channels".The first native Wix UCP storefronts were shoppable, not payable
probed 29 June 2026Within days of the first native Wix manifests appearing we probed the cohort store by store: 10 storefronts across 9 distinct sites. Every one declared the same four capabilities (checkout, fulfillment, catalog search, catalog lookup) and every one had an empty
payment_handlersarray. Several returnedunauthorized; others were unconfigured, one shipping a sample product literally titled "I’m a product".Roughly 88% of agent-ready supply sits on one platform
probed 25 June 2026A fleet scan across 3,000 candidate domains skipped 2,652 as Shopify against 342 without a usable manifest. The non-Shopify tail is thin, which is why a platform-level move matters more than any individual merchant signing up.
The distributor side is walled at settlement, not at discovery
probed 30 June 2026CJ Dropshipping settles only from a CJ-held balance with no API top-up path, so every payment mode is platform-fronted. Mouser requires an account opened on the buyer’s behalf. Both are reachable by an agent and neither is payable by a neutral one.
Declared AP2 support is mostly developer test sites
probed 11 July 2026Of the handful of domains declaring AP2, most are developer or sandbox targets, and none properly enabled checkout against it when probed. Declared is not payable, and the gap between the two is the entire finding.
What is wrong with this data
A number is worth what its provenance is worth. Here is what we would push back on if someone else published this.
- The grade distribution does not discriminate. In the 2026-08-31 reading, 14,690 of 15,942 verified stores score an A, 1,251 score a B, exactly one scores a C, and nothing scores below that. A score where 92% of the population lands in the top band is measuring presence, not quality.
- Capability counts exceed the verified merchant count, so the two are drawn from different populations. We compare tiers against each other and never present them as a funnel.
- The series is transcribed by hand from a weekly public report. There is no automated collection behind it, and two readings contain upstream corrections we have left in place rather than smoothed.
- Every Conduit probe finding on this page was run between 2026-06-25 and 2026-07-11, before the 2026-08-25 spec landed. They are dated individually and should be read as a snapshot of that spec era.
Our opinion
What we think this means, stated as opinion
The consumer-facing agentic commerce buildout is real and moving fast, and almost none of it is an executable purchase. A storefront that an agent can browse but not pay is a catalog with extra steps.
We think the gap closes on rails that were already built for machines rather than for card networks: invoices against approved terms, purchase orders, net terms.
Questions
- What is UCP (Universal Commerce Protocol)?
- UCP is an open standard, co-developed by Shopify and Google and launched in 2026, that lets AI agents discover products, negotiate capabilities, and complete checkout with any participating merchant. Conduit adopts UCP as one normalized input while keeping reputation and execution scoring neutral and cross-platform.
- What is AP2 and how do agent spend mandates work?
- AP2 (Agent Payments Protocol) lets a human approve a spend mandate once, covering limits, categories, and expiry, that an agent then transacts within. Conduit translates a single agent keypair into the mandate each merchant trusts, so autonomous payments stay inside boundaries you control and can revoke instantly.
- What happens if an agent cannot complete a checkout autonomously?
- Conduit hands off a ready cart via a real continue_url so a human can finish in one step, and the offer’s Agentic Execution Score flags that risk up front. Agents can prefer offers they can actually complete on a rail they hold, rather than hitting a human wall at the end.
- When will agentic commerce payments be possible?
- They are live now: Conduit’s Agentic Procurement MCP v1 lets AI agents discover and pay across thousands of merchants through a single MCP endpoint. v1 ships with multiple payable rails (x402 web-native crypto, cash-on-delivery (COD), and any card on merchant handoff, where a human completes checkout) within a human-approved mandate, plus a one-click human hand-off wherever a merchant still requires one. Invoice (B2B net terms) is coming soon. Fully agent-held card vault for autonomous card checkout comes later. There is no per-transaction fee between an agent and a merchant.