List Memories

Database and user

Use a registered memory-capable database, such as the SQLite database in the example API server. Supply db_id when several database IDs are available. A table selector requires db_id and selects a configured adapter; it does not create arbitrary storage.

Scoped identity overrides a supplied user_id. JWT user isolation is opt-in; non-admin service-account PAT callers always self-scope. When authorization is enforced, use the appropriate memories:read, memories:write or memories:delete scope.

The response has data and pagination meta. Pass multiple topics as one comma-separated query value, for example ?topics=preferences,work. User, agent, team and content filters apply within the selected database and caller's effective scope.

GET/memories

Retrieve paginated list of user memories with filtering and search capabilities. Filter by user, agent, team, topics, or search within memory content.

Authorization

HTTPBearer
AuthorizationBearer <token>

In: header

Query Parameters

user_id?|

Filter memories by user ID

agent_id?|

Filter memories by agent ID

team_id?|

Filter memories by team ID

search_content?|

Fuzzy search within memory content

limit?|

Number of memories to return per page

Default20
page?|

Page number for pagination

Default1
sort_by?|

Field to sort memories by

Default"updated_at"
sort_order?|

Sort order (asc or desc)

Default"desc"
db_id?|

Database ID to query memories from

table?|

The database table to use

topics?array<string>|

Comma-separated list of topics to filter by

Response Body

application/json

application/json

application/json

application/json

application/json

application/json

curl --request GET 'https://example.com/memories'
{  "data": [    {      "memory_id": "f9361a69-2997-40c7-ae4e-a5861d434047",      "memory": "User likes coffee.",      "topics": [        "preferences"      ],      "user_id": "123",      "updated_at": "2025-09-01T07:53:17Z"    }  ]}