fa_... key and returns JSON. For what FactBlocks and the TKG are, see What is Factagora?.
This page is about picking the right endpoint. For request and response details, follow the links into the API Reference.
Choosing an API
See Credits & Pricing for how usage is measured and what happens on failed requests.
Detect, then verify
Claim Detection and Fact Checker are meant to be used together. Detection takes a page of text and returns the sentences worth checking, each with anormalized_claim that resolves pronouns and references. Feed that into Fact Checker rather than the raw sentence, and the verdict has the context it needs.
This is the same pipeline the DeepVerify extension runs.
Public data or your own
By default the APIs search Factagora’s public corpus. If you want answers grounded only in your own material, Ingest puts your URLs, text, or files into a private graph, and Fact Search reads it back withsource=ingest. Collections goes further by merging many ingested documents into one corpus you can question directly.
Next steps
Quickstart
Get an API key and make your first request.
API Reference
Parameters, response fields, and language examples for every endpoint.
Credits & Pricing
How usage is measured and what each call costs.
Rate limits
Per-key limits and the headers on every response.

