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 a redaction_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

All requests require a Bearer token. See Authentication.

The memory store object

Endpoints

List memory stores

Response

Create a memory store

Request body

Response

Duplicate names for the same user return 400 Bad Request.

Get a memory store

Response

Delete a memory store

Returns 204 No Content.
Deleting a memory store removes its record. Ensure any entries relying on the store have been migrated or are no longer needed.

Redaction policy

The redaction_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.

Error codes