API Docs↗
API DOCUMENTATION

Build with DataBG.
Designed for agents.

Use predictable HTTP APIs, structured JSON, machine-readable discovery and x402 payments to connect AI agents and applications with web, domain, network and blockchain intelligence.

OVERVIEW

Data infrastructure for AI agents

DataBG provides structured datasets and machine-payable utility APIs. The tools are intentionally small and composable: an agent can use a single endpoint for a specific operation, combine several tools in sequence, and receive JSON that can be passed directly into its next reasoning step.

The current tool catalog covers web extraction, website metadata, DNS records, TLS certificate intelligence, combined domain intelligence, IP geolocation and Base Mainnet wallet balances.

TOOL REFERENCE

All DataBG API tools

WEB INTELLIGENCE

Web Page Extraction

Fetch a public HTTP or HTTPS page and return structured metadata, visible text and links.

GET /v1/web/extract · $0.005
WEB INTELLIGENCE

Web Page Metadata

Extract SEO, Open Graph, Twitter and technical metadata from a public web page.

GET /v1/web/metadata · $0.003
DOMAIN INTELLIGENCE

DNS Lookup

Resolve public A, AAAA, MX, CNAME, NS, TXT and SOA records.

GET /v1/tools/dns · $0.005
DOMAIN INTELLIGENCE

SSL Certificate Check

Inspect publicly logged TLS certificate information, including certificate and validity signals.

GET /v1/tools/ssl · $0.005
DOMAIN INTELLIGENCE

Domain Lookup

Combine public DNS and publicly logged TLS certificate intelligence for a domain.

GET /v1/tools/domain/lookup · $0.005
NETWORK INTELLIGENCE

IP Geolocation

Resolve a public IPv4 or IPv6 address to structured location and network information.

GET /v1/tools/ip/geolocation · $0.003
BLOCKCHAIN INTELLIGENCE

Wallet Balance

Read the native ETH balance of an EVM wallet on Base Mainnet.

GET /v1/tools/wallet/balance · $0.002

Open each tool page for its dedicated endpoint documentation, parameters, use cases and implementation guidance.

ACCESS

API keys and machine payments

DataBG supports an API-key access path for authorized clients and x402 machine payments for paid resources. API-key requests use the x-api-key HTTP header. x402-enabled resources can return HTTP 402 Payment Required with machine-readable payment authorization requirements.

API key request
GET https://api.databg.tech/v1/tools/dns?domain=example.com&type=A
x-api-key: YOUR_API_KEY
Accept: application/json
MACHINE DISCOVERY

Let agents discover DataBG automatically

Machine-readable resources make it possible for software to discover the DataBG catalog without relying on the visual website. Use the discovery document for platform-level capabilities and the OpenAPI document for HTTP endpoint definitions.

Discovery endpoints
GET https://api.databg.tech/.well-known/databg.json
GET https://api.databg.tech/.well-known/x402
GET https://api.databg.tech/openapi.json
X402

HTTP 402 machine payment flow

x402 turns an API request into a machine-readable payment negotiation. A client requests a paid resource, receives payment requirements, settles the required amount in USDC on Base Mainnet, and retries the request with payment authorization.

Request lifecycle
1. Agent requests API resource
2. DataBG returns 402 Payment Required
3. Client reads payment requirements
4. Client settles USDC payment on Base Mainnet
5. Client retries with payment authorization
6. DataBG returns structured JSON

This model is particularly suitable for autonomous agents because payment can happen at request time instead of requiring a traditional user account or subscription flow.

ERROR HANDLING

Design agents for predictable failures

Production integrations should treat HTTP status codes as part of the API contract. Depending on the tool, clients may encounter invalid input, payment requirements, upstream failures or internal errors.

400

Bad request

The URL, domain, IP address or other request input is invalid or missing.

402

Payment required

The resource requires x402 payment before the successful data response.

500

Server error

An unexpected error occurred while processing the request.

502

Upstream failure

An external resolver or requested web resource could not be fetched or processed.

AGENT WORKFLOW

Compose multiple tools into one workflow

DataBG tools are designed to be composable. An agent researching a domain could start with Domain Lookup, use DNS Lookup for a specific record type, inspect the TLS certificate with SSL Certificate Check, extract a public page with Web Page Extraction, and use Web Page Metadata when it needs SEO or social signals.

Example reasoning pipeline
Domain Lookup
    ↓
DNS / TLS details
    ↓
Web Page Metadata
    ↓
Web Page Extraction
    ↓
Structured evidence for the agent

For network-aware workflows, IP Geolocation can add geographic and ASN context. For blockchain-aware workflows, Wallet Balance can provide native ETH balance information from Base Mainnet.

Open live API specification →