List memory entries
Browse a layer by key prefix or search its keys and descriptions. Bodies stay behind.
key and description but never content.
metadata, spec, info. Fetch one entry to get its body: get by id returns content at the top level. Listing a large layer therefore stays cheap no matter how big the bodies are.
prefix walks the key path
Keys behave like file paths, and prefix treats them that way. Prefix-only, and case-sensitive.
policies/us/... and runbooks/... become browsable directories.
query searches keys and descriptions, folding case
search_memory tool scores trigram similarity over the same two fields, key and description, so a good description is how an agent finds an entry whose key it cannot guess.
content is searched by neither. A phrase that appears only in the body finds nothing, here or from the agent.
The two filters also disagree on case: prefix is case-sensitive, query is not.
Paging
limit is a page size, and pagination.nextCursor appears only when another page exists. The SDK iterator follows it for you, so limit never caps what you receive.
sortOrder=desc reverses. The default is asc, oldest key first by creation.
pagination is omitted entirely from the response when there is no next page, so read it defensively.
Related
Create a memory entry
description earns its place.Get a memory entry
content.Memory layers
Create a memory layer
type means.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"
Query Parameters
Maximum number of results to return
Pagination cursor from previous response
Filter by key prefix (e.g., "skills/postmortem/" to list all entries under that hierarchy). Matches against the entry's key, not its name.
Free-form search query
Filters by metadata labels. Comma-separated key=value pairs, e.g. "env=prod,team=ai". A resource matches only if every pair matches exactly (AND semantics).
Sort order for results (asc or desc by creation time)
When set to true you may use more of your alloted API rate-limit