Questions · Buy

Does the UCP checkout test place an order?

No. It creates a checkout session with a synthetic buyer whose email ends in @agent.ottom.io, reads the answer, and cancels the session. It never completes a checkout and never submits payment.

Why it happens

An agent platform that supports UCP reads the manifest at /.well-known/ucp, finds the shopping service and its endpoint, and calls it directly: search the catalogue, then create a checkout with the item, the buyer and the delivery address. No web page is involved, so a storefront that works in a browser says nothing about whether this route works.

Ottom makes those same calls with a synthetic buyer, reads what the store answers, and cancels the checkout. It never completes one and never submits payment. A failure counts against the store only when the endpoint itself failed: an error that is about who is calling, such as a rate limit, or a checkout that asks for more buyer details, is the protocol working.

It is reported at medium severity. The storefront checkout is graded on its own by the browser journey, and this is one channel failing rather than the store being unable to sell.

This comes up at the Buy stage. The full treatment, including how to reproduce it and what to change, is on The UCP checkout endpoint failed when an agent used it.

Related questions

Run a free scan and find out which of these your store actually hits.