Skip to content

UCP conformance

Independently probed against production with a tool we don't control — and reproducible by you in two commands.

What was independently validated

On 2026-08-04 we pointed spck-conformance — a third-party UCP checker (MIT, unaffiliated with us) that has never seen this codebase — at our production endpoint. The discovery probe:

terminal
Wrote probe.json for https://api.ordercore.ai/ucp (spec 2026-01-11).
  detected capabilities: dev.ucp.shopping.checkout,
                         dev.ucp.shopping.fulfillment,
                         dev.ucp.shopping.orders

The tool parsed our discovery document, resolved spec version 2026-01-11, and enumerated all three declared capabilities correctly. The discovery layer is externally validated.

What is deliberately gated

Only /ucp/.well-known/ucp is public. Checkout, fulfillment, and order routes require an API key, quota, and rate limiting — OrderCore is merchant-side infrastructure: agents transact with your store through your tenant, not with OrderCore as an open storefront. That is why the probe's full merchant lifecycle (which creates real carts and payments) is not run against production, and why no public catalog capability is declared.

Reproduce it yourself

No account needed — the discovery probe is public:

terminal
python3 -m venv venv && ./venv/bin/pip install spck-conformance
./venv/bin/spck-conformance --server https://api.ordercore.ai/ucp --init probe.json

Related

Get an API key