Universal Commerce Protocol profile invalid

What it detects

A UCP profile is published but fails schema validation — missing required fields, wrong types, or malformed service entries.

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 schema — required top-level keys are `ucp_version`/`services`, `capabilities`, and `signing_keys`; each service entry needs `version`, `spec`, `transport`, and (for non-A2A transports) `endpoint` and `schema` URLs. - Fix the specific validation errors reported by the scan (missing required fields, wrong types, malformed URLs) 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

• Universal Commerce Protocol specification