> ## Documentation Index
> Fetch the complete documentation index at: https://docs.anonalabs.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Browse what it knows

> Page through the memories themselves — no query, no ranking. The view that answers 'what did it actually store?'

[← All use cases](/use-cases/overview)

<div className="uc-examples"><a className="uc-api" href="/api-reference/memories">API reference</a></div>

## The scenario

Search answers "what is relevant to this question". It cannot answer "what is in
here", and those are different questions — the second one is what you need when
recall is disappointing and you are trying to work out whether the memory is
missing or merely unranked.

**What this recipe shows that no other does:** reading memories without a query
at all. Everything else in this cookbook searches.

## Step 1 — Page through it

```python theme={null}
page = client.list_memories(space_id="ops", limit=50, offset=0)
print(page["total"], "memories")
for m in page["items"]:
    print(m["date"], m["text"][:90])
```

`total` is the number people want first and search will never give you.

## Step 2 — Filter without ranking

```python theme={null}
client.list_memories(space_id="ops", memory_type="observation")
client.list_memories(space_id="ops", state="invalidated")
```

`state="invalidated"` is the interesting one: it lists what has been
[superseded](/use-cases/correct-a-memory) — a view of what the space used to
believe, which no search returns because superseded memories are excluded from
recall by design.

## Step 3 — Follow a memory back to its document

```python theme={null}
doc = client.get_document(space_id="ops", document_id=m["document_id"])
print(doc["source"], "->", doc["memory_count"], "memories")
```

## Step 4 — Remove a document and everything it produced

```python theme={null}
client.delete_document(space_id="ops", document_id=doc["document_id"])
```

One call removes the file and every memory extracted from it. That is what makes
"unpublish that outdated policy" a single operation instead of a hunt through
search results.

## Evals

1. Upload one document, note `memory_count` on it.
2. `list_memories` and confirm `total` moved by that amount.
3. Delete the document, list again, confirm `total` came back down.
4. Search for something only that document said. Empty is the correct answer —
   if it still returns, the deletion did not cascade and that is worth reporting.

## Guardrails

<Warning>
  **Deleting a document is irreversible and takes its memories with it.** That
  is usually what you want and it is never undoable. Check `memory_count` first
  so the blast radius is a number you have seen.
</Warning>

* **The list dedups by default.** `prefer_observations=True` hides raw facts a
  consolidation already covers, so `total` is smaller than the raw row count.
  Pass `False` to see the evidence layer underneath.
* **Browsing is not free of cost in attention.** A space with 40,000 memories
  cannot be read; use it to spot-check extraction, not to audit a corpus.
* **`offset` paging drifts under active writing.** For a full export, use
  [Take everything with you](/use-cases/take-everything-with-you) instead.