Skip to content

Docs

Documentation

Every answer is a set of cited, dated items, or a typed abstention that says why there is none.

Start here

01Make a first callCreate a key, send one question with curl, and read the answer.02Read a responseThe envelope part by part: items, negative results, and abstentions.03Connect an agentInstall the MCP server, or hand your agent the skill file.

Capabilities

Each route returns stored, cited facts. The same routes are MCP tools.

POST /v1/askA question in plain words, answered from cited items by the deterministic grammar and templates, or a typed abstention. With Accept text/event-stream the plan streams first.
POST /v1/facts:fetchTyped facts for entities and fields, current or as of a (valid, known) pair.
POST /v1/searchEntities whose current facts match a structured filter or free text over source passages, a page at a time in entity order, with their items; the total when asked, capped at 10000.
POST /v1/entities:resolveNames and identifiers to entities, with ranked, explained candidates.
POST /v1/entities:enrichThe bundle of an entity's kind: each part's facts, fetched together from one snapshot, and each part ok or missing.
POST /v1/compareWhat changed between an earlier Fetch or Ask response of this tenant and now, with the cause of each change.
GET /v1/changesTyped change events after a cursor, in commit order.
POST /v1/field-requestsAsk for a field; a request the catalog already answers returns the matched field and builds nothing, and any other is queued for people to build, with a status you can track. Needs the write_requests scope.