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

# v0.1.17

> New chat API, TKG graph editing, and search quality fixes

<Update label="2026-07-16" description="v0.1.17: chat, TKG graph editing, fixes">
  ## Added: `POST /api/v1/chat`

  A new streaming (SSE) chat endpoint.

  * Pass `collection_id` to ground answers in a collection's knowledge (semantic chunk search with knowledge-graph fallback). Session and message history are persisted.
  * Pass `tkg_id` to ground answers in a standalone knowledge graph instead.
  * Omit both for a one-off chat with no grounding and no saved session.
  * Choose a `model`: `gpt-5-nano`, `gpt-5-mini`, or `gpt-5`.
  * Enable `use_fact_search` / `use_evidence_finder` / `use_fact_checker` to let the model autonomously call those research tools during the conversation. Each tool call is billed individually at the same credit cost as its standalone endpoint, only when actually invoked.
  * The chat request itself is currently free while pricing for this endpoint is being finalized.

  ## Added: TKG graph editing endpoints

  `POST/PATCH/DELETE /api/v1/tkgs/{tkgId}/graph/nodes` and `POST/DELETE /api/v1/tkgs/{tkgId}/graph/edges` let you manually create, rename, and delete nodes and edges on a knowledge graph that isn't attached to a collection — the same graph-editing capability collections already had, now available standalone. These endpoints are free.

  A new `PATCH /api/v1/tkgs/{tkgId}/graph/nodes/{nodeId}/annotation` endpoint lets you attach a temporal annotation (`when` + `precision`: year/quarter/month/day) to a belief node.

  ## Fixed: qa-verify entity matching

  `POST /api/v1/collections/{id}/qa-verify` no longer over-matches on brand or product-family tokens that are common across many entities in the same collection (for example, matching almost any entity just because it shares a common brand name). Matching is now more precise.

  ## Fixed: entity-connected fact limit

  Raised the internal cap on how many connected facts are considered when resolving an entity from 20 to 50. Previously, some genuinely connected facts were cut off before relevance ranking, which could make a verdict appear `unsupported` when better evidence existed.
</Update>