PRACTICAL GUIDES / UPDATED 2026-11-15

Understand AI Watermark Verification Results

Ariadne reports several kinds of evidence separately. Read the recovered watermark, C2PA signature, issuer trust and asset binding together. A detected ID alone does not prove that every frame came from one service or that the content is true.

What the main results mean

Result What you can conclude
Supported watermark ID recovered The named method read an ID from the examined image or frame positions
Registry record found The configured registry has a record linked to that ID; inspect source policy and content binding
Signature valid The signature checks for the signed asset; issuer trust is a separate decision
Issuer trusted The issuer matches the configured trust policy; this does not establish factual truth
not_found That method completed its check without a supported result; not proof of human creation
not_checked The check did not complete or could not run; inspect the reason and search budget
multiple_ids More than one ID was observed; the report retains each with its evidence rather than choosing one for the file

For video, sample counts and read positions describe examined evidence. They are not a whole-video confidence percentage. For recovered provenance, exact_registered_file requires the registered file hash to match; an ID in a changed file can have content_binding=not_verified.

Why can a record be hidden in one place and visible in another?

The public verifier applies source-specific disclosure rules. Consider a file with an untrusted C2PA claim saying “Studio A” and a recovered watermark ID linked to a reviewed operator-registry record for “Studio B”.

Public-source configuration Untrusted C2PA free text Matching registry public fields
No approved sources Hidden Hidden
Registry publisher/system explicitly approved Hidden May be shown under the reviewed-field policy
Source does not match the approval Hidden Hidden

Approving public registry fields does not authenticate the uploaded file or make an unrelated C2PA issuer trusted. The registry result and uploaded claim remain distinct evidence sources.

public_output.redacted_fields lists paths, for example c2pa.record.publisher or recovery.record.publisher. A hidden path in the C2PA claim does not say that the corresponding field is hidden in every other source. Do not interpret the list as a global redaction flag.

Connect this to your app

Show the named result and its scope. Keep signature, trust and file binding distinct. HTTP 200 means the request was handled; it does not mean a watermark was found. Preserve the signed report when your workflow needs evidence, and verify its signature against your pinned report key.

Exact result contract · Signed reports · Public verifier and registry · Privacy and data handling

Browse documentation ↗