Skip to main content

Endpoints

GET

Retrieve memories

POST

Create memory

PATCH

Update memory

DELETE

Delete memory

POST Batch

Create up to 25

Get Memories

GET /v1/dev/user/memories

Retrieve your memories with optional filtering

Query Parameters

Response Example


Create Memory

POST /v1/dev/user/memories

Create a new memory

Request Body

Response Example


Create Memories (Batch)

POST /v1/dev/user/memories/batch

Create multiple memories in a single request (max 25)

Request Body

Each memory object accepts the same fields as the single create endpoint.

Response Example


Update Memory

PATCH /v1/dev/user/memories/{memory_id}

Update a memory’s content or visibility

Path Parameters

Request Body

At least one field must be provided.

Response Example


Delete Memory

DELETE /v1/dev/user/memories/{memory_id}

Delete a memory permanently

Path Parameters

Response Example

This action is permanent. Deleted memories cannot be recovered.

What Are Memories?

Memories are timeless facts about the user — preferences, relationships, personal details, and notable insights. They are NOT for notes, tasks, or time-sensitive information.
  • Good memories: “User is vegetarian”, “User’s sister Sarah lives in Portland”, “User prefers async communication”
  • Bad memories: “Meeting on March 15th”, “Call dentist tomorrow” (these are action items or conversations)
For notes, meeting summaries, or imported text content, use the Conversations API instead — it automatically extracts memories and action items.

Use Case: Store User Preferences

Import known facts and preferences about the user:

Memory Categories Explained

system

Useful context for the AI: preferences, work details, relationships, logistical info. Example: “User prefers dark mode”

interesting

Shareable, notable facts — things the user would excitedly tell someone at dinner. Example: “User climbed Mount Kilimanjaro”