Universal Commerce Protocol
Check whether a storefront publishes a valid Universal Commerce Profile at /.well-known/ucp and whether shopping agents can read it without friction.
What this validator checks
Endpoint reachability
We request the public HTTPS domain and confirm that /.well-known/ucp responds.
Schema hygiene
The response body is parsed as JSON and checked for UCP spec errors and warnings.
Agent access
robots.txt is reviewed so you can see whether major shopping and indexing bots are blocked.
Paste a domain and we'll fetch the live /.well-known/ucp document, parse every service, capability, payment handler and signing key, then validate it against the 2026-04-08 spec.
Before you run it
Use the public storefront domain
Enter the root domain only, like acme.com or www.acme.com. We always validate the HTTPS version.
We validate the full UCP 2026-04-08 spec
Services, capabilities, payment handlers, signing keys (JWK / RFC 9421), supported versions and transports are all parsed and checked.
robots.txt matters too
A valid profile can still be hard for agents to use if key crawlers are blocked higher up the stack.