Using Cloudflare's Agentic Interface to (Mostly) Seamlessly Launch a Website
The Automated Operator
SubscribeSign in
Using Cloudflare's Agentic Interface to (Mostly) Seamlessly Launch a Website<br>A small task, but a nice peek into how things may look when our agents are taking care of tedious tasks in the background.
Alex Willen<br>Jun 11, 2026
Share
I recently had to set up a website. Unlike most of what I write about here, this one was not related to my business. A group of my college friends decided to plan a trip for our collective 40th birthdays next year, and we needed to figure out where to go plus do all of the other requisite planning.<br>One guy set up a Google Sheet where people could fill out preferences, but I wasn’t about to let that be our main planning tool when I’ve got access to Claude Code. A world of effectively free engineering work should be a world where we have a little fun with the stuff we do online! Besides, it presented a great opportunity for me to try out Cloudflare’s newly launched tools that allow agents to register domains and deploy applications to them.<br>A quick quote from the link above to give you an idea of what they’re offering:<br>Starting today, agents can provision Cloudflare on behalf of their users. They can create a Cloudflare account, start a paid subscription, register a domain, and get back an API token to deploy code right away. Humans can be in the loop to grant permission and must accept Cloudflare's terms of service, but no human steps are otherwise required from start to finish. There’s no need to go to the dashboard, copy and paste API tokens, or enter credit card details.
Pretty cool! Much ink has been spilled over the topic of agentic commerce, with plenty of folks scoffing at the idea that anyone would ever let AI go onto Amazon and start buying stuff without approval. But they’re missing the point — agents won’t be buying a pair of shoes; the commerce they’re going to engage in will be the really boring kind.<br>I just bought some new filters for the RO filtration system that sits under my sink. There are four filters, and two are supposed to be replaced every six months, one every year and another every two years. It’s been a year since I replaced anything (oops), so I needed three of the four. Wouldn’t it have been nice if an agent would just track the replacement timelines and purchase those for me?<br>I know what you’re thinking: This can be solved by setting up subscriptions and in no way requires AI. But there are three websites I might buy them from, each of which has the cheapest price some portion of the time but is also intermittently out of stock. So every six months (or when I realize it’s been a while since I replaced any of them and it turns out to be a year), I click around, compare the three and order from whatever’s cheapest. This sort of deeply boring online purchasing task is where agentic commerce will thrive. If you’re a business, something like domain registration certainly fits the bill.<br>So let’s give it a whirl and see what our brave new world looks like.<br>Registering a Domain
Since the entire purpose of this domain is to plan a trip, the main criteria were:<br>Available
Cheap
Topically relevant
(Optional) Gets a chuckle
I gave Claude the context on what we were going to do here, told it to give me some options for domains and asked what it needed. First thing: An API token. Instructions:
To set this up, I had to fill out a form in which each cell in that table required selecting the right value from a dropdown. It would’ve taken me literal minutes, so out of laziness and for the sake of pointless AI maximalism, I had Claude in Chrome do it. Nothing could possibly go wrong from having my agent assign its own permissions, right?<br>Thankfully it worked fine, so I gave Claude the token and had it find some domain options for me.
Oh well look who’s Mr. Funny Claude…<br>(Worth noting that the prevalence of Vegas in the URLs is because I told it to do Vegas since that was where I wanted to steer the group, but I was unfortunately outvoted there.)<br>In some follow-up conversation on this, I discovered that it actually decided that Cloudflare didn’t have a way to search for domains and instead checked URLs on rdap.org, which offers public records of domain information. This is classic Claude Code — it is abysmal at search and extremely quick to assume that APIs lack capabilities that they absolutely have. I had ChatGPT find instructions on how to use the relevant CF APIs and sent those to Claude, making sure to note passive-aggressively that they came from ChatGPT, who is good at going through API documentation should Claude ever need help in the future. I told Claude to search again, correctly this time, because it’s important not to let it get away with this sort of indolence.<br>I ended up deciding on a domain not from the list, which I will not include here, seeing as you don’t need to visit it and start submitting answers to my questionnaire. I...