Get a memory layer
One layer’s configuration and entry count. The entries themselves live on a separate read.
info returns on every read, includeInfo is a no-op here, and it carries entryCount and createdBy. entryCount is the cheap way to see how full a layer is without paging its entries.
Two kinds of layer
spec.type tells you which, and it changes what the rest of spec means:
agentId, an episodicKey, and often an expiresAt. You do not create or edit an episodic layer directly.
Fetch by your own ID
Memory layers are top-level workspace resources, so they take an external ID:404.
Related
List memory layers
List memory entries
Update a memory layer
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"
Response
OK
MemoryLayer is a named container of memory entries that can be composed into an objective's memory cascade. Layers are workspace-scoped resources. The layer type controls how its entries participate in the agent loop — see MemoryLayerType for details.
See "Memory cascade composition" above for how layers compose at lookup time.