80trust / 100

Domain

by agosint in Developer tools

x402 APIPassing, checked 2 h ago

Domain intelligence and phishing-risk signals: domain age and expiry (RDAP/WHOIS), registrar, DNS (A, AAAA, MX, NS, TXT, CAA), SPF, DMARC and MTA-STS, DNSSEC, TLS certificate issuer and expiry, hosting network, and the company behind the site when it can be identified. Use when: deciding whether a domain, link or email sender is legitimate, or checking a domain's mail setup.

POST
https://agosint.shveik.dev/x402/domain
Price
$0.015
per call in USDC
Uptime
100%
last 30 days
Response time
108 ms
163 ms slowest 5%
Last check
Passed
2 h ago, next any minute now

Run a free test callHow to call it

Reliability

All checks passedSome failedAll failedNot checked

Status and outage history · Atom feed

How to call it

POST https://agosint.shveik.dev/x402/domain

Each call costs $0.015 in USDC on Base, paid with the request over x402.

Run a free test callOne unpaid request, the way an agent sends it. You see the payment challenge it gets back. Nothing is charged.

Example request

From the listing.

POST https://agosint.shveik.dev/x402/domain
content-type: application/json

{
  "domain": "example.com"
}

Parameters

ParameterTypeRequiredDescription
domainstringYes

Example response

The provider's example. We can't check it without paying.

{
  "age_days": 11113,
  "dns": {},
  "domain": "cez.cz",
  "entity_hint": {},
  "hosting": {},
  "mail_security": {},
  "note": "Public r…",
  "rdap": {},
  "receipt": {},
  "retrieved_at": "2026-10-…",
  "schema": "agosint.…",
  "signals": [],
  "source": "RDAP via…",
  "source_url": "https://…",
  "tls": {}
}

Call it from code

The curl command shows the payment challenge. The JavaScript and Python versions pay and call, and never pay more than $0.015.

curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i -X POST 'https://agosint.shveik.dev/x402/domain' \
  -H 'content-type: application/json' \
  --data-raw '{"domain":"example.com"}'

# x402 v2 sends the challenge base64-encoded in the PAYMENT-REQUIRED header (v1 sends it in the body).
# To read the header:
curl -sS -g -o /dev/null -D - -X POST 'https://agosint.shveik.dev/x402/domain' \
  -H 'content-type: application/json' \
  --data-raw '{"domain":"example.com"}' \
  | grep -i '^payment-required:' | cut -d' ' -f2 | tr -d '\r' | base64 --decode
JavaScript: pay and call
// npm i @x402/fetch @x402/evm viem
import { wrapFetchWithPayment, x402Client } from "@x402/fetch";
import { registerExactEvmScheme } from "@x402/evm/exact/client";
import { privateKeyToAccount } from "viem/accounts";

// Pays at most $0.015 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.015" });
registerExactEvmScheme(client, { signer: privateKeyToAccount(process.env.EVM_PRIVATE_KEY) });
const pay = wrapFetchWithPayment(fetch, client);

// Not sure it's safe to pay? ToolVet checks it first for $0.005. Pay for that from a separate
// client: this one is capped at $0.015 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fagosint.shveik.dev%2Fx402%2Fdomain&method=POST
const res = await pay("https://agosint.shveik.dev/x402/domain", {
  method: "POST",
  headers: { "content-type": "application/json" },
  body: JSON.stringify({
    "domain": "example.com"
  }),
});
console.log(res.status, await res.text());
Python: pay and call
# pip install "x402[requests,evm]"
import os
from eth_account import Account
from x402 import x402ClientSync
from x402.http.clients import x402_requests
from x402.mechanisms.evm import EthAccountSigner
from x402.mechanisms.evm.exact.register import register_exact_evm_client

# Pays at most $0.015 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.015"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))

with x402_requests(client) as session:
    res = session.post(
        "https://agosint.shveik.dev/x402/domain",
        json={
            "domain": "example.com",
        },
    )
    print(res.status_code, res.text)

Security scan

No findings

We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.

Recent checks

WhenResultHTTPTimePrice
2 h agoPassed402113 ms$0.015
6 h agoPassed40298 ms$0.015
11 h agoPassed402163 ms$0.015
15 h agoPassed402139 ms$0.015
18 h agoPassed402109 ms$0.015
Show 10 older checks
22 h agoPassed402105 ms$0.015
26 h agoPassed402134 ms$0.015
30 h agoPassed402150 ms$0.015
34 h agoPassed402146 ms$0.015
38 h agoPassed402175 ms$0.015
41 h agoPassed40296 ms$0.015
45 h agoPassed40288 ms$0.015
2 days agoPassed402100 ms$0.015
2 days agoPassed40297 ms$0.015
2 days agoPassed402108 ms$0.015