Zep
for LuumenAI

Read agent memory, sessions, and graphs — then write back with approval

Zep holds the memory behind your agents: sessions, threads, messages, and the knowledge graphs built from them. Luumen reads that history directly — session memory, thread context, node edges, task status — so you can see what an agent actually knew. Changes, like adding a fact triple or a new thread, are previewed and sent for approval first. Connects with an API key.

The Zep toolbox

41 tools: 22 read, 19 write. Reads answer instantly. Writes require approval by default. Everything is logged.

  • ReadGet Edge by UUIDRetrieve a specific edge by its UUID from the Zep knowledge graph.
  • ReadGet Graph by IDRetrieve a graph by its unique identifier from Zep.
  • ReadGet Group by IDRetrieve a group by ID from Zep.
  • ReadGet Node Entity EdgesRetrieve all entity edges for a specific node in the Zep knowledge graph.
  • ReadGet Project InfoRetrieve project information based on the provided API key.
  • ReadGet Session by IDRetrieve a session by its unique identifier from Zep.
  • ReadGet Session MemoryRetrieve memory for a given session including relevant facts and entities.
  • ReadGet Session Message by UUIDRetrieve a specific message by UUID from a Zep session.
  • ReadGet Session MessagesRetrieve messages for a given session from Zep.
  • ReadGet Task StatusCheck the status of asynchronous operations in Zep.
  • ReadGet Thread MessagesRetrieve conversation history for a specific thread from Zep.
  • ReadGet Thread User ContextRetrieve the most relevant user context from the user graph based on thread messages.
  • ReadGet User by IDRetrieve a user by their user ID from Zep.
  • ReadGet User NodeRetrieve a user's graph node and summary from Zep.
  • ReadGet User NodesRetrieve all nodes for a specific user from their graph in Zep.
  • ReadGet User SessionsRetrieve all sessions for a user from Zep.
  • ReadGet User ThreadsRetrieve all threads for a specific user from Zep.
  • ReadGraph SearchPerform hybrid graph search combining semantic similarity and BM25 full-text search across the Zep knowledge graph.
  • ReadList Groups OrderedRetrieve all groups from Zep with pagination support.
  • ReadList Sessions OrderedRetrieve all sessions from Zep with pagination and ordering support.
  • ReadList ThreadsRetrieve all threads from Zep with pagination support.
  • ReadList Users OrderedRetrieve all users from Zep with pagination support.
  • WriteAdd Fact TripleAdd a manually specified fact triple (subject-predicate-object) to the Zep knowledge graph. Approval by default
  • WriteAdd Session MemoryAdd memory messages to a specified Zep session. Approval by default
  • WriteAdd Thread MessagesAdd chat messages to a thread in Zep and ingest them into the user knowledge graph. Approval by default
  • WriteClone GraphClone a user or group graph with new identifiers in Zep. Approval by default
  • WriteCreate GraphCreate a new graph by adding data to Zep. Approval by default
  • WriteCreate GroupCreate a new group in Zep for multi-user graph management. Approval by default
  • WriteCreate SessionCreate a new session in Zep for storing conversation memory. Approval by default
  • WriteCreate ThreadCreate a new thread in Zep for a specific user. Approval by default
  • WriteCreate UserCreate a new user in Zep with properties like user_id, email, and metadata. Approval by default
  • WriteDelete GraphDelete a graph from Zep. Approval by default
  • WriteDelete GroupDelete a group from Zep. Approval by default
  • WriteDelete Session MemoryDelete a session and its memory from Zep. Approval by default
  • WriteDelete ThreadDelete a thread and its messages from Zep. Approval by default
  • WriteDelete UserDelete a user and all associated threads and artifacts from Zep. Approval by default
  • WriteUpdate GraphUpdate graph information in Zep including name and description. Approval by default
  • WriteUpdate GroupUpdate group information in Zep including name, description, and fact rating instructions. Approval by default
  • WriteUpdate MessageUpdate a message in a Zep thread. Approval by default
  • WriteUpdate Session MetadataUpdate session metadata in Zep. Approval by default
  • WriteUpdate UserUpdate an existing user's information in Zep including email, metadata, and ontology settings. Approval by default

One prompt, start to finish

What a governed Zep run looks like inside Luumen.

Questions

How does LuumenAI connect to Zep?

Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.

Can LuumenAI change things in Zep on its own?

Read actions answer immediately. Anything that writes — add fact triple, add session memory, add thread messages, clone graph, and more — is shown as a plan and requires approval by default, including the 5 actions classified as destructive. Administrators configure that per tool, so you decide exactly which actions can ever run unattended.

Who gets access to the integration?

You decide. Actions are granted per agent, skill, and team, and per environment — production is not staging. Read access can be broad while writes stay narrow.

Is there an audit trail?

Every call to Zep — read or write, approved or declined — is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.

Put Zep to work with Luumen

Connect in minutes. Every action scoped, approved, and audited from day one.