Claude Platform Docs

Almacenes de memoria

Crear un almacén de memoria
$ ant beta:memory-stores create
POST/v1/memory_stores
Listar almacenes de memoria
$ ant beta:memory-stores list
GET/v1/memory_stores
Recuperar un almacén de memoria
$ ant beta:memory-stores retrieve
GET/v1/memory_stores/{memory_store_id}
Actualizar un almacén de memoria
$ ant beta:memory-stores update
POST/v1/memory_stores/{memory_store_id}
Eliminar un almacén de memoria
$ ant beta:memory-stores delete
DELETE/v1/memory_stores/{memory_store_id}
Archivar un almacén de memoria
$ ant beta:memory-stores archive
POST/v1/memory_stores/{memory_store_id}/archive
Models
beta_managed_agents_deleted_memory_store: object{ type: "memory_store_deleted", id }

Confirmation that a memory_store was deleted.

type: "memory_store_deleted"
id: string

ID of the deleted memory store (a memstore_... identifier). The store and all its memories and versions are no longer retrievable.

beta_managed_agents_memory_store: object{ type: "memory_store", id, archived_at, 5 more }

A memory_store: a named container for agent memories, scoped to a workspace. Attach a store to a session via resources[] to mount it as a directory the agent can read and write.

type: "memory_store"
id: string

The unique ID of the memory store (memstore_...). Use it to attach the store to a session.

archived_at: string

When the memory store was archived, in RFC 3339, or null if it hasn't been.

Archiving can't be undone. An archived store can't be attached to new sessions. You can't create or update its memories or update the store. You can still read and delete its memories, redact their versions, and delete the store.

See the memory guide to learn more about archiving.

formatdate-time
created_at: string

When the memory store was created, in RFC 3339.

formatdate-time
description: string

Free-text description of what the store contains, up to 1,024 characters. Included in the agent's system prompt when the store is attached, so word it to be useful to the agent. Empty string when unset.

metadata: map[string]

Key-value pairs for your own use, such as the end user that the store belongs to.

A store has at most 16 pairs. Keys are 1 to 64 characters long and values at most 512 characters. You can't filter lists by metadata.

name: string

Human-readable name for the store. 1–255 characters. The store's mount-path slug under /mnt/memory/ is derived from this name.

updated_at: string

When the memory store was last changed, in RFC 3339.

Changing its name, description, or metadata updates it. Archiving the store does too. Changes to the store's memories don't.

formatdate-time

Almacenes de memoriaMemorias

Crear una memoria
$ ant beta:memory-stores:memories create
POST/v1/memory_stores/{memory_store_id}/memories
Listar memorias
$ ant beta:memory-stores:memories list
GET/v1/memory_stores/{memory_store_id}/memories
Recuperar una memoria
$ ant beta:memory-stores:memories retrieve
GET/v1/memory_stores/{memory_store_id}/memories/{memory_id}
Actualizar una memoria
$ ant beta:memory-stores:memories update
POST/v1/memory_stores/{memory_store_id}/memories/{memory_id}
Eliminar una memoria
$ ant beta:memory-stores:memories delete
DELETE/v1/memory_stores/{memory_store_id}/memories/{memory_id}

Almacenes de memoriaVersiones de memoria

Listar versiones de memoria
$ ant beta:memory-stores:memory-versions list
GET/v1/memory_stores/{memory_store_id}/memory_versions
Recuperar una versión de memoria
$ ant beta:memory-stores:memory-versions retrieve
GET/v1/memory_stores/{memory_store_id}/memory_versions/{memory_version_id}
Expurgar una versión de memoria
$ ant beta:memory-stores:memory-versions redact
POST/v1/memory_stores/{memory_store_id}/memory_versions/{memory_version_id}/redact