The recurring domain check

A domain record changes. Renewal can move the expiry date, a transfer can change the registrar, and a nameserver change can alter where the domain points. Keep the earlier paid response, then query the same apex domain when a review needs fresh registry facts.

whois accepts a domain and returns its RDAP record for 0.005 USDC. The response includes registered_date, expiration_date, registrar, nameservers, dnssec_signed, statuses, and flags. Registries often redact contact fields, so treat an empty contact record as a registry result. 

curl -X POST https://x402.agentutility.ai/whois \
  -H "Content-Type: application/json" \
  -d '{"domain":"example.com"}'

The first response requests x402 payment. Save the paid response with the request body. A later workflow can compare the fields that changed instead of asking an agent to reconstruct the last lookup.

Save a small record

Keep the request and the registry fields that can move. registered_date and age_days give context; expiration_date, registrar, nameservers, dnssec_signed, and statuses are the useful comparison fields. 

{
  "request": { "domain": "example.com" },
  "previous": {
    "expiration_date": "2027-08-14T04:00:00Z",
    "registrar": { "name": "Example Registrar" },
    "nameservers": ["ns1.example.net", "ns2.example.net"],
    "dnssec_signed": true,
    "statuses": ["clientTransferProhibited"]
  }
}

Use the same payload for the next paid call: 

agentutility price whois
agentutility call whois --data '{"domain":"example.com"}' --max-price 0.005 > whois-current.json

Compare whois-current.json with the saved record before changing a vendor profile, renewing a service, or escalating a link review. A changed field is a reason to inspect the record, not a conclusion about ownership or safety.

Ask for certificates only when the review needs them

Set include_certificates to true when a review also needs the returned certificate-transparency summary. Routine expiry and registrar checks can keep the smaller request body. 

{
  "domain": "example.com",
  "include_certificates": true
}

whois-lookup is the longer route name for the same job and price. Use whois when a tool plan already asks for WHOIS; use whois-lookup when the plan spells out an RDAP lookup.

Current recovery signal

The latest aggregate wallet-recovery snapshot has one repeat WHOIS buyer at risk after a 0.02 USDC cohort spend. This page gives that repeat job a saved request, a price check, and a concrete way to decide when another paid lookup is useful.