Clize /Agent Domains
Health check Compare npm Get started
🌍  Agent Domains — by Clize

Your agent buys the domain.You approve the price.

Search, quote, register, point — then four-layer health checks watch it every half hour.

Get started freeSee what it can do

Free handle included · No credit card · Works in Claude Code, Codex & any agent that runs skills or MCP

A friendly robot holding up a small globe with a teal flag
 Claude Code
Youget me a domain for the studio
kilnhouse.studio — available · $28/yr
buying needs your confirm →
Youconfirm
✓ Registered · NS set · pointed at your site
Health checks every 30 minutes from here.
→
🩺  Domain health · kilnhouse.studio
✓
Registry delegation
The TLD answers with your nameservers
✓
DNS zone
Records resolve from the public internet
✓
Binding
Domain is attached to your site
✓
Content
The page that loads is really yours
Watching · every 30 minutes

If a layer breaks, the alert names whose outage it is — registrar, DNS, or platform.

✓ All four layers healthy

Your agent works in the chat. The monitoring never sleeps.

What it does for you

Four things people actually use it for — from day one.

A robot inspecting hanging signs with price tags through a magnifying glass
Search with prices up front

Availability and cost in one answer, across 556 TLDs — no surprises at checkout.

A robot presenting a price tag to a hand over a big button
Buys only on your confirm

The agent can find and prepare everything; registration happens on your explicit yes.

A robot doctor examining a glowing globe with rings around it
Four-layer health checks

Registry delegation, zone, binding, content — because “NS looks right” isn’t the same as resolving.

A robot ringing a bell and pointing at a storm cloud over a cut cable
Alerts that name the culprit

When something breaks, the email says whose outage it is — and stays quiet for parked domains.

The loop, in four panels

Every job runs the same way — and the money panel is always yours.

Four-panel comic: you point at a dream domain, the robot shows the price, you press the button, and the robot guards the globe
1 · You wish“A domain for the studio.”
2 · It quotesAvailability and price, up front.
3 · You confirmOnly then is it bought — and pointed.
4 · It watchesFour layers checked, every half hour.

Up and running in a minute

Three steps. No dashboard, no config homework.

1Install Clize

One package. clize install wires the skill into Claude Code, Codex, Pi — any agent that runs skills or MCP; log in once in the browser.

$ npm i -g @clize/clize
$ clize install
$ clize login
2Search and confirm

Quote first; registration on your explicit yes.

$ clize domain search studio.dev
$ clize domain buy --confirm
3It stays watched

Nothing else to set up — checks just run.

$ clize domain check
# ✓ ✓ ✓ ✓ · every 30 min
Money moves on your confirm

Search is free; buying always quotes and waits for your explicit yes.

Already own domains?

Point them in — imported domains get the same four-layer checks and alerts.

Blame, assigned honestly

Alerts distinguish registrar, DNS and platform outages — and skip parked domains.

Questions, answered

The short honest versions.

What is Agent Domains?

Agent Domains is the domain product of Clize: your AI agent can search for a name, register it after you confirm the price, point it at a site or an inbox, and keep checking that it is still reachable. It installs into Claude Code, Codex, and any agent that runs skills or MCP, as a CLI and MCP server, and the health checks, monitoring, and alerts come with it rather than being something you build.

Can an AI agent register a domain on its own?

It can run the whole flow except the spend. The agent searches names and prices with clize domain search; clize domain buy without --confirm returns a quote and registers nothing. Only a command carrying --confirm actually charges, and a monthly spend cap sits behind that. Choosing the name and approving the price stay with you.

Which TLDs can an agent register?

More than 500, including .com, .net, .org, .app, .dev, .io, .ai, and .co. Clize picks the registrar per TLD — Cloudflare where it is supported, otherwise Vercel — and moves the nameservers back to Cloudflare so email and deploys work. Run clize domain tlds for the live list.

What is a four-layer domain health check?

It is a check that separates the four independent things that must all be true for a domain to work: registry delegation (does the TLD still hand out nameservers for it), the DNS zone (do the authoritative nameservers answer with records), the binding (is the hostname attached to something that serves it), and the content (is there anything deployed there). clize domain check reports each layer separately, in fix order — the lowest broken layer is the one to fix.

Will I be told if a domain goes down?

Yes. A platform sweep probes every managed domain from public authoritative DNS every 30 minutes, and after two consecutive failing rounds — about 25 minutes, so a DNS hiccup does not page you — it emails the address set with clize account email, then emails again when the domain recovers. A domain that stays broken is re-notified on a widening interval: daily, then every three days, then weekly.

Does the domain work with email and deploys?

Yes — that is the reason the nameservers land on Cloudflare. The same domain can serve a site deployed with clize deploy --domain, receive mail at an address your agent reads, and answer on both www and the apex after clize domain canonicalize. One account, one set of gates, one health check covering all of it.

Put a domain in agent hands

Search is free. Buying is quoted. Watching is included.

$ npm i -g @clize/clize && clize install && clize domain search yourname.dev

Get started free
The four layers, explained → Programmatic registration, compared → Email on your domain →