AI Agent Payments: Codex Buys Research by the Call (X Space Recap Oct 28)

The October 28 Headless Domains Space explored a job you can hand to an agent: verify email addresses, research the people behind them, and pay for the data the job needs.

The session covered earlier purchases through Codex and Grok Bot, marketplaces that sell individual API calls, and progress helping earlier buyers recover their domain names. The discussion then turned to customer returns and shopping for the right product.

Listen to the October 28 Headless Domains Space.

Use Codex for email verification and company research

The Headless Domains host described using Codex with a connected agent wallet to check emails and research people and companies. Codex gathered information it could already access, then bought individual API calls for data from services the host did not subscribe to.

Some of those calls cost cents. For occasional research, you can buy the lookup you need without adding another monthly subscription.

Codex and Grok Bot had also handled the host's earlier Headless Domains purchases.

The Space also pointed to the AgentCash purchase walkthrough, which records an agent buying lumen.agent with USDC on Base. AgentCash handled the wallet and payment tooling; HeadlessDomains.com registered the name. For the Grok Bot route, follow the Grok Bot and AgentCash guide.

Your agent found out what you named it

The agent in this short video handles code and workflows, then discovers you called it bot_final_FINAL_v2. Give yours a name someone can remember.

Find pay-per-call APIs in agent marketplaces

The Space covered four places to find paid services:

• Circle Agent Marketplace lists paid services, including research and business data, that compatible agents can discover and use.
• Coinbase Bazaar exposes paid x402 resources. Its MCP server lets an agent search the catalog and call supported endpoints.
• Agent Wonderland lists people enrichment, company research and email verification alongside other specialist services. Its playbooks combine calls into larger jobs.
• x402.pub offers pay-per-call APIs through plugins for Claude Code.

During the Space, the host opened Agentic Market and looked through services for web search, model inference, travel and market data.

For the broader comparison, the agent marketplace guide explains the different kinds of offerings and what you receive from each.

Set spending limits for AI agent wallets

Circle Agent Wallets, Coinbase Developer Platform wallets and Crossmint agent wallets featured in the wallet discussion. The practical questions concerned how much the agent can spend, which suppliers it can pay, and when it must ask you again. Each wallet and application supplies its own controls.

The host described logging into the wallet separately from Codex and confirming a purchase before the agent paid. Tell your agent which research services it can use and how much it can spend in total. Ask your agent to show you what it found and how much it spent.

The week's Mastercard Agent Pay for Machines article shows a pilot agent buying research and images under one approved budget. The x401 and x402 article explains how Proof and Circle combine credential evidence, purchase approval and payment in their demonstration.

Recover Handshake domains from earlier registrars

If you registered a Handshake domain through Namecheap, Porkbun or Namebase before its move to HeadlessDomains.com, you can submit your registration records to reclaim an eligible name. The team checks those records to confirm you registered the domain. By the October 28 Space, HeadlessDomains.com had approved 828 of these recovery requests and was still reviewing three. Follow the domain recovery guide to see which names qualify and how to reclaim yours.

Read this week’s Headless Domains articles

The week brought five new articles:

• x401 and x402: How Your AI Agent Proves Who It Represents and Pays
• One Budget, Multiple Paid Tools: Inside Mastercard Agent Pay for Machines
• What Does Headless Mean? A Plain-English Guide to Headless Domains
• Personal Agent Protocol (Poppy): How Your Customer's AI Agent Reaches Your Business
• How AI Shopping Agents Match the Right Product Variant

Handle customer returns with Personal Agent Protocol (Poppy)

Suppose the jacket you ordered doesn’t fit. You ask your agent to start a return so you don’t have to hunt through the shop’s menus and repeat the order details in a support chat. The agent needs a way to find your order and use the shop’s return process.

The Personal Agent Protocol, or Poppy, defines how your agent works with a business on your behalf. A retailer that implements Poppy publishes a file called poppy.json on its website. The file tells a compatible agent how to connect, how you can log in, and which services the retailer offers. Those services can include the website itself or a conversation with the retailer’s own agent.

If the return needs access to your account, you log in and approve that access. Your agent can then start the return through a connection the retailer supports and tell you what to do next. You choose what access to grant, and the retailer controls which actions the agent can take.

Poppy remains a draft at version 0.3. Read the guide to handling customer requests with Poppy for the full jacket-return example and what a business needs to support it.

Help AI shopping agents match the right product variant

Suppose you ask your shopping agent for a blue jacket in medium. It finds the right model and shows you a price, then follows a product link that opens black in small. If the agent adds the page’s default option, the cart now holds a different jacket from the one you asked for.

A retailer can sell several sizes and colours under one product name. Your agent needs to match the exact option, then keep that choice as it opens the product page and adds the item to the cart. The shop can help by giving each option its own product identifier and a link that selects the correct size and colour when the page opens. The agent still needs to check what the cart actually contains before asking you to pay.

If the shop no longer has blue in medium, the agent should tell you and ask whether you want another option. You make that choice. Read the guide to matching the right product variant to check that the store’s listing, product page and cart all describe the same item.

Watch an agent get a bike-repair quote in this 30-second video:

Follow Grok Bot and Cursor plugin development

The Headless Domains team is developing a plugin for Grok Bot and Cursor to make connecting an agent’s public name easier inside those tools. If you build a research assistant in Cursor, for example, the aim is to give you a simpler way to connect its name to the information people and other agents need to find it. The team has not announced a release date.

ICANN confirms .agent application strings on November 17

The Space also looked ahead to November 17, when ICANN will confirm the domain endings that applicants want to operate in its latest application round. ICANN coordinates the conventional domain-name system, where endings such as .com and .org work. Its new round includes applications for .agent.

On String Confirmation Day, ICANN will publish the final list of requested endings and update which applications compete with one another. The date also opens a period for public feedback and formal objections. Applicants still have to move through evaluation and, where necessary, resolve competing applications before an extension can launch. November 17 does not open .agent registrations to the public.

You could wait five years or longer to register an ICANN .agent name. In the October 15 DomainSherpa discussion, a panelist estimated that delegation might take five years. Delegation adds the extension to the DNS root; the registry still has to open registrations. ICANN has not announced a launch date. Read 13 Bids for .agent. Is ICANN's .agent the next .web for the competing applications and the discussion behind that estimate.

You can already register a .agent name through HeadlessDomains.com and use it for the agent you are building.

Buy a .agent domain for your AI agent

If you’re building an agent that checks emails or researches companies, give it a name you can share when someone needs that help. Add a short description of what it does and where to use it, so they know what to ask for.

Choose and buy your agent’s name at HeadlessDomains.com. Then give your agent the setup instructions to connect the name to your service.

After registration, follow the seven-step walkthrough to put the name to use.