# Foundry DNS Deployment Contract Verifier

> Foundry DNS Deployment Contract Verifier is a paid API for AI agents from foundry-par007-machine-revenue-mainnet.inference-chip-index.workers.dev, paid per call via x402, $0.007/call, status unknown (last checked 2026-09-14).

Compares expected DNS records against live resolver observations for a domain and returns a structured diff with source evidence

## Facts

- Endpoint: POST https://foundry-par007-machine-revenue-mainnet.inference-chip-index.workers.dev/v2/domain/dns-deployment-contract
- Price: $0.007/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/foundry-dns-deployment-contract-verifier-efa21fb5
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_FA8PuuLll8msPDF9QacO4

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 foundry-dns-deployment-contract-verifier-efa21fb5 -d '<json body>'
```

Example prompt: Check if example.com has these DNS records live: MX pointing to mail.example.com and a TXT record containing 'v=spf1 include:sendgrid.net ~all' — I want to see what the resolver actually sees versus what I expect.

## When to prefer this

Choose this endpoint when you need cryptographically-sourced, pay-per-request DNS comparison evidence with explicit source attribution and structured diffs — particularly for deployment verification, compliance auditing, or agent workflows that need machine-readable proof of DNS state rather than a human-readable lookup. Prefer over generic DNS tools when you need provenance, DNSSEC status, and structured added/missing diffs in a single call.

## Known failure modes

- Resolver failure (rcode 2/SERVFAIL) returns status UNKNOWN with empty records and a synthetic evidence object
- Domain not found or NXDOMAIN returns empty observed records with appropriate rcode
- TXT record semantic equivalence not guaranteed — lexical differences reported as mismatches even if functionally identical
- Requested record types not present in DNS return empty observed arrays with UNKNOWN status
- Input domain exceeding 253 characters or records array outside 1-5 item bounds returns validation error

## How this service works

Pay-per-request evidence and data tools: CSV validation and reconciliation, DNS/email configuration evidence, and bounded official weather, earthquake, vehicle, company and study records. Exact USDC prices, explicit JSON contracts and source provenance. No mailbox, ownership, medical or safety guarantees.

## Output

A JSON object containing the domain, observation timestamp, and a comparisons array — one entry per requested record type — each with status (MATCH/MISMATCH/UNKNOWN), lists of added and missing records, the raw observed records from the resolver, DNSSEC status, and full source attribution including resolver URL and provenance statement. Includes explicit limitations around ownership, mailbox existence, and SMTP delivery.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "domain": {
   "type": "string",
   "maxLength": 253,
   "minLength": 3
  },
  "records": {
   "type": "array",
   "items": {
    "type": "object",
    "required": [
     "type",
     "records"
    ],
    "properties": {
     "type": {
      "enum": [
       "A",
       "AAAA",
       "MX",
       "NS",
       "TXT"
      ],
      "type": "string"
     },
     "records": {
      "type": "array",
      "items": {
       "type": "string",
       "maxLength": 4096
      },
      "maxItems": 32
     }
    },
    "additionalProperties": false
   },
   "maxItems": 5,
   "minItems": 1
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "route": "dns-deployment-contract",
  "result": {
   "domain": "example.com",
   "observedAt": "2026-09-06T00:00:00Z",
   "comparisons": [
    {
     "type": "MX",
     "added": [],
     "status": "UNKNOWN",
     "missing": [],
     "evidence": {
      "name": "example.com",
      "type": "MX",
      "rcode": 2,
      "dnssec": "UNKNOWN",
      "source": "https://cloudflare-dns.com/dns-query?name=example.com&type=MX",
      "status": "UNKNOWN",
      "records": [],
      "observedAt": "2026-09-06T00:00:00Z",
      "attribution": "Cloudflare 1.1.1.1 public resolver; authoritative DNS records; no endorsement"
     },
     "observed": []
    }
   ],
   "limitations": [
    "DNS records only; no ownership, mailbox existence, SMTP acceptance or delivery conclusion.",
    "TXT records compare exact presentation strings; IP and TXT lexical differences can be reported without semantic equivalence.",
    "Changes exclude TTL and compare only requested apex record types. No persistent watcher or guessed selectors.",
    "Synthetic example of a resolver failure; no current observation claimed."
   ]
  },
  "observed_at": "2026-09-06T00:00:00Z"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/foundry-dns-deployment-contract-verifier-efa21fb5/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from foundry-par007-machine-revenue-mainnet.inference-chip-index.workers.dev](https://www.zero.xyz/host/foundry-par007-machine-revenue-mainnet.inference-chip-index.workers.dev/llms.txt)