POST /api/dns-propagationResolve the same DNS record against 4 public resolvers (Google, Cloudflare, Quad9, OpenDNS) in parallel; surface divergences. The first call you make after a DNS change — confirms the world sees what you intended.
| Field | Type | Description |
|---|---|---|
host * | string | Hostname to resolve |
type | string | Record type (default A) |
{
"host": "google.com",
"type": "A",
"consistent": true,
"resolvers": [
{
"resolver": "8.8.8.8",
"name": "Google",
"records": [
"142.250.80.46"
],
"count": 1
},
{
"resolver": "1.1.1.1",
"name": "Cloudflare",
"records": [
"142.250.80.46"
],
"count": 1
},
{
"resolver": "9.9.9.9",
"name": "Quad9",
"records": [
"142.250.80.46"
],
"count": 1
},
{
"resolver": "208.67.222.222",
"name": "OpenDNS",
"records": [
"142.250.80.46"
],
"count": 1
}
],
"queriedAt": "2026-06-19T20:00:00.000Z"
}
curl -i -X POST https://agent402.tools/api/dns-propagation \
-H "Content-Type: application/json" \
-d '{"host":"google.com","type":"A"}'
The response is HTTP 402 Payment Required with exact payment requirements. Any x402 v2 client pays automatically and retries:
import { wrapFetchWithPayment } from "@x402/fetch";
import { x402Client } from "@x402/core/client";
import { registerExactEvmScheme } from "@x402/evm/exact/client";
import { privateKeyToAccount } from "viem/accounts";
const client = new x402Client();
registerExactEvmScheme(client, { signer: privateKeyToAccount(KEY) });
const payFetch = wrapFetchWithPayment(fetch, client);
const res = await payFetch("https://agent402.tools/api/dns-propagation", {
method: "POST",
headers: { "Content-Type": "application/json" },
body: JSON.stringify({
"host": "google.com",
"type": "A"
}),
});
Wallet-only. This tool reaches the network/browser/storage, so it is paid in USDC via x402 (no proof-of-work tier).
GET /api/dnsDNS lookup for a domain. Supported record types: A, AAAA, MX, TXT, NS, CNAME.
POST /api/http-checkCheck any public URL: status code, latency, final URL after redirects, and response headers. The uptime primitive for ag…
POST /api/tls-certInspect the TLS certificate of any public host: subject, issuer, validity window, days remaining, SANs, and SHA-256 fing…