DNS and domain intelligence: A/AAAA/CNAME, MX (sorted), NS, TXT, SOA records plus email…
DNS and domain intelligence: A/AAAA/CNAME, MX (sorted), NS, TXT, SOA records plus email security posture — SPF record, DMARC policy, and DKIM selector probing. For deliverability, security, and research agents. ?domain=example.com
by api.webbersites.com · discovered, not yet claimed by its owner · updated 2026-10-11
Mirrored from Coinbase's public x402 Bazaar. The description is the provider's own text and has not been reviewed here; the payment requirements are copied as published.
What it does
DNS and domain intelligence: A/AAAA/CNAME, MX (sorted), NS, TXT, SOA records plus email security posture — SPF record, DMARC policy, and DKIM selector probing. For deliverability, security, and research agents. ?domain=example.com
Tags: Domain & Email Intelligence · bazaar
Call contract
- Method
- GET
- Input
- query parameters
- Output
- json
- Last paid call
- 2026-10-11
{
"domain": "example.com"
}{
"domain": "example.com",
"email": {
"dkim": {
"found_selectors": []
},
"dmarc": {
"policy": "reject",
"present": true
},
"mail_configured": true,
"spf": {
"present": true
}
},
"records": {
"a": [
"93.184.215.14"
],
"mx": [
{
"exchange": "mail.example.com",
"priority": 10
}
],
"ns": [
"a.iana-servers.net"
],
"txt": [
"v=spf1 -all"
]
},
"resolves": true
}Use with an agent
- Discover. Agents find this listing with
GET https://bazaar.saylorinnovations.com/discovery/search?query=…, the MCP toolsearch_resources, or/discovery/resources. - Inspect. Fetch
/resources/28923.jsonfor the price and payment options. - Pay. Call
GET https://api.webbersites.com/api/dns. The provider answers402with its payment requirements. An x402 client signs one of the options below and retries withPAYMENT-SIGNATURE. - Execute. The provider returns
200with the data. Agent Bazaar is not in the request path and never sees your payment.
For humans
You don't need an account or an API key; you need a wallet holding a small amount of USDC on Base, and an x402-capable client (see the examples below). Call the endpoint unpaid first to see exactly what it asks for.
Pricing & payment
- Price
- $0.002 / request
- Protocol
- x402 v2
- Auth
- No account or API key. Pay per request.
- Networks
- Base
- Demand
- 6 calls · 4 unique payers in 30d (public x402 Bazaar data)
x402 payment requirements
| Scheme | Network | Asset | Amount | Pay to | Timeout |
|---|---|---|---|---|---|
| exact | Base eip155:8453 | USDC | $0.002 | 0xdd5fcEa81CA6f1EB39FEd5B973DE794293B81ba6 | 300s |
accepts[] (raw JSON)
[
{
"scheme": "exact",
"network": "eip155:8453",
"payTo": "0xdd5fcEa81CA6f1EB39FEd5B973DE794293B81ba6",
"asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
"amount": "2000",
"amountUsd": 0.002,
"maxTimeoutSeconds": 300
}
]Schemas
Output schema (JSON Schema)
{
"properties": {
"example": {
"properties": {
"domain": {
"type": "string"
},
"email": {
"type": "object"
},
"records": {
"type": "object"
},
"resolves": {
"type": "boolean"
}
},
"type": "object"
},
"type": {
"type": "string"
}
},
"required": [
"type"
],
"type": "object"
}Example shape — generated from the schema, not a captured live response
{
"example": {
"domain": "string",
"email": {},
"records": {},
"resolves": true
},
"type": "string"
}Examples
curl -X GET 'https://api.webbersites.com/api/dns'
# -> 402 Payment Required; read PAYMENT-REQUIRED
# retry the identical request with PAYMENT-SIGNATUREconst res = await fetch("https://api.webbersites.com/api/dns", {
"method": "GET"
});
if (res.status === 402) {
const { accepts } = await res.json();
// pay one of accepts[] via an x402 client, then retry with the payment header
}import httpx
res = httpx.request("GET", "https://api.webbersites.com/api/dns")
if res.status_code == 402:
accepts = res.json()["accepts"]
# pay one of accepts[] via an x402 client, then retry with the payment headerDetails
- Provider
- api.webbersites.com
- Endpoint
- https://api.webbersites.com/api/dns
- Machine-readable
/resources/28923.json