Check your UCP manifest
A UCP checker reads the Universal Commerce Protocol manifest a store publishes at /.well-known/ucp and checks it against the rules the specification sets for every manifest: a dated version, a services registry, transports the specification defines, and https endpoints. Enter your store address to see each service, version and capability yours declares.
How to read the result
NONE means the store publishes no manifest, which is a fact about the store and not a fault: a scan raises nothing for it. BROKEN means a manifest is published and breaks a rule every manifest must keep, which a scan reports as a medium finding. #
Related checks
Agent view shows one product page as an AI agent receives it, and the sitemap and feed checker shows whether an agent can list your products at all.
Frequently asked questions
What is UCP?
The Universal Commerce Protocol, an open specification at ucp.dev for how an AI agent discovers what a store offers and talks to its checkout. A store says which parts it supports in a JSON manifest at /.well-known/ucp: the version of the specification it follows, the services it offers, how to reach each one, and its capabilities.
Do I need a UCP manifest?
Not to be found or bought from. An AI agent can still read your storefront and walk your checkout without one, and a scan does not count a missing manifest against you. Whether a store has one is mostly decided by its platform: Shopify generates one for every store, and most other platforms do not yet.
What makes a manifest invalid?
Breaking a rule the specification sets for every manifest: no ucp object, a version that is not a date written YYYY-MM-DD, no services registry, a transport the specification does not define, or an endpoint that is not an https URL. Fields only the newest version asks for are shown but not counted, because a store on an earlier version may leave them out.
My platform generates the manifest. What can I do if it is broken?
Raise it with your platform, and forward them this result: each broken rule is named with the service it is in. If you publish the file yourself, fix it to match the specification for the version it names, or remove it until it does. A manifest that cannot be read advertises a checkout an agent cannot reach.
What do you send to my store?
Two requests: robots.txt, then /.well-known/ucp, from our published user agent and a fixed set of static IP addresses listed on our agent page. We read the file and nothing else. No checkout is started. A result is kept for ten minutes, and we cap how often any one store is checked across all our free tools.
See how our own agent identifies itself, and how to opt out, on our agent page.
A manifest is a promise. A scan tests it.
A scan walks your store the way an AI shopper would and tells you where it stalls on the way to checkout. One free scan per store, per email address, every 30 days.