# DNS Doctor — DNS Record Watch

> DNS Doctor — DNS Record Watch is a paid API for AI agents from dnsdoctor.dev, paid per call via x402, $0.004167/call, status unknown (last checked 2026-10-29).

Starts a paid watch job that continuously monitors a specific DNS record type for a domain over a configurable time window, returning a poll URL to retrieve results.

## Facts

- Endpoint: POST https://dnsdoctor.dev/api/v1/watch/record?utm_source=zero.xyz
- Price: $0.004167/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-29
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/dns-doctor-dns-record-watch-b8c769f8
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_5mRnTD3HsxmyPSAsnNiiA

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 dns-doctor-dns-record-watch-b8c769f8 -d '<json body>'
```

Example prompt: Watch my SPF record on example.com for the next 4 hours and let me know when it changes — I just updated it and want to confirm it propagates correctly.

## When to prefer this

Use this endpoint when you need to continuously monitor a specific DNS record over a defined time window (up to 24 hours) rather than doing a one-off snapshot lookup. It is ideal for post-change propagation verification (e.g. after updating SPF, DMARC, MX, or CNAME records) where you want asynchronous polling rather than an immediate result. Prefer the bulk scan endpoint for auditing many domains at once, and prefer the propagation watch endpoint if you want multi-vantage-point geographic checks rather than record-type-specific monitoring.

## Known failure modes

- Invalid record type enum value — must be one of: spf, dmarc, txt, mx, cname, a, aaaa
- window_hours out of range — must be between 1 and 24
- Missing required domain field — returns validation error
- Payment failure via x402 protocol — watch job not created
- Invalid domain format — malformed hostname rejected
- Network timeout before job is queued — no watch_id returned

## How this service works

Scan, fix and verify your domain&#x27;s DNS: SPF, DMARC and DKIM, global propagation, DNS health and expiry. Deterministic copy-paste fixes, never an AI guess.

## Output

Returns a JSON object containing a unique watch_id, a poll_url to check the status of the watch job, the initial state ('running'), and an expires_at timestamp indicating when the watch window ends. The agent must poll the returned poll_url to retrieve actual propagation results.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "host": {
   "type": "string"
  },
  "kind": {
   "enum": [
    "spf",
    "dmarc",
    "txt",
    "mx",
    "cname",
    "a",
    "aaaa"
   ],
   "type": "string"
  },
  "domain": {
   "type": "string"
  },
  "window_hours": {
   "type": "number",
   "maximum": 24,
   "minimum": 1
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "state": "running",
  "poll_url": "https://dnsdoctor.dev/api/v1/watch/wid_example",
  "watch_id": "wid_example",
  "expires_at": "2026-09-06T12:00:00Z"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/dns-doctor-dns-record-watch-b8c769f8/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from dnsdoctor.dev](https://www.zero.xyz/host/dnsdoctor.dev/llms.txt)