Provenance comparison
Writing receipts record a session; Content Credentials carry asset provenance.
Both approaches use cryptographic concepts to make provenance harder to alter silently, but they address different layers. HumanTyped describes one writing session; C2PA standardizes signed provenance information associated with a digital asset.
Different unit of evidence
C2PA binds manifests to assets; HumanTyped binds a recorded operation journal to one sealed text receipt.
Different ecosystem
Content Credentials are an open standard; HumanTyped currently provides a product-specific public verification page.
Neither proves truth
A valid signature supports integrity and provenance claims, not the factual accuracy or moral quality of content.
What C2PA Content Credentials do
The C2PA specification defines manifests containing assertions, a signed claim, and bindings to an asset. Compatible tools can use that data to describe provenance, edits, ingredients, and the signer within a broader trust model.
This interoperability is valuable for images, video, audio, and supported document workflows that move across applications. The standard does not by itself guarantee that an assertion is true; users still assess the signer and context.
What a HumanTyped receipt does
HumanTyped records accepted text changes inside its editor, reconstructs the sealed result on the server, and exposes a signed receipt with session evidence and explicit limits. It is optimized for an inspectable URL connected to a short public text.
The receipt is not currently a C2PA Content Credential and should not be presented as standards-compatible asset metadata. Its value comes from the controlled writing workflow and the clear connection between the observed session and displayed text.
Where the approaches could meet
A future workflow could preserve a HumanTyped receipt as an assertion or ingredient referenced by broader asset provenance, provided the integration follows the current C2PA specification and its security requirements. That would require implementation and conformance work, not a marketing label.
For now, choose C2PA when cross-tool asset provenance is the requirement and HumanTyped when a public writing-session receipt is the requirement. Use both only when each layer remains understandable to the reader.
Side-by-side
Compare the evidence, not the slogans.
| Question | C2PA Content Credentials | HumanTyped |
|---|---|---|
| Scope | Interoperable provenance for digital assets | One text session in HumanTyped |
| Primary container | Manifest embedded in or associated with an asset | Public receipt URL and sealed record |
| Open standard | Yes | No—product-specific protocol |
| Proves factual truth or identity | No, not by itself | No |
Primary sources
Check the current product and evidence record.
Evidence, not certainty