Use caseFor B2B content agencies
Catch the wrong statute or figure before your client’s reviewer does.
Your writers turn SME interviews and source packs into FinTech whitepapers, cybersecurity reports, and regulatory explainers on agency deadlines. Lenz identifies the factual statements it can check against primary statutes, filings, and standards, and verifies that cited references exist and support what’s written before your client’s CISO, legal counsel, or compliance lead reviews the draft.
- Private by defaultstored in the EU
- Zero data retentionon Pro and Scale plans
01What you get back
Three statements in a regulatory whitepaper. One fine ceiling is wrong.
Here is a paragraph from a DORA and NIS2 compliance whitepaper, the way Lenz checks it.
Your text
“The Digital Operational Resilience Act (DORA) began to apply to EU financial entities on 17 January 2025. EU member states had until 17 October 2024 to transpose the NIS2 Directive into national law. Under NIS2, important entities face administrative fines of up to €10 million or 2% of worldwide annual turnover.”
What Lenz found
- TrueDORA applied on 17 January 202510/10 · high confidence
- TrueNIS2 transposition deadline: 17 October 202410/10 · high confidence
- FalseImportant entities face €10m or 2% fines2/10 · high confidence
The correction
€10m / 2%€7m / 1.4%
The €10 million or 2% ceiling applies to essential entities under NIS2. Important entities are subject to a minimum maximum ceiling of at least €7 million or 1.4% of worldwide annual turnover, whichever is higher.
Suggested rewriteUnder the NIS2 Directive, important entities must be subject to maximum administrative fines of at least €7 million or 1.4% of worldwide annual turnover, whichever is higher.
The sources
digital-strategy.ec.europa.euncsc.gov.iedigitalhorizon.hannessnellman.com+32 more
- Your text
Lenz reads your draft and picks out every factual statement it can check. Here it found three.
- A verdict for each fact
A verdict from True to False (or No Public Record), with a score from 1 to 10 for how strongly the sources back it. Two held up. One didn’t.
- A suggested correction
When the regulation or primary source establishes the right figure, Lenz suggests the correction and explains why. Your editor decides whether to accept it.
- The sources behind it
Every result lists the statutes, regulator releases, and sources it was checked against, so your editor and your client’s reviewer can inspect them.
A real deep check, run on 15 November 2026. Each statement opens the verification behind it.
Open the full verificationCitations
A reference that resolves can still contradict the sentence.
When a whitepaper or regulatory explainer cites an EU act, a US statute, an industry report, or a DOI, Lenz opens that source and checks whether it actually supports what the sentence claims.
The regulation exists and the EUR-Lex link opens, so nothing looks broken at a glance. Lenz reads Article 33(1) and flags that the draft swapped NIS2’s 24-hour early warning window into a GDPR citation.
Writers and AI assistants frequently paste a plausible-looking journal DOI or URL for a cloud-outage statistic. Lenz checks the registries and flags that the reference does not exist before the draft reaches the client.
02Use cases
Built for agencies writing in regulated B2B and technical verticals.
Verify AI citations and check for fake, made-up, or hallucinated references and claims in B2B agency deliverables, FinTech whitepapers, cybersecurity reports, and compliance content before publishing or sending a draft for client review.
-
FinTech & payments
Check statutory thresholds and filing figures before legal review. Whitepapers, PSD2, PSD3, and DORA explainers, and payment-infrastructure guides checked against EUR-Lex, US statutes, central-bank releases, and official filings before your client’s legal or compliance team reads the draft.
-
Cybersecurity
Check breach statistics and framework controls before the CISO marks up the copy. Threat and benchmark reports, NIST, ISO 27001, and SOC 2 explainers, and technical buyer guides checked against the cited studies and standards so every statistic and reference holds up.
-
RegTech & compliance
Check fine ceilings, deadlines, and statutory citations before handoff. NIS2, GDPR, EU AI Act, and SEC disclosure guides, regulatory briefs, and compliance playbooks checked against the enacted text so an account director can hand over the deliverable with the sources on record.
03Where you work
Check the deliverable in the tools your editors already use.
Choose where you work 3 ways to run a check
Review the draft in Word.
Upload a .docx, a PDF, or an image in the Workbench on desktop. Download the file with a Word comment from Lenz on each statement and citation that needs attention, and suggested edits written in as tracked changes you can accept or reject.
A suggested edit is not itself verified: read it alongside its sources before accepting it.
Administrative fines under NIS2
Under NIS2, important entities face administrative fines of up to €10 million or 2% of worldwide annual turnover must be subject to maximum administrative fines of at least €7 million or 1.4% of worldwide annual turnover, whichever is higher.
LenzFalse2/10
NIS2 requires important-entity fine ceilings of at least €7 million or 1.4%.
AcceptReject
Check a draft in Claude or ChatGPT.
Connect Lenz to Claude or ChatGPT with one sign-in and ask it to check a whitepaper section or regulatory explainer right in the thread.
- Extract the statementsSend the draft section; Lenz pulls out the checkable claims and citations.
- Triage with a quick checkGet a fast first read and confidence level per statement in ~15 seconds.
- Run a deep check on key linesEstablish the verdict with primary statutes, sources, and the reasoning in about a minute or two.
Check the statutes and figures in this whitepaper with Lenz.
Lenz · deep check · 3 statements
Lenz checked three statements. One fine ceiling swaps the NIS2 entity tiers:
- FalseImportant entities face at least €7M or 1.4% under NIS2, not €10M or 2%.
- True ×2DORA application date (17 Jan 2025) and NIS2 transposition deadline (17 Oct 2024).
In Google Docs, or against the client’s source pack.
Install the Google Docs add-on to review findings in a sidebar beside your text and apply suggested corrections in place, or wire an automated check step in n8n or Zapier.
When your writers work from a client’s source pack or product documentation, pass those files through the API (supplied_sources) so Lenz checks the draft against them alongside public statutes and registries.
# one command, then a sign-in
$ claude mcp add --scope user --transport http lenz https://lenz.io/mcp
# check a client whitepaper from your workspace
> check the claims and citations in drafts/nis2-dora-whitepaper.md
{
"statement": "Under NIS2, important entities face fines of up to €10M or 2%.",
"verdict": "False",
"lenz_score": 2,
"sources": ["digital-strategy.ec.europa.eu", "ncsc.gov.ie"]
}
04The record
Hand over the deliverable with its sources on record.
Every statement comes back with its own record: the claim as Lenz read it, the verdict and its score, the dated sources, and the case made for and against it before you send the deliverable to the client.
1–2min
Deep check
The record comes from a deep check. Lenz researches primary statutes and independent public sources, has models argue both sides, and returns the verdict with those sources and the reasoning, in about a minute or two per statement.
~15sec
Quick check
A panel of models returns a verdict and a confidence level in about fifteen seconds, for triaging a long whitepaper. When the deep check disagrees, rely on the deep check.
Under the NIS2 Directive, important entities can face administrative fines of up to €10 million or 2% of worldwide annual turnover.
Under the NIS2 Directive, important entities must be subject to maximum administrative fines of at least €7 million or 1.4% of worldwide annual turnover, whichever is higher.
- digital-strategy.ec.europa.euNIS2 Directive policy page
- ncsc.gov.ieNational Cyber Security Centre
- eur-lex.europa.euDirective (EU) 2022/2555, Art. 34
- +32 more
Illustration · record fields abridgedlenz.io/c/…
05Scope
What Lenz checks, and what stays with your reviewers.
Checks
The factual statements and cited references in your deliverable, against public sources and registries.
Dates, statistics, regulatory thresholds, enforcement fines, EU acts, US statutes, standards and framework references, DOIs, and public URLs—plus your client’s own source pack or product documentation when supplied through the API.
Doesn’t check
Not a substitute for your client’s legal counsel, compliance sign-off, or brand approval.
Lenz does not give legal opinions, approve financial promotions under FCA, SEC, or FINRA rules, judge tone of voice or editorial positioning, or guess whether prose was written by an AI model.
Warranty
Vendors disclaim accuracy. Lenz warrants the result.
On Pro and Scale, qualifying checks carry a contractual accuracy warranty, at no extra charge.
A deep check qualifies when it returns True or False with high panel confidence and enough independent sources behind it. Its certificate is a record you can send with the deliverable.
06Pricing
Try free, no card.
$7.99/ month
500 quick checks or 50 deep checks a month, in any combination.
Or $6.59 a month, billed $79 a year
Choose Plus$99/ month
5,000 quick checks or 500 deep checks a month, in any combination. Qualifying checks carry the accuracy warranty.
Or $83 a month, billed $990 a year
Choose Pro$399/ month
20,000 quick checks or 2,000 deep checks a month, for production volumes. Qualifying checks carry the accuracy warranty.
Or $333 a month, billed $3,990 a year
Choose ScaleYes. Upload a .docx in the Workbench on desktop and download the annotated .docx with Word comments on flagged statements and citations and suggested edits written in as tracked changes. Review any suggested edit before accepting it: a suggested edit is not itself verified.
Yes. Lenz looks up statutory citations across EUR-Lex, the US Code, the eCFR, UK legislation, German federal law, and CourtListener, resolves DOIs across Crossref, OpenAlex, PubMed, and Semantic Scholar, and reads public web links to check whether the source text supports the sentence. When a page is behind a paywall or login, Lenz marks it as needing a closer look rather than guessing.
No. Lenz catches wrong statutory thresholds, misquoted breach statistics, and broken or unsupported references before you send the draft over, so your client’s CISO, legal counsel, or compliance reviewer spends their time on positioning and judgment rather than redlining factual errors.
Yes, through the API you can supply the client’s reference documents or source pack so Lenz checks the draft against them alongside public sources. Those checks stay private and do not qualify for the warranty.
When no public record settles a statement, Lenz answers “No Public Record” instead of a score. That doesn’t make the statement false.
Every check is private by default, with account data and uploaded documents stored in the EU. On the Pro and Scale plans you can enable the zero-retention option so submitted text is never written to Lenz’s database.