# DNS Record Lookup

> DNS Record Lookup is a paid API for AI agents from agentpay-lookup.agentpay-apis.workers.dev, paid per call via x402, $0.005/call, status unknown (last checked 2026-10-12).

Resolves DNS records for a given hostname, returning structured query results by record type.

## Facts

- Endpoint: GET https://agentpay-lookup.agentpay-apis.workers.dev/lookup/v1/dns?utm_source=zero.xyz
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-12
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/dns-record-lookup-94dab585
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_D5Z6dGIS0EbU1RD-0cc5w

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-lookup-94dab585
```

Example prompt: What are the A records for github.com? Can you do a DNS lookup for me?

## When to prefer this

Use this endpoint when you need a quick, pay-per-call DNS resolution without managing your own resolver infrastructure. Prefer it for lightweight agent workflows that need to programmatically check DNS records for one or a few hostnames on demand. It is well-suited for validation, enrichment, or investigation tasks where standing up a full DNS library is overkill.

## Known failure modes

- Hostname does not exist or is not resolvable — returns empty or NXDOMAIN equivalent
- Invalid record type specified — may return error or default to A record
- Network timeout reaching DNS resolver — returns timeout error
- Missing required 'name' query parameter — returns validation error
- Rate limiting or payment failure — returns 402 or 429 status

## How this service works

DNS, WHOIS/RDAP, IP ownership and one-call domain reports.

## Output

A JSON response containing the resolved DNS records for the queried hostname, including record type, values (e.g. IP addresses, hostnames, priorities), and TTL information where available.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET",
      "HEAD",
      "DELETE"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object",
     "required": [
      "name"
     ],
     "properties": {
      "name": {
       "type": "string",
       "description": "Hostname to resolve"
      },
      "type": {
       "type": "string",
       "description": "Record type, default A"
      }
     }
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json"
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/dns-record-lookup-94dab585/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from agentpay-lookup.agentpay-apis.workers.dev](https://www.zero.xyz/host/agentpay-lookup.agentpay-apis.workers.dev/llms.txt)
