Lenz is an AI fact-checking API for products that cannot afford to hallucinate. It extracts verifiable claims from any text, then checks each one: searching independent sources, running multi-model debate, and routing through a review panel β returning a scored verdict with every source, argument, and step visible. Most AI tools give you one model's best guess from memory. Lenz ensures no single model's blind spots drive the conclusion. Available as API and MCP. Try it free at lenz.io/ph
Independent, multi-model fact-checking API for AI workflows
Lenz is an AI fact-checking API for products that cannot afford to hallucinate. It extracts verifiable claims from any text, then checks each one: searching independent sources, running multi-model debate, and routing through a review panel β returning a scored verdict with every source, argument, and step visible. Most AI tools give you one model's best guess from memory. Lenz ensures no single model's blind spots drive the conclusion. Available as API and MCP. Try it free at lenz.io/ph
Kosta here, co-founder of Lenz. Many businesses ship AI-generated content to their customers. Some of those use cases could benefit from factual verification of that AI output. That's why we built Lenz, packaged it as an API/SDK, and made it available across multiple platforms (n8n, Zapier, MCP, CLI), so people can easily integrate it into their workflows. Lenz verdicts come with a full audit trail - sources, citations, reasoning, confidence.Β
How Lenz is different than just asking a model:
(1) separate evidence gathering step (with source ratings) that doesn't rely on the model's memory or retrieval capabilities
(2) multi-vendor, multi-model approach to address single-model biases
(3) multi-round adversarial debate to crystallize the strongest for/against arguments
(4) multi-model jury reviewing the evidence and the debates across multiple axes
Key API primitives: /extract - extracts the factual claims from a text; /assess - quick assessment of a claim; /verify - the full deep claim verification; /ask - follow-up post-verification questions.
We measured the level of disagreement between the individual frontier models: on 23% of real-world claims, they disagree significantly, which sets the floor of the error Lenz is built to address.
Lenz
Kosta here, co-founder of Lenz. Many businesses ship AI-generated content to their customers. Some of those use cases could benefit from factual verification of that AI output. That's why we built Lenz, packaged it as an API/SDK, and made it available across multiple platforms (n8n, Zapier, MCP, CLI), so people can easily integrate it into their workflows. Lenz verdicts come with a full audit trail - sources, citations, reasoning, confidence.Β
How Lenz is different than just asking a model:
(1) separate evidence gathering step (with source ratings) that doesn't rely on the model's memory or retrieval capabilities
(2) multi-vendor, multi-model approach to address single-model biases
(3) multi-round adversarial debate to crystallize the strongest for/against arguments
(4) multi-model jury reviewing the evidence and the debates across multiple axes
Key API primitives: /extract - extracts the factual claims from a text; /assess - quick assessment of a claim; /verify - the full deep claim verification; /ask - follow-up post-verification questions.
We measured the level of disagreement between the individual frontier models: on 23% of real-world claims, they disagree significantly, which sets the floor of the error Lenz is built to address.
To try a Lenz verification via the UI: lenz.io/verify
More about the LLM disagreement research: lenz.io/research/llm-disagreement
To integrate Lenz: lenz.io/integrations
GitHub: github.com/lenzhq
Hope you find this useful. Let me know either way :)