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

# 2026-06

> Factagora API releases in 2026-06 (v0.1.2 – v0.1.6)

<Update label="v0.1.6" description="2026-06-29 · Collections API">
  ## New: Collections API

  Build a **per-brand private knowledge graph** by ingesting multiple URLs into one unified TKG (Temporal Knowledge Graph), then query it with grounded answers and Q\&A verification.

  ### How it works

  1. **Create** a collection for a brand (e.g. Hyundai UK)
  2. **Ingest** URLs: each page is extracted into claims, predictions, and causal edges that accumulate in one unified TKG
  3. **Ask questions** grounded only in that corpus (`/answer`)
  4. **Verify** existing Q\&A pairs against the knowledge graph (`/qa-verify`)

  ### New endpoints

  | Method   | Path                                          | Description                               |
  | -------- | --------------------------------------------- | ----------------------------------------- |
  | `POST`   | `/api/v1/collections`                         | Create a collection                       |
  | `GET`    | `/api/v1/collections`                         | List your collections                     |
  | `GET`    | `/api/v1/collections/{id}`                    | Get collection + ingested URL list        |
  | `DELETE` | `/api/v1/collections/{id}`                    | Delete a collection and all its data      |
  | `POST`   | `/api/v1/collections/{id}/ingest`             | Ingest a single URL (synchronous)         |
  | `DELETE` | `/api/v1/collections/{id}/sources/{sourceId}` | Remove a source URL from the collection   |
  | `GET`    | `/api/v1/collections/{id}/ingest-status`      | Poll ingestion progress                   |
  | `GET`    | `/api/v1/collections/{id}/graph`              | Get the unified knowledge graph           |
  | `POST`   | `/api/v1/collections/{id}/answer`             | Ask a question grounded in the collection |
  | `POST`   | `/api/v1/collections/{id}/qa-verify`          | Verify existing Q\&A pairs                |

  ### Key behaviors

  * **Synchronous ingestion**: `POST /ingest` processes URLs and returns results per URL including `claims_count` and `predictions_count`. Each URL takes 10–30 seconds.
  * **Unified TKG**: all ingested URLs share one knowledge graph per collection. Same-title entities are merged automatically.
  * **Semantic search**: `/answer` and `/qa-verify` use pgvector to retrieve the most relevant chunks before generating answers, improving accuracy over naive RAG.
  * **Grounded flag**: if the collection does not contain enough information to answer, `grounded: false` is returned instead of hallucinating.
  * **Tenant isolation**: collections are scoped to personal access tokens. A master key cannot access collection endpoints.

  ### Q\&A verification verdicts

  | Verdict       | Meaning                                                               |
  | ------------- | --------------------------------------------------------------------- |
  | `correct`     | Answer is supported by the knowledge graph                            |
  | `incorrect`   | Answer contradicts the knowledge, so a `correction` field is provided |
  | `unsupported` | Not enough information in the collection to verify                    |
</Update>

<Update label="v0.1.5" description="2026-06-23 · Unified source parameter">
  ## Changed: Unified `source` parameter across Evidence Finder, Fact Checker, and Fact Search

  `POST /api/v1/evidence-finder`, `POST /api/v1/fact-checker`, and `GET /api/v1/fact-search` now share a consistent `source` parameter for controlling which data sources are used.

  ### `source` parameter

  | Value     | Behavior                                                                                   |
  | --------- | ------------------------------------------------------------------------------------------ |
  | `default` | Public news sources only. This is the default, so there is no change to existing behavior. |
  | `ingest`  | Personal ingested knowledge base only. Requires a personal access token.                   |
  | `all`     | News + personal ingested knowledge base combined. Requires a personal access token.        |

  **Affected endpoints:**

  | Endpoint                       | Parameter | Default   |
  | ------------------------------ | --------- | --------- |
  | `GET /api/v1/fact-search`      | `source`  | `default` |
  | `POST /api/v1/evidence-finder` | `source`  | `default` |
  | `POST /api/v1/fact-checker`    | `source`  | `default` |

  **Backward compatibility:** `fact-search` previously accepted `source=news`. This value continues to work as an alias for `source=default`.
</Update>

<Update label="v0.1.4" description="2026-06-18 · Ingest API">
  ## New: Ingest API

  Two new endpoints that let you extract structured knowledge from any content source and store it in your personal Temporal Knowledge Graph.

  ### POST /api/v1/ingest

  Ingest a URL or raw text. Automatically extracts:

  * **Claims**: falsifiable factual statements
  * **Predictions**: future-oriented statements with measurable outcomes
  * **Causal edges**: relationships between claims and predictions (CAUSES, SUPPORTS, CONTRADICTS, etc.)
  * **Vector chunks**: semantic search index for the full content

  ### POST /api/v1/ingest/file

  Upload a PDF, Markdown, or TXT file directly for ingestion.

  ### GET /api/v1/fact-search?source=ingest

  Search your personal ingested knowledge graph. Returns chunks, claims, and predictions matching your query. Requires a personal access token, so only your own content is returned.
</Update>

<Update label="v0.1.3" description="2026-06-08 · Bug fixes and improvements">
  ## Bug Fixes and Improvements

  This release includes minor bug fixes and internal improvements across the API.
</Update>

<Update label="v0.1.2" description="2026-06-05 · Fact Search Rename">
  ## Fact Search Rename

  Renamed the News Search endpoint to Fact Search to better reflect the scope of the API.

  ### Changed

  * `GET /api/v1/news/search` has been renamed to `GET /api/v1/fact-search`

  **Migration:** Update any hardcoded endpoint paths from `/api/v1/news/search` to `/api/v1/fact-search`. Query parameters and response schema are unchanged.
</Update>