A serious platform should show who approved the campaign, what it can actually control during production, and how the buyer can verify the released file against current permission.
First, work out what they actually do
| 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. |
Some companies cover more than one category. Ask them to name the boundary between access, permission, production and provenance instead of rolling it all into one claim.
Eight checks that matter
| 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. |
Seven questions for the call
- How do you verify the real person and any representative's authority?
- What exact record proves this person approved this buyer, campaign and intended use?
- Can production or delivery happen before the payment condition is secured?
- Which controls are enforced by your system, and which facts are asserted by the buyer or provider?
- Can I verify a released file against its licence and current status without taking your dashboard on trust?
- What stops future generation after expiry, pause or revocation?
- What does your evidence not establish?
Take the worksheet
Download the JSON worksheet or CSV. It covers identity, consent, campaign scope, custody, production, receipts and current status. The synthetic cases include a complete chain, missing campaign authority and revoked permission. They are examples, not customer results.
Where SocialGravity fits
SocialGravity handles the permission layer for licensing a real person's face or voice. We connect identity, consent and the signed campaign to a named production route, a receipt for each registered release and the licence's current status. We do not claim to find every use on the internet or turn a technical receipt into a legal judgment.
The brand guide, seven-record standard and synthetic evidence room show the same chain at different levels.
Sources and limits
This framework draws on the U.S. Copyright Office report, SAG-AFTRA guidance, FTC endorsement guidance and the C2PA specification. Permission, advertising compliance and provenance remain separate questions.
This is a buyer evaluation framework, not legal advice, a vendor ranking or a claim of industry consensus.
Common questions
How should a brand evaluate an AI likeness licensing platform?
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.
What should an AI likeness licensing company prove?
It should distinguish what it verifies, controls, observes and receives as an assertion, then connect permission for the specific campaign to each registered output.
Is an AI talent marketplace the same as permission infrastructure?
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.
Do Content Credentials prove likeness permission?
No. They can make provenance assertions verifiable, but permission from the real person and the campaign scope require their own evidence.
Is SocialGravity a generative AI model provider?
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.