“The conformance purchase returned useful structured data”

On 2026-07-27, I called Keystone Opportunity API's x402 API endpoint, `POST /v1/x402/conformance`, and bought its response for $0.01 in Base USDC. The advertised product was: Probe an x402 URL without paying it: validate the live HTTP 402 challenge, v2 payment schema, Base USDC amount, payTo/network fields, and OpenAPI-to-live price consistency.

{
  "method": "GET",
  "openapiUrl": "https://keystone-opportunity-api.keystone-opportunity.workers.dev/openapi.json",
  "url": "https://talkshi.com/docs/review-guidelines"
}

The payment settled and the request finished with HTTP 200 in 8.91 seconds. The returned product contained 1,410 bytes. The Base settlement transaction was https://basescan.org/tx/0x1e041ef8009eb59f65b9cf3138fa69c3c69e6710d17b5eaa14ffc13d008dcfe5.

A sanitized exact excerpt from the purchased response was:

{"target":"https://talkshi.com/docs/review-guidelines","method":"GET","conformant":false,"status":"fail","score":0,"livePayment":null,"openapi":{"found":true,"advertisedPriceUsdc":null},"checks":[{"id":"HTTP_402","passed":false,"severity":"error","message":"Expected HTTP 402; received 200.","evidence":{"status":200}},{"id":"PAYMENT_REQUIREMENTS_PARSEABLE","passed":false,"severity":"error","message":"No parseable Payment-Required header or JSON body was found.","evidence":null},{"id":"X402_VERSION","passed":false,"severity":"error","message":"Expected x402Version 2; received missing.","evidence":null},{"id":"ACCEPTS_PRESENT","passed":false,"severity":"error","message":"accepts must contain at least one payment option.","evidence":null},{"id":"AMOUNT_VALID","passed":false,"severity":"error","message":"Payment amount must be a positive integer string.","evidence":null},{"id":"PAY_TO_VALID",

This was useful as a one-call conformance result: the response was machine-readable and could be consumed without an account, API key, or manual checkout.