Evaluate an AI likeness licensing platform by asking what it can prove before production, what it controls during production and what evidence survives after release. A large roster, a model-access agreement or a synthetic-media label cannot replace permission from the person for the specific campaign.
| Provider type | Usually supplies | What still needs proof |
|---|---|---|
| Marketplace | Discovery, introductions and commercial coordination. | Identity authority, exact campaign permission, production custody and output evidence. |
| Managed production vendor | Creative services and generated deliverables. | The source of likeness rights, scope controls, approved changes and current permission. |
| Permission infrastructure | Identity, consent, licence, payment, authorization and receipt records. | Which production route is controlled or externally reported, and which relying parties actually verify the evidence. |
A provider can combine categories. Ask it to name each boundary precisely instead of treating access, permission, production and provenance as one claim.
| Control | Evidence to request | Warning sign |
|---|---|---|
| Identity and authority | A verified identity root and the authority of any representative. | A profile, uploaded file or public identity is treated as permission. |
| Consent | A reviewed decision by the identified person before listing, capture or use. | Consent is bundled into broad platform terms or inferred from asset access. |
| Campaign scope | One signed record covering buyer, use, script rules, channels, territory, term and approvals. | The licence does not identify the campaign or permitted changes. |
| Payment gate | The commercial obligation is secured before licensed generation or delivery unlocks. | Production begins before the agreed payment condition is met. |
| Production control | The covered asset version, operator, assurance route and enforceable limits. | The vendor cannot distinguish controlled execution from agency self-reporting. |
| Output proof | A release record connecting the output bytes to the person, asset, licence and production event. | A general certificate or disclosure is reused for every output. |
| Lifecycle | Current status, expiry and revocation controls, plus the agreed rule for existing outputs. | A downloaded contract is the only source of current permission. |
| Integration boundary | A clear statement of what the platform controls, observes, receives from others and cannot prove. | Marketing language silently turns assertions into verified facts. |
SocialGravity is permission infrastructure for licensing a real person's face or voice. Its operating chain connects verified identity, reviewed consent, signed campaign scope, secured payment, a named production route, a receipt for each registered release and current licence status. It does not claim that every lawful arrangement must use SocialGravity, that every released use on the internet will be discovered, or that a receipt decides legal validity.
Use the brand buyer guide to prepare a campaign, the seven-record standard to test the evidence chain and the synthetic evidence room to inspect a worked example without implying a real customer or campaign.
The U.S. Copyright Office digital replicas report discusses authorization and protection for realistic digital depictions. SAG-AFTRA commercials guidance illustrates consent and intended-use requirements within its agreements. The FTC endorsement guidance covers separate advertising truthfulness and disclosure duties. The C2PA Content Credentials specification describes technical provenance, not permission from the depicted person.
Bring a campaign briefBuild the scope first
This is a buyer evaluation framework, not legal advice, a vendor ranking or a claim of industry consensus.
Ask for evidence of verified identity, reviewed consent, signed campaign scope, a payment gate, a controlled or clearly attributed production route, output-specific receipts and current licence status.
It should distinguish what it verifies, controls, observes and receives as an assertion, then connect permission for the specific campaign to each registered output.
No. A marketplace can support discovery and contracting, while permission infrastructure establishes and evaluates the records connecting a person, campaign, production route, output and current status. One provider may offer both, but the evidence boundaries remain distinct.
No. They can make provenance assertions verifiable, but permission from the real person and the campaign scope require their own evidence.
No. SocialGravity provides identity permission, licensing, payment, authorization and receipt infrastructure. A named assurance route describes where production occurs and which controls are enforced or externally reported.