Verify
Check factual claims and receive structured verdicts, explanations, confidence, evidence strength, and cited sources through one runtime endpoint.
Send text, transcripts, audio, images, or posts to one Verify API. FactLens handles transcription, evidence retrieval, safety checks, and analysis internally, then returns structured verdict data with citations, confidence, evidence strength, and response timing.
curl https://api.factlens.pro/v1/verify \
-H "Authorization: Bearer fl_live_••••" \
-H "Content-Type: application/json" \
-d '{
"mode": "text",
"claim": "A claim to verify"
}'
import requests
response = requests.post(
"https://api.factlens.pro/v1/verify",
headers={"Authorization": "Bearer fl_live_••••"},
json={"mode": "text", "claim": "A claim to verify"},
)
print(response.json())
const response = await fetch("https://api.factlens.pro/v1/verify", {
method: "POST",
headers: {
Authorization: "Bearer fl_live_••••",
"Content-Type": "application/json"
},
body: JSON.stringify({ mode: "text", claim: "A claim to verify" })
});
console.log(await response.json());
payload := strings.NewReader(`{"mode":"text","claim":"A claim to verify"}`)
req, _ := http.NewRequest("POST", "https://api.factlens.pro/v1/verify", payload)
req.Header.Set("Authorization", "Bearer fl_live_••••")
req.Header.Set("Content-Type", "application/json")
resp, err := http.DefaultClient.Do(req)
FactLens exposes one focused runtime operation while handling transcription, evidence retrieval, analysis, and safety internally. Use REST, the SDK, or the CLI without stitching together separate provider APIs.
Check factual claims and receive structured verdicts, explanations, confidence, evidence strength, and cited sources through one runtime endpoint.
Install factlens once for a typed Node.js/TypeScript SDK and a complete command-line workflow with human and JSON output.
Give every API key its own source preferences, verdict names, colors and selection rules, plus stage-specific prompt instructions and input budgets.
Verify text, transcripts, audio, images, and posts through the same result contract so your application does not need separate service integrations.
Prioritize trusted domains and exclude blocked domains for every verification request, so you control which sources FactLens favors and avoids.
Inspect request volume, latency, usage, stage-aware failures, and redacted request details from the developer console.
One public Verify operation keeps integration predictable while FactLens handles the internal verification stages.
Submit a text claim, transcript, audio file, image, or post through POST /v1/verify.
When needed, FactLens transcribes media, retrieves current evidence, performs safety checks, and analyzes the claim internally.
Receive a verdict, explanation, citations, confidence, evidence strength, request usage, timing, and an identifiable failure stage if verification cannot complete.
Qualifying builders, researchers, educators, journalists, student projects, and public-interest teams can apply for up to $1,000 in free FactLens API credits to validate a real fact-checking integration before committing to ongoing paid usage.
The FactLens developer console gives you the operational tools expected from a modern API platform without exposing implementation noise.