Fact-checking

Why fact-checking is in the loop

Speed without checks moves embarrassment earlier. Jeenie runs fact-checking between draft and publish so shaky claims are caught while the job is still in flight — not in a Slack thread after go-live.

How it works

1. Extract claims from the draft (statistics, dates, comparative statements, etc.)
2. Gather evidence via SERP research (DataForSEO when configured)
3. Verdict each claim: supported, unsupported, or uncertain
4. Optional rewrite — Unsupported claims may be revised before publish (configurable via FACT_CHECK_REVISE)

Results appear in job metadata on Jobs.

What it guarantees

Fact-checking improves confidence — it is not legal or medical review. Treat it as editorial QA, especially for regulated topics.

Configuration (workspace admins)

Environment-level limits (set by your deployment):

• FACT_CHECK_MAX_CLAIMS — max claims extracted (default 5)
• FACT_CHECK_SERP_CLAIMS — live SERP lookups per job (default 3)
• FACT_CHECK_REVISE — set false to skip automatic rewrites

Related

• Job status
• Generate an article