Memories Endpoints
Create, retrieve, update, delete, and search memories. Memories are the core building block of Rekall, supporting all seven memory types with rich metadata and semantic embeddings.
Overview
The memories API provides full CRUD operations on memory records as well as semantic search. All memory types (episodic, semantic, procedural, long-term, short-term, execution, preferences) are managed through these endpoints.
| Method | Endpoint | Description |
|---|---|---|
POST | /v1/memories | Create a new memory |
GET | /v1/memories | List memories |
GET | /v1/memories/:id | Get a specific memory |
PUT | /v1/memories/:id | Update a memory |
DELETE | /v1/memories/:id | Delete a memory |
POST | /v1/memories/search | Semantic search over memories |
Create Memory
List Memories
Get Memory
Update Memory
Delete Memory
Search Memories
Relevance scoring
The relevance field is a similarity score between 0 and 1, where 1 is an exact semantic match. Use min_relevance to filter out low-quality results. A threshold of 0.7 works well for most use cases.
Memory Object
The following table describes all fields in a memory object.
| Field | Type | Description |
|---|---|---|
id | string | Unique memory identifier (prefixed with mem_) |
type | string | Memory type: episodic, semantic, procedural, long_term, short_term, execution, preferences |
content | string | The memory content (1-50,000 characters) |
context | string | Memory context: agent, user, hive, global |
agent_id | string | Associated agent ID (if context is agent) |
metadata | object | Arbitrary key-value metadata (tags, importance, custom fields) |
strength | number | Current memory strength (0-1), affected by decay and access |
access_count | integer | Number of times the memory has been accessed |
created_at | string | ISO 8601 creation timestamp |
updated_at | string | ISO 8601 last update timestamp |
last_accessed_at | string | ISO 8601 timestamp of last access |
