A likeness is an AI asset. Give it terms, a price and a paper trail.
Most likeness disputes are not really about detection — they are about the absence of a record. The registry turns a voice and a face into an enrolled, consented, AI-licensable asset with machine-readable terms that survive contact with the internet.
- enrolment
- voice + face
- grant format
- signed JSON
- revocation
- immediate
- consent
- recorded
What a grant actually says
A licence written in prose cannot be enforced by a model or a crawler. A grant written as structured, signed data can be checked automatically by a generative AI tool before it synthesises, by a platform at upload, by a studio at render time, and by our own discovery agents when they find a match.
- ScopeWhich asset — a specific enrolled voice, face, or both.
- PermissionMedia types, AI contexts and channels that are allowed.
- ExclusionsCategories that are never permitted, whatever the fee.
- Term & territoryStart, end, renewal, and where the licence applies.
- ConsiderationFee basis and reporting obligations for royalties.
- RevocationConditions under which the grant stops being valid.
Built for a roster, not a single celebrity.
Agencies manage hundreds of clients, studios manage thousands of assets, and both need approvals that do not depend on one lawyer answering an email.
Consented enrolment
Guided capture for voice and face with explicit, recorded, revocable consent to AI synthesis — and proof of who consented, when, and to what.
Roster management
Group talent by agency, division or production. Delegate approvals, set default terms, and lock categories that are never licensable.
Machine-readable grants
Every licence is issued as signed structured data with a human-readable counterpart, so systems and people can both act on it.
Verification API
Any AI tool or agent can ask, in one call, whether a proposed synthetic use is covered by a live grant before it generates anything.
Term & revocation
Grants expire on their own. Revoking one propagates immediately to scanning, takedown and any integrated platform.
Royalty-ready records
Usage reported against a grant becomes an auditable statement — the basis for settlement without a spreadsheet archaeology project.
A grant nobody can check is just a PDF.
The registry is designed to be queried by systems that are not ours: generative AI vendors, agent frameworks, platforms at upload, studios in the render pipeline, and rights databases already in use.
Grants are published as signed credentials with a stable identifier, so a third party can verify authenticity and current status without an account and without learning anything about the holder beyond what the grant discloses.
Where a platform supports content credentials, a grant reference can be bound directly into the C2PA manifest of the produced asset — turning “we had permission” from a claim into something checkable at the file level.
const grant = await pv.registry.check({
subject: class="text-brand">"did:proveniro:mad-9f31",
intendedUse: {
media: class="text-brand">"advertising",
territory: class="text-brand">"GB",
context: class="text-brand">"in-game voiceover",
},
});
class=class="text-brand">"text-ink-4">// class="text-brand">"granted" | class="text-brand">"denied" | class="text-brand">"expired" | class="text-brand">"revoked"
if (grant.status !== class="text-brand">"granted") {
throw new Error(grant.reason);
}From enrolment to enforcement in four moves.
- 01
Enrol
Capture voice and face under guided consent, with liveness on the capture itself so the enrolment cannot be poisoned.
once
- 02
Define terms
Set defaults for the roster and exceptions for the individual. Legal writes the policy once, not per deal.
once
- 03
Issue grants
Every licensed use gets a signed grant with an identifier that a counterparty can verify independently.
per deal
- 04
Enforce
Scanning matches against the registry, so anything outside a live grant is by definition unauthorised.
continuous
- identifiers
- Decentralised identifier per subject; stable grant IDs; optional ISNI / IPI cross-reference
- signatures
- Ed25519 signatures with published verification keys and revocation lists
- consent record
- Captured statement, timestamp, scope, and revocation history retained for the life of the asset
- storage
- Biometric templates encrypted at rest with per-subject keys; raw enrolment media optional and deletable
- content credentials
- C2PA manifest binding with grant reference and issuer assertion
- access
- Role-based, with agency, division and individual scopes plus delegated approval chains
Put AI terms on the asset before someone else sets them for you.
Talent agencies, studios and individual performers are enrolling now. The registry is free to browse for verification and priced per managed asset.
soc 2 type ii in progress · eu & uk data residency · no ai training on your data