Proof Issue
What rights exist?
Transforms verified authority, explicit consent and approved terms into a signed, portable and revocable licence credential.
- API
- POST /v1/licence-requests
- OUTPUT
- LICENCE CREDENTIAL
THE PROOF PROTOCOL Rights infrastructure for generative media
Proof makes authority operational across the entire synthetic-media lifecycle: issue the rights, authorize the job, bind the output and verify every use.
ONE PROTOCOL / FOUR DECISIONS
What rights exist?
↓May this job run now?
↓What was actually created?
↓Is this use valid here?
✓PRODUCT SURFACES A complete control loop
Each service answers a different question. Keeping them separate prevents a valid signature from being confused with permission to perform any action, anywhere, forever.
Transforms verified authority, explicit consent and approved terms into a signed, portable and revocable licence credential.
Evaluates the licence against the requester, reference asset, provider, model, script, territory, channel, time and usage limits.
Registers the final output, cryptographic digest, optional durable fingerprint, provider evidence and C2PA manifest reference.
Returns an explainable allow, deny or review decision from signature, status, policy, asset binding and distribution context.
Identity, IP, organisations and mandates.
Expiry, suspension and revocation.
Append-only events and receipts.
Optional, chain-agnostic external anchoring.
END-TO-END DEMO Marcus Vale × Northstar Sports
A fictional but realistic journey showing how a GenAI platform would use Proof before and after generating a licensed fan video.

International football player
Northstar Sports requests 50 multilingual fan videos. Marcus or his authorised agency approves the purpose, script family, channels, territories, providers, duration, duties and prohibitions.
Open the complete token record ↗subject: Marcus Vale licensee: Northstar Sports purpose: Fan welcome campaign territories: FR, GB max_assets: 50
Signed VC · active until 30 Sep 2026
TRUST ARCHITECTURE Separate what must not be confused
Proof uses different artefacts for durable rights, temporary execution and later verification. Compromise of one layer must not silently rewrite another.
Private, encrypted evidence. The legal agreement remains authoritative.
Portable policy, issuer key, dates, status reference and evidence digests.
One requester · one job · short expiry
Output hash · provenance · counter
Allow, deny or review with stable reasons and checked-at time.
A platform can request issuance, never invent consent.
Possession alone never authorizes a generation.
Media history and rights authority remain distinct.
Blockchain anchoring is optional and replaceable.
INTEGRATION MODES Start with the authority available
Platforms can adopt Proof without becoming issuers. Enterprise partners with an existing mandate can later enable tightly constrained just-in-time issuance.
The user presents an existing licence. The platform calls Proof Authorize before every generation and Proof Bind after output.
Fastest integration · lowest governance burdenWithout a token, the platform opens a Proof Issue workflow. The rightsholder approves outside the generation interface.
Best for marketplaces and new commercial usesAn accredited partner issues only inside a pre-approved mandate, schema, spend, scope and audit policy.
Enterprise profile · enhanced controls required