# fetchx402 DNS Resolver

> fetchx402 DNS Resolver is a paid API for AI agents from api.fetchx402.com, paid per call via x402, $0.005/call, status unknown (last checked 2026-09-13).

Resolves live public DNS records (A, AAAA, MX, TXT, CNAME, NS, SOA) for any fully-qualified domain name

## Facts

- Endpoint: GET https://api.fetchx402.com/v1/tools/dns
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/fetchx402-dns-resolver-2dafcbc9
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_zNIqFT0jjW0Dq7Qd8j5KR

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability fetchx402-dns-resolver-2dafcbc9
```

Example prompt: What are the MX records for github.com right now — look them up live, don't guess from memory.

## When to prefer this

Use this endpoint when you need authoritative, real-time DNS data that cannot be guessed from training data or memory. It is ideal for debugging email delivery (MX/TXT), confirming DNS propagation after changes (A/CNAME), validating domain security configurations (TXT for SPF/DKIM), or enumerating nameservers (NS/SOA). Prefer this over static knowledge bases or web scraping when freshness and accuracy of DNS data is critical.

## Known failure modes

- Domain not found or NXDOMAIN — returns error if the domain does not exist in DNS
- Invalid domain format — IPs, localhost, internal/mDNS names, and malformed hostnames are rejected
- No records of requested type — the domain exists but has no records of the specified type
- DNS resolution timeout — transient network issue reaching upstream resolvers
- Unsupported record type requested — only A, AAAA, MX, TXT, CNAME, NS, SOA are accepted

## How this service works

Resolve public DNS records (A, AAAA, MX, TXT, CNAME, NS, SOA) for a domain. Use when you need live DNS data and must not guess from memory or training data.

## Output

Returns the current live DNS records for the queried domain and record type, including record values (e.g. IP addresses for A records, hostnames and priorities for MX records, string values for TXT records, alias targets for CNAME, nameserver hostnames for NS, and authority data for SOA). Data is fetched in real-time from authoritative or recursive DNS, not from cached training data.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET",
      "HEAD",
      "DELETE"
     ],
     "type": "string"
    },
    "headers": {
     "type": "object",
     "additionalProperties": {
      "type": "string"
     }
    },
    "queryParams": {
     "type": "object",
     "required": [
      "domain"
     ],
     "properties": {
      "type": {
       "enum": [
        "A",
        "AAAA",
        "MX",
        "TXT",
        "CNAME",
        "NS",
        "SOA"
       ],
       "type": "string",
       "description": "DNS record type. A = IPv4 addresses, AAAA = IPv6, MX = mail exchangers, TXT = text (SPF/DKIM), CNAME = alias, NS = nameservers, SOA = start of authority. Defaults to A if omitted."
      },
      "domain": {
       "type": "string",
       "description": "Public fully-qualified domain name to resolve, such as example.com. IPs, localhost, and internal/mDNS names are rejected."
      }
     }
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "ttl": 20,
  "type": "A",
  "rcode": "NOERROR",
  "domain": "example.com",
  "records": [
   {
    "address": "104.20.23.154"
   }
  ],
  "resolver": "1.1.1.1"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/fetchx402-dns-resolver-2dafcbc9/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.fetchx402.com](https://www.zero.xyz/host/api.fetchx402.com/llms.txt)