REAL SDK OUTPUTS · INDEPENDENT C2PA CHECK

A signed manifest.
Inside the file.

Each successful SDK export embeds signed C2PA provenance in the supported output file. You can inspect it with a standard C2PA reader, without an Ariadne registry.

Embedded in the file

Part of a successful SDK export. Carries AI-origin actions and the declared provider, system/version, creation time and asset ID.

Public registry API

Optional access to a stored manifest copy for recovery. Turning this off does not turn off the manifest inside the file.

Homepage image demo

A watermark-only example. Use the complete SDK files below to inspect signed C2PA.

Download. Inspect. Compare.

These are exact public release 0.7.3a4 sample bytes, checked again on 16 November 2026. The official c2patool 0.28.6 read each file with network disabled and no registry mounted. All four contained an embedded manifest with a validated signature and matching asset hash.

Development fixtures: the signing issuer is intentionally untrusted. This demonstrates embedded provenance and file binding, not production CA trust, legal certification or proof that an AI model made these procedural test inputs.

Original SDK fileIndependent resultReport / SHA-256
image.png ↓
254,954 bytes
Embedded
Signature + asset hash validated
Validator JSON ↗
f8340edecd36…
economy_5s.mp4 ↓
113,834 bytes
Embedded
Signature + asset hash validated
Validator JSON ↗
ba0933efe1ab…
economy_2s.mp4 ↓
155,948 bytes
Embedded
Signature + asset hash validated
Validator JSON ↗
637aed4f9b56…
resilient.mp4 ↓
75,775 bytes
Embedded
Signature + asset hash validated
Validator JSON ↗
c5fc62466eea…

What the independent validator reads

c2patool image.png --detailed
c2patool economy_5s.mp4 --detailed

Repeat with economy_2s.mp4 or resilient.mp4. The linked JSON files are the raw validator outputs; the summary records every file hash, the validator identity and the source archive hash.

Read the complete check summary and public record fields ↗ · Original release and sample archive ↗ · Full release qualification ↗

Embedding and public API access are different

The file receives its signed manifest during export. The kit's --public-manifests setting and per-job publish_manifest: true control whether a stored copy may be served through the public recovery API. They do not disable embedding.

After metadata is stripped, watermark recovery and a persistent registry can help reconnect a record. A recovered record does not automatically authenticate an edited copy. Configure real signing credentials and trust for production.

Kit and publication settings ↗ · Recovery workflow ↗ · Production signing ↗

Make your own SDK export ↗Try the watermark-only image demo ↗