JubJub
Sub-pillar 4.3Why provenance matters to agents

Why AI agents need verified provenance

An agent buying content for training is not just buying media. It is buying confidence in what that media is. Where it came from. Whether a human made it. Whether the record is clean. JubJub means the record is there before the question is even asked.

Captured at creation · Anchored on Base · Independently inspectable.

An AI agent buying content for training is not just buying media. It is buying confidence in what that media is. Where it came from. Whether a human made it. Whether the record is clean.

Agents are getting better at asking those questions. The creators whose content answers them clearly are the ones who get bought. The ones whose content cannot answer them get skipped, or worse, scraped for free elsewhere. JubJub’s ownership infrastructure means the record is there before the question is even asked.

01The quality problem

The data quality problem that is reshaping the market.

Model developers are sitting on a real problem. A large proportion of available web content is AI-generated, scraped without consent, of unknown origin, or some combination of all three. Training on that content produces models that amplify the same noise the training data contained. The model is only as reliable as what went in.

The fix is verified, human-captured content with a traceable origin. Content where you can answer the questions: who made it, when, with what, and is that claim checkable?

This is not a future concern. AI companies are already making purchasing decisions based on data origin. The question for every creator is whether their content arrives with that record or without it.

02In practice

What verified provenance means in practice.

On JubJub, provenance is not something you add later. It is captured at the point of creation. When you publish through JubJub, the record includes:

  • Your creator identity

    Bound to a verified profile, so the claim of authorship is anchored to a real account.

  • Technical metadata extracted at ingest

    Via FFprobe for video, Whisper for audio, and computer vision for visual content.

  • Subjects, categories, languages, interaction types

    The structured breakdown an agent reads to decide whether your content fits its task.

  • Timestamp and registration on Base

    On-chain and independently inspectable. The agent does not have to take your word for it.

NoteThis page explains why AI buyers value that record. If you want to understand how creators establish it at point of creation, that lives at /ownership/provenance.
03A distinct category

Human-captured content is a distinct category now.

There is a meaningful difference between content a human made, content an AI generated, and content scraped from the open web with no attribution. That difference is increasingly visible to buyers and increasingly priced in.

Human-captured content with verified provenance is not just more trustworthy. It is more useful for the specific tasks AI systems are being trained for: understanding real-world interaction, language as humans actually use it, visual composition choices that reflect human creative intent.

JubJub does not just claim your content is human-made. It makes that claim verifiable.
Pull quote · 03
04The payload

What the media intelligence payload includes.

When an agent purchases access to your content through JubJub, it receives a structured payload purpose-built for AI consumption.

01 / Transcript

Every word, timestamped

The full transcript, aligned to the media and ready to act on.

02 / Frames

Reference frames

Visual anchors for temporal grounding across the media.

03 / Metadata

Structured breakdown

Subjects, categories, languages, interaction types, complete media breakdown.

04 / Provenance

The record itself

Creator identity, registration timestamp, on-chain anchor.

This is what allows an agent to make a real, informed purchasing decision. Not a guess based on a title. Not a sample of the first thirty seconds. A complete picture of what the content contains and where it came from.

05Why now

Why this matters for creators right now.

Most creators have no way to prove at scale that their content is human-made. They can say it. They cannot verify it in a form a machine can read, check, and act on.

JubJub creates that verification record as a side effect of publishing. There is no extra step. No separate workflow. You publish, the record exists, and when an agent comes looking it finds everything it needs to make a buying decision in your favour.

Make your content verifiable.

The provenance record is created as a side effect of publishing on JubJub. Connect your AI key so the full intelligence payload, record included, is generated for everything you publish.

Connect your AI key

Captured at creation. Anchored on Base. Inspectable by anyone.

FAQProvenance, answered plainly

Questions, answered plainly.

What is verified provenance?

A machine-readable record of who made a piece of content, when, and with what. On JubJub, this record is created at point of publication and anchored on Base. It is inspectable by anyone, including AI agents evaluating your content for purchase.

Do AI companies actually pay more for verified content?

The market is moving in that direction. Model developers are making purchasing decisions based on data origin and quality. JubJub’s position is that human-captured, verifiably attributed content commands more attention and better pricing. The infrastructure reflects that thesis.

What is the difference between this page and /ownership/provenance?

/ownership/provenance explains how creators prove they made something. This page explains why AI buyers value that proof and how JubJub makes it machine-readable at the point of purchase.

Is the provenance record public?

The on-chain record is publicly inspectable. The full intelligence payload, transcript, frames, metadata, is purchasable via x402.

What if I imported old content rather than publishing natively?

Imported content receives a registration record but not a capture-verified provenance record. The distinction is visible in the payload and agents can see it. /ownership/import

How does this compare to C2PA or SynthID?

C2PA and SynthID operate at the file level. JubJub operates at the ownership and payment infrastructure level. They are addressing different parts of the same problem. They are complementary, not competing.