Graph memory

How understanding is stored and stays true over time. Supermemory builds a living knowledge graph of facts on top of other facts — not a static folder of embeddings, and not classic entity–relation–entity triples you maintain by hand. The pipeline that turns a chat or file into memories is How it works. This page is the model: what a memory is, how edges form, and why agents utilize supermemory’s graph

Try it

Get a key from the developer console — API Keys → Create API Key — then add a memory and pull it back with related edges:

import Supermemory from "supermemory";

const client = new Supermemory({ apiKey: "sm_..." }); // from console.supermemory.ai → API Keys

await client.add({
  content: "Alex mentioned he just started at Stripe",
  containerTag: "user_123",
});

const results = await client.search({
  q: "where does Alex work?",
  containerTag: "user_123",
  include: { relatedMemories: true },
});

Full walkthrough with a live example: Quickstart.

Documents vs memories

	Documents	Memories
What	Raw input you send	Facts Supermemory extracts
Examples	PDF, chat log, Drive file, URL	“Alex is a PM at Stripe”
Role	Source of truth for RAG / SuperRAG	Personal and entity state over time
Lifecycle	You add / update / delete	Graph updates, extends, derives, forgets

Think of documents as books you hand the system. Memories are the insights it keeps — connected to each other as new content arrives.

Uploading a long PDF does more than store bytes: Supermemory derives many memories and links them to what it already knows about that entity or user. Chunks of the document remain available for SuperRAG grounding.

Properties and rules of memories

Memories are atomic - Each memory has enough information and context about one particular topic
They always build on top of each other - with updates, the model knows the history, a memory extends from other memories, and new facts are derived (derives relation) from existing knowledge.

Memory relationships

When content is processed, new facts connect to existing ones through three relationship types.

Updates — information changes

New fact replaces what was true before for search purposes; history can remain for audit.

Memory 1: "Alex works at Google as a software engineer"
Memory 2: "Alex just started at Stripe as a PM"
         → Memory 2 UPDATES Memory 1

Getting Started

Concepts

Using supermemory

Deployment

Other resources

Migration Guides

Try it

Documents vs memories

Properties and rules of memories

Memory relationships

Updates — information changes

​Try it

​Documents vs memories

​Properties and rules of memories

​Memory relationships

​Updates — information changes

Try it

Documents vs memories

Properties and rules of memories

Memory relationships

Updates — information changes