> ## Documentation Index
> Fetch the complete documentation index at: https://docs.factagora.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Ingest

> Best practices for the Ingest API

## 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.

```json theme={null}
{ "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.

```bash theme={null}
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. See [Searching Ingested Content](/api-reference/ingest#searching-ingested-content) for the request format.

## 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](/api-reference/fact-checker) to verify them against live news.

```
Ingest (extract claims) → Fact Checker (verify each claim)
```