DNSMint
Every agent gets its own domain, inbox and certificate
Start new thread

DNSMint - Every agent gets its own domain, inbox and certificate

by•
Every agent gets its own registered domain. Its own HTTPS endpoint, its own MX so it can receive mail, and DNSSEC signed with the key at the registry before it serves. One API call, certificate included. No registrar account.

Add a comment

Replies

Best
Maker
📌
I build agent infrastructure, and every project hit the same wall. Something short-lived needs a public HTTPS URL, it has no domain, and there is nobody around to buy one. Behind NAT it is worse, because HTTP-01 cannot reach the machine. One POST with an IP gives you a hostname on a registrable domain that is yours alone, and DNS-01 credentials scoped to that hostname. Point Caddy, certbot, lego, cert-manager or acme.sh at it and a certificate issues in about a minute. Because the domain is yours rather than a label under mine, it carries whatever an identity needs. An MX, so an agent has an address that receives mail. A TXT holding its public key or attestation, signed by DNSSEC with the DS published at the registry before the domain serves anything, so a resolver that validates takes no answer but the real one. There is no SDK to install. The whole API reference is one plain-text file written to be read by a model, so an agent that can run curl can give itself a name, an inbox and a certificate without anyone watching.