Infrastructure x402 offerings

Change watch for does site use webp images: runs the check, compares it with the result from your previous call for the same domain (kept 90 days) and returns the current answer, changed true/false, the fields that changed with before/after values, and when it was last seen. Schedule it to be alerted when this changes. $0.02 per check.

Change watch for does site use wistia: runs the check, compares it with the result from your previous call for the same domain (kept 90 days) and returns the current answer, changed true/false, the fields that changed with before/after values, and when it was last seen. Schedule it to be alerted when this changes. $0.02 per check.

Change watch for does site use wix: runs the check, compares it with the result from your previous call for the same domain (kept 90 days) and returns the current answer, changed true/false, the fields that changed with before/after values, and when it was last seen. Schedule it to be alerted when this changes. $0.02 per check.

Change watch for does site use yandex metrica: runs the check, compares it with the result from your previous call for the same domain (kept 90 days) and returns the current answer, changed true/false, the fields that changed with before/after values, and when it was last seen. Schedule it to be alerted when this changes. $0.02 per check.

Change watch for does site use yotpo: runs the check, compares it with the result from your previous call for the same domain (kept 90 days) and returns the current answer, changed true/false, the fields that changed with before/after values, and when it was last seen. Schedule it to be alerted when this changes. $0.02 per check.

Change watch for does site use youtube embed: runs the check, compares it with the result from your previous call for the same domain (kept 90 days) and returns the current answer, changed true/false, the fields that changed with before/after values, and when it was last seen. Schedule it to be alerted when this changes. $0.02 per check.

Change watch for does site use zapier: runs the check, compares it with the result from your previous call for the same domain (kept 90 days) and returns the current answer, changed true/false, the fields that changed with before/after values, and when it was last seen. Schedule it to be alerted when this changes. $0.02 per check.

Change watch for does site use zendesk chat: runs the check, compares it with the result from your previous call for the same domain (kept 90 days) and returns the current answer, changed true/false, the fields that changed with before/after values, and when it was last seen. Schedule it to be alerted when this changes. $0.02 per check.

Send a list of domain names and this tool tells you exactly how old each one is, when it was first registered, when it expires, and how much time is left before expiration. Great for spotting brand-new suspicious domains, researching competitors, or evaluating domains before buying or linking to them. Works with over 100 domain extensions worldwide.

Check a domain in one call: registration via RDAP (registered or likely available, registrar, created and expiry dates, status, nameservers; DNS fallback for TLDs without RDAP), DNS (A, NS, MX, CAA, DNSSEC) and email security (SPF, DMARC policy, DKIM on common selectors) with a 0 to 100 score, grade and findings. Params: domain (required).

Give this API up to 10 domain names and it tells you whether each has a registration record at the official registry. It uses RDAP, the structured replacement for WHOIS, so there is no free-text parsing. Each domain comes back as 'registered', 'unregistered', or 'indeterminate' when the registry has no RDAP for that ending. 'Unregistered' means no record was found, which usually means available - but reserved and premium names also return no record. Registration status only; no pricing.

Due-diligence check on any domain: registration age via RDAP, registrar, DNS posture (A/MX/NS), SPF and DMARC presence, SSL certificate history, and risk flags like newly-registered or no-mail-setup. One call, one JSON verdict. $0.008 USDC per call, pay via x402, no API key.

Screen a domain name for phishing, fraud, and scam association in the C3 community database. Matches the exact hostname and its subdomains. Returns risk score and matching report details.

Use when an agent must decide whether a domain is real and reachable before trusting it: everything DNS says about it in one call - whether it is registered, its A and AAAA addresses, nameservers, MX servers, SPF and DMARC, DNSSEC, and whether it looks parked. Built for going through a list of domains one at a time. Live DNS, no API key, no account.

Live DNS records resolved via Cloudflare 1.1.1.1 DNS-over-HTTPS (public facts, real time). Query: ?name=anthropic.com&type=MX (type in A|AAAA|MX|TXT|NS|CNAME, default MX). Or ?name=anthropic.com&check=email -> combined MX + SPF + DMARC with an email_ready boolean, useful before emailing or invoicing a contact. JSON with records list; 5 min cache.

DNS/domain-security intelligence for agents: A/AAAA/MX/TXT/NS/CNAME/SOA, structured CAA issuance policy, SPF/DMARC, parsed common-selector DKIM evidence, MTA-STS/TLS-RPT, BIMI readiness, DNSSEC plus RDAP age/expiry, registrar-lock and nameserver-redundancy signals.

Focused email-authentication diagnostics for agents: MX routing/provider hint, SPF mechanisms/include/redirect/all plus bounded recursive potential DNS-lookup analysis against the RFC limit of 10, DMARC p/sp/pct/alignment/reporting metadata, parsed common-selector DKIM evidence, MTA-STS/TLS-RPT, BIMI DNS/DMARC readiness, CAA issuance posture, DNSSEC, compact registrar-lock/expiry context, transparent risk flags and prioritized deterministic fixes.

Domain Health Check API. Check domain DNS, MX, SPF, DMARC, and email configuration health and receive a structured JSON score with issues and recommendations. Useful for agents, developers, email deliverability checks, domain diagnostics, infrastructure investigation, and security workflows. Paid per call via x402.

Requires an unauthenticated caller-owned baseline; returns real current NS/MX records, added/removed sets and tri-state target-provider transition. Current DNS comes from one bounded native recursive-resolver query; existing Dossier provides context. Resolver caching may apply; no account ownership or global migration-completion claim. Existing provider patterns are reused without new invented attribution. At most50records,domain253chars,9sbudget; DNSsubquery2s/oneattempt. Unknown provider remai

Requires an unauthenticated caller-owned baseline; returns real current NS/MX records, added/removed sets and tri-state target-provider transition. Current DNS comes from one bounded native recursive-resolver query; existing Dossier provides context. Resolver caching may apply; no account ownership or global migration-completion claim. Existing provider patterns are reused without new invented attribution. At most50records,domain253chars,9sbudget; DNSsubquery2s/oneattempt. Unknown provider remai

Requires an unauthenticated caller-owned baseline; returns real current NS/MX records, added/removed sets and tri-state target-provider transition. Current DNS comes from one bounded native recursive-resolver query; existing Dossier provides context. Resolver caching may apply; no account ownership or global migration-completion claim. Existing provider patterns are reused without new invented attribution. At most50records,domain253chars,9sbudget; DNSsubquery2s/oneattempt. Unknown provider remai

Requires an unauthenticated caller-owned baseline; returns real current NS/MX records, added/removed sets and tri-state target-provider transition. Current DNS comes from one bounded native recursive-resolver query; existing Dossier provides context. Resolver caching may apply; no account ownership or global migration-completion claim. Existing provider patterns are reused without new invented attribution. At most50records,domain253chars,9sbudget; DNSsubquery2s/oneattempt. Unknown provider remai

Requires an unauthenticated caller-owned baseline; returns real current NS/MX records, added/removed sets and tri-state target-provider transition. Current DNS comes from one bounded native recursive-resolver query; existing Dossier provides context. Resolver caching may apply; no account ownership or global migration-completion claim. Existing provider patterns are reused without new invented attribution. At most50records,domain253chars,9sbudget; DNSsubquery2s/oneattempt. Unknown provider remai

Requires an unauthenticated caller-owned baseline; returns real current NS/MX records, added/removed sets and tri-state target-provider transition. Current DNS comes from one bounded native recursive-resolver query; existing Dossier provides context. Resolver caching may apply; no account ownership or global migration-completion claim. Existing provider patterns are reused without new invented attribution. At most50records,domain253chars,9sbudget; DNSsubquery2s/oneattempt. Unknown provider remai