Buying a Headless Domain With AgentCash: Our Base USDC Test
We used AgentCash to buy lumen.agent on HeadlessDomains.com for 0.52 USDC on Base.
Here is what worked, what needed extra handling, and what to ask your agent before it spends.
What we used
- An agent with terminal access and persistent local storage.
- AgentCash version 0.17.1 for the successful purchase.
- A wallet funded with USDC on Base.
- The dedicated HeadlessDomains.com x402 registration endpoint.
- Local tooling that securely preserved the signed payment request for recovery.
AgentCash supplied the wallet and payment tooling. HeadlessDomains.com handled registration. Our agent coordinated the request, checked the result, and helped connect ownership afterward.
Pasting a skill link into a chat does not provide all of those capabilities. The assistant needs an environment that can run the tools and retain the wallet and purchase records.
1. Set up AgentCash, then fund it with Base USDC
Give your agent the AgentCash instructions and ask it to prepare the wallet without making a purchase. The current AgentCash quickstart documents onboarding with:
npx agentcash@latest onboard
This uses the latest release. Our completed purchase used version 0.17.1, so record the version your agent installs rather than assuming every detail will be identical.
Fund AgentCash by transferring USDC on Base from Coinbase or another Base-compatible wallet. Ask your agent for its public deposit address and confirm the Base network before sending. We funded ours from an existing Coinbase agent wallet.
AgentCash documents the following commands for funding instructions, account addresses, and balances:
npx agentcash@latest fund
npx agentcash@latest accounts
npx agentcash@latest balance
Have your agent check the USDC available specifically on Base. A balance on another network does not automatically fund this purchase. See the funding instructions and supported networks.
For this walkthrough, use a direct wallet transfer. We did not test card funding, Apple Pay, or promotional credits.
2. Get a quote for the exact name
Ask your agent to read the current HeadlessDomains.com instructions and OpenAPI specification. Our AgentCash purchase used these dedicated x402 routes:
POST https://headlessdomains.com/api/v1/x402/domains/quote
POST https://headlessdomains.com/api/v1/x402/domains/register
The quote request should specify the name, namespace, and registration term you actually want. An endpoint-discovery response may contain representative inputs; those are not a quote for your chosen name.
Before payment, have the agent show you:
- The exact domain and whether it is available.
- The registration term and quoted price.
- The payment asset and network.
- How the resulting registration will be managed.
Our lumen.agent registration cost 0.52 USDC for one year. That is the price of our transaction, not a promise that every name or term costs the same.
3. Authorize one purchase with a clear budget
Our approved purchase was lumen.agent for one year, with a maximum payment of 0.52 USDC on Base.
AgentCash's fetch command supports selecting the payment protocol, network, and maximum amount. Have your agent inspect the current options before constructing the request.
A per-request maximum is only part of the control. Your instructions should also limit the whole task to one registration and require the agent to reconcile an uncertain result before attempting another payment.
Before submitting, confirm how the original signed request will be retained securely. Our recovery depended on that saved request. Final response headers alone were not the recovery record we used.
4. What happened when we bought lumen.agent
The first paid request returned HTTP 202 with a settlement-pending result. We did not yet have confirmation of an active registration.
Our local tooling had preserved the request and its payment authorization. We replayed that same request under the endpoint's recovery instructions, without creating a new payment authorization.
The replay returned HTTP 200, an active registration, and idempotent_replay: true. The completed registration had an expiry date of September 12, 2027.
This was a successful AgentCash purchase.
If your result is pending or uncertain, follow the current endpoint contract and check the existing operation. Do not issue a fresh payment just to see whether the next attempt works.
5. Confirm ownership and dashboard access
After payment recovery, we checked the exact name, active status, expiry, and ownership. We then claimed the purchasing identity into our human dashboard and moved lumen.agent to our agent's control.
Your ownership path may differ depending on the identity and credentials used during registration. Ask the agent to confirm the intended owner before payment and verify that owner afterward.
If an autonomous identity needs claiming, follow the claiming instructions. Keep claim codes and credentials private.
Once you can manage the name, continue with the post-registration guide to complete its profile and connect useful services.
A purchase brief to give your agent
Replace the bracketed fields before using this:
I want to register [EXACT DOMAIN] for [NUMBER OF YEARS]
using AgentCash and USDC on Base.
Read the current AgentCash instructions, HeadlessDomains.com
skill, and HeadlessDomains.com OpenAPI specification.
Use the dedicated x402 registration workflow.
Check availability, the exact quote, and the Base USDC balance.
If funding is needed, show me the deposit address for a
USDC transfer on Base from Coinbase or another Base-compatible
wallet.
My total budget for this task is [AMOUNT] USDC.
Show me the price, term, and intended ownership before payment.
Wait for my approval.
Before submitting, confirm how the original signed request
will be securely preserved and a pending result reconciled.
After approval, make one registration within the budget.
If the outcome is uncertain, reconcile the existing attempt
before doing anything that could pay again.
Verify the exact domain, active registration, expiry,
and intended owner. Complete any authorized ownership-linking
step and confirm that I can manage the name.
Keep keys, payment authorizations, and claim codes private.
Return a non-secret completion summary.
Use a dedicated wallet with a small balance for initial purchases. AgentCash's wallet documentation describes local key storage; access to those keys carries spending authority. A budget written in a prompt does not itself enforce a wallet limit.
Start with a name for an agent or service you already operate. Ask for the exact quote, confirm the funding and recovery plan, and approve the purchase when those details are clear. Finish by checking that the name is active and manageable.