Verifiable content provenance for the claims pipeline.
Hashproof is the substrate that sits underneath your existing intake, scoring, and SIU stack. We sign every piece of submitted media at ingest, resolve it across re-submissions, and verify it when a claim is flagged. Your forensic vendor keeps doing what it does, on top of a portable C2PA manifest.
What is going wrong
Three structural gaps in current claim media handling, each independently load-bearing.
Synthetic media is reaching claims intake
AI-generated damage photos, voice clones in recorded statements, and fabricated documents are appearing in first-notice-of-loss submissions. Most carrier intake stacks were built before generative tools were ubiquitous and have no native way to flag a synthetic submission.
Forensic vendors are vertical-locked
Existing fraud-detection products bundle proprietary scoring, workflow tools, and storage. Switching costs are high; running multiple vendors on the same claim is harder than it should be. Carriers want a substrate underneath their forensic vendors, not a replacement for them.
Audit chains break across vendors
When a claim escalates to litigation or reinsurance review, the chain of custody for submitted media has to be reconstructable, end-to-end. Audit trails that live inside one vendor are hard to share; audit trails that span three vendors usually do not exist.
What Hashproof brings
Four primitives, exposed as one HTTP API. Same substrate that powers news provenance, training-data lineage, and government archives.
Provenance at intake
Hashproof signs every piece of submitted media at the moment it enters your system. Each photo, video, audio recording, and document gets a C2PA manifest with cryptographic provenance, indexed for later resolution and verification.
Forensic verification on demand
When a claim is flagged, the verify endpoint returns signature validity, trust-list match, full lineage, and per-edge confidence scores. The same response shape that powers automated triage also feeds the SIU human-review surface.
Lineage that survives re-submission
Re-encoded, cropped, or compressed media still resolves to its original manifest. Useful when the same asset is submitted to multiple carriers, or when a third-party administrator forwards a transformed copy upstream.
Audit-ready evidence chain
Every signed manifest carries a Merkle inclusion proof anchored to Base L2 on an hourly cadence. The proof is independently verifiable on-chain. Reinsurance review and litigation discovery get the same primitives, with no vendor-specific replay.
Where it sits in the workflow
Hashproof is invoked at four points in a typical claim lifecycle. It does not replace your intake, scoring, or workflow systems. It provides the verifiable layer they sit on.
01
Intake
Your FNOL system POSTs each piece of submitted media to the Hashproof signing endpoint. The original bytes are preserved; a signed C2PA manifest is returned and stored alongside the claim record.
02
Triage
Your existing fraud-detection vendor reads the verified manifest, the lineage graph, and any structured trust-status fields. Hashproof does not score the claim. It tells your scoring stack what is and is not synthetic, and what the upstream lineage looks like.
03
Adjudication
When SIU reviews the claim, the forensic mode returns per-edge confidence scores and the full ingredient DAG. Reviewers see whether a piece of media was sourced from another claim, derived from a known-synthetic source, or arrived with a clean chain.
04
Audit
For reinsurance and litigation, the compliance reporting endpoint produces an auditor-ready PDF and JSON, with manifest-level evidence URLs and on-chain proof references. Custodial-grade record retention without custodial vendor lock-in.
How Hashproof is different
We are not a vertical fraud-detection product. We are the cryptographic substrate that vertical products and your in-house stack can both run on.
Horizontal substrate, not vertical product
Hashproof is the same primitive used by news organizations, AI labs, and government archives. Your forensic vendor sits on top of it; you keep your existing scoring and workflow tooling. We do not bundle a SIU UI, a claim management system, or a carrier dashboard.
Neutral and multi-vendor by design
Run two forensic stacks side-by-side, or migrate from one to another, without rebuilding the audit chain. Hashproof manifests are a portable, vendor-neutral artifact backed by the C2PA 2.x specification.
Standard-driven, not proprietary
C2PA 2.x is a Linux Foundation specification with 500+ member companies. Manifests issued by Hashproof verify against the official C2PA conformance suite and federate with peer registrars over mutual TLS. The standard is the moat.
Compliance fit
The same provenance layer satisfies multiple converging regulatory obligations. Reports are generated directly from the signed corpus.
EU AI Act Article 50
Article 50 requires synthetic-content disclosure obligations to be reportable. Hashproof generates auditor-ready reports directly from your signed corpus, scoped to a date range, with manifest-level evidence URLs. Enforcement begins August 2026.
NAIC Model Law 880
The NAIC Insurance Antifraud Model Act expects carriers to maintain documentary evidence of suspected fraud for the life of the claim plus statutory retention. Hashproof retention windows scale to seven years on Scale and to custom durations on Enterprise.
State-level disclosure regimes
A growing list of states (California AB 2655, Tennessee ELVIS Act, others) require disclosure of AI-generated content in specific commercial contexts. The same provenance manifests serve as the underlying evidence layer.
Built for carriers, claim platforms, and forensic vendors.
Insurance deployments live on the Scale and Enterprise tiers, with EU residency, BYO-HSM, and DPA available on Enterprise. Sandbox a connection on the Free tier before you commit.