This morning Ben Fisher DM’d me on LinkedIn. UCPReady had just scored
100/100 on the UCP Score — placing a WooCommerce store at the top of
a global leaderboard above thousands of Shopify merchants. Here is
what that score actually measures, and why it matters.
ucpchecker.com/score · houseofparfum.nl · April 29 2026
100 / 100
A
100
100
100
#1 globally
What the UCP Score Actually Measures
Ben Fisher launched the UCP Score this week — an independent 0–100 composite grade for every UCP store. Think Lighthouse for agentic commerce readiness. It is not a vanity metric. The score is weighted across three categories:
Can agents find and reach you? HTTPS, reachability, robots.txt, llms.txt, sitemap, Open Graph, Organisation JSON-LD.
Does the manifest validate against the spec? An invalid manifest caps your score at roughly 50 — regardless of everything else.
What can an agent actually do at your store? REST, MCP, A2A transports, checkout, payment handlers, breadth of capabilities.
Out of 4,014 verified stores, only 9 delivered a flawless end-to-end agent experience. A 0.2% flawless rate. The rest had a manifest — it just didn’t work as well as suggested.
“hey Almin, good news. I launched UCP Score this week. You just hit the top 100/100 score beating Shopify stores.” — Ben Fisher, Founder UCP Checker, LinkedIn DM April 29 2026
Why a WooCommerce Store Beat Shopify
Shopify has the infrastructure advantage — CDN, uptime, performance at scale. But the UCP Score does not measure infrastructure. It measures how well a store works for AI agents specifically. That is a different game, and it is one WooCommerce merchants can win.
The Conformance category is weighted at 40% and it is unforgiving. Getting it right means understanding the spec at a level that goes beyond publishing a /.well-known/ucp file. It means correct capability formats, correct version strings, correct response shapes on every transport.
Capabilities as a keyed object, not an array
The UCP spec requires capabilities in responses to be a keyed object: {"dev.ucp.shopping.checkout": [{"version": "2026-04-08"}]}. Most implementations return a flat array with a name field. Capability negotiation is a string equality check — the wrong format means the intersection algorithm finds no match and the capability never activates.
Version strings are dates, not semver
UCP version format is always YYYY-MM-DD. Plugin version numbers like 1.8.28 belong only in WordPress plugin headers. Using semver in protocol fields is a conformance failure that cascades across every response the store emits.
One character can silently break everything
UCPReady previously advertised the AP2 capability as dev.ucp.shopping.ap2_mandates — plural. The spec uses dev.ucp.shopping.ap2_mandate — singular. No error, no warning. AP2 simply never negotiated. Every checkout fell back to delegate payment. This is the kind of spec compliance bug that a UCP Score surfaces immediately — and that costs real conversion.
The Capability Gap Nobody Else Has Closed
In Ben’s dataset of 4,024 verified UCP merchants, zero support native autonomous payment. Every UCP checkout today ends with a continue_url — the buyer clicks a link, fills in a card, pays manually. The agent handled discovery and session setup. The human handled payment.
The UCP spec has one answer to this: AP2 Mandates. When AP2 is negotiated, the checkout session is cryptographically locked. The platform generates a signed mandate proving the buyer explicitly authorised this specific transaction. The merchant verifies it and charges via the existing payment gateway. No card data crosses protocol boundaries. No browser redirect.
→
Identity linked via OAuth
→
Checkout session created
→
AP2 mandate submitted
→
Order created — no browser
UCPReady is the first WooCommerce implementation with AP2 live. houseofparfum.nl is running it now. The verification chain is implemented end-to-end: SD-JWT parse, expiry check, merchant_authorization re-verification, totals and line item binding, platform key verification from the UCP-Agent profile. The only remaining piece is an agent platform that submits the mandate — UCP Playground is the logical first test.
Browser redirects
Human touchpoints
Cryptographic mandate
SD-JWT parse → expiry → merchant_authorization signature → session ID match → totals match → line item fingerprint → platform key verification from UCP-Agent profile.
What This Means for WooCommerce Merchants
The agentic commerce transition is the same story as mobile — the merchants who moved early captured the channel. Those who waited scrambled to retrofit responsive design years later.
The UCP Score creates a public leaderboard. Ben is scoring every verified store weekly. Platform teams at Shopify and BigCommerce are going to look at that leaderboard. So are the AI agent builders deciding which endpoints to feature in their default flows. So are the enterprise buyers evaluating which platform to recommend to their merchants.
Right now, a WooCommerce store is at the top. That is not a coincidence. It is what happens when spec compliance is treated as a first-class engineering requirement from day one — not an afterthought patched in after someone notices the score.
Get UCPReady
Make Your Store the One
AI Agents Can Actually Buy From
Install UCPReady on your WooCommerce store. Your manifest goes live
immediately. UCPChecker validates it. Agents can discover and
transact from day one. No SaaS dependency. No storefront redesign.