Cloudflare opens domain registration to agents and automation

Cloudflare has released its Registrar API in beta, letting developers search for, check, and register domains programmatically. The move closes a long-standing gap for builders who wanted domain purchasing to work inside editors, deployment pipelines, and AI agent workflows, rather than forcing a jump to a separate dashboard.

Since launching Registrar seven years ago at cost with no markup, Cloudflare has become one of the fastest-growing registrars. The new API extends that model to machine-driven flows, where a user can go from idea to registered domain without leaving the tool they are already in.

What the beta covers

The initial release focuses on three operations across a curated set of popular TLDs:

  • Search — submit a domain query, with or without an extension
  • Check — query the registry directly for real-time availability and pricing
  • Register — purchase a domain with a minimal request body

The only required field in a registration request is the domain name. WHOIS privacy is enabled by default at no charge, the account's default registrant contact is used when one exists (otherwise contact details can be provided inline), and the default payment method is charged automatically. Premium domains are supported where available but require an explicit fee acknowledgement, with the Check response returning the registry-set price that must be echoed back on registration.

Because the Registrar API is part of the full Cloudflare API, it is immediately accessible through the Cloudflare MCP. No separate integration or custom tool definition is needed—agents in Cursor, Claude Code, or other MCP-compatible environments can discover and call the endpoints using the same search() and execute() patterns they already use for the rest of the API surface.

How a registration flow works

The intended workflow resembles a natural extension of an agentic build session. An agent suggests candidate names, checks availability in real time, surfaces the price for approval, and completes the purchase once confirmed. In code, that translates to three calls:

  1. Search returns candidate names using cached data; results are fast but non-authoritative.
  2. Check contacts the registry directly; this call should be made immediately before registering and its price response treated as the source of truth.
  3. Register completes synchronously within seconds in most cases; if it takes longer, the API returns 202 Accepted with a workflow URL to poll, and the response shape remains consistent either way.

Agents and non-refundable purchases

Domain registrations are non-refundable once complete, and an agent acting on a user's behalf charges the default payment method. A responsible agent flow should confirm the domain name and price with the user before calling the registration endpoint—the Check step exists to make that confirmation explicit. Cloudflare's API documentation includes agent-facing instructions to seek permission during the register call, but ultimately the human designing the agent is responsible for ensuring it will not buy domains without approval.

Why an integrated registrar matters

Cloudflare operates the registrar itself, so the same platform that hosts and deploys a project can also handle domain search, registration, and management. The at-cost pricing model applies consistently whether a domain is registered through the dashboard, directly via the API, or through an agent—Cloudflare charges exactly what the registry charges with no added markup and no premium upsells beyond the registry's own fees.

What comes next

The beta intentionally covers only the first moment of the domain lifecycle. Cloudflare says it is actively working to expand the API to cover lifecycle management—transfers, renewals, contact updates, and related operations—with the stated aim of launching a broader registrar-as-a-service offering later this year. That service would let website builders, hosting providers, AI products, and other multi-tenant platforms embed domain registration directly into their own user experiences.

Get started

The registrar API is live in beta. Builders can review the Registrar API guide and the API reference to begin integrating. Feedback on missing functionality or broken workflows can be shared via the Cloudflare Community, X, or the Cloudflare Developers Discord server.