# DNS Doctor Watch Ping

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

Starts a recurring DNS monitoring watch job for a URL, polling at configurable intervals to track DNS health changes over time.

## Facts

- Endpoint: POST https://dnsdoctor.dev/api/v1/watch/ping
- Price: $0.004167/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/dns-doctor-watch-ping-441a983f
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_IrFJfd81S59gtsl0R9x5V

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-watch-ping-441a983f -d '<json body>'
```

Example prompt: Set up a DNS watch on example.com that checks every 5 minutes for the next 12 hours so I can track whether my DNS changes are propagating correctly.

## When to prefer this

Use this endpoint when you need continuous, scheduled DNS monitoring over a defined window rather than a one-shot DNS scan. It is ideal after DNS record changes (SPF, DMARC, DKIM, A records) when you want to watch propagation in near-real-time at 5- or 15-minute intervals without manually re-triggering checks. Prefer it over single-scan endpoints when tracking temporal changes matters.

## Known failure modes

- Invalid or unreachable URL returns an error
- window_hours outside the 1–24 range causes a validation error
- cadence_seconds must be exactly 300 or 900; other values are rejected
- Expired or duplicate watch IDs may result in conflicts
- Payment failure (x402) prevents job creation

## How this service works

One DNS Doctor HTTP ping watch: a URL is checked from five regions on four continents on a 5- or 15-minute cadence for a paid window of up to 24 hours, polled by handle.

## Output

Returns a JSON object containing a unique watch_id, the state of the watch job (e.g. 'running'), a poll_url to retrieve updates, and an expires_at timestamp indicating when the watch window ends.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "url": {
   "type": "string"
  },
  "window_hours": {
   "type": "number",
   "maximum": 24,
   "minimum": 1
  },
  "cadence_seconds": {
   "enum": [
    300,
    900
   ],
   "type": "integer"
  }
 }
}
```

## 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-watch-ping-441a983f/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)