Get Memory Topics

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 is a JSON array of unique topic strings within the selected database and effective user scope. It is not an inventory across every user when the caller is scoped.

GET/memory_topics

Retrieve all unique topics associated with memories in the system. Useful for filtering and categorizing memories by topic.

Authorization

HTTPBearer
AuthorizationBearer <token>

In: header

Query Parameters

user_id?|

User ID to filter topics for

db_id?|

Database ID to query topics from

table?|

Table to query topics from

Response Body

application/json

application/json

application/json

application/json

application/json

application/json

curl --request GET 'https://example.com/memory_topics'
[  "preferences",  "communication_style",  "technical",  "industry",  "compliance",  "code_examples",  "requirements",  "healthcare",  "finance"]