Get API keyProduct / Evidence ledger
Every claim.
A traceable
path.
Follow an answer back to the record. Keep the source, the timestamp and the gaps—even when the facts change.
Follow the evidence Open your ledger The evidence chainFictional example
01 / AI answer
One company.
Three claims.
CompanyProof
Example Limited
Claim → source → time → historyInspect the connection. Not just the conclusion.
01 / From answer to source
Don’t take the
answer’s word for it.
Select a highlighted claim. See the observed value and the record behind it, or the evidence that is missing.
Illustrative registry
01Company record extract
CompanyProof Example Limited
Registration numberEXAMPLE-001
- Company status
- Active
- Registered office
- 12 Example Street,
London
The observed value matches the claim at the time of verification.
Selected claim
demo_clm_statusHow verification works 02 / The record moves forward
The past stays put.
The present moves.
A correct answer can become outdated. Move between the two observations to see exactly what stays—and what changes.
Example observations
Your evidence history29 AUG 2026 / PRESERVED 29 AUG 2026 / LATEST✓
Company status
ActiveCompany status
ActiveWhat your application receives—
Awaiting a source change
No change event
The answer is still supported by the original observation. Select 14 September to introduce a source change.
Possible next steps in your workflow
Review claimUpdate answerNotify agent
29 Aug · original check
Inspect the example event JSON
Illustrative payload, not an API schema. No webhook is sent by this demo. Monitoring and delivery depend on the source and your configuration.
{
"example": true,
"event": "claim.stale",
"proof_id": "demo_prf_01J62E8A",
"claim_id": "demo_clm_status",
"field": "company_status",
"published_value": "Active",
"current_value": "Dissolved",
"verified_at": "2026-08-29T08:42:11Z",
"changed_at": "2026-09-14T11:06:00Z",
"source": "Illustrative registry",
"source_record": "EXAMPLE-001"
}API documentation 03 / From your team to the next
The answer is short.
The record is complete.
A reviewer shouldn’t need to repeat your research. Give them the claims, available source context and history together.
Fictional example · no account requiredOpen your saved evidenceEvidence summaryCompanyProof
CompanyProof
Example Limited
United Kingdom · 29 August 2026
03claims
- 2 Supported
- 1 Unverified
Evidence gaps remain part of the record.
Know the boundaries
Evidence is time-specific +
A supported verdict describes the source at verification time. It is not a guarantee about the company.
Coverage varies by source +
Source links, documents and monitoring depend on the jurisdiction, field and connected source.
Agree retention upfront +
Contractual retention and verified deletion controls are being finalised. Agree a retention schedule during procurement.
Give the next answer
a record to stand on.
FREQUENTLY ASKED QUESTIONS
Company evidence ledger FAQs
What is a company verification evidence ledger?
It is a persistent record connecting a company claim with its verdict, observed value and supporting evidence. It lets reviewers understand what was checked and why the result was produced.
What information is stored with a verified claim?
The ledger retains the published claim, observed value, verdict, verification identifier and available source context. Retrieval time, source links and relevant events help explain the result and its history.
How is an evidence ledger different from API logs?
API logs describe request handling and technical events. An evidence ledger preserves the factual basis for a decision, including the claim, comparison value and source context needed to review that decision.
Does the ledger preserve evidence for contradicted claims?
A proof records claim-level results, including contradictions and evidence gaps. Preserving the submitted value alongside the observed value helps reviewers understand a correction without losing the original assertion.
Can a verified company claim become stale?
Yes. A company status or another supported value can change after verification. Eligible monitoring compares later evidence with the stored value and records when the original claim is no longer supported.
Does marking a claim stale erase the original verification?
No. The original result remains part of the history. A stale event describes a later change, allowing a reviewer to distinguish what was supported at publication from what is supported now.
Can I export company verification evidence?
JSON and PDF proof exports are available. Exports help move the claim, verdict and evidence context into an internal review or record-keeping workflow, subject to the data rights in your agreement.
How long is verification evidence retained?
Durable storage does not mean indefinite retention. Production retention and deletion requirements should be agreed during procurement; do not assume a specific retention period without a contractual commitment.
Review procurement requirementsHow do stale-claim webhooks work?
A configured webhook notifies your application when an eligible monitored claim changes or loses its supporting value. Verify the signature and handle repeated deliveries safely before updating a downstream decision.
Read webhook documentationDoes every saved browser result have monitoring enabled?
No. Saving a browser text proof preserves the result but does not automatically enable monitoring. Use the supported monitored-claim workflow and confirm its eligibility, credit use and delivery configuration.