v1

Get Memory

One memory, with the facts it asserts that are true now. The ones a later fact superseded are its history: GET /v1/memories/{id}/history.

get/v1/memories/{memory_id}

Request

  • Base URL: https://api.korely.ai
  • URL: https://api.korely.ai/v1/memories/{memory_id}
  • Auth: HTTP bearer

Path parameters

memory_idstring required

Response

Successful Response

idstring required
contentstring required
user_idstring nullable required
agent_idstring nullable required
run_idstring nullable required
clientstring nullable

The tool that wrote it: the X-Korely-Client header of the write, or the name an MCP client gave when it connected. A label, not a namespace: no read is scoped by it and the agent cap does not count it.

kindstring

note, or session for the log of a work session (kind of the write).

metadataobject required
statusstring

Whether this memory's typed facts are queryable yet: 'processing', 'ready', or 'error'. Extraction runs after the write returns, so a read taken immediately can legitimately find no facts. Poll GET /v1/events or read the memory again: no webhook says that extraction finished (memory.created is sent when the memory is stored, before its facts).

created_atstring nullable required
updated_atstring nullable required
factsobject[]

Changes

No recorded changes to this operation across all 1 revision of this API.