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 aname - the server assigns the permanent space_id you use in every other call:
Retain
Store a memory.POST /v1/memories
Recall
Query memories semantically.POST /v1/search
Reflect (Insights)
Synthesize insights across accumulated memories.POST /v1/insights
API Key
Every request needsAuthorization: Bearer <key>. Keys come in two flavors:
anona_live_...- productionanona_test_...- testing
Tenant Isolation
Each organization’s memories live in their own database schema - no shared tables. Aspace_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