Generate session memories
Extracts memories from messages appended since the last run and infers memory↔fact relationships. The session stays active and can keep receiving messages. Append-only: it never re-extracts messages already covered by a prior run, so re-running it only adds memories for what's new, but it does not deduplicate against memories from a previous run. Call it intentionally rather than on every turn.
Authorization
Bearer writeEach operation lists the OAuth scope (read or write) it requires.
In: header
Scope: write
Path Parameters
ID of the patient
^[A-Za-z0-9._-]{1,128}$Unique session ID returned when the session was created.
1 <= lengthResponse Body
application/json
application/json
curl -X POST "https://example.com/v1/patients/string/sessions/string/memories"{ "ok": true}Append session messages POST
Appends user/assistant messages to an open session's transcript, in order. The session stays open. Tool-call turns are recorded separately by the MCP layer and are not accepted here.
List session memories GET
Returns the memories extracted from this session, paginated. Sorted by `createdAt` descending (newest first) by default.