Delete a memory store in Anthropic
A documented Anthropic operation that changes something in your account. Describe the outcome you want in plain words — HumDay writes the program, proves it, and runs it.
What this operation does
Delete a memory store
- DELETEChanges data
api.anthropic.com/v1/memory_stores/{memory_store_id}?beta=true
How HumDay uses it
- You describe the outcome. Not this operation by name — what you want to happen. HumDay works out which operations it needs.
- The contract names it. Before anything is built, you see exactly which Anthropic operations the program may use, and this is one of them.
- You approve access. Because this one changes data, it cannot run until you have explicitly granted it.
Other Anthropic operations
- Create a MessagePOST · changes data
- Create a MessagePOST · changes data
- Create a Message BatchPOST · changes data
- Create a Message BatchPOST · changes data
- Create User ProfilePOST · changes data
- Count tokens in a MessagePOST · changes data
- Count tokens in a MessagePOST · changes data
- Create SkillPOST · changes data
Questions
- Can HumDay delete a memory store in Anthropic?
- Yes. This operation is published in Anthropic's own API description, so HumDay can use it without a hand-built connector — once you have approved it for your automation.
- Will this change my Anthropic data?
- Yes — this is a DELETE operation, so it changes something in Anthropic. HumDay holds anything that writes behind an approval you grant explicitly, and the contract you approve says what it may touch.
- Do I need to write code?
- No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a proof run before anything touches your Anthropic account.
Where this came from
Read from the API description Anthropic publishes themselves at storage.googleapis.com/stainless-sdk-openapi-specs/anthropic/anthropic-893a61e9c1cd6c69a70. The description above is the provider’s own wording, not ours.