Skip to main content

Core Concepts

Essential terminology for working with Anona Memory.

Memory Space

Isolation boundary per tenant/application. A Memory Space is where memories for a specific app or context live. Multiple spaces can exist within your organization; each is fully isolated from the others. Spaces are created with a name - the server assigns the permanent space_id you use in every other call:
API reference: Spaces API

Retain

Store a memory. POST /v1/memories
The content is embedded and indexed for semantic search automatically. API reference: Memories API

Recall

Query memories semantically. POST /v1/search
Recall finds memories by meaning, not keyword overlap. API reference: Search API

Reflect (Insights)

Synthesize insights across accumulated memories. POST /v1/insights
Unlike Recall (which returns raw matching memories), Reflect runs an agentic pass over the space and returns a synthesized answer. API reference: Insights API

API Key

Every request needs Authorization: Bearer <key>. Keys come in two flavors:
  • anona_live_... - production
  • anona_test_... - testing
Created and revoked from the dashboard (SettingsAPI Keys). The full key is shown once at creation; afterward only the prefix is visible.

Tenant Isolation

Each organization’s memories live in their own database schema - no shared tables. A space_id from one organization is meaningless (and inaccessible) to another, enforced both at the gateway (authorization check) and the database layer.

Next Steps

API Reference

Detailed endpoint documentation

Python SDK

Client library reference