Niches · Agent memory

Delete a fact or a whole user's memory and make sure it stays gone

Four or more companies' docs show a full fit.

5companies, full fit
13companies, fit with a limit
30companies carry the tag
8share of the category's work
3first-hand accounts

What counts as done

After the delete, a search for the fact returns nothing, a fetch of the id returns 404 or gone, and the fact is absent from derived indexes, caches and history tables on the same host.

How agents ask for it: forget my address, delete everything you know about this user, purge that secret I pasted

Does the job 5

The docs show it meets the test above, and nothing we read says otherwise.

ListingWhy
Basic Memory A
Basic Memory LLC
bm_delete removes a note or directory, a later bm_read is a NOT_FOUND error, and a locked note refuses deletion with HTTP 423. source
Context Mode Engine C
MKSF LTD
ctx_purge deletes indexed data by session, source or project from the local database. source
Graphiti D
Zep Software, Inc.
delete_episode cascades to the entities and facts the episode solely created, delete_entity_edge removes a fact, and the CRUD API deletes nodes by uuid or by group_id. source
LangMem D
LangChain (the licence file gives no legal form)
The manage tool updates or deletes a memory by id, the manager can delete with enable_deletes, and the store is the owner's own, so a delete removes the record from search. source
MemMachine C
MemVerge, Inc.
Episodic and semantic memories are deleted by id or filter through the API and the MCP delete_memory tool, and deleting a project removes everything in it. source

Does the job, with a limit 15

It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.

ListingWhy
Amazon Bedrock AgentCore Memory A
Amazon Web Services, Inc. (regional AWS entities by account location)
DeleteMemoryRecord removes a long-term record and DeleteEvent an event, but the pages read do not say whether deleting an event removes records already extracted from it. source
AI Memory B
Fabio Akita
memory_delete_page removes a page from recall, but the README says nothing is hard-deleted: the original stays in git and restore-page brings it back, so a pasted secret needs the operator purge commands. source
claude-mem C
Alex Newman
The local MCP server exposes no delete tool; only the hosted beta has DELETE /v1/memories/:id and a project purge, so a local user edits the SQLite database by hand. source
Cognee D
Topoteretes UG (haftungsbeschränkt)
forget removes graph, vector and relational data and the session answers built on an item, but search history stays until a dataset forget unless clean_history is set, and the page says stored bytes can remain on disk. source
EverOS BB
Evermind AI, Inc.
delete removes an owner's or session's memories and delete_by_ids targets ids, with 503 SESSION_BUSY while memorising; the index catches up later and derived profiles and cases are not mentioned. source
Hindsight D
Vectorize, Inc.
Deleting a document removes its memories and DELETE /memories clears a bank, but a single memory is only invalidated (kept for audit, reversible) rather than removed. source
Honcho B
Plastic Labs, Inc.
Session and workspace deletes return 202 and cascade in the background, a conclusion delete is immediate, but derived conclusions outlive their session and must be deleted one by one. source
Hy Memory C
Tencent
client.delete(id) and delete_all exist, but the listing's code reading found copies in history.db and cache.db after a delete and the raw conversation retained. source
Mem0 Platform + MCP E
Embedchain, Inc. (DBA Mem0)
delete, batch_delete and delete_all by user, agent or run exist, but the docs warn an empty user_id matches every memory in the project, and the OSS v3 MCP exposes no update or delete (map blocker). source
MemPalace B
MemPalace (open-source project)
mempalace_delete_drawer and delete_by_source remove drawers from the vector backend, but deletes are irreversible and remove revisions (listing note), and knowledge-graph facts are only invalidated. source
past.dev BB
Revo Inc.
Deleting a data point or an ingestion erases the memory derived from it with a 202 deletion operation, but request log payloads are kept for the plan's retention window. source
Supermemory API + MCP C
Supermemory
forget soft-deletes memories by id or by meaning with a dry run, excluded from search but preserved; documents are deleted separately and a SOC 2 user found no retrieval audit or PII checkpoint (issue 1348). source
TencentDB Agent Memory C
Tencent
atomic/delete, conversation/delete and chat-memory/clear report per-item counts of L0, L1 and profile rows removed, but clear trusts the bearer and service id with no user-level check. source
Tokenrip B
Quintel, LLC
artifact_delete moves to a 30-day trash and trash_purge or artifact_version_delete remove for good; whether trashed items leave search was not stated. source
Zep BB
Zep Software, Inc.
Edges, nodes and episodes delete asynchronously, but an edge or node shared with other episodes survives an episode delete and node summaries are not regenerated, so the deleted episode's information may remain in them. source

Couldn't check 2

The docs were closed to us, or silent. These carry no mark either way.

ListingWhy
Agent Platform Memory Bank B
Google LLC
The memory management page returned 404 and the retrieve page did too, so delete behaviour was not read.
Graphicle BB
KarLex AI, Inc.
None of the 25 MCP tools deletes a memory; a memory can be retired through review, but the pages read do not say how or whether sources are removed.

Doesn't do this job 2

Listings in the category that do something else, with the reason.

ListingWhy
Egoist AI Passport C
Egoist Machines, Inc.
No delete tool for agents in the docs; the owner manages memory and passes on my.ego.ist. source
Memori D
Memori Labs Inc.
No delete or forget tool appears in the MCP tool list or the docs index. source

What stops agents finishing

  • no delete tool exposed to the agent (Mem0 OSS v3 ADD-only)
  • copies stay in history.db and cache.db after delete (Hy Memory)
  • an empty user id in delete_all matches every memory in the project (Mem0)
  • purge is irreversible and removes revisions (MemPalace, Context Mode)

Around it

Before: agent-memory.user-facts-recall. After: compliance.audit-log.

Where this comes from

Weight 8 of 100 in Agent memory: 3 of 36 accounts touch deletion (Mem0 #5352 soft-delete workaround, Supermemory #1348, claude-mem privacy); the buyer check names it, so weighted above its count

The same as data: /api/v1/use-cases/agent-memory.delete-fact.json, or the MCP tool get_use_case with id agent-memory.delete-fact. Other jobs in this category: /api/v1/niches?category=agent-memory.

Draft, read 2026-11-12 from public docs and first-hand accounts, not yet reviewed by a person. A mark says what the docs show, not what a run measured.

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.