Receipts and audit

Every time an agent reads memory, Niadra leaves a receipt: which source read, about whom, for what purpose, at which verification level, under which policy version, which items were delivered and how many were withheld. The receipt is written before the answer goes out, it is never optional, and receipts are chained by SHA-256 so nobody can change the past without breaking the chain. It is how you answer, months later, why an agent said what it said.

What leaves a receipt

Kind	Produced by
`read`	Context reads (`POST` and `GET /v1/context`) and object reads
`history`	History navigation: search, timeline and open
`analytics`	Base-wide analysis, pseudonymous by default; a reveal records its reason
`admin`	Governance actions: merges, unmerges, erasures, policy changes, retracted patterns, rule changes, export runs, review verdicts, approved diffs and actions in the Console
`holdout`	The control group: the pack that would have been delivered, recorded and not delivered

Agent actions, links and administrative changes land on the same trail, so “who did what” and “who read what” live in one place.

What a receipt holds

{
  "receipt_id": "0192f7a4-2b61-7c1e-8a3d-5f0e9c7b1d24",
  "kind": "read",
  "surface": "object",
  "read_at": "2026-09-22T17:07:03Z",
  "source_id": "src_voice",
  "profile_id": "prf_01J1",
  "conversation_id": "call-4471",
  "audience": "customer_agent",
  "purpose": "customer_service",
  "verification": "V1",
  "policy_version": "pol-14",
  "item_ids": ["fct_01", "act_01J8ZK", "oi_01J8ZK"],
  "withheld": 2,
  "manifest_hash": "sha256:5b1e0c",
  "day": "2026-09-22",
  "slice": 3,
  "seq": 88213,
  "prev_hash": "sha256:0d9f3a",
  "hash": "sha256:7e21c8"
}

Items are listed by id and content is never copied into the receipt. The manifest_hash points to the provenance manifest of that delivery, which records:

every item included, with the event it came from;
every exclusion, with its reason: policy, verification, budget or quarantine;
the versions of the compiler, template, policy and extractor;
tokens per section and the prompt-cache decision.

Navigation receipts also record the query, the filters and the items returned by hash.

The chain

Receipts are append-only. Each one carries its position (seq) and the hash of the previous receipt (prev_hash), chained per space, per slice and per day. A small space has one slice; a large one has up to 16, chosen by the profile, so the busiest space still writes without a single bottleneck. Once a day the heads of the slices are combined into a daily root, which goes to immutable storage with object lock. Changing any past receipt breaks every hash after it and no longer matches the root. A quick continuity check over one page of a slice:

import os
import httpx

response = httpx.get(
    "https://acme-prod.us-east-1.api.niadra.com/v1/receipts",
    params={"conversation_id": "call-4471"},
    headers={"Authorization": f"Bearer {os.environ['NIADRA_API_KEY']}"},
)
items = sorted(response.json()["items"], key=lambda r: r["seq"])
for previous, current in zip(items, items[1:]):
    if current["seq"] == previous["seq"] + 1:
        assert current["prev_hash"] == previous["hash"], current["receipt_id"]

const url = new URL("https://acme-prod.us-east-1.api.niadra.com/v1/receipts");
url.searchParams.set("conversation_id", "call-4471");

const response = await fetch(url, {
  headers: { Authorization: `Bearer ${process.env.NIADRA_API_KEY}` },
});
const items = (await response.json()).items.sort((a: { seq: number }, b: { seq: number }) => a.seq - b.seq);
for (let i = 1; i < items.length; i++) {
  if (items[i].seq === items[i - 1].seq + 1 && items[i].prev_hash !== items[i - 1].hash) {
    throw new Error(`chain broken at ${items[i].receipt_id}`);
  }
}

curl "https://acme-prod.us-east-1.api.niadra.com/v1/receipts?conversation_id=call-4471" \
  -H "Authorization: Bearer $NIADRA_API_KEY"

The full check is on the server: GET /v1/receipts/verify?day=2026-09-22 walks every slice of that day and answers valid, the count of receipts, the heads of each slice, any breaks it found, and whether the recomputed root matches the anchored one (root_matches). The receipt routes are governance routes: a Console person with the security role, or a key with the admin scope. Filter the list by profile_id, conversation_id, source_id, kind and a since/until window, and page with cursor. See List receipts.

Three questions receipts answer

Why did the agent say X? At 2:07 pm the voice agent told Marina the $40 credit was already applied. The receipt of call-4471 lists act_01J8ZK, the billing agent’s 2:06 pm action, among the delivered items; the manifest shows it came from the credit action on invoice:erp:0823, confirmed by the ERP event. Receipt, manifest, item, event: four steps from the sentence to its source, and GET /v1/lineage/receipt/{receipt_id} walks them for you, returning the receipt, the delivered items with their origin and the exclusions. Who saw fact F? GET /v1/lineage/fact/{fact_id} returns every receipt whose delivery carried that fact: each source that received it, with purpose, level and time. What was withheld, and why? withheld says how many items the policy held back; the manifest says which reason applied to each (policy, verification, budget or quarantine). The agent learns only the count, never the content, so it knows that verifying the customer releases more.

Receipts in your SIEM

Receipts leave in seconds through the same delivery mechanism as webhooks, as JSON in the OCSF schema, or as files in your bucket together with the continuous export. You choose the path. SIEM delivery is optional on the Production plan and included on the Regulated plan.

Receipts and erasure

When a data subject is forgotten, read receipts are not rewritten: they already hold only ids and hashes, so they prove a read happened without keeping what was read. The erasure itself leaves an admin receipt, the erasure receipt, which lists what was erased and the export runs that already contained it. Measurement rows follow the retention and policy of the receipt they belong to.

Next steps

Privacy, erasure and export

the erasure receipt and the lineage it walks.

Context use

every signal opens the receipt of its delivery.

Context and views

withheld items and the verification levels.

List receipts

the endpoint in detail.

Memory basics

What the agent receives

Governance

Receipts and audit

What leaves a receipt

What a receipt holds

The chain

Three questions receipts answer

Receipts in your SIEM

Receipts and erasure

Next steps

Privacy, erasure and export

Context use

Context and views

List receipts

​What leaves a receipt

​What a receipt holds

​The chain

​Three questions receipts answer

​Receipts in your SIEM

​Receipts and erasure

​Next steps

Privacy, erasure and export

Context use

Context and views

List receipts

What leaves a receipt

What a receipt holds

The chain

Three questions receipts answer

Receipts in your SIEM

Receipts and erasure

Next steps