Is Your UCP Validator Lying to You About Cart and Catalog?

You ran validation. Your store got a "FAIL" on Cart and Catalog capabilities. The report says your catalog endpoint returns an invalid response shape. You spend an afternoon debugging endpoints that look fine when you test them manually.

The problem isn't your store. It's your validator. Here's why.

The draft-spec trap nobody talks about

The Universal Commerce Protocol isn't static. As of the April 2026 release:

• Identity Linking is stable. The spec is finalized. Agents expect a specific response shape, and that shape won't change without a new protocol version.

• Cart and Catalog are draft. The endpoints exist and work. Agents interact with them in production. But the schema, response shapes, and exact field names are still evolving. The spec explicitly says they "MAY version independently when breaking changes are required."

When a validator doesn't distinguish between stable and draft capabilities, here's what happens:

Your Catalog endpoint returns products correctly. An AI agent asks "show me hiking boots under $200" and your store responds with actual products. But the response includes an optional metadata field that the draft spec didn't mention six months ago, or it nests variant data differently than the current draft expects.

A spec-unaware validator flags this mismatch as a failure. Hard stop. Red X. "Catalog validation failed."

The agent, meanwhile, browses your catalog just fine. It reads the products that matter, ignores the extra fields, and builds a cart. Your store works in practice. But your validator says it doesn't.

What a hard-fail actually costs you

False negatives aren't just annoying - they steer you toward the wrong work.

When your validator says Cart validation failed, you investigate. You compare your endpoint response to the draft schema. You spend hours figuring out whether the mismatch is on your side or the spec's. You might even modify your endpoint to match a draft schema that changes next month.

Meanwhile, the actual problems - signing keys that rotated, a CDN that changed how it serves .well-known/ucp, payment handlers referencing an old gateway endpoint - go unnoticed. These are genuine, production-breaking failures that get buried under draft-spec noise.

The validator that flags everything with equal severity trains you to ignore all of it.

The fix: draft-aware validation

As of July 2026, UCPtools handles draft capabilities differently:

• Stable spec requirements: checked as before. If your Cart endpoint returns a 4xx, if your Catalog doesn't serve JSON, if a required stable-spec field is missing - those are real failures.

• Draft-spec mismatches: produce warnings, not failures. If your response shape doesn't match the current draft schema, you get a clear warning explaining what's different - not a red X that blocks everything else.

You still see the mismatch. You still know something changed. But you're not punished for a moving target.

Three things to check in your current validation workflow

1. Does your tool report spec status for each capability?

If every failure looks the same - same severity, same color, same urgency - you can't tell a broken endpoint from a draft-spec evolution.

2. Does a Cart/Catalog failure block your entire validation run?

A genuine signing_keys failure and a draft-spec Catalog warning are not the same problem. If your tool treats them identically, you're spending time on the wrong one.

3. When was your tool last updated against the current UCP spec?

The April 2026 update was the largest spec release since January. If your validator hasn't been updated since then, it's validating against a version of the protocol that no longer reflects what agents expect.

The spec is moving. Your validation should move with it.

Google shipped the April 2026 update with Cart, Catalog, and Signals. Shopify Editions Spring '26 made UCP the default on every store. The protocol is in active development - and that's a good thing. It means agentic commerce is real enough that the spec keeps improving.

But point-in-time validation tools that don't distinguish between draft and stable create more noise than signal. You end up debugging spec evolution instead of fixing what actually breaks agent interactions.

---

Check if your validation handles draft specs correctly: Validate your UCP profile - free, no account needed.

Running validation across multiple domains? Start a free 7-day trial for monitoring and multi-domain dashboards. No credit card required.