Search across everything the company knows

The scenario

The answer exists. It is in a design doc, or a thread, or a deck from last quarter, and the person who knows which is on leave. Keyword search fails here because the document does not use your words. You are asking “why do we bill on ingest?” and the doc says “retention-time accounting”.

Step 1 — Put the sources in one space

for path in ["rfcs/", "decisions/", "postmortems/"]:
    for f in Path(path).glob("*.md"):
        client.upload_file(space_id="company", file=str(f), tags=[path.strip("/")])

Tag by source so a later question can be narrowed without a second space.

Step 2 — Ask, in your own words

print(client.reason(
    space_id="company",
    query="Why do we bill on ingest rather than on storage?",
))

Extraction stores meaning, not just tokens, so a question phrased in the words you actually have finds a document written in the words you do not.

Step 3 — Show where it came from

res = client.retrieve_receipt(
    space_id="company",
    query="billing model rationale",
    receipt_detail="full",
    prefer_observations=False,  # the facts carry the file; a note does not
)
for row in res.memories:
    if row.get("document_id"):
        print(row["content"][:100], "→ document", row["document_id"])

A default retrieve often answers with a note — a synthesis across several facts, and possibly several documents — whose document_id is null. Asking for the facts underneath is what gets you a file per answer. For internal search this matters more than it looks. An answer with no source is a rumour, and people are right not to act on it.

Evals

Collect ten questions your team asked in Slack that were answered by a link.
Ask all ten and score against the linked document.
Deliberately ask one using vocabulary that appears nowhere in the corpus. A semantic system should still find it; if it does not, the source is missing rather than the search being bad.
Check document_id resolves for every fact you would act on.

Guardrails

Access control is per space, not per document. Everything you upload into one space is readable by everyone with access to it. Do not mix a public handbook with board material and rely on the question not being asked — use separate spaces.

Stale beats missing, but only just. An archived RFC answers as confidently as a current one. Tag by status and filter, or supersede explicitly.
reason costs more than retrieve. Use retrieve where the user can read the results themselves, and reason where they need them synthesised.
Don’t ingest everything. A corpus of drafts, duplicates and superseded versions produces confident contradictions; curate at the folder level.

Built from

Both are complete, runnable scripts: document_qa.py, memory_basics.py.

Getting Started

For Agents

Anona CLI

API Essentials

Memory (data plane)

LLM Proxy (drop-in)

Account (control plane)

SDKs & MCP

Integrations

Guides

Use Cases

Legal

Changelog

Search across everything the company knows

The scenario

Step 1 — Put the sources in one space

Step 2 — Ask, in your own words

Step 3 — Show where it came from

Evals

Guardrails

Built from

​The scenario

​Step 1 — Put the sources in one space

​Step 2 — Ask, in your own words

​Step 3 — Show where it came from

​Evals

​Guardrails

​Built from

The scenario

Step 1 — Put the sources in one space

Step 2 — Ask, in your own words

Step 3 — Show where it came from

Evals

Guardrails

Built from