Get a memory entry
The one read that returns an entry’s content. The list omits it; this hands it back.
content.
content is top-level, not under spec
The body sits beside spec, not inside it. spec holds key and description; content is its own field on the response.
content back. The list leaves it out so paging a big layer stays cheap, so fetch a single entry when you need its body. A missing ID is a 404.
The agent reads it differently
content here is for you. The agent never calls this endpoint; it reads the same entry through get_memory, resolved against the cascade by key. If the entry has expired (its layer or its own TTL), get_memory filters it out, but this endpoint still returns the row while it exists.
info.memoryLayer names the layer the entry belongs to, and info.createdBy the profile that wrote it.
Related
List memory entries
Create a memory entry
content is written, and why reads redact it elsewhere.Memory layers
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Path Parameters
"workspace_01HXKD2E5NQM3T9AYWCF133E3Q"
Memory layer ID. Accepts canonical memlyr_… form or external_id: form.
"memlyr_01HXKD2E5NQM3T9AYWCFFFBMJH"
"mementry_01HXKD2E5NQM3T9AYWCF5E52Z0"
Response
OK
MemoryEntryDetail is the full representation of an entry, including the resolved content body. Returned by GetMemoryEntry, CreateMemoryEntry, and UpdateMemoryEntry.
Standard metadata for persistent, named resources (e.g., agents, tools, prompts)
MemoryEntrySpec is the metadata portion of an entry — the fields that identify and describe it, without the body. It appears on both the summary (MemoryEntry) and detail (MemoryEntryDetail) views.
The resolved body of the entry. For entries created or updated via an upload_id, this is the ingested content, not the original upload handle. May be empty; an entry with only a key and description is valid (e.g., a stub skill being drafted, or an entry where the frontmatter alone is the payload).