Buy the name.
We write everything it points to.
Your AI searches live registry availability and quotes you both numbers — what it costs now and what it renews at. The purchase happens on a browser approval only you can pay. Then the same conversation writes the zone: your app on the apex, outbound mail with its own DKIM key, inbound mail arriving.
Two afternoons, and the email still broke.
You are not price-shopping. You are fear-shopping. You have done this before and you remember which parts hurt: the checkout that fills itself while you are not looking, and the DNS panel afterwards where a wrong value fails silently for a week.
A cart can only show you a number. A tool call can withhold the purchase.
The usual way to buy a name is a shopping cart, and a cart's job is to complete. It can display the renewal price — on another page, in smaller type — and then complete anyway. Ours cannot. When the renewal is 1.5× the registration price or worse, register_domain refuses until the renewal figure has been said out loud and you have agreed to that number specifically.
Registration and renewal are different numbers on 365 of 815 TLDs, measured 2026-08-12. search_domains carries a separate renewsAt field for exactly that reason, and never describes a domain as costing its registration price per year.
The AI never holds a card.
This is the objection worth answering properly, because “I let an AI buy things” should worry you. register_domain is structurally incapable of charging. It runs a preflight and then mints an approval link that is live for 30 minutes. The account owner opens it, signs in, and sees the price, the renewal figure and the term on a clickwrap before paying on-session with bank authentication. A member of your project can ask for a domain. Only the owner can pay for one.
Before any purchase, an ICANN registrant contact must be on file for the project — one call, once. Retry safety is built into the idempotency key, so a retry after a refunded failure is a new charge and a same-attempt retry can never double-charge you.
Cost, plus four dollars. Per transaction, not per year.
We are not at cost, and we are not going to say we are. Here is the exact function instead. It is the same function that charges your card, imported by the price sheet so the two can never drift apart.
Four dollars is a flat fee on the transaction, not on each year. A two-year block carries one four dollars, not two. Flip the toggle and watch the wholesale figure double while the fee does not.
Prices come live from the registry at search time — not from a cached table that is wrong by the time you approve.
Both rungs trip the gate. Neither can be sold to you until you have been told the second number and agreed to it.
We will not silently kill your email.
preflight_domain reads public DNS over DoH and tells you what is already there — nameservers, web records, MX, SPF — and it names your current mail provider by brand rather than making you recognise a hostname.
It costs nothing, changes nothing, and needs no ownership. You can run it on a domain you have not bought yet, or on one you own somewhere else and are only thinking about moving. It is read-only, full stop.
The warnings come back worst-first, in plain English, and your AI reads them to you verbatim. add_existing_domain returns one embedded in its response — so the warning lands before the nameservers move, not after.
warnings · worst firstMoving the nameservers will stop delivery to Google Workspace until the MX records are re-created here.
Nothing in this call touches your zone, your registrar or your account. It is a DNS read that anyone could perform — we just read it properly and say what it means.
The 60-day lock doesn't apply to you.
The single most common reason people don't move: “I registered it three weeks ago, so I'm stuck for two months.” ICANN's 60-day lock blocks transfers. It has never blocked a nameserver change — and a nameserver change is all we need. add_existing_domain creates the zone here and hands you two nameservers. No registrar transfer happens. There is nothing to wait for.
Four planes, one call each.
You do not edit records. You turn on a capability and every record that capability needs is written correctly, in one go — and comes back marked managed so that nobody, including you, can quietly break it later. Flip the switches and watch the zone fill.
The ordering is real, not a UI nicety: email_sending before email_routing. Turn routing on first and the zone's MX writes lock — the bounce MX can never be added afterwards and outbound mail is permanently wrong. So the tool refuses, and prints why.
Burn a subdomain, not your business.
Bulk mail and campaign mail attract spam complaints. Complaints damage the sending reputation of the name they came from. If that name is the one your invoices, your password resets and your reply-to all use, a bad campaign takes those down with it.
So enable_service takes an optional host and the tool actively recommends using one for anything bulk. news.yourbusiness.com gets its own sending identity, its own DKIM key and its own reputation — while inheriting ownership and verification from the parent. No separate purchase. No separate verification.
Up to 25 hosts per domain.
The bleed stops at the boundary because reputation is scoped to the sending host, and each host carries its own key.
Every tool, grouped by the job.
Domains lives in the assistant you already talk to — Claude, ChatGPT, Cursor, anything that speaks MCP. There is no dashboard step in the middle, because the buying surface is the conversation. Every tool is gated to the project owner; register_domain and renew_domain also accept a project member, who can ask but cannot pay.
The interesting question is who eats the failure.
Reassurance is worthless here, so this is machinery instead. Four real failure modes, what the system actually does, and what lands on your card.
| what happened | what the system did | what you were charged |
|---|---|---|
| The registration failed at the registrar | The uncaptured authorisation was cancelled. The error says you have NOT been charged. | $0.00 |
| The registrar leg of a renewal failed | Auto-refunded in the same call, and the error text tells you whether the refund landed. | $0.00 |
| A refund did not land | A cron retries owed refunds until they do. Nobody has to notice, and nobody has to file a ticket. | refunded |
| Our prepaid registrar float ran dry | The registrar's own auto-renew was deliberately left on as a backstop, because the failure was ours. | domain does not lapse |
The renewal ladder, and its asymmetry
At T-50 days we charge you and renew. At T-40, if it is still unpaid, we disable the registrar's own auto-renew — but only when the failure was tagged as a payment failure, i.e. you didn't pay. If the failure was ours, or could not be classified, the backstop stays on and the domain renews anyway. We take the loss rather than let your name lapse.
We will never sell your renewal
We buy from the registrar out of a prepaid balance. Before any new sale, the float is checked against every renewal already promised — and the new sale is refused if taking it would eat money that belongs to somebody's renewal. Renewals themselves never consult that reserve. The queue runs in the right order on purpose.
Renewals price from the registry's renewal price list, plus the same flat $4. That was broken once and fixed on 2026-08-22, proven with a live charge: $14.99 taken, statement descriptor PARSONS.AI, registrar renewed, expiry moved 2027 → 2028, receipt emailed.
Observe here. Act in chat.
This is deliberate, and it is the opposite of what most product pages claim about their dashboard. The console at /app is read-only, with exactly one action on it: Check now. You cannot register, add, wire or edit DNS from it — all of that lives in the tools.
What it is for is the question you actually have at 11pm: is anything wrong? Delegation status, the expiry and auto-renew truth, a health dot per mail plane, the DNS table with its managed locks, and the activity trail of every call that touched the zone.
It is part of your subscription, so it sits behind the same paywall as everything else. It is a trust surface, not a store.
One plan. It includes every other Parsons product.
Monthly or yearly, your choice at checkout — pay for the year and two months are free. No seats, no enterprise tier, no free tier. Past an included allowance, the extra draws from prepaid credits at roughly wholesale-plus-half — building stays free inside the numbers, and the bill starts when real usage does. The domain itself is a separate, one-time charge — it never becomes a subscription line you forget about.
- Every domain tool — the surface is not tiered
- All four planes on every domain, and on subdomains
- 10 domains per project — an anti-abuse ceiling, not an upsell
- App storage 1 GB · object storage 5 GB · 10,000,000 CPU-ms
- Every other Parsons product, same login
And also, on the same subscription.
These are account-wide, not Domains-specific. The bottom four are metered and deliberately never limited, because they do not drive our cost — so their limit column has no number in it at all.
Projects are unlimited, and included.
One for the business, one for the client, one for the thing you are not sure about yet — each with its own domains, its own data, its own members and its own spend caps, at no extra cost. Three businesses is three projects, not three subscriptions. There is nothing to upgrade to and there are no seats to buy.
The domain is not a subscription line.
It is a one-time charge per term — registry cost + $4, approved by you in a browser, on a page that prints the renewal figure. It does not sit inside the $15 and it does not renew silently: set_auto_renew is an explicit answer you give at purchase, changeable at any time in either direction. A .com is $14.99. A .ai, on the registry's mandatory two-year block, is $175.99.
14-day free trial on your first subscription · billed monthly or yearly · cancel any time
Is it worth fifteen dollars a month?
That is the honest question at this price, and it deserves figures rather than adjectives. Here is what the same money buys elsewhere, what we deliberately do not charge for, and where a specialist tool genuinely beats us.
One app's price, twenty-two products.
Most people reading this already pay $15 or more, every month, for a single one of these things. A CRM on its own runs $48–$99/mo at HubSpot, Pipedrive or Attio; hosted auth at 100,000 monthly users is roughly $1,025/mo at Clerk. Base is $15 for the registrar and DNS plane, the mail plane, auth, database, object storage, deploy, scheduler, CRM and the rest — one login, one bill, one place the wiring already matches.
Per app, a specialist can be cheaper. We would rather say it.
If you want exactly one of these things and nothing else, a single-purpose tool may cost less than $15 — an issue tracker from $8/seat, a personal-finance app at $13/mo. We are not going to claim otherwise on a page you can fact-check in a browser tab. Against the bundle, though, nothing is close: buying these separately is six or seven subscriptions and none of them know about each other.
Nothing per seat, per workspace or per project.
Projects are unlimited and included — three businesses is three projects, not three subscriptions. Members carry no price, monthly active users on Auth are uncapped, MCP tool calls are uncapped. The figure on the card is the whole subscription figure. The usual way a $15 plan quietly becomes $90 is seats and workspaces, and neither exists here.
The subscription is access. Consumption is prepaid, capped and separate.
The $15 buys the tools, the zone and the wiring — the domain itself is bought separately and visibly, at a printed formula, on your own on-session approval. What genuinely costs per unit sits on a prepaid wallet with its own ceiling: AI at provider cost × 1.5, voice at $0.03/min, an outbound SMS segment at $0.02. Nothing draws down that you did not put there, and anything recurring we buy on your behalf — a US phone number at $3.99/mo, a domain renewal — is a separate line you approved.
Before you say the name.
Will moving my nameservers break my email?
Run preflight_domain first — it reads public DNS and names your current provider by brand, then warns you worst-first. Then enable_service email_routing re-creates the MX records here. The warning arrives before the move, not after it.
Can I bring a domain I registered two weeks ago?
Yes. ICANN's 60-day lock blocks transfers, not nameserver changes, and a nameserver change is all we need. add_existing_domain creates the zone and hands you two nameservers. No transfer happens.
Can I transfer a domain in?
Not yet — it is genuinely not built. Bring it by delegation, or buy the name here. We would rather say this than let you find out at the end of a form.
What happens at renewal?
Charged at T-50 days from the registry's renewal price list, plus the same flat $4. If the registrar leg fails you are auto-refunded. If the failure is ours, the registrar's own auto-renew is left on so the domain does not lapse.
Can I leave?
get_transfer_code hands over the EPP auth code on request. No retention flow, no phone call, no delay we control. set_transfer_lock is yours to set or clear in either direction.
Does the AI have my card?
No. register_domain cannot charge at all. It mints an approval link that is live for 30 minutes; the account owner opens it, signs in, sees price, renewal and term on a clickwrap, and pays on-session with 3-D Secure. A project member can ask for a domain and cannot pay for one.
Is .ai available?
Yes, on the registry's mandatory two-year term: $175.99 for the block, from $85.60/yr wholesale. Note that the .ai registry forbids WHOIS privacy — we cannot give it to you there, and the search result says so before you buy.
Do I get free WHOIS privacy?
Wherever the registry permits it, yes, at no charge. 20 registries forbid it — including .ai, .us, .uk, .de, .fr and .ca. Every result carries privacySupported so this is never a surprise.
What if I have three businesses?
Three projects. Each with its own domains, data, members and spend caps — and projects are unlimited and free. One subscription, one login.
Is there a yearly price?
Yes — $150/yr, against $180 if you pay by the month. That is two months free, and you pick the interval at checkout. Nothing about the plan changes: same allowances, same products, same unlimited projects.
Does the free trial take a card?
Yes. It is a Stripe Checkout subscription with 14 trial days, and Checkout collects a payment method. Cancel any time inside the trial and you are not charged. The trial is first-subscription-only.
Can I use a subdomain?
Yes, and for bulk or campaign mail you should — enable_service host:"news". It inherits ownership and verification from the parent, gets its own DKIM key and its own sending reputation, and needs no separate purchase. Up to 25 hosts per domain.
What if I delete the project?
Registrar holds are released and DKIM keys are retracted before anything is deleted — so a closed project can never leave an invisible recurring charge, or a stranded ownership claim that burns the name for whoever gets it next.
Say the name. The rest is wiring.
One conversation buys it, one conversation wires it, and the approval that spends the money happens in your browser, under your own sign-in.