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)Documentation Index
Fetch the complete documentation index at: https://docs.memoclaw.com/llms.txt
Use this file to discover all available pages before exploring further.
GET /v1/memories/core
List all pinned core memories for your wallet.Query Parameters
Filter by namespace. Defaults to all namespaces.
Maximum number of results (1–100).
Pagination offset.
Response (200)
Array of pinned memory objects.
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 theirmemory_type half-life.
Request Body
UUID of the memory to pin.
Response (200)
Always
true.The pinned memory’s UUID.
Example
Response
Errors
| Status | Description |
|---|---|
| 404 | Memory not found or belongs to another wallet. |
| 422 | Invalid UUID format. |
DELETE /v1/memories/core/:id
Unpin a core memory. The memory is not deleted — it simply resumes normal type-based decay.Path Parameters
UUID of the memory to unpin.
Response (200)
Always
true.The unpinned memory’s UUID.
Example
Response
Errors
| Status | Description |
|---|---|
| 404 | Memory not found or not pinned. |
| 422 | Invalid UUID format. |
When to Use Core Memories
How Memory Works
Learn about type-based decay and why pinning matters.
Store Memory
Set
pinned: true at store time to pin immediately.