Can AI shopping agents actually find your store?
Assistants are starting to shop on people's behalf. They do not browse your storefront the way a shopper does: they look for a protocol profile at a fixed path on your domain, read your structured data, and move on if either is missing. This checks whether yours is there.
Free, no account. Reads only public pages, the same way an agent would.
Validated against the published UCP specification, currently 2026-08-25. We check what the spec says, not what a vendor blog says it says.
Four things decide whether an agent can buy from you
Agent discovery
Whether a UCP profile exists at /.well-known/ucp, parses, declares services and capabilities, and is served the way the spec demands: HTTPS, no redirect, public cache header.
AI crawler access
Whether robots.txt quietly blocks the crawlers behind ChatGPT, Gemini, Claude, Perplexity or Alexa. Blocking these removes a store from those surfaces outright.
Product data agents can read
Whether product pages carry schema.org Product markup with a complete offer, and whether products carry the identifiers agents use to match and compare them.
Catalogue reachability
Whether a sitemap and a machine-readable product endpoint exist, so an agent can learn the whole catalogue rather than the pages it stumbled on.
If the profile is missing, we publish it
A managed UCP profile for your domain. We generate it from your real catalogue, serve it so it satisfies the spec, monitor it, and move you to each new spec version as it lands.
- A conformant profile at /.well-known/ucp on your own domain, no redirect
- Correct Content-Type and public cache headers, held to spec
- Moved to each new UCP version, so negotiation never goes stale
- Daily conformance check, with an email the moment it breaks
- A one-line proxy rule for nginx, Apache, Cloudflare, WordPress or Next.js
We would rather you scan before you buy. If the scan says your platform already handles this, it says so, and you should not pay us.
Straight answers
What is the Universal Commerce Protocol?
⌄
UCP is an open standard for how AI agents discover and transact with a business. A store publishes a JSON profile at /.well-known/ucp describing the protocol version it speaks, the services it exposes and the payment handlers it accepts. An agent fetches that profile, intersects its capabilities with yours and negotiates from there. No profile, no negotiation.
I am on Shopify. Do I need this?
⌄
Probably not for the profile itself. We checked: Shopify already serves a conformant UCP profile for its merchants, currently version 2026-08-25. Run the scan anyway, because the other three checks are yours, not Shopify's, and a blocked AI crawler in robots.txt will undo the rest. We will tell you plainly if there is nothing for us to sell you.
Why can't I just publish the file myself?
⌄
You can, and if you run your own web server it is an afternoon. Two things make it stick: the spec forbids serving the profile through a redirect, which rules out the simplest workaround on most hosted platforms, and version matching is exact. The spec moved three times in eight months, and a profile pinned to an old version stops negotiating silently.
Will this make AI agents recommend my products?
⌄
No, and anyone promising that is guessing. Discovery and conformance are necessary, not sufficient. What we can tell you honestly is whether an agent following the protocol can find you, read your catalogue and price it. Whether it then picks you is down to your products, price and reputation.
What does the scanner actually do to my site?
⌄
A handful of GET requests to public URLs: /.well-known/ucp, /robots.txt, /sitemap.xml, /llms.txt, your homepage and up to three product pages. It identifies itself as StoreDeployBot. It does not log in, submit forms or crawl at volume.