Content Credentials answer questions about a file’s provenance. An AI identity licence answers whether a real person permitted the specific use of their face or voice. They solve different layers of the same trust problem.
| Question | Content Credentials | AI identity licence |
|---|---|---|
| Primary purpose | Record the origin and history of a media asset | Record permission, scope and commercial terms for identity use |
| Core object | A signed provenance manifest bound to media | A signed licence connected to verified identity and an asset version |
| Proves consent? | Only if a trusted consent assertion and its evidence are included | Consent and signed scope are explicit parts of the chain |
| Controls future generation? | No | Revocation and expiry stop future generation through the platform |
A provenance credential with no licence can show how content was made while leaving permission unanswered. A licence with no output linkage can show that an agreement existed while leaving the specific file unanswered. SocialGravity’s receipt links the person, asset, licence, generation and credential.
C2PA describes Content Credentials as a way to store and access cryptographically verifiable provenance information. It also cautions that verified provenance is not a judgment that the underlying assertion is good or true.
Source: C2PA Content Credentials specification.
The interactive receipt walkthrough makes that distinction concrete: a signature can pass while the buyer still lacks evidence of consent, a matching original file or current permission. It uses synthetic test data, not a real licence.
Check the SocialGravity verifierDefine content provenance
A SocialGravity receipt links its generation event to a content credential as one part of a wider permission chain. The public receipt specification documents the exact fields and verification process.
No. Provenance records information about content. Generation controls, licence expiry and revocation are separate operational mechanisms.
For licensed AI likeness content, ask for both the permission record and output-level provenance, connected to each other.