FOR TEAMS BUILDING SHOPPING AGENTS

Ship a shopping agent that checks out safely.

You’re building a shopping-orchestration AI that carts and checks out across merchant platforms over UCP. It handles real money and real user accounts — and you can test the ways it goes wrong (paying the wrong amount, getting phished, failing the checkout) that passing conformance can’t catch.

45
Failure modes tested
6
You can watch live
100%
Proven to catch the bug

Your agent can pass conformance and still lose money.

A conformance test reads the shape of the messages your agent sends. It can’t see your agent quietly paying a total that doesn’t add up, following a phishing link out of an error message, or trusting a store response it never verified. Those are behaviors — and they’re where real checkouts go wrong, with a real user’s card.

Shapeis not behavior
Schema checks read the message shape; they can’t see behavior — paying a bad total, following a phishing link, trusting a forged response. Conformance is not reliability. That’s the gap you can close here.

The six ways an agent goes wrong — that conformance misses.

Each is a real behavior your agent must get right when it shops. Every test is proven to catch its own bug — it passes a known-good agent and provably fails the broken one. Watch all six live in the demo.

💰

Pays the wrong amount

The line items and total don’t reconcile, but the agent completes the purchase anyway instead of stopping for the buyer.

watch live
🎣

Gets phished

The agent follows a decoy link hidden in an error message and hands the user’s login to an attacker’s server.

watch live
🔒

Trusts a forged response

The agent skips verifying the store’s signed response, so a tampered or fake reply is accepted as real.

watch live
🔑

Links accounts unsafely

Missing PKCE or an unchecked issuer lets an attacker hijack the OAuth flow and capture the linked account.

watch live
💳

Pays with the wrong method

The agent pays with a payment type the store never offered — an unauthorized instrument.

watch live
🧹

Leaks or over-shares

Sends fields it shouldn’t, forgets to identify itself, or never revokes access when the user unlinks.

45 failure modes in all

Point your agent at a reference store. See if it actually buys.

Try a full UCP checkout against a reference store that the UCP schema oracle validates — and one that misbehaves on purpose. Run it locally in one command, or watch recorded runs in the demo.

1

Your agent shops the store

Run your agent against the bundled merchant sandbox — clone the repo or spck-conformance --agent — and let it run a full checkout: discovery, payment, the works.

2

The store misbehaves on purpose

Bad signatures, spliced login servers, mismatched totals, phishing decoys — the things a real store might do wrong or an attacker might try.

3

You get a reliability report

Exactly which behaviors your agent got right, and which ones would have cost a user real money — the findings conformance never surfaces.

Watch a correct agent — then break it.

The demo replays real recorded runs. Flip one flaw and watch exactly what the agent does wrong — and how it’s caught. No signup.

or run it against your own agent
# clone the suite and run the agent-reliability lane
$ git clone https://github.com/vishkaty/ucp-conformance
$ python3 conformance/agent/run_agent.py
agent lane: reference agent — 44 agent checks
PASS — every check passes a correct agent and catches its bug.
Open the live demo →
Building the merchant side instead? Test that AI shopping agents can actually discover and buy from your catalog, cart & checkout.
Merchant platforms →

Building a shopping agent — or vetting one?

If you’re shipping an AI that checks out, or a platform that has to trust third-party agents, test what actually breaks before it touches a real card. The demo is free and open.