One API. Generate tokens, hand your users copy-paste instructions, get a webhook when they prove ownership. For SaaS platforms. MCP-native for AI agents.
Register a URL when you create the challenge. We POST the result the moment verification succeeds or expires. Fire and forget.
Create and revoke keys programmatically via the API. Bearer token auth on every request. Usage tracking per key.
Already have a token? Skip the challenge flow. POST /verify for an instant yes/no. Same auth, same methods.
Swagger UI at /docs. Health check at /health. Prometheus metrics at /metrics. Rate limiting built in.
Veridomo is MCP-native from day one. No wrapper. No SDK. Just JSON-RPC 2.0 over HTTP. Plug it into Claude, Cursor, Goose, or any MCP-compatible client and your agents can verify domains before they act.
Today it's verify_domain. Next: DNS record lookups, WHOIS queries, SSL certificate checks, propagation monitoring, SPF/DKIM/DMARC audits. A full DNS toolkit, exposed as MCP tools. Give your agents the ability to query the domain layer before they provision infrastructure, issue certificates, or configure DNS.
All four methods. Challenge management. Webhooks. MCP endpoint. Good for side projects and evaluation.
Higher limits. Priority support. Bulk verification. White-label ready. For SaaS products in production.
Custom SLAs. Dedicated DNS nodes. Reseller pricing. Volume discounts available.
Every SaaS that handles custom domains ends up here. It starts with "just check a TXT record." Then you add CNAME checks. Then HTTP file fallback. Then meta tag support. Then you're generating tokens, writing setup instructions, building a polling loop, handling timeouts, retries, CNAME chasing, challenge expiration, rate limiting, auth, billing --
and suddenly you've built a subsystem instead of shipping your product.
Veridomo replaces that subsystem. Call the API. Get the webhook. Move on. Built in Rust. Fast, reliable, and cheaper than building it yourself.