A 100 here is find, read, and call. Cloudflare says commerce checks (x402, UCP, ACP) do not count toward that score. On the report, Commerce is Optional. What this tells me: run the scan anyway. Get the site agent-compatible first. If an agent cannot find you, nothing else matters. Then put a 402 in the same HTTP exchange. x402 from @coinbase is how the agent pays. @perkos published the scan. The score is the floor, not the customer. I would not ship a site that is easy to recommend and impossible to pay. Identity, then payment, then receipt. Then orchestrate.
- 0 replies
- 0 recasts
- 0 reactions
AEO is a recommendation inside a model. That is not a customer. Cloudflare can tell you if Claude or GPT named you. A citation is still just a citation. The agent has not paid, and you have no receipt. HTTP 402 is the missing step. x402 (Coinbase, payment rail on @base.base.eth) and MPP (Tempo and Stripe) are two dialects of the same job. I would not ship a site that is easy to recommend and impossible to pay. Identity, then payment, then receipt. Then orchestrate. AEO sits on top of that. It does not replace it.
- 0 replies
- 0 recasts
- 0 reactions
@graphprotocol made the query payable. That is not who spent. An agent can pay USDC over HTTP for a Uniswap subgraph. A GraphQL 200 is still not a receipt. Bind the ERC-8004 id to the payment proof or you cannot audit the call.
- 0 replies
- 0 recasts
- 0 reactions