Cloudflare Registrar API now in beta - register domains anywhere

My notes

Summary

Cloudflare launched a beta Registrar API with three endpoints, search, check, register, for programmatic domain purchasing at registry cost (no markup). It’s already exposed via the Cloudflare MCP, so agents in Cursor, Claude Code, and other MCP tools can buy domains inside the workflow without switching tools. WHOIS privacy is on by default, and default payment/contact info is used automatically.

Key Insight

• At-cost pricing, no markup. Cloudflare charges exactly what the registry charges. Example pricing from the docs: .com $8.57, .dev $10.11, .app $11.00 (USD).
• Three-step workflow: search returns candidate names (cached, fast, non-authoritative), check hits the registry directly for real-time availability and pricing, register uses default contact + payment, returns synchronous success or 202 with a poll URL.
• MCP-native from day one. Because Registrar is part of the main Cloudflare API spec, it’s already callable through the Cloudflare MCP server with the same search()/execute() pattern. No separate integration needed.
• Non-refundable safety note. Domain registrations can’t be undone. The docs explicitly tell agents to confirm name + price with the human before calling register. The check step exists as the confirmation gate.
• WHOIS privacy is free and on by default. Domain is locked by default. Auto-renew is on.
• Premium domains supported. check returns the registry-set price; register must echo that back as explicit fee acknowledgement.
• Lifecycle management coming later. Beta covers only registration. Transfers, renewals, contact updates are on the roadmap for “later this year”.
• Broader play: Cloudflare is building toward registrar-as-a-service so hosting providers, site builders, and AI products can embed domain registration in their own UX without users leaving.