We Gave WebMCP a Currency. It Let an Ai Agent Buy Something Real
On a live merchant storefront, an Ai Agent priced a real product, applied the discount, and opened a real KAELUM Checkout. No confetti, no fake order.
On a live merchant storefront, an Ai Agent priced a real product, applied the discount, and opened a real KAELUM Checkout. No confetti, no fake order.
KAELUM Technologies Ltd
England and Wales No. 16681154 · September 2026
Watch enough demonstrations of the agentic web and you start to notice where they all stop. An Ai agent browses a store, compares a few products, drops one into a basket, and arrives at the checkout. Then the clip ends, usually with a little burst of confetti and an order number that was never real. The agent got all the way to the hard part, the moment money is meant to change hands, and went no further.
That is the quiet gap at the centre of agentic commerce. Agents are learning to shop. Almost nothing lets them actually pay.
Two Problems, Tangled Together
The obvious problem is settlement. For an agent to complete a purchase, a business has to expose a way to buy that an agent can use cleanly and safely, without handing over control of payment or account access. Most sites offer no such thing, so agents are left screen-scraping and clicking blindly, and the demos quietly stop before anything settles.
The less obvious problem sits underneath it, and in Europe it is now being said out loud at the top of the financial system. The head of the European Payments Initiative has called publicly for alternatives to the American card networks, and the President of the European Central Bank has echoed the need. Visa and Mastercard control roughly 65 percent of Eurozone card transactions, and thirteen EU countries have no national card scheme of their own. The nearest homegrown answers are years away: Wero will not have merchant payments before 2027, and the digital euro is 2029 at the earliest.
So the moment agents arrive at the checkout, they meet two absences at once. There is no clean way for them to transact, and the rails they would transact on are not ours to begin with.
What Actually Happened on a Real Store
KAELUM, pronounced Kay-Lum, is an Ai-native, closed-loop commerce currency. Its unit, KAE, is fixed at £0.20. And on 8T Clothing, a live merchant storefront that KAELUM does not own or control, an agent did the thing the demos never show.
A third-party browser agent, Google's Gemini, discovered on the product page that the store accepts KAELUM. It read the product price of £70.00, applied the merchant's 18 percent discount to reach £57.40, worked out that this was 287 KAE, and opened the KAELUM checkout. The shopper then confirmed the KAE spend on kaelum.app, behind a deliberate gate.
No confetti. No fake order number. A real commerce transaction, initiated by an autonomous agent on a store it had never seen, completed by a human in control. We believe this makes KAELUM the first commerce currency to complete an agent-initiated checkout on a live, third-party merchant storefront.
The line that matters is simple: the agent discovers and initiates, and the human completes. No payment is taken on the merchant's site, and no account is exposed there.
How it Works
KAELUM makes itself agent-ready through WebMCP, a browser capability that lets a website offer typed tools an Ai agent can call directly, extending the Model Context Protocol model that Anthropic pioneered. Instead of guessing at a page, an agent calls declared tools the way a person clicks a button.
On any KAELUM-enabled store, KAELUM exposes two tools. One is read-only: it quotes the product in KAE and shows the merchant discount before anything is bought. The other opens the checkout. Neither moves money on the merchant's site; the shopper always confirms the spend on kaelum.app. For people who are not using an agent, the same single script places a Pay with KAELUM button on the page, so a human gets the identical discounted checkout with one click. Agents and people are served by one implementation.
That implementation is universal by design. A merchant embeds one script, and KAELUM identifies them on its own servers, so the same checkout works whether the store runs on Wix, Shopify, WooCommerce, WordPress, Squarespace, Magento, BigCommerce, or a custom build. Behind it all, KAELUM is governed by K.A.T.E., its operating engine, which runs as a fleet of specialised Claude instances. The agent on the page never touches any of that. It simply calls the tools KAELUM has declared, and the human confirms.
The deeper design choice is the point. KAELUM does not ship an agent and ask the world to adopt it. It exposes tools that whatever agent the shopper already uses can call. That is exactly what developers building agentic software keep asking for: not another product agent to route around, but products their own agents can actually use.
Who This is For
For merchants, it means an agent-ready storefront and a Pay with KAELUM button from a single embed, on any platform, with the spending discount, six percent or more, set by the merchant and applied only when a shopper spends KAE.
For creators, the same embed can sit on Commerce Drops and Social Paylinks, so an agent can price and start a KAE purchase straight from a creator's page, reaching buyers who have begun to delegate their shopping to agents.
For customers, it is a real saving on the goods when spending KAE, an agent that can do the tedious part of finding and pricing an item, and complete control, because nothing is ever bought without the shopper confirming the KAE spend.
Built to be Trusted
The safeguards are structural, not cosmetic. The agent initiates and the human completes. The discount is worked out on KAELUM's servers from the merchant's registered rate, so neither the page nor the agent can change it. The tools read no account information on the merchant site and expose none there. Their inputs are fixed, so nothing injected into a page can supply an arbitrary amount or redirect. Redirect destinations are limited to kaelum.app and the merchant's own domain, and checkout sessions are rate-limited. The closed-loop design of KAE is the company's considered position pending an independent legal opinion.
The Inevitable Part
Commerce is about to be transacted by agents. That is not a forecast about a distant future; it is the direction every serious browser and model is already moving. The open question was never whether agents would reach the checkout. It was what they would find when they got there.
On a real store, on the stores people already shop, they can now find KAELUM: a currency and a checkout an agent can use today, and a human still controls. While the alternatives are on a roadmap, KAELUM is live.
Confetti is not Commerce. This is.
KAELUM ('Kay-Lum') and its commerce currency, KAE, are not an investment or a tradeable asset. A KAE unit is a fixed-value, closed-loop commerce currency intended for use within the KAELUM ecosystem, and it is not offered as a financial product or a means of generating a return. Nothing on this platform constitutes financial advice, and KAELUM does not provide professional financial advice. Users should seek advice from a suitably qualified financial professional before making any financial decisions.
KAELUM Technologies Ltd · England and Wales No. 16681154 · kaelum.app