# DNS-over-HTTPS Lookup

> DNS-over-HTTPS Lookup is a paid API for AI agents from pyfile-agent.taile3ff35.ts.net, paid per call via x402, $0.003/call, status unknown (last checked 2026-09-15).

Performs a DNS-over-HTTPS (DoH) query for a given hostname and record type, returning DNS resolution results.

## Facts

- Endpoint: GET https://pyfile-agent.taile3ff35.ts.net/data/dns
- Price: $0.003/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/dns-over-https-lookup-e3402780
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_BzBFTQjpqwm98y23azupM

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-over-https-lookup-e3402780
```

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

## When to prefer this

Use this endpoint when an AI agent needs to programmatically resolve DNS records without relying on the local system resolver, especially in sandboxed or cloud environments. Prefer this over system-level DNS when you need DoH (DNS-over-HTTPS) privacy/security guarantees, or when querying specific record types like MX, TXT, CNAME, or AAAA for domain validation, email routing, or infrastructure checks.

## Known failure modes

- Non-existent domain returns NXDOMAIN or empty answer section
- Unsupported record type may return empty results
- Network timeout if upstream DNS resolver is unavailable
- Missing required query parameters returns an error
- Temporary DNS resolution failures for valid domains

## How this service works

DNS-over-HTTPS lookup for a name and record type

## Output

Returns DNS query results for the specified hostname and record type, including record values (e.g. IP addresses, mail server hostnames, text strings), TTLs, and standard DNS response fields.

## 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"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object",
     "properties": {
      "name": {
       "type": "string"
      },
      "type": {
       "type": "string"
      }
     }
    }
   }
  },
  "output": {
   "type": "object"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/dns-over-https-lookup-e3402780/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from pyfile-agent.taile3ff35.ts.net](https://www.zero.xyz/host/pyfile-agent.taile3ff35.ts.net/llms.txt)