Every qualifying fact check comes with a warranty.

AI vendors and fact-checking APIs disclaim accuracy in their terms. Lenz warrants the verdict. On a paid Developer or Scale plan, every verification that qualifies carries a contractual warranty — automatically, at no extra charge — and every full verification tells you in the response whether it qualified.

€10,000 per certificate, €500,000 across all Lenz certificates in any rolling 12 months.

Four steps, and you can check every one of them.

• Verify. Submit the claim through /verify, the web app or the workbench. Nothing changes about how you submit, as long as you keep the default standard depth.
• Qualify. The result carries a coverage block. If it did not qualify, the same block says why, in one word: plan, depth, verdict, quality, withdrawn, issue_failed. Verdicts that do not qualify are told so rather than left to guess.
• Publish, or send it on. A certificate is signed and given a qualified timestamp from an authority on the EU Trusted List, within minutes. Publish after the qualified timestamp lands. Cover requires the timestamp to precede what you publish or send. If you publish automatically, key on the certificate.timestamped webhook rather than verification.completed — the second fires while the qualified timestamp is still pending.
• If a court says otherwise, we pay. A court or regulator makes a finding contradicting the verdict — final once the time to appeal has passed, or appeals are exhausted — and awards damages against you on that basis. Lenz pays the damages awarded, up to the per-certificate cap.

What qualifies

Not every verdict does, and that is the point of a gate. A verdict qualifies when it is True or False — the two ends of the scale, not the three middle labels — run at standard depth on a paid Developer or Scale plan, with confidence reported as high, at least three distinct source domains, and no degradation during the run. Degradation includes a search provider failing, evidence Lenz could not check against its source, and a panelist whose score contradicted its own verdict.

Mostly True, Mixed and Mostly False are never warranted — a hedged verdict is one the evidence did not settle.

What is not covered

Stated here rather than left in the terms, because these are the cases people ask about.

• Fines and regulatory penalties. The measure is damages awarded against you in a proceeding.
• Settlements. Findings only. A settlement is not a finding, and a trigger that turned on one would be a trigger neither side could determine.
• Defence costs and consequential loss.
• Anything you published or sent to a client before the qualified timestamp. Verify, then publish or send, in that order — the qualified timestamp has to come first.
• Anything you already knew about. If you knew or should reasonably have known of circumstances likely to give rise to a claim when you ran the verification, it is outside the warranty.
• Free, Plus and complimentary plans. The warranty runs on the commercial terms that come with a paid Developer or Scale plan.

The record, and why it is not just our word

Every certificate is a document you can check without us. It carries the claim, the verdict, the score, the warnings that narrow it, the sources, and a hash over all of it. That hash is signed with a key whose private half we cannot export, then given a qualified timestamp by a third party — so the ordering the warranty turns on is not a date in our database. That third party is a Qualified Trust Service Provider under the EU's eIDAS Regulation. The signed record is also anchored to the Bitcoin blockchain as a durability backstop.

Download the record, run the checker against it, and it recomputes the hash, checks the signature against our published keys and checks the timestamp. Lenz is not in the loop. The checker is one Python file with three dependencies, and the sources on the certificate are there so you can read the evidence yourself.

Cover applies only to the Lenz customer who requested the verification.

Who this is for

Teams whose output creates exposure to someone else: publishers and newsrooms, regulated marketing and financial promotions, health and pharma copy, political-ad compliance, and the compliance and due-diligence work that reaches a client as a memo rather than an article. Cover applies to what you send a client as much as to what you publish.