Do AI agents complete purchases on websites yet?

What agents can do today

Assistants with browser control navigate pages, fill forms and click, the way a person would, and fail where a person would not: hidden required fields, CAPTCHAs, layouts that only make sense visually. Sites that register WebMCP tools give the assistant a documented function instead, which is faster and fails less. Payment without a human at the keyboard needs a rail such as the Agentic Commerce Protocol, the Universal Commerce Protocol or x402, and adoption is early.

How to measure it on your site

Put data-agent-goal on the element that means done: the order button, the booking confirmation. Register the checkout as a tool if you have WebMCP. The overview then shows conversions per day and the Tools view shows where calls fail. A session is attributed to an agent from the referrer or user agent, so a purchase by a person sent from ChatGPT counts as an AI referral conversion, and a purchase driven by an assistant in the browser counts as an agent conversion.

<button type="submit" data-agent-goal="order_placed">Place order</button>

Reading the gap

Tool calls without conversions mean agents try and do not finish; the error class in the Tools view usually says why. Conversions without tool calls are people. Neither number appears anywhere else, because a purchase by an agent looks like any other purchase to a shop system.

What this site will publish

Aggregate rates by site type, once enough shops run the pilot and their owners agree. Until then the number that matters is your own, and it takes one attribute to get.

In short