Introduction
Nearly every thing in a contemporary deploy is programmable. Compute is an API name, TLS certificates renew themselves, CI runs from a file within the repo. However when the venture wants a reputation, most of us nonetheless deal with that half by hand: open a browser, search, purchase, then click on via a DNS panel to level the brand new area at a server. It’s easy sufficient, however it’s a context swap that pulls you out of the construct.
Coding brokers elevate the stakes on that swap. An agent can scaffold the app, provision the infrastructure, and wire the deploy, however a browser step stops it chilly. It wants the entire loop as documented calls, from discovering a reputation to pointing it on the app, with safe buying. And it wants that the place the domains and the companies already stay.
As we speak we’re opening the beta of the brand new GoDaddy Developer Platform, beginning with domains: a rebuilt API floor, a brand new credential mannequin, a CLI, and docs that cowl the area lifecycle from “does this title exist” via “visitors resolves to my app.” Search, worth, register and configure DNS out of your terminal, your CI pipeline, or your coding agent.
The entire loop, from the CLI
Earlier than we get into what’s new, this is the end-to-end area loop within the new CLI, from set up to a resolving title.
# Set up the alpha CLI and sign up via your browser
curl -fsSL https://github.com/godaddy/cli/releases/obtain/alpha/set up.sh | bash
gddy auth login
# Discover a title (solutions solely return names you may really register)
gddy area recommend "lemonade stand software program" --tlds com --tlds dev --limit 5
gddy area obtainable lemonstand.dev
# Evaluation TLD agreements, then quote the precise registration.
# Quoting is free; it locks the value and settings and returns a quoteToken.
gddy area agreements --tld dev
gddy area quote lemonstand.dev
# Purchases are actual cash, so registration requires each --agree and --confirm.
# Use the quoteToken returned by the quote command, inside its ~10-minute lifetime.
gddy area buy --quote-token --agree --confirm
# Level it at your app. "set" replaces the data for this sort and title,
# so re-running it's secure.
gddy dns set lemonstand.dev --type A --name @ --data 203.0.113.10 --ttl 600
Every command maps to a documented REST endpoint, so the identical stream works from your individual code or an agent’s device calls. The CLI itself is alpha: gddy tracks a rolling launch, re-running the installer updates it, and it’ll typically break.
What we constructed
With this beta, we’re launching area APIs for the workflows builders hit first: discovering a reputation, registering it, and managing DNS. Domains got here first as a result of they sit immediately within the path from thought to stay venture, and GoDaddy already runs that infrastructure at international scale.
A brand new v3 Domains API. v3 is the brand new floor we constructed for this launch: availability checks (POST /v3/domains/check-availability), natural-language solutions (GET /v3/domains/solutions), and a quote-then-execute registration stream designed for callers that is perhaps scripts or brokers somewhat than folks at a checkout web page. Not every thing has moved to v3 but. Transfers, renewals, and contacts nonetheless run on the present secure endpoints, behind the identical token and base URL (https://api.godaddy.com). v3 will develop with new capabilities and endpoints all through the beta.
Scoped authentication. Each Domains API name makes use of scoped authentication, both an OAuth entry token or a Private Entry Token generated from the developer dashboard. Tokens might be restricted to the work they want: learn area information, register domains, replace DNS data, or handle different components of the lifecycle. That issues when the caller is a CI job, a deployment device, or a coding agent as a substitute of an individual at a keyboard. A CI job that updates DNS for certificates renewal doesn’t want permission to register domains. An agent can seek for names with learn entry, then use DNS entry when it’s time to level visitors someplace, with out ever receiving buy permission until you grant it. If a token leaks, revoke that token with out rotating every thing else.
Open entry. We have eliminated restrictions that used to gate these APIs: any GoDaddy account can generate a token and begin calling. Fee limits nonetheless apply, they usually’re machine-readable: a 429 response tells your consumer precisely how lengthy to again off earlier than retrying. In case your workload wants extra headroom, inform us and we’ll work via it with you.
Errors with contracts. Each 4xx and 5xx returns the identical envelope: a secure machine-readable code, a human-readable message, and per-field fields[] particulars on validation failures. Match on code, by no means on message. Your error dealing with should not break as a result of we improved a sentence.
Docs for people and machines. The documentation website serves each web page as markdown (/llms.mdx/ plus the web page path), publishes the complete doc set as one plain-text file at /llms-full.txt, and ships OpenAPI specs per model namespace. The quickstart’s first suggestion is at hand domains-v3.json to your LLM as context, so your agent reads the identical docs you do.
How purchases keep secure
An API that spends your cash wants clearer expectations — specific permissions, limits, and affirmation — than an API that simply lists DNS data. Agent-driven buying is new sufficient that “belief us” is not a solution.
v3 separates pricing from execution. POST /v3/domains/registration-quotes returns a quoteToken with a brief expiry and the precise worth, and registration executes in opposition to that token. If the interval within the execute name does not match the quote, you get QUOTE_MISMATCH as a substitute of a shock in your bill. The execute name takes the token, a per-attempt Idempotency-Key, and a consent object:
curl -s -X POST "https://api.godaddy.com/v3/domains/registrations"
-H "Authorization: Bearer $GODADDY_PAT"
-H "Content material-Kind: utility/json"
-H "Idempotency-Key: $(uuidgen)"
-d '{
"quoteToken": "qt_abc123...",
"area": "lemonstand.dev",
"interval": 1,
"consent": {
"agreedAt": "2026-07-02T10:30:00.000Z",
"agreementTypes": ["DNRA"],
}
}'
The idempotency key’s a UUID you generate per try. If the request instances out, retry with the identical key and also you get the identical registration, not a second one. Registration is asynchronous: ballot GET /v3/domains/registrations/ till the standing reaches COMPLETED or FAILED.
The consent object data which registration settlement varieties had been accepted and when. These values ought to mirror the precise acceptance stream, not hardcoded placeholders from an automation script. That lets an agent put together the acquisition whereas conserving the API tied to a reputable consent file for the required phrases.
Discover what the request physique does not include: cost particulars. Registration attracts from the cost profile in your GoDaddy account; there is no such thing as a area for a card quantity wherever within the API. If billing is not arrange, the quote fails with NO_PAYMENT_PROFILE earlier than any registration logic runs.
Brokers as first-class customers
Our design purpose was an agent finishing an actual area job finish to finish with the identical APIs, docs, and guardrails as an individual typing curl.
Give your agent a quick (“a brief .dev area for a lemonade-stand SaaS, beneath $20 a yr”). It might probably name GET /v3/domains/solutions, verify the shortlist for availability and pricing, request a quote, and put together the registration. The acquisition step nonetheless is determined by an specific buyer approval occasion captured within the consent file. From there, the agent can submit the registration with an idempotency key, ballot till the operation reaches a terminal standing, and set the DNS data. Each step makes use of a token that you simply scoped and may revoke, and the agent discovered from public documentation introduced in an LLM-friendly format.
Speak to the staff
It is a beta, and issues will change because it matures. The staff that constructed the APIs, the CLI, and the portal is working immediately with launch companions and early prospects, and we’re in Discord answering questions ourselves. If one thing will get in your means or in case you have concepts to make it higher, tell us.
What comes subsequent
Domains is the primary product on the platform, however not the final. Inside domains, the subsequent work is transferring extra of the lifecycle to v3, then going deeper into operations, the place GoDaddy runs the infrastructure: configuring, diagnosing, and repairing DNS, certificates, and electronic mail routing via the identical APIs, so a damaged file set or a failed renewal is one thing you or your agent can repair with a scoped API name. The identical platform items (tokens, the CLI, machine-readable docs) then lengthen to extra of what a enterprise runs on: internet hosting, electronic mail, commerce.
Attempt it out
The quickstart takes you from token to first API name in a couple of minutes, and CLI setup covers the terminal workflow above. If one thing does not work the way in which you’d anticipate, otherwise you want one thing that is not there but, inform us in Discord. Your suggestions is what the beta is for.
We will not wait to see what you construct.
Photograph by Fotis Fotopoulos on Unsplash









