How we check a store
A check asks a store for its UCP profile the way an agent would, reads the answer against the store's own release, and gives it a status and a score. Here is every step, what each answer leads to, and how the score is made.
What we send
Two requests, both from UCPCheckerBot. Nothing is sent to the store but these, plus the public pages we read for the score.
GET /.well-known/ucp HTTP/1.1
Host: yourstore.com
Accept: application/json
User-Agent: UCPCheckerBot/1.0 (+https://ucpchecker.com/methodology)
Signature-Agent: sig1="https://ucpchecker.com/.well-known/http-message-signatures-directory"
Signature-Input: sig1=("@authority" "signature-agent";key="sig1");…;tag="web-bot-auth"
Signature: sig1=:…:
HTTPS onlyand only to public addresses; a redirect to http or a private network is refused2 secondsfor the profile, about the time an agent waitsUp to 3 redirectseach hop signed for its own host, and every hop shown in the check traceSigned (RFC 9421)Web Bot Auth with an Ed25519 key, so a store can verify the request is ours. About UCPCheckerBotrobots.txt firstasked as text/plain; if it disallows us, we don't fetch the profile
The path a check takes
Four steps. A store's answer either passes a step or stops there with a status.
-
1
Read the store's robots.txt
robots.txtWe ask whether UCPCheckerBot may fetch /.well-known/ucp and /. A missing, empty or unreadable robots.txt means yes.
- Disallowed for UCPCheckerBot Blocked Blocked by robots.txt. We stop and don't fetch the profile.
-
2
Ask for the profile
GETGET https://{domain}/.well-known/ucp over HTTPS, signed, with a 2 second limit. We follow up to 3 redirects, signing each hop for its own host, so we can show where they lead.
- 404 Not Detected No profile at the address.
- 401 or 403 Blocked A firewall or bot wall turned us away. We keep the answer as evidence.
- 429 No change Rate limited: we learned nothing, so the store keeps its last status (pending if it had none).
- 5xx, a timeout, DNS or TLS failure, a redirect to http or to a private address Unreachable The store didn't answer in a way an agent could use.
-
3
Read the answer
JSONA 200 must be a JSON object. The spec says the profile must not redirect. When yourstore.com only forwards to www.yourstore.com (or the other way round) and the profile is served there directly, we judge it there, and the redirect is a To fix. Any other redirect is a spec break. Neither changes the status.
- Not JSON Invalid The body isn't JSON (UCP_RESPONSE_NOT_JSON).
-
4
Check it against its release
RulesFirst the UCP project's own validator (ucp-schema) checks the profile against the schema of the release it declares. That decides whether it is valid. Our rules come on top and can only be stricter.
- Rejected by UCP's validator Invalid Doesn't match its release's schema. Each error is listed with its path.
- Missing ucp, version, services or payment_handlers, or a version that isn't YYYY-MM-DD Invalid Present but broken. Each problem is listed with its code and how to fix it.
- Accepted by UCP's validator, and everything we require is there Verified Verified. Warnings, like missing keys, are listed but don't change it.
A store we have never managed to observe is Pending, not Unreachable: we don't give a verdict we haven't observed. An attempt that observes nothing, like a rate limit, never changes a store's status, score or timing; those always describe the last answer we actually got, and every page says when that was.
What a profile must have
On top of the UCP project's validator, which checks the whole profile against its release's schema. The same at every release since 2026-01-23. (The first release, 2026-01-11, asked for capabilities in place of payment_handlers; we check the few stores still on it against the later rules.) The UCP profile guide explains each part; the UCP Validator runs these rules on a profile you paste.
ucp.versiona release date, YYYY-MM-DDucp.servicesat least one, each with its transport and endpointucp.payment_handlerspresent (empty is a warning, not a failure)
ucp.capabilitieswhat an agent may dokeysa JWK Set beside ucp (signing_keys before 2026-08-25); we accept either at every release
Releases we know: 2026-08-25 (current) 2026-04-08 2026-01-23 2026-01-11 . A profile on a release we don't know is checked against the current rules, with a warning.
How we read the web
The market read behind every figure about the wider web on /stats, the home page and the platform pages. It is separate from the daily checks of the stores we check, described above. Quote any figure with credit to UCP Checker and a link to the page and month; anything more needs our permission. Citing and reuse
- What we read
- Every month we read about 4 million ecommerce sites with measurable shopper traffic (November 2026), the same list each month, not only the stores we check. We ask each one for its UCP profile the way an agent would.
- Live sites, and what is left out
- About 3.7 million of them were live ecommerce sites. A site we couldn't reach (DNS, certificate, server error or timeout), one that turned automated visitors away, and one that isn't a live store (closed, behind a password, forwarding elsewhere, or not a store) are left out of the live count. Left out, as shares of every ecommerce site read (about 4 million): unreachable 2.5%; turns automated visitors away 4.1%; not live 1%.
- Where we look
- Every UCP profile lives at one address: /.well-known/ucp on the site's own domain. The path is registered with IANA in the well-known URI registry, the same registry as /.well-known/security.txt, so it is the standard public address any agent asks for. A site that blocks the path, or puts it behind a login, hides its profile from every agent, and from this read; the spec also says an agent must not follow a redirect there, so the profile has to answer on the domain itself.
- What counts as a UCP profile
- A UCP profile counts when the site serves it publicly at /.well-known/ucp and it passes the official validator; a profile behind a login or a bot wall can't be counted.
- How often
- Once a month, over the same list of sites, so one month compares with the next. Every figure from the read carries its month; a month-on-month change inside the margin says so.
- What each share is of
- Every share of the web is of the live ecommerce sites (about 3.7 million live ecommerce sites). Shares of what a profile declares (capabilities, releases, transports) are of the sites with a valid public UCP profile (about 1.2 million sites with a valid public UCP profile). The one chart of every site read is of all sites read, and says so. A true zero reads "none"; a share above 0 and below 0.1% reads "under 0.1%", and one above 99.9% but below 100% reads "over 99.9%", except Shopify, whose shares above 99.9% read 100%: it serves the profile on every store, and the few read without one are edge cases. A group of fewer than 20 gets no share. The stores we check are described by shares only, never counted. We measure what a profile declares, not what a store can do.
- Which shares are least certain
- We read as a verified, signed bot. The biggest sites are the hardest to reach, so more of them are left out of the live count, and the shares for the top traffic bands are the least certain.
Why the address matters for a store: /.well-known/ucp is now in IANA's registry › · the fields and common mistakes: the UCP profile guide ›
The UCP Score
A number from 0 to 100: three areas, each scored 0 to 100, weighted and added. It describes the last answer we got. Model 1.0.0.
Discovery
Can a UCP agent find and read the profile: HTTPS, an answer at /.well-known/ucp, robots.txt allowing it, and five files outside UCP (llms.txt, sitemap, Open Graph, Organization schema, viewport).
Conformance
Does the profile follow the spec: valid against its release (counted three times), a dated release, keys published, few warnings, spec and schema links that resolve.
Capabilities
What an agent can do here: how many capabilities, checkout, at least one service, payment handlers, and services that answer our check.
Four stores, scored
Scored here by the model itself, before the services check.
Valid profile at the current release with keys, six capabilities including checkout, three transports, a payment handler, and all five files.
Valid profile with checkout only, one transport, no keys, and none of the five files.
A profile is there, but payment_handlers is missing and there are three other warnings. Two of the five files.
The profile exists, but a bot wall answers 403. Robots.txt allows us and the five files are there.
A store that's blocked, unreachable or has no profile scores 0 for Conformance and Capabilities. A pending store has no score yet.
What else a check reads
/llms.txtanswers, isn't empty and isn't an HTML page/sitemap.xmlis a real sitemapOpen Graphog:title, with og:type or og:urlOrganization schemaJSON-LD naming the businessviewportthe mobile viewport tag
A file behind a bot challenge page or a rate limit, or a request that got no answer at all, is not assessed and left out of the score, never counted as missing. We also note newer agent files, like agents.md or an MCP server card, when they're there. They aren't scored.
MCPa tools/list call to each declared MCP endpointRESTa read-only search_catalog (or search_locations) call, when the profile declares catalog (or location) search; otherwise the service is shown as declared, not calledLinksevery spec and schema URL in the profile
Read-only: nothing is created, carted or bought. The results count for 20% of Conformance (links) and of Capabilities (services).
One store, one address
Whatever is typed, a store has one page. We trim it, drop the scheme, the path and a leading www., drop a pasted profile filename, and lowercase it.
https://www.YourStore.com/products/hatyourstore.com/status/yourstore.com
What it costs
The check, the score, the status pages and the validators are free, with no sign-up. To be gentle on stores, each store is checked live at most once every 10 minutes, whoever asks, our own daily check included: inside that window you see the latest result and when it can be checked again. A shared limit on live checks across the site keeps them fair for everyone; when it's reached, we ask you to try again in a minute.
