Overview
A memory store is a named, user-scoped container that agents can read from and write to for long-term memory. Each store carries aredaction_policy that is applied to content before it is persisted or surfaced to a model.
This scaffold owns the store record itself: create, list, get, and delete. Reading and writing individual memory entries through a store is handled by the agent runtime and memory APIs.
Memory stores are scoped to the authenticated user. The organization_id is captured at creation time for billing and audit grouping.
Base URL
The memory store object
Endpoints
List memory stores
Response
Create a memory store
Request body
Response
400 Bad Request.
Get a memory store
Response
Delete a memory store
204 No Content.
Redaction policy
Theredaction_policy object is interpreted by the agent runtime before memory is persisted or returned to a model. Common fields include:
The exact set of supported keys depends on the configured memory pipeline. Unknown keys are ignored.