Skip to content
Universal Commerce Protocol Universal Commerce Protocol Protocol registry / en

Free tool / UCP readiness

Assess what your commerce stack can already prove.

An operational pre-diagnostic to expose gaps across catalog, transaction, trust, and operations before committing to a UCP program.

Checks
12
Layers
4
Data
0
sent

Readiness ledger / local self-assessment

12 factual checks. No hidden weighting.

Answer from evidence available today, not from the roadmap. An unknown answer is classified as “not demonstrated”.

Local / private / instant

Your answers stay in this browser. The diagnostic creates no account, sends no answers, and calls no paid model.

Single scoring scale

0, 1, or 2 points per check. Every check has exactly the same weight.

  1. 00 / 02

    Not demonstrated

    Missing, unknown, or undocumented

  2. 01 / 02

    Partial

    Documented or deployed, but not verified end to end

  3. 02 / 02

    Verified

    Deployed and tested on a representative scenario

Progress 0 / 12

Layer 01

Catalog & discovery

Agents find products from stable, current data.

Do products and variants use stable identifiers across catalog, cart, and order?

Evidence example: SKU or identifier mapping tested across all 3 stages.

Are prices, availability, variants, and policies structured and refreshed on a defined schedule?

Evidence example: timestamp, refresh SLA, and discrepancy check.

Can a system search for a product, then retrieve an already known identifier exactly?

Evidence example: repeatable Search and Lookup scenarios.

Layer 02

Capabilities & transaction

The merchant exposes deterministic capabilities and transaction flows.

Are supported capabilities, versions, and endpoints declared in a machine-readable profile?

Evidence example: versioned test profile with reachable endpoints.

Is the cart-to-checkout lifecycle defined through reproducible states, transitions, and errors?

Evidence example: tests for creation, update, confirmation, and expiry.

Are final commercial terms recalculated and confirmed before the buyer is committed?

Evidence example: price, stock, delivery, and tax confirmed before validation.

Layer 03

Identity, payment & trust

Mandates, confirmations, and safeguards are explicit and testable.

Is the agent’s mandate explicit, limited, and checked before a sensitive action?

Evidence example: amount, duration, merchant, and allowed categories.

Does the flow separate payment preparation, consent, and irreversible confirmation?

Evidence example: log of all 3 stages and cancellation test before confirmation.

Are authentication, signatures, secrets, and replay protections documented and tested?

Evidence example: key rotation and a rejected replay attempt.

Layer 04

Operations & governance

Teams can monitor, correct, and evolve the implementation.

Are errors, retries, and repeated requests handled without creating duplicate actions?

Evidence example: idempotency key and recovery after a timeout.

Are order status, cancellation, return, and refund exposed consistently?

Evidence example: complete post-purchase scenario in a test environment.

Are an owner, alerts, and a regression test suite defined?

Evidence example: named owner, dashboard, and scheduled tests.

Calculate my diagnostic

Your answers stay in this browser. The diagnostic creates no account, sends no answers, and calls no paid model.

What the score measures

Operational evidence, not ambition.

A declared snapshot

The score reflects only your answers. It helps order verification work and prepare a discussion across commerce, product, payment, security, and operations.

No certification

The diagnostic does not replace official specifications, schemas, or conformance tests. A human review remains optional and only applies if you choose to explore the result further.