Building the World Cup Oracle 2026 has been an experiment in fully AI-driven development. I wanted every piece of the stack - from the UI to the deployment- to be built entirely through prompts. But when it came time to deploy, I hit a wall: buying a domain usually requires leaving the terminal, clicking through a registrar's UI, and typing in a credit card.
How do you get an AI agent to buy a domain for you?
Enter AgentDomainSearch.com. Itβs an agent-first domain registry that uses x402 for inline USDC payments and EIP-191 wallet signatures for authentication. No accounts, no API keys, no UIs required.
Here is the exact tutorial on how I prompted my AI agent to buy worldcuporacle.org and link it to my Vercel app.
Step 1: Funding the Agent's Wallet
First, the agent needs a wallet (give it automatically). AgentDomainSearch runs on the Base network, so I generated a standard Ethereum wallet for my agent and sent it some USDC (Base) to cover the domain cost.
I saved the private key in a .env file:
WALLET_PRIVATE_KEY=0xYourPrivateKeyHere
Step 2: Prompting to Buy the Domain
With the agent funded, I needed it to interact with the AgentDomainSearch API. Because the API uses x402 (a standard for agentic payments), the agent can use the official Python SDK to handle the 402 Payment Required challenges automatically.
Here is the prompt I used:
Prompt: Create a Python script using the
x402SDK to buyworldcuporacle.orgon agentdomainsearch.com. Use theWALLET_PRIVATE_KEYfrom the.envfile to sign the EIP-3009 payment authorization. Ensure you provide the necessary contact details in the payload.
The agent wrote a beautiful script that:
- Hit the
POST /worldcuporacle.orgendpoint. - Caught the
402 Payment Requiredresponse. - Used the wallet to sign the exact USDC amount required.
- Retried the request with the
PAYMENT-SIGNATUREheader.
In seconds, the domain was mine. The wallet address that paid the USDC became the owner automatically.
Step 3: Prompting to Setup Vercel DNS
Now that the agent owned the domain, it needed to configure the DNS to point to my existing Vercel deployment. Vercel requires an A record for the root domain pointing to 76.76.21.21 and a CNAME for www pointing to cname.vercel-dns.com.
AgentDomainSearch handles DNS management via an authenticated PUT /:domain/dns endpoint, using an EIP-191 signature (agentdomainsearch.com:<unix-timestamp>) as the Bearer token.
Here is the prompt to automate the DNS setup:
Prompt: Create a bash script
setup_domain_vercel.shthat automates connecting our new domain to Vercel. First, create a Python script to update the DNS on AgentDomainSearch to point the@A record to76.76.21.21and thewwwCNAME tocname.vercel-dns.com. Authenticate using the EIP-191 signature from the owner's wallet. Second, runnpx vercel domains add <domain>. Finally, trigger a Vercel deployment to link it up.
The agent got to work. It reverse-engineered the payload structure:
{
"records": {
"A": [{"subdomain": "", "ip_address": "76.76.21.21"}],
"CNAME": [{"subdomain": "www", "hostname": "cname.vercel-dns.com"}]
}
}
It wrapped the Python DNS update logic, the Vercel CLI domain addition, and the redeployment trigger into one elegant bash script.
The Result
I ran the agent's script:
./scripts/setup_domain_vercel.sh worldcuporacle.org
Output:
π Setting up domain: worldcuporacle.org
----------------------------------------
π‘ 1/3: Configuring DNS records on AgentDomainSearch...
β
DNS update successful!
βοΈ 2/3: Adding domain to Vercel project...
> Success! Domain worldcuporacle.org added to project worldcup-oracle.
π 3/3: Deploying and aliasing...
π Aliased: https://worldcuporacle.org
π SUCCESS! worldcuporacle.org is now fully configured and live.
Why This Matters
This wasn't just about saving five minutes of clicking around a registrar dashboard. This proves that end-to-end infrastructure provisioning can now be fully agentic.
By combining x402 payment standards with modern, API-first services like AgentDomainSearch and Vercel, an AI agent can conceptualize a project, write the code, purchase the domain, configure the DNS, and deploy the application-all autonomously, interacting purely machine-to-machine.
The future of DevOps is here, and it doesn't rely on a GUI.
(This is a follow-up post to "Build and Deploy a World Cup 2026 Oracle in Under 10 Minutes")

Top comments (0)