Skip to main content
GET
https://api.memoclaw.com
/
v1
/
memories
/
{id}
Get Memory
curl --request GET \
  --url https://api.memoclaw.com/v1/memories/{id}
{
  "id": "<string>",
  "user_id": "<string>",
  "namespace": "<string>",
  "content": "<string>",
  "metadata": {},
  "importance": 123,
  "memory_type": "<string>",
  "session_id": {},
  "agent_id": {},
  "pinned": true,
  "expires_at": {},
  "created_at": "<string>",
  "updated_at": "<string>",
  "accessed_at": "<string>",
  "access_count": 123
}
Price: FREE

​
Path Parameters

​
id
string
required
UUID of the memory to retrieve.

​
Response (200)

Returns the full memory object.
​
id
string
UUID of the memory.
​
user_id
string
UUID of the owning user.
​
namespace
string
Namespace of the memory.
​
content
string
The memory text.
​
metadata
object
Metadata attached to the memory.
​
importance
number
Importance value (0–1).
​
memory_type
string
Memory type: correction, preference, decision, project, observation, or general.
​
session_id
string | null
Session ID, if set.
​
agent_id
string | null
Agent ID, if set.
​
pinned
boolean
Whether the memory is pinned (exempt from decay).
​
expires_at
string | null
ISO 8601 expiry date, if set.
​
created_at
string
ISO 8601 creation timestamp.
​
updated_at
string
ISO 8601 last update timestamp.
​
accessed_at
string
ISO 8601 last access timestamp.
​
access_count
number
Number of times this memory has been recalled.

​
Errors

StatusDescription
404Memory not found, deleted, or belongs to another wallet.
422Invalid UUID format.

​
Example

curl https://api.memoclaw.com/v1/memories/550e8400-e29b-41d4-a716-446655440000
Response
{
  "id": "550e8400-e29b-41d4-a716-446655440000",
  "user_id": "7c9e6679-7425-40de-944b-e07fc1f90ae7",
  "namespace": "default",
  "content": "User prefers dark mode and vim keybindings",
  "metadata": {
    "tags": ["preferences", "ui"]
  },
  "importance": 0.8,
  "memory_type": "preference",
  "session_id": null,
  "agent_id": null,
  "pinned": false,
  "expires_at": null,
  "created_at": "2025-01-15T10:30:00Z",
  "updated_at": "2025-01-15T10:30:00Z",
  "accessed_at": "2025-01-20T14:22:00Z",
  "access_count": 3
}