Skip to main content

​
Use URLs for public articles

The fastest way to ingest is to pass a URL directly. The API fetches and parses the content automatically using Mozilla Readability. 
{ "url": "https://www.reuters.com/article/..." }

​
Use the file endpoint for internal documents

For PDFs, reports, or markdown documents, use the /api/v1/ingest/file endpoint. Supports PDF, Markdown, and TXT files. 
curl -X POST "https://api.factagora.com/api/v1/ingest/file" \
  -H "Authorization: Bearer fag_your_api_key" \
  -F "file=@quarterly-report.pdf" \
  -F "visibility=private"

​
Keep private data private

Ingested content defaults to private. Only set visibility=public if the content is already publicly available. Private content is only searchable by the token owner.

​
Search your knowledge graph after ingesting

After ingesting, use fact-search with source=ingest to semantically search across your knowledge graph — chunks, claims, and predictions are all searchable. 
curl "https://api.factagora.com/api/v1/fact-search?q=your+query&source=ingest" \
  -H "Authorization: Bearer fag_your_api_key"

​
Use the ingest_source_id to trace back

The ingest_source_id in the response links every extracted claim and prediction back to its source document. Store it if you need provenance tracking.

​
Combine with Fact Checker

After ingesting claims, pass them to Fact Checker to verify them against live news. 
Ingest (extract claims) → Fact Checker (verify each claim)