Agentic Commerce Skipped the Ownership Layer | Elacity
The card networks gave AI agents a payment rail this month. It moves money but settles nothing about who owns what an agent buys. This is the ownership layer agentic commerce skipped.
Agentic Commerce Got a Payment Rail. It Skipped the Ownership Layer.
This month an AI agent gained the ability to pay another AI agent on your behalf, at machine speed, without checking with you twice. This is the moment agentic commerce became real for money. It is not yet real for ownership. When an agent buys something you made, the payment clears in milliseconds, and your claim on the thing being bought stays exactly where it has always been, which is nowhere.
On June 10 the card networks made it official. Mastercard shipped Agent Pay for Machines, built for the high-frequency, low-value payments that agents fire at each other continuously. Visa opened Intelligent Commerce Connect, a network-agnostic on-ramp for agents to transact on your behalf. Around them sits a fast-growing stack of agent payment protocols from OpenAI, Stripe, Google, and Skyfire, all racing to let machines settle money.
Read the announcements closely and you notice they all solve the same half of the problem. They move money. None of them touch what the money is for.
The Ownership Layer Agentic Commerce Skipped
The payment rail is real progress, and it is worth saying so plainly. Letting an agent pay per request, in tiny amounts, at machine speed, removes a genuine bottleneck. Stablecoins and these new rails are the money half of the agentic economy, and that half is arriving on schedule.
But a payment settles money. It does not settle ownership. Those are different problems, and only one of them got a launch event this month.
When an agent buys your article to summarise it, or licenses your dataset to fine-tune a model, the transaction records one fact: a dollar moved from one party to another. It does not record that the work was yours. It does not record what rights you granted, whether the buyer may resell it, or that a share should return to you each time the work is used again.
So a payment, on its own, leaves the questions that actually matter to you unanswered:
- Who owned the thing being bought, and can they prove it?
- What rights really transferred: a single use, or a copy the buyer keeps forever?
- Does anything flow back to the source when the work is used a thousand times more?
Today those answers live in a contract nobody reads, or in a royalty statement that, for many creators, pays in fractions of a cent. The rail got faster. The ownership question got skipped.
Put the Rights Inside the Good
Elacity starts from the asset, not the checkout. The fix for skipped ownership is not a faster way to pay. It is making the thing being bought carry its own rights, so that ownership settles in the same motion as the payment.
"The people who create the value should own it. That is the entire reason Elacity exists." Sasha Mitchell, Founder.
1. The good carries its own terms
With Elacity dDRM, a song, dataset, model, or document is packaged into a Wealth Capsule: an encrypted, programmable, royalty-bearing good. The terms travel inside the asset, not in a side agreement. An agent does not buy a loose file it can copy and pass on for free. It buys defined, enforced access to a good whose owner set the conditions.
2. The key is used, never owned
At the moment of use, the key that unlocks the capsule exists in the clear for a split second, inside a sealed sandbox, welded to that one transaction, then wiped. It is split across an owned set of independent machines, a two-of-three quorum, each of which re-checks your on-chain rights before releasing its share. The agent gets the use: the stream, the inference, the working copy. It never gets the asset itself, which is the same principle that keeps an agent's own keys used but never held.
3. The royalty is part of unlocking, not a promise after
Because rights and payment settle together at the gate, what returns to the owner is a condition of access, not a statement mailed three months later. The capsule will not open unless its terms are met, including the share routed back to its source. A receipt is not a royalty: one records that a sale happened, the other makes the sale impossible on any terms but the owner's.
What This Is, and What It Isn't
Honesty about the edges is part of the design. The owned quorum is trust-minimised, not trustless: a colluding set of operators could in principle reconstruct a key, which is a deliberate trade for recoverability, and we say so out loud. The consumer portal to create and sell capsules is still being built. The agent-facing pieces, agent wallets and an autonomous approval loop, are in progress, though the hard primitive beneath them, a key an agent can use but never see, already works today.
Visa let strangers transact without trusting each other. Elacity lets humans and AI agents compute together without surrendering their keys. The agents will keep getting better at paying. The open question, the one this month did not answer, is whether the things they pay for are ever yours to begin with.
Follow Elacity on X to watch the ownership layer get built.