Skip to content

For teams that publish what their AI writes

Every qualifying fact check comes with a warranty.

AI product vendors disclaim accuracy in their terms. Lenz warrants the verdict.

On a paid Pro 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.

See plans Questions about the terms
A real warranty certificateTerms v1

The Great Wall of China is visible from the Moon with the naked eye.

verdict
False · 1/10
confidence
9.7/10
sources
29, from 26 domains
cover
€10,000 per certificate
certificate
fd7dcc7f…566f6deb
issued
qualified timestamp
Namirial,
OpenTimestamps
Bitcoin attestation
record hash
3f45d7b2…3e7f1163
Warranted verdictSee the certificate

01What Lenz is on the hook for

Lenz pays when all of these hold.

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

  1. You published a warranted statement, or sent it to someone outside your organisation, after its qualified timestamp.

  2. A court or regulator later made a finding on the warranted statement that contradicted the verdict, once the time to appeal has passed or appeals are exhausted.

  3. Damages were awarded against you on that basis.

  4. When you verified, you had no reason to expect a proceeding over it.

  5. The proceeding began within 12 months of publication, and you told Lenz at support@lenz.io within 30 days of being served.

Fines, penalties, settlements and defence costs are not part of the warranty. Full conditions in the terms

02How it works

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

  1. 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 and leave certificates on for your account (an account can turn them off on the API credentials page).

  2. Qualify

    A verdict qualifies when it is a clear True or False from a standard-depth check on a paid Pro or Scale plan, and the analysis met Lenz’s quality bar. One that does not qualify is told so, with the reason, and carries no certificate. See the exact fields.

  3. 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.

  4. 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.

03The gate

What qualifies.

A verdict qualifies when it is True or False, run at standard depth on a paid Pro or Scale plan, with high confidence, at least three distinct source domains, and no degradation during the run.

Not every verdict does, and that is the point of a gate. Mostly True, Mixed and Mostly False are never warranted: a hedged verdict is one the evidence did not settle. A “No Public Record” answer is never warranted either: it carries no score for the warranty to stand behind. Degradation includes a search provider failing, evidence Lenz could not check against its source, and a panelist whose score contradicted its own verdict.

04The limits

What the warranty does not pay.

The warranty pays the damages a court or regulator awards against you on a contradicted verdict. These cases fall outside it.

  • 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 Pro or Scale plan.

05The record

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.

The certificate and the coverage block, field by field

06Fit

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. The warranty applies to what you send a client as much as to what you publish.