# Foundry DNS Lookup

> Foundry DNS Lookup is a paid API for AI agents from minty-sprout.onrender.com, paid per call via x402, $0.001/call, status unknown (last checked 2026-11-01).

Resolves DNS records (A, AAAA, MX, TXT, NS, CNAME, SOA, CAA) for a domain using DNS-over-HTTPS via Cloudflare

## Facts

- Endpoint: POST https://minty-sprout.onrender.com/v1/dns-lookup?utm_source=zero.xyz
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-11-01
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/foundry-dns-lookup-c8e571ab
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_j4NKAROq0qdTs4G4msalL

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-lookup-c8e571ab -d '<json body>'
```

Example prompt: What are the MX records for coinbase.com? Use DNS-over-HTTPS to look them up.

## When to prefer this

Use this endpoint when you need to resolve any standard DNS record type for a domain using DNS-over-HTTPS for privacy and reliability. It's ideal for agents checking mail routing, validating domain ownership, verifying security records (SPF, DKIM, DMARC via TXT), or investigating infrastructure. Prefer this over raw DNS queries when you need a structured JSON response with TTL data and no local DNS resolver dependency.

## Known failure modes

- Domain does not exist (NXDOMAIN) — returns empty records or error
- Unsupported record type specified — may return error or empty result
- Malformed input string — missing domain or invalid format
- Network timeout reaching the DoH resolver
- Rate limiting or upstream resolver unavailability

## How this service works

DNS lookup: A, AAAA, MX, TXT, NS, CNAME, SOA or CAA records for a domain, via DNS-over-HTTPS. Input: 'example.com MX'.

## Output

Returns a JSON object with the domain name, queried record type, the list of matching DNS records (each containing name, type, TTL, and data), and the resolver used (e.g. cloudflare-dns.com via DoH).

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "input": {
   "type": "string",
   "maxLength": 8000,
   "description": "Domain, optionally followed by a record type, e.g. 'example.com TXT'"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "name": "coinbase.com",
  "type": "MX",
  "records": [
   {
    "ttl": 300,
    "data": "1 aspmx.l.google.com.",
    "name": "coinbase.com",
    "type": "MX"
   }
  ],
  "resolver": "cloudflare-dns.com (DoH)"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/foundry-dns-lookup-c8e571ab/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from minty-sprout.onrender.com](https://www.zero.xyz/host/minty-sprout.onrender.com/llms.txt)