Valid JSON, broken discovery: the UCP checks that should fail your build

Ensuring that a merchant's website is discoverable and trustworthy through the Unified Commerce Protocol (UCP) is crucial for integrating with agents like Google's Smart Shopping Cart. Here are key points to address when setting up UCP validation in CI:

Critical Checks That Should Fail CI

1. Manifest Fetch Failure (UCP_FETCH_FAILED):

   • Ensure that the .well-known/ucp endpoint returns a valid JSON manifest.

2. Endpoint Security (UCP_ENDPOINT_NOT_HTTPS):

   • All UCP endpoints must be served over HTTPS to ensure secure communication.

3. Trailing Slashes in Endpoints (UCP_ENDPOINT_TRAILING_SLASH):

   • Ensure that all endpoint URLs do not have trailing slashes, as this can cause issues with discovery and validation.

4. Version Compliance (UCP_MISSING_VERSION, UCP_INVALID_VERSION_FORMAT):

   • The manifest must include a valid version field to ensure compatibility with the latest UCP standards.

5. Manifest Structure (UCP_MISSING_ROOT):

   • Ensure that the JSON structure adheres to the expected format, specifically including the root object for UCP.

6. **Namespace Authority and Schema Origin

Read the full article at DEV Community

---

Want to create content about this topic? Use Nemati AI tools to generate articles, social posts, and more.