AI Data Licensing Marketplaces Skipped Custody | Elacity
AI data licensing marketplaces from Cloudflare and Microsoft finally pay creators. You still upload the file first. Elacity puts enforcement in the data itself, so the key is used, never owned.
AI Data Licensing Marketplaces Will Pay You. You Still Hand Over the File.
Cloudflare and Microsoft will now pay you when an AI reads your work. To collect, you upload the file to their catalog first. The moment you do, the thing you were trying to protect is readable on someone else's server, and the only wall between your data and its next use is a contract you have to trust them to keep.
This is the new shape of the data economy, and it arrived fast. Cloudflare bought the licensing marketplace Human Native in January to pay creators for the data that trains AI. Microsoft opened its Publisher Content Marketplace weeks later, paying publishers based on how their content actually gets used. The scrape-for-free era is closing. A metering era is opening.
What the marketplace actually fixed
For two years the arrangement was simple and one-sided. A model crawled your site, learned from your words, and paid you nothing. The marketplaces change the accounting. They give you a counterparty, a price, and a log of what was used. The market is even shifting from buying a scraped dump once to renting a live feed continuously, part of a broader re-licensing of AI training data now underway.
Getting paid at all is a real leap from being harvested for free. It is worth saying so before saying what still breaks.
What it did not fix
Payment and custody are different problems, and the marketplace solved only the first. To list your data, you deposit it with the broker in a form it can read and show to buyers. From that instant, enforcement is a promise. The platform promises the AI uses only what it paid for, promises to meter honestly, promises its catalog will not be breached or subpoenaed. Your leverage ends where their honesty begins.
A receipt records that something happened. It cannot stop the next thing. Once a model has read your data in the clear, no invoice un-trains it. The marketplace decentralised discovery and payment. Custody of the actual file it left exactly where it was, in the middle.
Enforcement belongs in the data, not the middleman
Elacity starts from the opposite end. Instead of depositing your file with a broker, you wrap it. With Elacity dDRM you package a dataset, a song, a model, or a document into an encrypted, programmable good, a Wealth Capsule, with your terms and royalties written into the good itself.
The data stays encrypted everywhere except one sealed moment of use. When an AI agent pays to read it, the key that unlocks it is never handed to the agent, the app, or Elacity. It is split across an owned set of independent machines, a 2-of-3 quorum, and each machine re-checks your on-chain rights before it releases its share. The secret exists in the clear for a split second inside a sealed sandbox, welded to that one paid transaction, then wiped.
Keys are used, never owned. The agent receives the computation it paid for. It never receives the copy it could keep and reuse. Bitcoin made money ownable; Elacity makes data ownable.
This is trust-minimised, not magic. The quorum today is an owned, operator-run set, so a colluding majority could in principle rebuild a key. We say that plainly, because the alternative on offer is a single company holding your data in the clear and asking you to believe its dashboard, which is the model the new marketplaces just rebuilt with a nicer invoice.
What changes when the data enforces its own terms
- You license access, not the file. The AI computes on your data and pays for it, but never holds a copy to keep.
- Your terms travel with the asset. Royalties and limits live inside the good, not inside a platform contract you cannot audit.
- There is no central honeypot. No readable catalog of everyone's work sits waiting to be breached or handed to a court.
- The key is used, never owned. It is reassembled for one paid use inside a sealed sandbox, then destroyed.
This decides who actually captures the value. In a marketplace, the platform sets the terms and takes the spread, and the biggest catalog wins the best rate. When the terms live in your asset, you set them. As Sasha Mitchell, Founder of Elacity, puts it: "The people who create the value should own it. That is the entire reason Elacity exists."
The consumer portal for wrapping and listing your own capsules is still being built. The enforcement layer beneath it, the sealed key and the on-chain rights check, already runs. We would rather ship the hard part first and be honest about the rest.
The middleman becomes optional
The marketplaces answered a real question: how do creators get paid when machines read their work. They left the harder one open: how do you sell access to something without surrendering it. Answer that at the data layer, and the broker in the middle becomes a convenience you can take or leave. Follow Elacity on X for how the ownership layer gets built.