Your AI was rightwhen it said it.Is it still right?
Claims decay — versions go EOL, CVEs publish, APIs change. Reverify continuously re-verifies your systems’ claims against ground truth and attaches signed, evidence-cited challenges when the world moves on.
Claims decay.
A claim is a statement your system depends on: X is true now. It is temporal — it rots by design. Keep scrolling and watch one go bad.
{ "subject": "lodash@4.17.21", "claim": "no known vulnerabilities" }
“lodash 4.17.21 — vulnerability identified in OSV database.”
The world moves. Silently.
Versions go EOL
The runtime you pinned reaches end-of-life and stops receiving patches. Nothing alerts you — the claim just quietly turns false.
CVEs publish
A dependency that was clean at deploy time appears in the OSV database overnight. Your system keeps trusting it until someone checks.
APIs change
Library semantics drift between versions. What the docs said last quarter is not what the docs say now — and your output still cites the old truth.
Submit. Watch. Challenge.
Two endpoints, one rule: attach, never mutate. Your claims stay immutable — the evidence accumulates around them.
Submit claims
POST the statements your output depends on. Batch up to 100 — verdicts return inline within a 500ms budget, idempotent by design.
We keep checking
Six checkers route every claim to ground truth — OSV, endoflife.date, wp.org, library docs. Volatile claims every 6 hours, versioned daily, stable once.
Challenges, not silent rot
When ground truth moves, an Ed25519-signed challenge attaches to the claim — quoted evidence, source tier, retrieved-at — pushed to your webhook.
Verified against ground truth,
not other models.
Six checkers live in production. Each one watches a different slice of the world.
The closed service proposes.
The open checker disposes.
Witnesses are signed witness/v1 packets — artifact-bound by sha256, verifiable by anyone with the open-source @reverify/checker. No trust in us required.
{
"type": "reverify/witness/v1",
"id": "wit_51dz…",
"claim_id": "clm_8f2k…",
"artifact_sha256": "9c2f…",
"checks": ["signature", "artifact-hash",
"schema", "taint-path", "version-range"],
"verdict": "valid-structural",
"signature": "ed25519:3j9F…kQ=="
}$ npx @reverify/checker verify --witness wit.json --artifact plugin.zip✓ valid-structural — verified independently
Powering Living Audits at WP HealthKit.
WP HealthKit grades WordPress plugins & themes. Every grade is a bundle of claims about the world — this version is clean, this plugin is maintained, this runtime is supported — and claims rot.
So their audits don’t go stale. Reverify re-verifies every claim behind every grade, and when the world moves, a signed challenge lands and the audit updates itself. Evidence attached, never mutated.
Be tenant #2.
Reverify is live in production at api.reverify.co.uk, dogfooding with its first tenant. Join the list for tenant #2 and beyond.