Can an AI agent actually buy from you?
Assistants find companies, read their docs, then stop dead at checkout — no account, no API key, no way to pay. Paste a domain and get a measured, reproducible answer in about ten seconds.
Free, no signup. We fetch only what a public agent fetches — llms.txt, robots.txt, sitemap.xml, schema.org markup, /.well-known/* manifests, your pricing page, and an HTTP 402 probe.
Findings
Get the 2-minute teardown
Three assistants attempting a real purchase from you, time-stamped at the moment they fail — plus the one-page fix list.
Not one has a live HTTP 402 challenge. 189 of 206 are gated at “Sign up”.
Across 206 companies. Nobody finishes the funnel.
Block an unattended agent at purchase, and 0 publish a pay-per-call endpoint.
Six gates. Everyone passes the cheap ones and fails the one that pays.
Measured on 206 public surfaces — payments, logistics, healthcare, insurance, HR, martech, dev-infra, travel. Reproduce any row with node audit.js <domain>.
Read the full Verified Agent Report → · watch a machine buy something live →
Twelve files, generated from your public site in one command.
Not a slide deck. node build.js <domain> produces the surface, and the same auditor that scored you scores the result: 100/100, checkable live at acme-data.outcomedev.com.
What you pay, what you get, and when.
Three options, priced against what one agent transaction is worth. No seats, no per-call meter on our side, no annual lock-in.
Seven days. Know your own number before you commit to anything.
- You get: agent traffic instrumented on your site — which assistants arrive, what they attempt, where they fail, with timestamps
- You get: the one-page fix list for your domain
- You pay: on signature, and it is credited in full against a build within 30 days
For anything an agent buys for $1 or more — labels, messages, payments, bookings, reports.
- You get: all twelve files built against your API and deployed — llms.txt, agent card, MCP server, schema.org pricing, 402 pay-per-call endpoint, spend-cap policy
- You get: one paid agent transaction completed end to end on your rails, and the recording of it
- You get: us as merchant of record for the agent channel — tax, disputes, settlement
- You pay: 50% on signature, 50% at go-live. About two weeks.
- Then: 15% of agent-sourced revenue, billed monthly in arrears — first $10,000 free
2,000 agent actions a month at $8 is $192,000 a year of channel revenue; the fee pays back in about six months.
For per-call pricing under a cent, where a percentage take is meaningless and card networks cannot settle.
- You get: machine-readable catalog and pricing, prepaid credits so agents can spend without a human, and an x402 / MPP micropayment endpoint
- You get: the same proof — one paid agent call completed end to end
- You pay: 50% on signature, 50% at go-live
- Then: a flat platform fee on credits spent, not a percentage
We grade every target from what one agent transaction is worth. If the build cannot pay for itself at your transaction size, we will say so and quote option 3 instead — or tell you to wait and come back.
The honest answers.
What exactly do I get for $15,000?
Two weeks of engineering against your API, and the twelve files that make it purchasable by a machine: a metered access layer, agent identity with spend caps, payment acceptance across four competing protocols (x402, MPP, scoped card credential, prepaid credits), a merchant-of-record wrapper so you are not handling tax and disputes, schema.org pricing, an A2A agent card, a working MCP server, and one paid agent transaction proven end to end. It is the same shape of work as any integration project — roughly a developer-month plus payments expertise — delivered in two weeks because the surface is generated, not hand-written.
When do I pay?
Measurement on signature, credited against a build within 30 days. On a build: 50% on signature, 50% at go-live, about two weeks later. The 15% channel fee only starts once agents are actually spending, is billed monthly in arrears, and the first $10,000 of it is free — so in practice the fee begins in a later quarter than the build.
What if it does not work?
Start with the $2,000 measurement: if agent traffic to your site is negligible, you will know in a week and we will say so rather than sell you a build. On the build, the second invoice is cancelled if three criteria fail — agent traffic measured and attributed within 7 days, at least one paid agent transaction settled end to end, and a cost per paid transaction below your human-assisted alternative.
Who owns the customer?
You do. We are merchant of record for the agent channel only, which means we absorb the tax, the disputes and the settlement plumbing. Your existing customer relationships, pricing and contracts are untouched.
How fast?
Measurement in a week. A full build is about two weeks from kickoff, and the surface is generated rather than hand-written — which is why it is two weeks and not two quarters.
What if agents never buy anything?
Then you have spent $2,000 and learned your own number, and the machine-readable work still improves how assistants describe and recommend you — which is measurable today: AI-referred traffic converts better than human traffic in Adobe's and Shopify's published data. We would rather tell you that than sell you a story.