Ask an AI assistant for a winter coat that is warm enough for New York in January and packs flat. You won’t get 280 search results. You’ll get a shortlist of three or four products, each with a reason attached.
The brands that didn’t make the list never get a chance to compete. Shoppers are already working this way. Adobe’s AI Traffic Trends Report found that 42% of shoppers now consult an LLM when making a purchase, and that shoppers sent to retail sites by AI convert 60% more often than all other traffic. Meanwhile the average ecommerce site converts only about 2.9% of its visitors.
The scale is hard to ignore. Retail is a $30 trillion industry. McKinsey estimates that AI agents could mediate $3 trillion to $5 trillion of global consumer commerce by 2030, and Bain expects agents to account for 15–25% of US e-commerce sales by then. Whatever the final number, agents will be buying on behalf of consumers, and the infrastructure underneath them will matter a great deal.
Being recommended is not being paid
Most of the conversation so far has been about visibility: how a brand gets found by an agent. That matters, and it is why product data now needs to be written to be read by machines. But a recommendation is not a sale. A merchant has to be able to receive the agent’s request, confirm what’s in stock, take the order and settle the payment.
That is the layer Rezolve Pay is built for. Rezolve Ai sits on the merchant’s side of the interaction. Our merchant-side agents turn a customer’s request into an order, and Rezolve Pay connects that order to payment.
Whichever agent the customer chooses
Consumers will pick different assistants, and they will change their minds. Retailers can’t afford to build a separate integration for each one, or to bet on a single winner. They need to serve whichever agent their customer arrives with.
Our recent announcement shows this in practice. In a demonstration video, Meta’s Muse interacts with a coffee shop’s Rezolve Pay agent to place an online order for in-store collection. Muse is the example we chose, but the architecture is designed to support transactions with any consumer AI agent through compatible merchant integrations. The receipt even identifies Muse as the agent that placed the order. That gives merchants a view of which AI channels generate orders, and how customer behaviour changes as agentic commerce grows.
The coffee shop is deliberately ordinary. The same requirement faces grocers, fashion brands, department stores and local businesses: be ready to transact when the customer arrives through an agent, online or in store.
Why the rails matter
Rezolve Pay combines payment orchestration with our own payment infrastructure, including digital-asset and stablecoin rails. The aim is to streamline payment execution, speed up settlement and improve the economics of accepting payments for merchants. Owning that layer gives us a role in the infrastructure and economics beneath the purchase, not just the conversation above it.
It also opens a second route to reach. Beyond deploying with merchants directly, we see an opportunity to license our technology to platforms, financial institutions and payment networks that want to support agent-driven commerce.
What this means
Merchants run on thin margins and can’t rip out the systems they have. They need new layers on top that let them be chosen, converted and paid in an agent-led world. As more consumers delegate shopping to AI, more merchants will need that infrastructure, whichever assistants win.
At our Investor Day I called the opportunity every agent and every merchant. A coffee order is a small example of it, but the implications reach across global retail.
Forward-looking statements: this article contains forward-looking statements about RezolvePay’s capabilities, adoption and the agentic commerce market. Third-party market estimates are projections, not forecasts of Rezolve’s revenue or market share. See the Company’s SEC filings for risks.
