Issue an attestation for every piece of content you ship — proof it came from a consented person under a live, scoped license. The biocode mark and verify page are the visible token; the SDK returns valid or invalid; a revocation flips it the moment it lands.
C2PA-adjacent, but consent-first: the attestation carries the consent record, not just the signing chain. Revoke the license and the attestation goes invalid — everywhere that checks. The person stays the proof; a seal is only the footnote.
Content credentials prove a file's history. Ours go further: the attestation carries the consent record — who agreed, to what use, under which live license.
The biocode mark and verify page are what a viewer actually sees and checks. A scan-to-verify seal is the audit footnote — never the hero. The proof is the human.
Revocation invalidates the attestation in real time. The answer is valid or invalid — never “maybe.” A frozen credential can't say that.
An attestation isn't a watermark you trust on faith — it's a live check against the consent ledger. Here's what runs at each stage, and the standards it speaks to. Watch the ledger run underneath.
Every attested output references a verified person, a live license, and the provenance of how it was made.
An attestation is issued for each piece of content, with an optional content-credentials manifest — and the biocode as the visible token.
The SDK returns valid or invalid against the ledger. A revocation flips it the moment it lands.
Designed to these regimes. Not a certification.
We'll attest one file, verify it through the SDK, and revoke the license so you can see it flip.