Build Fact-Checking Into Your Application
VeriFact API 3.3 provides a versioned REST interface for claim extraction, evidence retrieval, stance analysis, confidence scoring, citations, and review-ready reports. Developers can submit one claim, a prompt-and-answer pair, or a longer document and receive structured results for an editor, dashboard, browser extension, CMS, or internal workflow.
- Authenticated tenant and project workspaces using developer keys or OAuth/OIDC service accounts.
- Synchronous checks, batch requests, asynchronous jobs, request deduplication, idempotency keys, retries, and cursor pagination.
- Python and JavaScript client libraries backed by a generated OpenAPI 3.3 contract.
- Signed, replay-protected webhooks for job completion and integration events.
- Rate limits, project budgets, usage exports, audit exports, health checks, metrics, and structured request tracing.
Evidence, Provenance, and Human Review
The API is designed as an editorial decision aid rather than a black-box truth switch. Each result can preserve evidence URLs, retrieval timestamps, content hashes, source diversity, conflicts, confidence, and a provenance digest for later review.
- A reusable claim registry with normalized identifiers and semantic duplicate search.
- Collaborative review cases with assignments, comments, status changes, and audited decisions.
- Sandboxed evidence-provider manifests with outbound-host restrictions and provider trust policies.
- Signed verification receipts, safe key metadata, verification endpoints, and a hash-chained transparency log.
- Evidence maps that show supporting, conflicting, and independently sourced material.
Policy, Privacy, and Deployment Controls
Organizations can apply versioned policy packs by jurisdiction or editorial standard, redact personal information before processing, set retention and data-region controls, and export or delete tenant data. VeriFact supports managed, self-hosted, private, edge, and offline-oriented deployment profiles, with PostgreSQL, Redis, container, and high-availability options.
WordPress and Third-Party Integrations
VeriFact WordPress Plugin 3.3 is the reference CMS integration. It connects through server-injected credentials and exposes claim checks, review cases, evidence maps, policy packs, receipts, entitlements, and transparency controls inside WordPress. The same endpoints are available to approved developers building other plugins, applications, and editorial tools.
The VeriFact API source repository is private and access-controlled. Approved developers receive the applicable endpoint, credentials through a secure secret-delivery process, the OpenAPI contract, SDK guidance, and a conformance checklist. Raw credentials are never distributed in documentation or committed to source control.