# DNS Record Diff

> DNS Record Diff is a paid API for AI agents from api.delx.ai, paid per call via x402, $0.001/call, status unknown (last checked 2026-09-15).

Compares two caller-supplied DNS record snapshots and returns a deterministic diff of added, removed, and unchanged records without making any live DNS requests.

## Facts

- Endpoint: POST https://api.delx.ai/api/v1/x402/dns-record-diff
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/dns-record-diff-d9236ad8
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_AE1P566GOnBqu04MT1I39

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-record-diff-d9236ad8 -d '<json body>'
```

Example prompt: Compare these two DNS record snapshots I captured before and after the deployment — the before list has the old records and the after list has the new ones — and tell me exactly which records were added, removed, or stayed the same.

## When to prefer this

Use this endpoint when you already have two DNS record snapshots in memory and need a fast, deterministic diff without issuing another live DNS lookup. Ideal after repeated DNS or MX inspections to detect infrastructure changes cheaply. Prefer this over re-querying DNS when network calls are expensive, rate-limited, or when you need a reproducible audit trail of exactly what changed between two known states.

## Known failure modes

- Exceeds 500-item limit on either 'before' or 'after' array — request rejected
- Malformed array items that cannot be compared — may produce unexpected diff results
- Missing 'before' or 'after' fields — invalid input error
- Payment failure via x402 — request not processed

## How this service works

Compare two bounded caller-supplied DNS record snapshots and return canonical added, removed, and unchanged records. Use after repeated DNS or MX inspections to detect an infrastructure change without another parser. Returns deterministic JSON for 0.001 USDC via x402 on Base; local-only, memory-only, and no DNS request is made.

## Output

A deterministic JSON object containing three lists: added records (present in 'after' but not 'before'), removed records (present in 'before' but not 'after'), and unchanged records (present in both). No live DNS requests are made; computation is entirely local and memory-only.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "after": {
   "type": "array",
   "maxItems": 500
  },
  "before": {
   "type": "array",
   "maxItems": 500
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "added": [
   {
    "type": "A",
    "value": "192.0.2.2"
   }
  ],
  "schema": "delx/util-dns-record-diff/v1",
  "changed": true,
  "removed": [
   {
    "type": "A",
    "value": "192.0.2.1"
   }
  ],
  "after_count": 1,
  "before_count": 1,
  "unchanged_count": 0
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/dns-record-diff-d9236ad8/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.delx.ai](https://www.zero.xyz/host/api.delx.ai/llms.txt)