Niches · Agent memory

Track how facts about a person or account change over time, with dates and sources

Two or three companies' docs show a full fit.

2companies, full fit
5companies, fit with a limit
35companies carry the tag
10share of the category's work
4first-hand accounts

What counts as done

A query for an entity returns the current fact and the superseded ones each with valid-from and valid-to dates and the source episode, and a time-filtered query returns only facts valid at that time.

How agents ask for it: did this buyer ever raise HOA fees, what medications was the patient on in March, when did this change and what was it before

Does the job 2

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

ListingWhy
past.dev BB
Revo Inc.
occurredAt and supersededAt on artifacts, occurredFrom and occurredTo windows, a queryTimestamp perspective, sources with excerpts, and trace lineage and timeline routes that say which memory replaced which. source
Zep BB
Zep Software, Inc.
Facts are bi-temporal with created_at, valid_at, invalid_at and expired_at, episodes are stored verbatim as sources, edge searches take datetime filters, and CallSphere relied on the validity windows for healthcare records. source

Does the job, with a limit 6

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
Basic Memory A
Basic Memory LLC
Observations can carry dates and bm_search filters by valid_at, valid_overlaps and time_kind, but validity windows and supersession are written by hand and there is no entity graph with source episodes. source
Graphicle BB
KarLex AI, Inc.
Reviewed memories carry validity, immutable revisions and source citations, queryable as of a time, but they are about a code project and must pass human review; not people or accounts. source
Graphiti D
Zep Software, Inc.
Edges carry bi-temporal metadata for point-in-time queries and get_episode_entities traces provenance, which CallSphere used for validity windows; but self-hosting needs Neo4j or FalkorDB and bulk writes hit LLM rate limits (issue 290). source
Hindsight D
Vectorize, Inc.
Facts carry occurred_start, occurred_end and mentioned_at and temporal search fills a date window, but there is no valid-to on a fact and invalidation is a manual PATCH. source
MemPalace B
MemPalace (open-source project)
Triples carry valid_from and valid_to, supersede closes and opens at one boundary, query_entity takes as_of and timeline lists history in SQLite; but triples are written by the agent, not extracted, and carry no source episode. source
Supermemory API + MCP C
Supermemory
Updates, extends and derives relations with isLatest keep history and a date field backfills, but no valid-from or valid-to fields or point-in-time query appear in the docs read. source

Couldn't check 1

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

ListingWhy
Memori D
Memori Labs Inc.
A knowledge graph is documented, but the graph page was not read and no validity windows appear in the pages that were.

Doesn't do this job 15

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

ListingWhy
Amazon Bedrock AgentCore Memory A
Amazon Web Services, Inc. (regional AWS entities by account location)
Records carry createdAt and a timestamp but no valid-from, valid-to or graph; the episodic strategy stores episodes, not dated fact histories. source
AI Memory B
Fabio Akita
Wiki pages with version chains; no dated facts with valid-from and valid-to about entities. source
claude-mem C
Alex Newman
No validity windows or entity graph; observations carry dates only. source
Cognee D
Topoteretes UG (haftungsbeschränkt)
The graph has no validity windows; temporal_columns exist only for structured dlt ingestion. source
Context Mode Engine C
MKSF LTD
No facts or entities; the Engine stores tool output and session rows. source
Egoist AI Passport C
Egoist Machines, Inc.
No dated facts, validity windows or graph in the agent docs. source
EverOS BB
Evermind AI, Inc.
Episodes and facts carry timestamps; no valid-from or valid-to windows or graph edges. source
Agent Platform Memory Bank B
Google LLC
Revisions record change history but there are no valid-from and valid-to facts or a graph to query by time. source
Honcho B
Plastic Labs, Inc.
Conclusions carry premises, not valid-from and valid-to windows, and there is no entity graph to query at a time. source
Hy Memory C
Tencent
The graph layer holds schemas and mental models; only intentions carry an expiry, and no fact has valid-from and valid-to windows. source
LangMem D
LangChain (the licence file gives no legal form)
Memories are store documents with updated_at; no validity windows or graph. source
Mem0 Platform + MCP E
Embedchain, Inc. (DBA Mem0)
Graph Memory, timestamps and Temporal Reasoning order results by time, but ADD-only extraction never closes a fact, so no valid-to or superseded history exists. source
MemMachine C
MemVerge, Inc.
Episodes carry timestamps and search sorts by them; no validity windows or point-in-time query. source
TencentDB Agent Memory C
Tencent
Atoms carry created_at and updated_at and a version; no validity windows or point-in-time query. source
Tokenrip B
Quintel, LLC
Artifact versions have dates; no dated facts about entities. source

What stops agents finishing

  • self-hosting needs a graph database (Neo4j or FalkorDB) running
  • each write runs LLM extraction, so a burst hits the provider's rate limit (Graphiti #290)
  • MCP server needs OAuth through Google Workspace, so a headless agent can't use it (Zep)

Around it

Before: crm.sync, document-extraction.records. After: agent-memory.user-facts-recall.

Where this comes from

Weight 10 of 100 in Agent memory: 4 of 36 accounts (CallSphere on Zep, three Graphiti issues) plus Thoughtworks' Trial rating; fewer accounts than the vendor pages suggest

The same as data: /api/v1/use-cases/agent-memory.temporal-graph.json, or the MCP tool get_use_case with id agent-memory.temporal-graph. 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.