Open-Source Fact-Checking Tool: Adding an Independent Verification Trust Layer to AI Agents

Open-source tool adds independent fact-checking to AI Agents via dual Truth Score and Confidence Score mechanism.
This article introduces recommend-agentic-trust-layer, an open-source project that tackles the "false confidence" problem in large language model outputs. Its core design separates Truth Score from Confidence Score: the former verifies claims by fetching real-time external sources, while the latter honestly reflects how reliable the fact-check itself is. The tool also supports cross-verification of internal document consistency — especially valuable for enterprise documents beyond the reach of public web search — and achieved zero false positives in a demo with four deliberately planted errors. It supports browser-based use, MCP integration into Agent workflows, and batch knowledge-base verification.
The AI "95% Confident" Problem
Ask a large language model "how sure are you?" and it will almost always answer "95%" — regardless of whether the answer is right or wrong. In casual conversation, this may not matter much. But when an AI Agent is about to take action based on that "information" — writing it into a report, storing it in a knowledge base, or even making decisions from it — the problem becomes serious.
An open-source project from the Reddit developer community addresses exactly this pain point. Its core idea is simple yet critical: before an AI asserts something, verify whether that claim actually holds up. The project is called recommend-agentic-trust-layer and is fully open-source under the MIT license.

Why Model-Output "Confidence" Can't Be Trusted
A large model's confidence output is fundamentally a product of probability distributions — not a genuine judgment about factual truth. It can express high confidence in a completely wrong statement because, statistically speaking within its training corpus, the assertion "looks plausible." Once an Agent enters an automated pipeline, this false certainty gets amplified layer by layer, ultimately leading to cascading decisions built on faulty premises.
Dual-Score Mechanism: Completely Separating Truth from Confidence
The most noteworthy design of this fact-checking tool is its complete separation of two metrics that are typically conflated:
Truth Score
Measures whether a claim is actually true. Crucially, the tool doesn't "recall" an answer from the model's memory — it fetches real sources in real time for verification. This is essential: it simultaneously sidesteps both model hallucinations and the risk of stale training data.
Confidence Score
Measures how much you should trust the fact-checking result itself. When supporting sources are scarce, or when different sources contradict each other, this score drops accordingly. In other words, it honestly tells you "how certain this judgment is" rather than always outputting an inflated number.
Beyond the two scores, the tool also returns cited sources and a plain-language explanation of "why," making the entire fact-checking process transparent and traceable — not a black-box verdict.
Beyond the Public Web: Verifying Internal Document Consistency
The developers note that the most valuable capability for their team isn't checking against public internet information — it's verifying whether a document's claims are consistent with the sources it references.
This capability is especially critical for enterprise use cases. Information like internal policies, metric definitions, and database schema documentation simply has no "opinions" available on the public web. Traditional web-based fact-checking fails entirely here, while this tool can cross-verify against the sources a document itself cites.
Demo Results: Precise Detection with Zero False Positives
To demonstrate this capability, the developers constructed a scenario where they deliberately planted four errors in a fictional financial policy document package, while keeping one unmodified control document intact. The result: the tool accurately caught all four errors while generating zero false positives on the clean control document.
This "catches what's wrong, doesn't flag what's right" performance is exactly the reliability baseline needed for serious use cases like internal compliance, financial auditing, and legal review.
Three Deployment Modes — Up and Running in Minutes
The project is quite fully engineered, offering three usage modes to fit different scenarios:
- Standalone browser execution: No complex environment setup — verify individual claims directly in the browser.
- Integration as an MCP tool into Agents: Via the Model Context Protocol, embed fact-checking capabilities directly into AI Agent workflows, so Agents automatically run a fact check before taking action.
- Batch verification across entire knowledge bases: Bulk-validate consistency and truthfulness across large document collections.
The developers say that after obtaining two free API keys, you can get it running locally within minutes.
Real Implications for the AI Agent Ecosystem
As AI Agents evolve from "able to chat" to "able to act," trustworthiness is shifting from an academic topic to an engineering necessity. An automated Agent without an external verification mechanism will let every erroneous claim settle into knowledge bases, get written into reports, and trigger downstream actions — creating technical debt that's nearly impossible to trace.
The positioning of this "Trust Layer" is clear: it doesn't try to make the model itself smarter. Instead, it establishes an independent verification checkpoint between the model and the real world. The separation of truth and confidence scores, along with the ability to check internal document consistency, reflects a deep understanding of real enterprise scenarios.
For developers building Agent applications, this kind of fact-checking tool is worth considering in your technology stack. As an open-source project, it also welcomes community feedback and contributions — the developers openly note in their post that a GitHub star helps more than you might think.
A note of caution: the information in this article comes from a single Reddit developer post, and the demo results and real-world performance await further independent verification. Interested readers are encouraged to visit the project repository and evaluate it firsthand.
Related articles

Catalyst: A Vision for an Enzyme-Like Testing Framework for AI Agents
A developer shared Catalyst on Reddit, an Enzyme-inspired framework for AI Agents, exploring why agents need observable, testable dev tools and the design philosophy behind them.

The Real Capability of AI Coding Agents: Best Models Complete Only 35% of Feature Development Tasks
The 'Agents on Rails' benchmark finds top AI models complete only 35% of feature development tasks. What this means for coding agents and developer teams.

How to Prevent Duplicate Refunds After an AI Agent Crashes: CellaFlow's Durable Execution Approach
How can AI agents avoid duplicate refunds after a crash without deadlocking workflows? CellaFlow uses durable execution, shared work identity, leases, and fencing to solve safety and liveness in multi-agent systems.