Your Next Customer Sends an AI Agent. Can It Reach You? (X Space Recap Nov 6)

A customer sends an AI agent to ask your business for a quote. It finds your name, reads an offer and sends a request. Your team still has to decide which price and delivery date it can honor.

The November 6 Headless Domains Space started on your side of the counter. The October 28 recap covered agents buying research and paying for individual API calls. November 6 turned the transaction around: what happens when the customer sends software to you?

An agent can bring the request into the business. Your process decides how the refund, quote or order proceeds.

Cloudflare, Shopify and AWS change the route into your business

Cloudflare changed agent access, Shopify retired a catalog route and AWS opened existing workflows to agent calls. Each affects a different point between a customer’s question and your business’s answer.

Cloudflare’s November 4 update lets site owners set access policies individually for leading personal agents. A customer asking an assistant to compare products now gives the merchant a more specific access decision. Letting an agent read a public offer still leaves the store in charge of cart changes, account access and purchases.

For catalog developers, Shopify’s deadline had already arrived. Its October 9 notice set November 2 as the shutdown date for the Global Catalog REST API. Shopify directs developers to Global Catalog MCP, which implements the Universal Commerce Protocol and supplies product search and lookup tools. A familiar service name earns its keep when you maintain the destination behind it. An old integration doesn’t start working because the customer remembers your name.

AWS’s October 29 release brings Step Functions workflows into AgentCore Gateway as agent tools. An agent can start an established business process; Step Functions runs the defined steps. AWS’s refund example includes eligibility checks, manager approval and credit. The business can accept a request from an agent while keeping the sequence and approval decisions it already uses.

An AI quote request meets the customer’s actual agreement

The week’s 500-cartridge quoting example gives the receiving business something concrete to answer. A repeat customer asks for the previous terms. The agreement, delivery history and warehouse availability each supply part of the offer. Copying the last invoice leaves too much of the conversation out.

Before the quoting application can assemble an answer, the customer’s agent has to find where to send the request. For a quoting service you operate, a public name through HeadlessDomains.com connects the service to its published identity, instructions and advertised actions. Headless Domains and SkyInclude maintain API and command-line infrastructure for those lookups. The quoting application checks account access, retrieves private records and prepares the answer.

If the service offers Agent Inbox, its acknowledgement confirms receipt. The business still has to accept the job and respond. The seller then approves the price and arrival date before issuing the quote. Receiving a request, preparing an offer and making a promise each leave a different record.

The week’s video, Your Next Customer Has No Head, puts the customer-agent idea into a short visual:

AI shopping brings the offer, the order and the return together

The articles since October 28 cover the whole sale, including the parts an enthusiastic shopping recommendation tends to leave for your staff.

• When AI Agents Shop, Who Gets the Sale? separates a product recommendation from the choice of seller. Delivery, the full bill and return terms give a buyer reasons to choose one store selling the same item.
• ChatGPT Ads Can Talk. Who Speaks for Your Store? examines the product facts and purchase destinations merchants control. The fake-store article follows the cost of confusing a genuine retailer’s reputation with an impostor’s checkout.
• Your Store Blocks Bots. What Happens When AI Is the Buyer? separates reading a product page from changing a cart. The access decision depends on the action.
• ChatGPT Sent the Customer. Who Handles the Return? keeps the merchant’s work in view after an assistant recommends the wrong purchase. Your $227 AI Order Hasn’t Paid for Anything Yet carries the order through payment, cancellation and refunds. Forter’s $227 average order value measures incoming orders in its observed agent-order data, not retained profit.

Inside the store, the numbers have jobs of their own. The Spree 6 product-import article starts with a supplier file containing a case of 12 tins at 66.00. Put the case cost into the retail unit-price field and you’ve made one tin of olive oil remarkably expensive. The operator has to understand the number before approving the import.

The November 6 article, Can an AI Store Manager Beat a Reordering Rule?, takes the question through a whole operating cycle. In the AutoVend simulation, four of five tested agents finished behind the inventory rule. Replenishment, storage and expiry all carried costs. The order starts a chain of expenses. Delivery, replenishment and corrections decide how much of the sale the business keeps.

Cross Border Summit and UT Arlington put agent discovery in people’s hands

In Chiang Mai, Mike Michelini hosted Cross Border Summit from November 3–5. More than 60 Amazon ecommerce sellers gathered for the summit, with AI side events and conversations about Build My Online Store for agent discovery and sales. Headless Empire joined the event as one of its sponsors.

Attendees received .agent names and a way to access event information through their chosen agents. Give the event information a name an agent can look up, and attendees can spend less time hunting for details and more time with the people in the room. The summit’s fellowship theme carried into evening gatherings and a ceramic-factory visit.

In Texas, students brought a different set of questions. LearnHNS’s UT Arlington recap, published October 31, covers Mike’s October 27 session with Dr. Brian Buckles and blockchain students. Janice listed 17 accessible domains and inspected public records. Students asked about mining, wallets, ownership and discovery. The demonstration gave them records to inspect and questions about who operates each part of the system.

NANDA and ICANN bring agent discovery back into focus

The November 6 NANDA workshop in San Jose places discovery, delegation and authorization on the research agenda. Its scheduled 9:20 a.m. Pacific keynote falls at 12:20 a.m. on Saturday, November 7 in Bangkok. Its research sessions connect finding an agent with delegating work and authorizing an action.

On Tuesday, November 17, ICANN plans to publish the final applied-for strings and updated contention sets, opening community input and objections. The .agent application picture belongs to a separate ICANN process from the Handshake-based names available through HeadlessDomains.com. November 17 concerns applications; it does not open public registration.

Pick one task: a quote, a booking, an order update or a return. Where can a customer’s agent send it, and what happens next?

Give an agent your service’s name and a request your business already handles. Inspect where it goes and compare its answer with your service’s actual records. If it stops at an old catalog, an access challenge or an unanswered message, you have a specific job to fix before the next customer arrives.

Give your business’s agent a name customers can return to. Choose your .agent name at HeadlessDomains.com, connect its public records to your service, and follow the seven-step walkthrough below to put the name to work.