API Docs↗
DOMAIN INTELLIGENCE

DNS Lookup API.

Resolve public DNS records programmatically and return structured results for AI agents, security tools and automated workflows.

$0.005Per request
USDCPayment currency
BaseMainnet
x402Machine payment
DNS RECORDS

Resolve DNS
without scraping.

Query public DNS over HTTPS and receive normalized machine-readable records for common DNS types.

ENDPOINT

GET /v1/tools/dns

Provide a domain and optionally select a DNS record type.

?domain=google.com&type=A
SUPPORTED

Common DNS records

Designed for practical domain and infrastructure lookups.

AAAAAMXCNAMENSTXTSOA
USE CASES

Infrastructure intelligence

Useful for domain research, security automation, email configuration checks and agent workflows.

SecurityInfrastructureResearch
API DISCOVERY

Ready for AI agents.

Use the machine-readable API specification to integrate DNS lookups into autonomous workflows.

View OpenAPI →
DETAILED DOCUMENTATION

API reference for AI agents and developers.

DataBG tools are designed as small, machine-readable building blocks for automated workflows. Each request uses a predictable HTTP endpoint and can be accessed with an API key or, where enabled, through x402 machine payments.

DNS LOOKUP API

Resolve public DNS records with one API request

The DataBG DNS Lookup API provides programmatic access to common public DNS records. It is designed for AI agents, developers and infrastructure workflows that need domain information in structured JSON rather than through manual DNS tools.

Request

GET https://api.databg.tech/v1/tools/dns?domain=example.com&type=A

Required: domain. Optional: type. The supported record types are A, AAAA, MX, CNAME, NS, TXT and SOA. The default type is A.

Record types

A and AAAA are useful for address resolution; MX for mail routing; CNAME for aliases; NS for authoritative name servers; TXT for text-based DNS configuration; and SOA for start-of-authority information.

How AI agents can use DNS data

DNS information can enrich domain profiles, support infrastructure research, help investigate email configuration and provide context for security and monitoring workflows. Agents can also combine DNS results with DataBG Domain Lookup and SSL Certificate tools.

Transport and output

The service resolves public DNS using DNS over HTTPS and returns machine-readable results. This is useful when an application needs a simple HTTP interface instead of maintaining its own DNS resolver integration.

Access and errors

The listed price is $0.005 per request in USDC on Base Mainnet. Clients should handle HTTP 400 for invalid or unsupported queries, HTTP 402 for payment requirements and HTTP 502 for resolver failures.

MACHINE PAYMENTS

How x402 access works

DataBG paid tools can use the HTTP 402 Payment Required flow. A compatible client requests a resource, receives machine-readable payment requirements, settles the requested amount in USDC on Base Mainnet, and retries the request with payment authorization. This model is designed for autonomous software that can discover and pay for individual API calls.

Agent → DataBG endpoint
       ↓
402 Payment Required
       ↓
USDC payment on Base Mainnet
       ↓
Retry with payment authorization
       ↓
Structured JSON

For implementation details, use the live API specification and machine-readable discovery resources linked below.

Open API specification → Machine-readable discovery →