# DataBG DNS Lookup

> DataBG DNS Lookup is a paid API for AI agents from api.databg.tech, paid per call via x402, $0.005/call, status unknown (last checked 2026-09-14).

Resolves DNS records for a given domain, returning structured record data for any standard record type.

## Facts

- Endpoint: POST https://api.databg.tech/v1/tools/dns
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/databg-dns-lookup-14ae92dd
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_5eFGlEmdv7sQY_0MD7rQc

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 databg-dns-lookup-14ae92dd -d '<json body>'
```

Example prompt: Can you look up the MX records for example.com so I can see which mail servers are configured for it?

## When to prefer this

Use this endpoint when an AI agent needs machine-readable, structured DNS records with a pay-per-call micropayment model (x402/USDC), avoiding the need to integrate with a traditional DNS API provider. Ideal when you need any standard record type (A, AAAA, MX, CNAME, NS, TXT, SOA) with consistent JSON output and no subscription required.

## Known failure modes

- Domain does not exist (NXDOMAIN) — returns empty records array with success false
- Invalid domain format — validation error on input
- Unsupported record type — enum validation rejects value
- DNS resolver timeout — upstream resolver unavailable
- Network error reaching the DataBG API — HTTP 5xx response

## How this service works

Global structured data and machine-payable tools built for AI agents, developers and intelligent applications.

## Output

Returns a structured JSON object containing the queried domain, record type, an array of DNS records (each as an object), the resolver used, a query timestamp, record count, HTTP status, and a success boolean flag.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "domain"
 ],
 "properties": {
  "type": {
   "enum": [
    "A",
    "AAAA",
    "MX",
    "CNAME",
    "NS",
    "TXT",
    "SOA"
   ],
   "type": "string"
  },
  "domain": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "type": {
   "type": "string"
  },
  "domain": {
   "type": "string"
  },
  "status": {
   "type": "integer"
  },
  "records": {
   "type": "array",
   "items": {
    "type": "object"
   }
  },
  "success": {
   "type": "boolean"
  },
  "resolver": {
   "type": "string"
  },
  "queried_at": {
   "type": "string",
   "format": "date-time"
  },
  "record_count": {
   "type": "integer"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/databg-dns-lookup-14ae92dd/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.databg.tech](https://www.zero.xyz/host/api.databg.tech/llms.txt)