What does a UCP agent find at your store?
We read the UCP profile at /.well-known/ucp, check it against the release it declares, call the services it lists, and show what we found and what to fix.
The status page. The verdict on your store, every finding with the spec rule it comes from, how your store answered each way in, and your UCP profile exactly as served.
The score page. Your UCP Score and how it is made, the fixes that raise it with copy-ready code, and the spec rules it doesn’t count yet. Only a store whose UCP profile we could read gets a score.
What we check at your store
There are five ways a UCP agent can reach a store. We try each one, record every request we make, and show what each one met. Shown here on an example store that offers all five; your result shows what your store met.
6 requests · 350 ms at the store · public requests only
-
Finding the profileOpen
-
Acting for the buyerOffered
-
In the buyer's browserDeclared
-
Calling its servicesOpen
-
Sending the buyer to the websiteOffered
- 2 requestsFinding the profile/.well-known/ucp · 200
- read from profileActing for the buyerdeclared · accounts.yourstore.com
- not calledIn the buyer's browserEmbedded · declared
- 2 requestsCalling its servicesREST, MCP · answered
- read from profileSending to the websitedeclared · /buy
- 2 requestsOutside UCPhomepage · /llms.txt
- 01 PROFILEGET /.well-known/ucp → 200, 3.0 KB of JSON120 ms
- 01 PROFILEGET /robots.txt → allows /.well-known/ucp–
- 01 PROFILEValid against the 2026-08-25 schema; keys publishedlocal
- 04 SERVICESPOST /mcp tools/list → 200140 ms
- 04 SERVICESGET /ucp → 20090 ms
- 03 NOTEEmbedded service declared; not called by this check–
- OUTSIDE UCPGET / → 200, Organization schema found–
- OUTSIDE UCPGET /llms.txt → 200, 2.3 KB–
- Verified
- The store publishes a UCP profile that is valid against the release it names. It doesn’t mean every agent purchase works: that shows only when an agent tries.
- Invalid
- We found a profile, but it breaks the release’s rules, for example a missing field or broken JSON. The result lists what to fix.
- Not Detected
- Nothing at
/.well-known/ucp, usually HTTP 404. The result shows how a UCP profile starts. - Blocked
- Our request was refused (HTTP 401 or 403), or robots.txt disallows it. That is what our checker met, not how the store treats other agents.
- Unreachable
- No answer: a timeout, a DNS or certificate error, or a server error (5xx).
- Pending
- In our list but not checked yet. Check it here to run it now.
