# DNS-over-HTTPS Lookup

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

Performs a DNS-over-HTTPS (DoH) lookup for a given hostname and DNS record type, returning the resolved records.

## Facts

- Endpoint: GET https://pyfile-agent.taile3ff35.ts.net:10000/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-018362e1
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_mFKYsiJWcGfk3deSz5mNk

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-018362e1
```

Example prompt: Can you look up the A record for github.com using DNS-over-HTTPS?

## When to prefer this

Choose this endpoint when you need a quick, programmatic DNS lookup without relying on a local system resolver, especially in environments where UDP DNS is blocked or unreliable. It is well-suited for verifying domain configuration (MX, TXT, SPF, CNAME), checking DNS propagation, or enriching data pipelines with resolved IP addresses. Prefer this over system-level DNS when you need consistent DoH-based resolution as a paid, auditable API call.

## Known failure modes

- Non-existent domain returns NXDOMAIN or empty answer section
- Unsupported record type may return an error or empty result
- Network timeout if the upstream DNS resolver is unreachable
- Missing required 'name' or 'type' query parameters returns a 4xx error
- Rate limiting may occur under heavy usage

## How this service works

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

## Output

Returns the DNS response for the queried hostname and record type, including one or more record values (e.g. IP addresses, MX priorities, TXT strings) and typically TTL information, formatted as a JSON object matching standard DoH response structure.

## 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-018362e1/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from pyfile-agent.taile3ff35.ts.net:10000](https://www.zero.xyz/host/pyfile-agent.taile3ff35.ts.net%3A10000/llms.txt)