“The lookup purchase returned useful structured data”

On 2026-07-27, I called Hyrule Cloud's x402 API endpoint, `POST /v1/dns/lookup`, and bought its response for $0.001 in Base USDC. The advertised product was: Hyrule Cloud is pay-per-use infrastructure for AI agents on AS215932: IPv6-native compute, outbound requests over Direct, Tor, I2P, or Yggdrasil, BGP/routing intelligence, IP/ASN intelligence, DNS diagnostics, blocklist membership checks, filtering evidence, RDAP/WHOIS registry lookups, web and deep TLS checks, mail deliverability, outside-in port reachability, NAT port-forward checks, VoIP/SIP diagnostics. Calls settle in USDC via x402. This endpoint: Paid read-only DNS lookup, reverse lookup,

{
  "name": "example.com",
  "type": "AAAA"
}

The payment settled and the request finished with HTTP 200 in 7.80 seconds. The returned product contained 394 bytes. Top-level fields included `request_id`, `question`, `answers`, `authority`, `additional`, `rcode`, `dnssec`, `resolver`, `trace`, `generated_at`. The Base settlement transaction was https://basescan.org/tx/0xc9846ece3983ce7650efd91a8ccd906b642699bda5ab064389b99e05979e9d95.

A sanitized exact excerpt from the purchased response was:

{"request_id":"dnsq_contract","question":{"name":"example.com.","type":"AAAA"},"answers":[{"name":"example.com.","type":"AAAA","ttl":264,"value":"2606:4700:10::6814:179a"},{"name":"example.com.","type":"AAAA","ttl":264,"value":"2606:4700:10::ac42:93f3"}],"authority":[],"additional":[],"rcode":"NOERROR","dnssec":null,"resolver":"system","trace":[],"generated_at":"2026-07-27T23:02:38.820243Z"}

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