UCP Checker

Paste a store’s address and see whether its UCP discovery file is really there — and really valid.

UCP (Universal Commerce Protocol) is the open standard that lets an AI assistant shop on a store’s behalf. A store that speaks UCP publishes a machine-readable JSON profile at /.well-known/ucp — its protocol version, the services it offers, the payment handlers it accepts, and the public keys it signs with. This checker fetches that file from our server, checks it against the hosting and profile rules in the official specification, and probes the endpoints it declares. The Agent Readiness Checker looks for the discovery file as one signal among many; this tool is the deep dive for the UCP one. The companion article what UCP is and how to check it walks through a real document by hand.

Last updated:

Check a store

A domain (allbirds.com) or a full URL (https://allbirds.com). The checker requests https://<domain>/.well-known/ucp — always over HTTPS, never following a redirect.

🔒 The target is fetched by our checker server, never by your browser — so no CORS block, and the store sees the checker’s request, not yours. Nothing about you is sent to the store.

What lives at /.well-known/ucp

A UCP profile is a JSON object with a required ucp member. Inside it, ucp.version, ucp.services and ucp.payment_handlers are required — the last two must be present even when empty. ucp.capabilities is optional, though a useful commerce profile normally advertises at least one. A top-level keys[] array may publish the store’s public signing keys as an RFC 7517 JWK Set.

Versions are dates, never words like "draft": the first release was 2026-01-11 and the latest stable version is 2026-08-25. A profile that declares an older version still validates, but this checker warns — and lists the breaking changes below — because counterparties may reject entries whose version does not match the profile’s own. A store that still serves older versions lists them in supported_versions, each pointing at its own leaf profile.

Among the breaking changes in 2026-08-25, these touch a published profile: the old signing_keys[] field was removed and replaced by the top-level keys[] JWK Set; fulfillment config was restructured (flags lost their allows_ prefix, multi_destination became an array); buyer consent moved from fixed boolean flags to a dynamic map keyed by reverse-DNS identifiers; and payment extensions moved from dev.ucp.shopping.* to dev.ucp.common.payment.*.

Hosting rules are strict because profiles are trust material: a profile must be served over HTTPS, must not redirect (any 3xx is a failure), and must carry Cache-Control: public with max-age of at least 60 seconds — never private, no-store or no-cache. Shopify storefronts serve a 2026-08-25 profile at /.well-known/ucp by default — try the demo button.

What this checker does — and what it does not

It fetches, validates and probes — from the server. The checker requests https://<domain>/.well-known/ucp directly (one request, no redirect following), validates the document against the rules on this page, and probes each endpoint the document declares with a HEAD request (a GET where HEAD is refused). Your browser never contacts the target, so the check is not blocked by CORS.

It does not place orders, does not authenticate as a buyer, and does not validate the cryptography of payment handlers. A profile that passes here proves the store can be discovered and its endpoints reached — not that a checkout will succeed, a price is right, or a payment handler is trustworthy.

It does not check ACP, AP2 or x402 documents — only UCP. An unreachable declared endpoint is a warning, not an error: the endpoint may require authentication, and a 401 or 404 response still counts as reachable, because the server answered. Only a connection that fails outright counts as unreachable.

Be honest with yourself before you trust a profile

A valid profile is not a working checkout. Discovery is step one: the profile says what the store offers and where its endpoints live. Whether those endpoints accept real requests, return real prices and complete a real order is a different question, and this checker does not answer it.

An old version is a warning, not a failure, for a reason. A store on 2026-04-08 can still transact with a platform that speaks 2026-04-08 — but a platform that speaks only 2026-08-25 must reject entries whose version does not match, so an old profile narrows who can shop there.

A 404 usually means "no UCP here", not "broken store". Most sites on the internet publish no UCP profile at all — the negative demo shows exactly that. Treat a missing profile as a fact about the store’s agent readiness, not as an error in the store itself.

Key facts

Universal Commerce ProtocolThe open standard that lets an AI assistant discover a store’s catalog, checkout and after-sales, and transact on a buyer’s behalf.
Discovery fileThe JSON profile published at /.well-known/ucp on the store’s own domain.
Latest version2026-08-25. Versions are dates; the first release was 2026-01-11.
Required fieldsucp.version, ucp.services, ucp.payment_handlers — the last two must be present even when empty. ucp.capabilities is optional.
Cache ruleCache-Control: public with max-age of at least 60 seconds; never private, no-store or no-cache.
Redirect ruleProfiles must be served over HTTPS with no redirects — any 3xx response is a failure.
Official specificationUniversal Commerce Protocol (UCP) Official Specification

Frequently asked questions

Why does the check run on a server instead of in my browser?

Because browsers block cross-origin reads. A page on sysosx.com cannot fetch another store’s /.well-known/ucp directly — the store’s server would have to opt in with CORS headers, and most do not. The checker fetches the file from its own server, where that restriction does not apply, and returns the result to your browser.

My store runs on Shopify — do I need to publish anything?

No. Shopify serves a 2026-08-25 profile at /.well-known/ucp on every storefront by default — try the demo button, which checks allbirds.com. If your store is on Shopify and the check fails, something else is wrong (a redirect in front of the store, or a custom domain that is not serving the storefront).

The document exists but the verdict is "partial" — what do I fix first?

Fix the findings marked Fail first: a missing required field (version, services or payment_handlers), a document that is not valid JSON, or a redirect. Warnings — a cache header below 60 seconds, an old version, an unreachable endpoint — are advisory and do not block a UCP-ready verdict on their own.