The whole hunk
from line 1, old and new numbered
/
lines
from line 1
1---
2title: Create a memory
3url: https://platform.claude.com/docs/en/api/beta/memory_stores/memories/create
4---
5
16# Create a memory
27
38**POST** `/v1/memory_stores/{memory_store_id}/memories`
from line 31
2631
2732 - `string`
2833
29 - `"message-batches-2024-09-24" or "prompt-caching-2024-07-31" or "computer-use-2024-10-22" or 41 more`
34 - `"message-batches-2024-09-24" or "prompt-caching-2024-07-31" or "computer-use-2024-10-22" or 42 more`
3035
3136 - `"message-batches-2024-09-24"`
3237
from line 79
7479
7580 - `"user-profiles-2026-08-18"`
7681
82 - `"user-profiles-2026-09-04"`
83
7784 - `"advisor-tool-2026-03-01"`
7885
7986 - `"managed-agents-2026-04-01"`
from line 123
116123
117124 - `"mid-conversation-system-clear-at-2026-08-21"`
118125
126- `"anthropic-workspace-id": optional string`
127
119128## Body parameters
120129
121130- `content: string or null`
from line 143
134143
135144 A `memory` object: a single text document at a hierarchical path inside a memory store. The `content` field is populated when `view=full` and `null` when `view=basic`; the `content_size_bytes` and `content_sha256` fields are always populated so sync clients can diff without fetching content. Memories are addressed by their `mem_...` ID; the path is the create key and can be changed via update.
136145
146 - `type: "memory"`
147
137148 - `id: string`
138149
139150 Unique identifier for this memory (a `mem_...` value). Stable across renames; use this ID, not the path, to read, update, or delete the memory.
from line 176
165176 - `path: string`
166177
167178 Hierarchical path of the memory within the store, e.g. `/projects/foo/notes.md`. Always starts with `/`. Paths are case-sensitive and unique within a store. Maximum 1,024 bytes.
168
169 - `type: "memory"`
170179
171180 - `updated_at: string`
172181