Product / Verification
A record anyone can check.
Every delivery mints a public verification page: what was made, with which models, and - stated plainly - how each claim was evidenced. No account, no trust-us. Open one now.
The four evidence grades.
What are Archibal's evidence grades? Every provenance claim is labeled attested, integration-reported, studio-logged, or user-declared - a plain-language statement of how the information reached the record and how much confidence it earned.
Provenance claims are not all equal, and pretending they are is how trust gets spent. Every claim in an Archibal record carries one of four grades - here is what each one takes to earn, and what it actually tells you.
What earns it: Verifiable capture evidence arrived with the file: an embedded workflow graph a validator can re-open, or a cryptographically signed manifest.
What it means: The strongest grade. The claim can be checked against the evidence itself, not just against a report about it.
What earns it: A generation service reported the details over a trusted automatic channel - a verified webhook from the vendor, carrying its own metadata.
What it means: The vendor said so, machine-to-machine, at generation time. Strong, but it rests on the vendor being right.
What earns it: A studio pipeline or orchestration tool logged the job, and the log was imported and matched to the file.
What it means: A production system recorded it as it happened. The log is evidence of process, one step removed from the file itself.
What earns it: A person stated how the file was made - by declaring a model or uploading with a description.
What it means: A declaration on the record, honestly labeled as one. It is never silently upgraded to look like captured evidence.
No manufactured certainty
We show you what we know and how confident to be - nothing more.
A verification page will tell you a model is unknown when it is unknown, that a stage was not captured when it was not, and that a claim is a declaration when a person made it. Records freeze at delivery, so what a certificate said then is what it says forever - and revoked deliveries say so in red, on the page. The one thing you will never find is a certainty the evidence did not earn.
Three ways to check: a delivery's own verify link, the registry lookup (fingerprint-based - it survives metadata stripping), and the C2PA inspector for reading Content Credentials in any file.
Frequently asked
Who can open a verification page?
Anyone with the link - no account needed. It shows what was delivered, which models were involved, the risk summary as frozen at delivery, and how the provenance was captured, at the disclosure level the creator chose.
What if the file was re-encoded or its metadata stripped?
The registry lookup matches by perceptual fingerprint, which is derived from the content itself - a transcoded or metadata-stripped copy still finds its original signed record.
What does "no match" mean?
Only that the file is not in the Archibal registry. It does not mean the file is fake, unverified, or AI-free - absence of a record is stated as exactly that, never dressed up as a verdict.