Catch AI in a Lie in 5 Minutes
Three simple tricks to find errors in AI responses - works today, no payment needed
- 1.Open the AI response you want to check. Highlight three to four main claims in it: numbers, dates, names, facts. Write them down separately.
Check actual factual claims: 「The capital of France is Paris」, 「GDP grew 2.1% in Q2 2026」, 「The hydrogen bomb was created in 1952」 - not opinions.
Text editor or notepad ↗ - 2.For each claim, open FactOrFake (checkthisfact.com) in your browser. Type one claim from the AI response into the chat box and press Enter.
FactOrFake is a free donation-based tool. It searches in real-time and gives an answer within 30 seconds. No registration required.
FactOrFake ↗PromptVerify if this is true: [claim from AI response]
What this prompt doesReplace [claim from AI response] with one of your highlighted statements. For example: 「Verify if this is true: Brazil's population exceeds 220 million people」. FactOrFake will check this against authoritative sources and give you a rating (true, false, or unclear). - 3.Record the FactOrFake result for each claim. If it got a TRUE rating - good. If FALSE or MIXED - you found an error in the AI response.
Look for clear errors, not perfection. A MIXED rating usually means the AI oversimplified or distorted a complex fact.
FactOrFake ↗ - 4.Repeat steps 2-3 for the remaining claims (3-4 checks total). This will take 2-3 minutes.
You don't need to check the entire response. Focus on the most important and disputed claims - the ones the whole idea rests on.
FactOrFake ↗ - 5.If the AI was wrong in two out of four checks - that's a red flag. The result is unreliable. Trust only facts you've confirmed yourself from authoritative sources.
Research shows: when AI makes an error in one place, it often makes errors elsewhere too. This is not coincidence - it's a pattern.
- freeFactOrFakeCompletely free service, runs on donations; no limits on checks per day.
- freeEntire recipeAll tools in this recipe are free, no credit card needed.
Why today
AI services change fast - interfaces and free limits may differ from what's described.