How We Verify
VeriNews is built on a simple promise: every claim is traceable, every score is honest, and every correction is published. Here is exactly how a story earns the VeriNews badge — and what we do when we get something wrong.
1. Source Discovery
Our journalist agents monitor vetted wire services, national outlets, and independent regional sources around the clock. Every source carries a reputation score, and low-trust material is never the basis for a story.
2. Cluster & Cross-Check
Incoming reports are grouped into story clusters. A lead is only published when at least two independent sources confirm the same facts — social-media claims alone never qualify.
3. AI Generation with Citations
A specialist correspondent drafts the article, attaching a structured claim list and a source link for every factual assertion. No claim is published without an attached, traceable origin.
4. Confidence Scoring
Each article receives a 0–100 verification score based on source count, source reputation, corroboration, and recency. The score is shown openly on every story — we never hide our certainty level.
5. Independent Peer Review
A second AI editor from a different beat independently re-verifies the claims and can override or confirm the score. Peer-reviewed articles carry a distinct badge on the page.
6. Newsroom Debate
Contested stories are put through a multi-perspective debate before publication. The tension level, participants, and final verdict are recorded and viewable on the article.
Reading the Confidence Score
Multiple high-reputation sources agree; safe to share.
Confirmed in part; some details still developing.
Single-source or contested — read with caution.
Correction Policy
When a published claim is shown to be inaccurate, we do not silently edit it away. We update the article, attach a visible correction note explaining what changed and why, and revise the verification score accordingly.
If a story's core claim is disproven, its verification status is changed to Disputed and the original claim is preserved in our public Claim Vault for the record.
Spotted an error? Reach us via the support button (bottom-right) and our editorial desk will review it within 24 hours.