Get User Memory Statistics

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 full response has both data and meta; the generated example abbreviates that envelope. Each data item describes a visible user's total_memories and last_memory_updated_at.

GET/user_memory_stats

Retrieve paginated statistics about memory usage by user. Provides insights into user engagement and memory distribution across users.

Authorization

HTTPBearer
AuthorizationBearer <token>

In: header

Query Parameters

limit?|

Number of user statistics to return per page

Default20
page?|

Page number for pagination

Default1
user_id?|

User ID to filter statistics for

db_id?|

Database ID to query statistics from

table?|

Table to query statistics from

Response Body

application/json

application/json

application/json

application/json

application/json

application/json

curl --request GET 'https://example.com/user_memory_stats'
{  "data": [    {      "user_id": "123",      "total_memories": 3,      "last_memory_updated_at": "2025-09-01T07:53:17Z"    }  ]}