Universal Commerce Protocol profile absent
UCP_PROFILE_ABSENT · v2.0
Computed by Scovant Core ≥ 0.10.0 (open source) — pin that version and you get the same verdict.
What it detects
No Universal Commerce Protocol profile is published at /.well-known/ucp, or the path answers with an HTML page instead of a profile.
Why it matters
UCP is the emerging standard agents use to discover a merchant's services, checkout capability, payment handlers and signing keys in one machine-readable document; without a profile, an agent has no standardized way to transact with the site at all.
How to fix
- Check what `/.well-known/ucp` returns (the Universal Commerce Protocol discovery path, spec at ucp.dev): a 404, or an HTML page from a catch-all route — both mean no profile. - Publish a JSON business profile as the UCP v2026-08-25 schema defines it: `ucp.version` (`"2026-08-25"`), `ucp.services` with a `dev.ucp.shopping` binding (lowercase `transport` — `rest`, `mcp`, `a2a` or `embedded` — plus an `endpoint` for rest/mcp/a2a), `ucp.payment_handlers` (present even when empty), and `dev.ucp.shopping.checkout` under `ucp.capabilities`. A top-level `keys` JWK Set of public signing keys is optional. - Reference ucp.dev/specification/overview for the full schema and github.com/Universal-Commerce-Protocol/samples for working reference implementations to adapt; serve it over HTTPS without redirects. - Verify: `curl` `/.well-known/ucp`, confirm HTTP 200 with a JSON object (not HTML), and run it through the official conformance suite (github.com/Universal-Commerce-Protocol/conformance).
References
Last reviewed: 2026-09-01 · rule v2.0