Skip to content

Use caseFor AI content platforms

Check every article and report your platform publishes.

When your platform generates articles, market reports, or regulatory explainers for paying customers, one fabricated statistic or broken reference erodes trust in the whole pipeline. Lenz checks each factual statement against primary and authoritative sources or your own reference documents, and checks that cited references exist and support what’s written—returning structured results your code can gate on.

Your pipeline’s draft“Google rolled out AI Overviews to search users in the United States in May 2024. That February, Gartner predicted that traditional search engine volume would drop 50% by 2026 as users shift to AI chatbots and virtual agents. OpenAI said in October 2025 that ChatGPT had 800 million weekly active users.”

What Lenz found

Two of the three statements hold. One forecast is wrong.

FalseGartner predicted a 25% decline in traditional search engine volume by 2026.

A generation step conflates two separate Gartner forecasts. Lenz checks each statement against primary sources and returns suggested_rewrite and sources so your pipeline can revise or hold the draft before delivery.

01Example

Three statements in a generated article. One forecast is wrong.

Full verification · Checked 15 November 2026.

Open a row for the sources it used and the reasoning that weighed them.

A full verification returns the fields your code branches on — verdict, confidence, lenz_score, key_finding, suggested_rewrite, and sources — so the release decision stays in your pipeline: publish, revise, or route to an editor.

02The API

One call between generation and delivery.

An LLM and RAG hallucination detection and fact verification API for AI-generated content platforms before you publish reports and citations.

  1. 01
    Review a complete draft in one callPOST /api/v1/review (or /api/v1/review/file for .docx and .pdf) · pass escalate.max_citations and escalate.suggest_edits. Lenz extracts the claims, runs assessments, escalates disputed statements to full verification, and checks the citations.
  2. 02
    Or compose the four primitivesPOST /extract (0 credits, 1,000 calls/day), triage claims with POST /assess (~15 seconds per call, 1 credit), check references with POST /citecheck, and escalate adverse or low-confidence claims to POST /verify (~90 seconds at standard depth for 10 credits, or ~60 seconds at depth: "low" for 5 credits).
  3. 03
    Gate on outcome, issues, and suggested editsCheck outcome == "clean" (or "issues_found", "incomplete", "unchecked"). Route flagged claims in issues[] and broken references in citation_issues[] to your revision step with claims[].suggested_edits.
  4. 04
    Connect via SDK, webhook, n8n, Zapier, or MCPOfficial Python and TypeScript SDKs, HMAC-signed async webhooks, n8n and Zapier workflow steps, or the MCP server.
# pip install lenz-io
from lenz_io import Lenz

client = Lenz(api_key="lenz_...")
review = client.review_and_wait(
    text=generated_draft,
    max_verifications=5,
    max_citations=10,
    suggest_edits=True,
)

# outcome is "clean", "issues_found", "incomplete", or "unchecked"
if review.outcome != "clean":
    for item in review.issues:
        print("CLAIM:", item.claim, item.verdict)
    for cite in review.citation_issues:
        print("CITATION:", cite.finding, cite.cited_url or cite.doi)

Python SDK: pip install lenz-io. TypeScript SDK: npm install lenz-io. Also available as an n8n node, Zapier app, and MCP server. Full endpoint reference on the developer page.

03Citations and your sources

Check the references, and check against your customer’s source pack.

3 sources cited in a generated draft2 need attention
3/3
DOI not registereddoi.org/10.1038/s41591-024-09912-4
2/3
Does not supportnejm.org · 10.1056/NEJMoa2307563The 20% reduction applies to the composite primary endpoint, not death from cardiovascular causes alone.
1/3
Supportspassage attached

Citation checking

POST /citecheck resolves DOIs (Crossref, OpenAlex, PubMed, Semantic Scholar), statutory and case citations (EUR-Lex, US Code, eCFR, UK, German law, CourtListener), and public URLs, then checks whether the source passage supports the sentence.

Customer reference documents

On API version 2026-10-11, pass supplied_sources (up to 50 reference documents, 100,000 characters each, 500,000 characters total) on /review, /review/file, /verify, /verify/batch, or /citecheck so generated content is checked against your customer’s brief, dataset, or filing alongside the public record. Checks using supplied_sources stay private, bypass cache, and do not qualify for the warranty.

A guardrail filters. Lenz investigates.

In-process guardrails

Compare generated output against the prompt context at token time. Built for sub-second chat filtering, not checking whether an external statistic, date, or cited study is true.

LenzPre-publish verification

Searches independent primary sources and registries, runs an adversarial debate across multiple model vendors, and has three independent reviewers score the evidence.

Returns the verdict, score, sources, reasoning, and a suggested rewrite your pipeline can apply or route to an editor.

The open evaluation: where frontier models disagree on real-world fact-checks

FieldMeaning/assess/verify
verdictTrue, Mostly True, Mixed, Mostly False, False, or “No Public Record” on /verifyYesYes
confidenceAgreement and certainty across the reviewer panel (high, medium, low)YesYes
lenz_scoreInteger score from 1 to 10; null for “No Public Record”NoYes
key_findingThe decisive finding in one sentenceNoYes
suggested_rewriteCorrected sentence when a factual detail is wrong, guarded for token preservationNoYes
sourcesURL, title, snippet, and publication date for each cited sourceNoYes
coverageWhether the verification qualified for the warranty and its signed certificateNoYes

Warranty

Vendors disclaim accuracy. Lenz warrants the result.

A verdict can qualify when a full verification returns True or False with high panel confidence and enough independent sources behind it. Your code reads that from the coverage block.

On a paid Pro or Scale plan, every full verification that qualifies carries a contractual warranty, at no extra charge.

How the warranty works

05Pricing

Try free, no card.

Free

$0

100 assessments or 10 full verifications a month, in any combination.

Try free
Plus

$7.99/ month

500 assessments or 50 full verifications a month, in any combination.

Or $6.59 a month, billed $79 a year

Choose Plus
Pro · warranty included

$99/ month

5,000 assessments or 500 full verifications a month, in any combination. The warranty on qualifying verdicts.

Or $83 a month, billed $990 a year

Choose Pro
Scale · warranty included

$399/ month

20,000 assessments or 2,000 full verifications a month, for production volumes. The warranty on qualifying verdicts.

Or $333 a month, billed $3,990 a year

Choose Scale

Every plan includes 1,000 extractions a day, an extraction being one call however long the text.

Compare plans

06Questions

Start with /review when you have a complete generated draft and want claim triage, full verification, citation checks, and claims[].suggested_edits in one asynchronous job. Check outcome == “clean” to gate delivery, and inspect issues[] and citation_issues[] when a draft needs attention. Use /extract, /assess, /verify, and /citecheck separately when your pipeline needs custom per-claim routing thresholds.

Yes. On API version 2026-10-11, pass supplied_sources (up to 50 documents, 100,000 characters per document, 500,000 characters total) on /review, /review/file, /verify, /verify/batch, or /citecheck. Lenz checks statements and matched citations against your supplied text as well as public sources and registries. Supplied-source checks are always private, never served from cache, and excluded from the warranty.

/assess is synchronous and takes ~15 seconds per call. /verify takes ~90 seconds at standard depth (~60 seconds at depth: “low”) and supports async webhooks. /review runs asynchronously over a complete draft with polling or webhook delivery. Lenz is built for pre-publish content and report pipelines, not sub-second chat token streaming.

A RAG groundedness check measures whether an answer stayed close to a retrieved prompt chunk, and an AI content detector estimates whether prose was written by a model. Lenz checks whether the factual claims and citations in the text are supported by independent sources and registries.

When no public record settles a statement, Lenz answers “No Public Record” instead of a score. That doesn’t make the statement false.

Yes. The Lenz n8n node, Zapier app, and MCP server call the same endpoints and return the same structured fields.

Not answered here? Talk to us

Add a check before your next customer delivery.