UCP status report
papchecker.com
No UCP profile was found at /.well-known/ucp on papchecker.com.
Not Detected
HTTP 404
Response 179 ms
Checked 22 Oct, 15:00 UTC
Check trace
How papchecker.com answered our check
Our request for the profile got no profile back, so the other four ways in were never reached.
0 of 5 reached
4 requests · 179 ms at the store · public requests only
4 requests · 179 ms at the store · public requests only
-
Finding the profileNot found
-
Acting for the buyerNot reached
-
In the buyer's browserNot reached
-
Calling its servicesNot reached
-
Sending the buyer to the websiteNot reached
UCP Checkerpublic requests
- 2 requestsFinding the profile/.well-known/ucp · 404
- Acting for the buyernot reached
- In the buyer's browsernot reached
- Calling its servicesnot reached
- Sending to the websitenot reached
- 2 requestsOutside UCPhomepage · /llms.txt
Not found
01 · Finding the profile2 requests
Nothing at /.well-known/ucp (404 Not Found).
Not reached
The other four ways in
Without the profile there is no list of services, sign-in or links to try.
- 01 PROFILEGET /.well-known/ucp → 404 Not Found179 ms
- 01 PROFILEGET /robots.txt → allows /.well-known/ucp–
- 01 PROFILENothing to validate: no profile was read–
- OUTSIDE UCPGET / → 200, no Organization schema found–
- OUTSIDE UCPGET /llms.txt → 404, not found–
Request
GET https://papchecker.com/.well-known/ucp
Response
404 Not Found, in 179 ms
The fix
Publish a profile at
/.well-known/ucp and it will be read and scored on the next check. {
"ucp": {
"version": "2026-08-25",
"services": {
"dev.ucp.shopping": [
{
"version": "2026-08-25",
"spec": "https://ucp.dev/2026-08-25/specification/overview",
"transport": "rest",
"schema": "https://ucp.dev/2026-08-25/services/shopping/rest.openapi.json",
"endpoint": "https://papchecker.com/ucp"
}
]
},
"capabilities": {
"dev.ucp.shopping.checkout": [
{
"version": "2026-08-25",
"spec": "https://ucp.dev/2026-08-25/specification/shopping/checkout",
"schema": "https://ucp.dev/2026-08-25/schemas/shopping/checkout.json"
}
]
},
"payment_handlers": {
"com.example.processor": [
{
"id": "processor-1",
"version": "2026-08-25",
"spec": "https://example.com/ucp/handler",
"schema": "https://example.com/ucp/handler/schema.json"
}
]
}
}
}
Is papchecker.com your store?
Claim it with one DNS record.
Why isn't papchecker.com verified for UCP?
We checked
papchecker.com/.well-known/ucp and there's no profile file there. That doesn't necessarily mean papchecker.com doesn't want to support agentic commerce — most stores simply haven't gotten around to publishing one yet. UCP is still early.Can AI agents still shop on papchecker.com?
Sort of. Agents can scrape the public website like any other crawler, but without a UCP profile they have no reliable contract for product data, cart operations, or checkout. Expect higher failure rates, slower interactions, and frequent fallback to "contact a human" flows.
How can papchecker.com get verified?
Publishing a profile takes a few hours of engineering work for most stacks. Start with the UCP developer tools guide — it walks through the schema, common pitfalls, and validation. If you work at papchecker.com, we'd love to see you on the directory.
How was this UCP report for papchecker.com generated?
Our crawler fetches
papchecker.com/.well-known/ucp directly, parses the profile against the official UCP JSON schema, checks robots.txt for its rules for AI crawlers, and runs payment-handler validation. No manual review, no opinions — just what the profile actually says. The check ran 12 hours ago.How do I get a newer result for papchecker.com?
This page shows the stored result of our last check and when it was observed. To run a new check, use Check again on this page.
Why does this status matter?
Universal Commerce Protocol is an open standard that lets a UCP agent find out what a store sells, build a cart and check out through a published contract instead of reading web pages. A valid UCP profile is how a store declares that support.