AI Agent Payments: The Seller Got a Receipt | Elacity
AI agents now have their own accounts, with spending limits, approvals and kill switches. Every rule protects the buyer. The seller of the data still gets a payment and no terms.
AI Agent Payments: The Buyer Got Rules. The Seller Got a Receipt.
If an AI agent pays for your dataset, your archive or your API, it now does so under rules its owner wrote: how much it may spend, where, and when a human has to approve. You, the seller, get a payment. Nothing in that payment says what the agent may do with your work afterwards.
AI agent payments moved fast this month. On November 17, Lightspark launched Agent Accounts, which let agents hold, spend, send and receive money for a person or business, with account holders setting spending limits and deciding which payments need their approval. Five days earlier, Wirex launched Navoka, an invite-only agent with its own IBAN, debit card and stablecoin wallets, under merchant lists, limits and daily caps the agent cannot change.
Rain's Agent Vaults follow the same pattern, with a control layer that sets how much an agent can spend, which merchants it can pay and when a payment is permitted. The money side of the Agentic Economy, which we track in DeFi & Market Strategy, now works for machines.
The Failure of AI Agent Payments: Every Rule Sits With the Spender
Read those launches side by side and the design is consistent. Limits, approvals, kill switches and audit trails all protect the person whose money the agent holds. That is the right first problem to solve. Nobody should hand an agent an unlimited card.
The other side of the transaction gets a balance update. When XDC Network and Keyban partnered on accounts for AI agents, Keyban's founder put the demand plainly: "real work costs money: for data, APIs and digital services." Under that partnership, agents pay for APIs in USDC, per call, while finance teams set how much each agent can spend.
So the buyer arrives with a rulebook. The seller arrives with a price, at best.
Sellers have gained some ground. Cloudflare's pay per crawl lets site owners allow, block or charge AI crawlers per request, and Coinbase's x402 standard lets a server answer with a payment request that an agent settles before it receives the resource. Both let you set a price at the door.
Neither says anything about the room. Once the response leaves your server, a paid call and a scraped one end the same way: a copy, held by someone else, under no terms you wrote. We have looked at who holds the meter in AI content licensing. Payment rails decide how the meter gets paid, not what the payment buys.
Why a Payment Is Not a License
A license answers questions a payment cannot. May the agent keep the file after the task ends? May it train on it? Pass it to another agent? Sell an output built from it? Pay you again when it does?
Today those answers live in terms of service, if anywhere, and enforcing them means finding the breach after the fact. It is the same asymmetry we saw in surveillance pricing: the side that runs the system sets the terms, and the other side reads them later.
Agents make this sharper, not softer. A person reads a license once, maybe. An agent can buy far more often than anyone reads terms, and the only rules it is built to check are the spending rules its owner set.
The Elacity Solution: Terms That Travel With the Work
The seller needs what the buyer already has: rules checked at the moment of the transaction, not argued about afterwards. That is what we are building Elacity dDRM for.
1. Package the work as a Wealth Capsule
In the design, you wrap a dataset, a model, an archive or a song into a Wealth Capsule: a programmable, royalty-bearing good with your terms written in, covering who may use it, for how long, for what purpose and at what price. The terms belong to the good, not to a page on a website.
2. Check the terms at the point of use
Elacity dDRM is designed so that each use is checked against those terms, the way an agent's card is checked against its owner's limits every time it is used. An agent that wants to train on your work, rather than read it once, meets a different term and a different price, both set by you.
3. Let the terms follow the good
Because the terms travel with the Wealth Capsule, they are designed to stay attached when it changes hands. If one agent passes your work to another, the royalty you wrote in goes with it, instead of ending at the first sale.
None of this replaces the spending controls in this month's launches. It is the other half of them. Elacity dDRM is not live yet, and we will keep saying so plainly until it is. What it is built to add is the half of agent commerce the people being paid have been missing: terms the buyer has to meet.
"The people who create the value should own it. That is the entire reason Elacity exists." Sasha Mitchell, Founder, Elacity
Agents now carry wallets with rules. Your work should carry rules too. Follow Elacity on X as we build it.