Skip to main content
Core memories are pinned memories that are exempt from type-based decay. Use them for critical facts that should persist indefinitely — user identity, foundational preferences, or key decisions that never expire. Price: FREE (all core memory endpoints)

GET /v1/memories/core

List all pinned core memories for your wallet.

Query Parameters

string
Filter by namespace. Defaults to all namespaces.
number
default:"20"
Maximum number of results (1–100).
number
default:"0"
Pagination offset.

Response (200)

array
Array of pinned memory objects.
number
Total count of core memories.

Example

Response

POST /v1/memories/core

Pin an existing memory as a core memory. Pinned memories are exempt from type-based decay — they never fade regardless of their memory_type half-life.

Request Body

string
required
UUID of the memory to pin.

Response (200)

boolean
Always true.
string
The pinned memory’s UUID.

Example

Response

Errors


DELETE /v1/memories/core/:id

Unpin a core memory. The memory is not deleted — it simply resumes normal type-based decay.

Path Parameters

string
required
UUID of the memory to unpin.

Response (200)

boolean
Always true.
string
The unpinned memory’s UUID.

Example

Response

Errors


When to Use Core Memories

Good candidates for pinning:
  • User identity (name, timezone, role)
  • Foundational preferences that rarely change
  • Critical project decisions
  • Corrections that must persist indefinitely
Avoid over-pinning. If everything is a core memory, nothing is. Reserve pinning for truly permanent facts. Most memories benefit from natural decay — it keeps recall results relevant.

How Memory Works

Learn about type-based decay and why pinning matters.

Store Memory

Set pinned: true at store time to pin immediately.