Current Production Contract
The deployed VeriFact service reports version 3.5.0 and exposes its stable contract under /api/v1. FastAPI supplies typed request validation and an OpenAPI description; VeriFact adds tenant isolation, authenticated scopes, request and trace identifiers, lifecycle headers, audit records, and evidence-focused response models.
Applications can extract claims from longer content, check one claim, submit a batch, create a durable asynchronous job, maintain project workspaces, search verification history, export reports, and render the compact inline citations returned with a completed review.
Developer Features in 3.5.0
- Scoped, hashed developer keys plus optional OAuth/OIDC service-account bearer tokens when a production identity provider is configured.
- Idempotency keys, request deduplication, batch checks, durable jobs, retry controls, cursor-based history, usage reporting, budgets, and explicit rate-limit metadata.
- Allowlisted HTTPS completion webhooks with body signatures, timestamps, unique event identifiers, retry attempts, and delivery audits.
- A tenant-scoped claim registry, semantic duplicate search, collaborative review cases, versioned policy packs, evidence maps, and integration conformance checks.
- Signed verification receipts, verification endpoints, safe public key metadata, provenance hashes, conflict indicators, and a hash-chained transparency log.
- Subscription, license activation, site installation, entitlement, billing-portal, and customer-usage endpoints for approved commercial deployments.
Evidence and Provenance
VeriFact is not a black-box truth switch. A result records the claims checked, selected providers, linked evidence, confidence, retrieval context, policy and model versions, redaction state, data region, and a provenance digest. Provider trust tiers, freshness limits, HTTPS requirements, source conflicts, and circuit-breaker status help applications explain why a claim is supported, refuted, disputed, outdated, or still lacks enough evidence.
The public service currently reports Wikipedia as its active evidence provider. Additional primary-source or private-provider integrations require their own approved configuration and should not be represented as active until they pass health and conformance checks.
Privacy, Reliability, and Deployment
Requests support consent metadata, default personal-information redaction, content-hash-only storage when consent is absent, retention controls, tenant export and confirmed deletion, and data-region metadata. Operational endpoints include health, readiness, metrics, request traces, provider-circuit status, audit exports, and deployment capability reporting.
The codebase includes container, high-availability, Kubernetes, load-test, SLO, and disaster-recovery guidance. Those artifacts are deployment tools—not a claim that every installation is automatically multi-region. Operators must still configure production DNS/TLS, Vault-backed secrets, identity providers, databases, Redis, monitoring, backups, evidence providers, and recovery exercises.
Integrate WordPress or a Standalone Application
WordPress Plugin 3.5.0 is the reference CMS client. The Standalone Blog 1.0.0 demonstrates the same reader experience without WordPress: normal prose, sentence-level source links, accessible tooltips, article-level status, and evidence cards. Every production client should call VeriFact from a trusted server-side component and keep licenses, API keys, and bearer tokens out of browser code.
The API repository and production credentials are access-controlled. Approved developers receive the applicable endpoint, scoped credentials through a secure secret-delivery process, OpenAPI guidance, lifecycle documentation, webhook verification instructions, and a conformance checklist.