Claim evidence
that holds up in court.
Verdict seals disputed claim evidence — photos, reports, telematics exports — to the public Sigstore Rekor transparency log. The resulting record is independently verifiable by any court, opposing counsel, or reinsurer without trusting Verdict Systems or the carrier.
Not document storage. Not a vault. A cryptographic anchor: proof that a record existed, unchanged, at a specific moment in time — the exact standard FRE 901 requires.
Digital evidence is easy to fake.
Hard to prove it wasn’t.
The Coalition Against Insurance Fraud estimates fraud costs U.S. insurers over $308B annually. A material share involves manipulated digital evidence — photos, timestamps, geolocation records — that carriers cannot reliably authenticate with current tooling.
Federal Rule of Evidence 901 requires that digital evidence be authenticated before admission. Courts are increasingly demanding hash-verified, timestamped provenance for photos, videos, and sensor data submitted in disputed claims. Screenshots and unverified files are failing.
Post-incident evidence is most defensible when sealed closest to the event. Adjusters, policyholders, and defense counsel who seal at first-report create a cryptographic anchor that holds through litigation — even years later.
Seal a claim record.
Verify the anchor yourself.
The same production code path your claims pipeline would use. Paste any structured claim record — adjuster notes, damage description, incident summary — and get a real Sigstore Rekor anchor with a clickable verification URL. No account. No install. Under five seconds.
A replay of the real /live-seal flow, ending on a genuine Sigstore Rekor entry minted 2026-05-15. Run it yourself →
Every line of business.
One evidence standard.
Property claims
Seal adjuster photos, drone footage, and damage assessments at first-report. Sigstore anchoring produces a timestamp-verifiable record that withstands defense challenge — no reliance on metadata that can be stripped or forged.
Auto & collision
Scene photos, telematics exports, and repair estimates sealed immediately post-accident. Subrogation teams get authenticated records that hold up against opposing counsel without expert witness testimony on authenticity.
Workers comp
Medical records, incident reports, and surveillance evidence with a tamper-evident chain of custody from day one. Reduces the he-said-she-said surface that inflates settlement values in soft-tissue and repetitive stress claims.
Fraud detection
When a sealed record's hash doesn't match the file presented at litigation, the tamper is provable — not argued. Verdict gives SIU teams a cryptographic baseline that turns fraud investigation into a binary verification.
Insurance defense counsel
Defense firms representing carriers need authenticated records that survive Daubert challenges and FRE 901 scrutiny. A Verdict-sealed evidence record + Rekor entry is the same standard courts are already applying to blockchain-anchored evidence.
Reinsurance & subrogation
Cross-carrier subrogation depends on both parties trusting the underlying evidence. A public Sigstore anchor creates a neutral, third-party verifiable record — neither carrier has to trust the other's document management system.
Four steps.
No vendor trust required.
Hash
SHA-256 of the evidence file or structured claim record is computed client-side. The file never leaves your infrastructure.
Sign
An ephemeral ECDSA P-256 signing key attests to the hash and a structured SER metadata envelope — business, event time, severity tier.
Anchor
The signed record is submitted to the public Sigstore Rekor transparency log. A logIndex, UUID, and Merkle inclusion proof are returned.
Verify
Anyone — courts, opposing counsel, reinsurers — can verify the hash and timestamp against the public log without trusting Verdict Systems or the carrier.
The evidence file never leaves carrier infrastructure. Verdict receives only the SHA-256 hash and structured metadata. The public Sigstore Rekor log is operated by the Linux Foundation — not Verdict Systems. Full technical specification →
Drop into your claims pipeline.
Three paths to production.
verdict_create_evidence_recordDrop into any AI-assisted claims workflow via the Model Context Protocol. Claude, GPT-4o, Gemini — one tool call seals any structured claim record.
POST /api/mcpJSON-RPC 2.0 endpoint. 300 req/min, 256KB payload cap. Integrates directly into claims management systems, FNOL platforms, and adjuster mobile apps.
@verdict-systems/mcpNode.js SDK for server-side sealing. Batch evidence records, automate at FNOL trigger, embed in existing claims pipeline.
# Install via npm
npm install @verdict-systems/mcp
# Or use the live MCP endpoint directly
claude mcp add verdict --transport http --url https://verdict.systems/api/mcp
# One tool call seals a claim record and returns a Rekor anchor
verdict_create_evidence_record({
"content": "Adjuster report: 2026-05-24. Property at 1234 Oak St shows roof damage consistent with May 22 hail event. Photos attached. Damage estimate: $18,400.",
"business_name": "Progressive Insurance",
"event_time": "2026-05-24T14:30:00Z",
"severity": "high"
})Verdict Systems is an independent company. We are not an endorsed vendor or panel partner of any carrier listed or referenced on this page. The Sigstore Rekor transparency log is operated by the Linux Foundation — not Verdict Systems. The technical claims on this page — FRE 901 defensibility, Merkle inclusion proofs, SHA-256 integrity — are grounded in published standards and independently verifiable at verdict.systems/live-seal. Three USPTO patent applications are filed. Nothing here constitutes legal advice. If you are a carrier, SIU lead, or defense counsel evaluating Verdict for production use, we want to talk. Reach the founder directly →
The claim happened.
Prove it was never touched.
Carriers, SIU teams, and insurance defense counsel evaluating tamper-proof evidence infrastructure — start with the live demo, then talk to the founder.