Let every conversation continue where the last one ended.
Memory is persistent per-user preferences, history, relationships, and outcomes. Knowledge is your business's facts, documents, products, policies, and media. They work together, but they are not the same thing.
What is the easiest way to add memory to an LLM app?
Intelliverse Memory stores durable context about a specific end user, then recalls the relevant preferences, history, relationships, and outcomes on the next turn. Put business documents and policies in Knowledge; put what happened with this user in Memory.
Watch one coffee order become Knowledge and Memory.
Meet Maya, a regular at the fictional Sundial Coffee. What the shop knows (menu, policies) is Knowledge. What it remembers about Maya (oat milk, her usual) is Memory. Watch how a single reply draws on both.
Squares are the shop's Knowledge — its own facts, the same for every customer. Circles are Maya's Memory — hers alone, erasable anytime. The hexagon is one reply, built fresh from both sides.
Maya: Hi! One latte, please.
The assistant checks Knowledge first — the menu is the shop's own truth, the same for everyone. Tap any revealed shape to read it in plain English.
Equivalent relationship list (16)
Prefer reading? Every connection in the picture, in plain words. This list is part of the page itself, so nothing is lost if JavaScript is unavailable.
Remember
Store durable user preferences, history, relationships, and outcomes with an explicit user identity.
Recall
Load only the relevant user context before the next reply, call, or channel turn.
Continue
Use the same subject identity so web, messaging, and voice continue the same relationship.
Correct or forget
Inspect, correct, consolidate, or delete user Memory without changing business-owned Knowledge.
Remember once. Continue on the next turn.
The same App ID and key call the Memory verbs. A stable subject ID keeps each user's context separate from business-owned Knowledge.
# 1. Remember a durable preference for one user
curl https://router.intelli-verse-x.ai/v1/memory/remember \
-H "Authorization: Bearer $INTELLIVERSE_API_KEY" \
-H "Content-Type: application/json" \
-d '{ "app_id": "APP_ID", "subject_id": "USER_123",
"content": "Prefers window seats" }'
# 2. Recall relevant context on a later turn
curl https://router.intelli-verse-x.ai/v1/memory/recall \
-H "Authorization: Bearer $INTELLIVERSE_API_KEY" \
-H "Content-Type: application/json" \
-d '{ "app_id": "APP_ID", "subject_id": "USER_123",
"query": "What should I know before booking?" }'Scoped to app and user
Each Memory operation carries an App ID and subject identity, so context can follow one user without becoming shared business Knowledge.
Continuous across channels
Use the same subject identity in web, messaging, and voice so each conversation can pick up relevant prior context.
Six explicit verbs
Remember, recall, get context, correct, forget, and consolidate through one documented API.
Inspect and correct
Memory is not a hidden transcript dump. Apps can inspect, correct, consolidate, and delete user context.
Knowledge stays distinct
Policies, product facts, documents, and media belong in Knowledge. Memory records user-specific preferences, history, relationships, and outcomes.
Look inside your app's memory
The dashboard lets authorized app owners inspect the context associated with users, including its scope and history.
Your apps deserve to remember
Memory ships with every tier — Free included. Create an app, get an App ID, and give it a memory in the next five minutes.