Your content has always been one sale at a time. A person finds it, watches it, pays for it. That model still works. But a second model is running alongside it now, and most creators have no idea it exists.
AI agents are buying content. Autonomously. They query catalogues, evaluate payloads, and settle payments without a human anywhere in the loop. If your content is on JubJub, they can already find yours, sample it, and pay for it. If it is not, they cannot.
01The sequenceWhat actually happens when an agent buys your content.
No magic. Just a clean sequence that runs without you.
An agent connects via the MCP server
It receives a machine-readable catalogue of available content and pricing. See how the MCP server works.
It requests a sample
Transcript, reference frames, and structured metadata for the content it is interested in.
It evaluates the sample against its task
Training, research, content alignment, something else entirely. The agent decides on what is actually in the content.
If the content fits, it pays
Via x402 or MPP. USDC settles directly to your connected wallet. JubJub takes 3%. You keep 97%. No payout hold.
That is the whole flow. You set your price at publish time. Everything after that is infrastructure.
02The payloadWhat the agent gets back.
When an agent purchases media intelligence through JubJub, it receives a structured payload built for machine consumption, not human browsing.
Every word, timestamped
The full transcript, searchable and aligned to the media.
Visual anchors
Temporal grounding across the media for alignment work.
Structured breakdown
Subjects, categories, languages, interaction types, complete media breakdown.
This is not a file. It is not a link to your video. It is a purpose-built intelligence payload an agent can act on immediately, without any further processing on its end. That is what makes it worth buying.
You publish. Agents pay. Everything in between is infrastructure.
03The protocolsThe two protocols behind it.
Two open standards make machine payments possible. JubJub implements both.
x402
An HTTP payment protocol. An agent requests a resource, receives a 402 Payment Required response with pricing, pays, and retries.
- The entire exchange happens at the HTTP layer
- No wallets to connect, no approval flows
- No human in the loop
MPP
Machine Payment Protocol. It complements x402 by adding sessions, spending authorisation, and multiple payment rails.
- Stablecoins, cards via Stripe, Bitcoin via Lightning
- Authorise a spending limit once
- Many payments within one session
Together they cover every agent that comes looking. JubJub does not ask which protocol the buyer is running. It speaks both.
04DiscoveryHow agents find your content, and what it costs.
Agents do not browse. They do not scroll. They query.
When an agent connects to JubJub’s MCP server, it receives a structured catalogue: what you have published, what each item covers, and what each item costs. The agent reads that catalogue, pulls a sample payload on anything relevant, and makes a buying decision based on what is actually in the content, not what the title says.
You set the price. JubJub surfaces it. The rest happens without you.
05Not your problemWhat you do not have to do.
You do not have to build a payment API. You do not have to manage agent wallets, negotiate licensing terms per buyer, or monitor which agents have accessed what. None of that is your problem.
JubJub handles the infrastructure. You publish. Agents pay. The payment rails, the catalogue, the enforcement, all of it sits underneath the work you were already doing.
