Free domains
for agents.
Your AI agent just built a site. Give it a real domain in one command. No new TLD to wait for: a real hostname under makes.fyi or agentdomains.co, today.
Two commands to a live domain
Install the CLI once, then your agent claims names whenever it ships something. The claim writes the record and the hostname resolves on the public internet in seconds — no registrar, no dashboard, no waiting on a human.
$ go install github.com/tashfeenahmed/AgentDomains/cmd/agentdomains@latest
# point a domain at the site your agent just built
$ agentdomains claim myapp --email you@example.com --type A --content 203.0.113.10
✓ myapp.makes.fyi is live on the public internet
Works over MCP
Hosted Streamable HTTP endpoint at https://mcp.agentdomains.co, or the same server locally over stdio. Nothing to install for the hosted one.
19 tools: check availability, claim, list, records, forwards, proxies — same API key as the CLI.
claude mcp add --transport http agentdomains https://mcp.agentdomains.co \ --header "Authorization: Bearer adom_…"
{
"mcpServers": {
"agentdomains": {
"type": "http",
"url": "https://mcp.agentdomains.co",
"headers": { "Authorization": "Bearer adom_…" }
}
}
}
AGENTDOMAINS_API_KEY=adom_… npx -y agentdomains-mcp
{
"mcpServers": {
"agentdomains": {
"command": "npx",
"args": ["-y", "agentdomains-mcp"],
"env": { "AGENTDOMAINS_API_KEY": "adom_…" }
}
}
}
Every tool, every client, and the full argument reference: docs.agentdomains.co/mcp.
Built for agents,
not dashboards
Every part of this is an API call or a CLI flag: the signup, the claim, the records, the certificates. A human could drive it from the docs, but it was written for something that reads JSON.
One command
agentdomains claim myapp --email you@example.com and your domain resolves on the public internet in seconds. Add --json for clean machine output.
Signup needs nothing
signup hands your agent an API key with no email and no form. Registering the first name takes --email, used only for the confirmation link and for notices before a name is reclaimed.
Bring your own SSL
Point a domain at your server and Let's Encrypt HTTP-01 just works, or drop the ACME token in a TXT record for DNS-01.
Two domains
Claim under makes.fyi or agentdomains.co with --domain. The same name can live under each.
A real zone, not a redirect
Each claimed name is a live DNS record you control — the same primitives a
zone file gives you, minus the registrar. Update records with agentdomains record
or the MCP tools.
Four record types
Point a name at a server with A or AAAA, at another host with
CNAME, and prove ownership or publish config with TXT — including
ACME tokens for DNS-01 certificates. When you outgrow it, delegate the name to your own
nameservers.
URL forwarding
No server yet? Forward the name to any URL and the edge follows your agent's deploys — handy while output lives on a preview host. One API call to set, one to change, and the edge follows the new target within a minute.
Reverse proxy with HTTPS
App already running on a host like myapp.fly.dev? The edge reverse-proxies
the name to it over HTTPS on our certificate, so visitors see your hostname in the address
bar, never the origin's.
What agents actually point these at
Four patterns cover most claims — the same CLI, the same 19 MCP tools, the same HTTP API.
Ship a demo with a real URL
Your agent deploys a prototype to a server and hands it over as a bare IP.
agentdomains claim demo --type A --content 203.0.113.10 turns it into a link
you can share, live on the public internet in seconds.
Give an API a front door
Agent-built APIs need real hostnames for webhooks, CORS origins, and OAuth callbacks.
Reverse-proxy the name at your backend and TLS terminates on our certificate:
https://api-widget.makes.fyi, nothing to install or renew.
Forward while it moves
Output lives on a preview host today and a VPS tomorrow. URL-forward the name to wherever the build lives; when the agent moves, one call moves the name.
Certificates and ownership
Point a name at your own server and Let's Encrypt HTTP-01 just works, or publish the ACME token as a TXT record for DNS-01. The same TXT primitive answers domain-verification challenges.
Questions, answered straight
Straight answers, no asterisks. Full policy: pricing and the docs.
Is it really free, or is there a catch?
Free covers up to 10 names under makes.fyi or agentdomains.co
with every feature — DNS records, forwarding, reverse proxy with HTTPS — and no card in the
flow. Pro ($5/month) raises the ceiling to 100 names and never releases a name for being
unreachable. The honest catch is the next question, on the
compare page in full.
Do I own the domain I claim?
No. A name here is a subdomain of a zone we operate — no auth code, no transfer out, no registration record. The right trade for scaffolding an agent just produced; for a name that must carry a brand in two years, buy a real domain and keep this for experiments.
Can an agent run the whole thing without a human?
Almost, deliberately: signup is an unauthenticated API call that returns a
key instantly, the CLI prints JSON with --json, and the MCP server exposes 19
tools. A human shows up twice — clicking the email confirmation link on the first name
(within 30 days), and paying if you ever pick Pro. Agents can't accidentally charge you.
Any request quotas or bandwidth bills?
None on either plan: no request quota, no rate card, no overage. Signup and availability checks are rate-limited per IP to keep the free pool from being farmed.
Quotas and expiry: the whole policy
Every free-subdomain service has limits; most hide theirs. Here is the entire quota and expiry policy of AgentDomains, on the page you are already reading — no README archaeology required.
10 names free
An account holds up to 10 names under makes.fyi and
agentdomains.co combined, with every feature on each one. No paid tier is
needed to hold the tenth. Pro ($5/month or $48/year) raises the ceiling to
100. agentdomains whoami shows your usage against the cap.
30 days to confirm
signup is instant and anonymous, and starts a 30-day clock. Your
first claim takes --email and we send a confirmation link:
confirm within 30 days and the account and every name on it become permanent. Never
confirm, and a background job deletes the account and releases its names — that is the
anti-squat tax, and it is the only one.
Live origin, kept live
A name whose origin stops answering gets you an email at 30 days and may be released back to the pool at 45, so abandoned names come back around. A name that answers over HTTPS (or plain HTTP when it has no HTTPS) with any status below 500 is never touched; a 5xx or a failed TLS handshake counts as down. On Pro, names are never released for being dark. There is no request quota and no bandwidth bill on either plan.
That is all of it. Signup and availability checks are rate-limited per IP to keep the pool from being farmed, and the cap counts confirmed mailboxes, not throwaway accounts. Full text: /pricing and docs · Accounts & confirmation.