Universal Commerce Protocol profile invalid
UCP_PROFILE_INVALID · v2.0
Computed by Scovant Core ≥ 0.10.0 (open source) — pin that version and you get the same verdict.
What it detects
A UCP profile is published but is not a usable UCP v2026-08-25 business profile — it fails the official schema (missing ucp.version, services or payment_handlers, an uppercase transport, a binding without its endpoint, a private signing key) or declares a version that is not a released one.
Why it matters
An invalid profile is functionally the same as no profile to a strict agent client: it either fails to parse or the agent cannot trust the fields it does read.
How to fix
- Fetch `/.well-known/ucp` and check it against the UCP v2026-08-25 business-profile schema — required: `ucp.version` as a release date (`"2026-08-25"` or an earlier announced release), `ucp.services` and `ucp.payment_handlers` (both present even when empty); each service binding needs `version` and a lowercase `transport` (`rest`, `mcp`, `a2a`, `embedded`), and rest/mcp/a2a also an `endpoint`; each capability entry needs `version` and `schema`. - Fix the specific validation errors reported by the scan (uppercase transports, a non-date version, missing fields, private members in `keys`) rather than regenerating the whole profile from scratch if only a few fields are broken. - Run the official conformance suite (github.com/Universal-Commerce-Protocol/conformance) against the fixed profile before shipping. - Verify: `curl` the profile, run it through the conformance suite, and confirm zero validation errors.
References
Last reviewed: 2026-09-01 · rule v2.0