Sanaf AI
Start free
Artificial Intelligence

Zep, worked by an AI employee

Not another app for your team to learn, and not a set of rules for you to build. You hire an AI employee, you give it access to your Zep account, and you ask it for things in Slack or Teams the way you would ask anyone else on the team. There is nothing to map and nothing to maintain.

  • Artificial Intelligence
  • Connects with a key
  • 43 ready-made tools
  • Asked in Slack or Teams
At work

An illustration of how the conversation reads, not a transcript from a client account.

What Zep is

The Foundational Memory Layer for AI. Equip your agents with the knowledge to complete tasks, from the mundane to monumental.

You paste in a key from your own Zep account. It is kept encrypted, and you can withdraw it from inside Zep whenever you like.

How a run works

One message in, the work done in Zep.

  1. 01

    You ask

    You message your AI employee in the chat your team already has open, in one sentence, in your own words.

  2. 02

    It works out the step

    It decides what the job needs in Zep. You do not pick anything from a menu or wire anything together.

  3. 03

    It does the work

    Signed in to your own Zep account, inside the access you granted it, doing the thing you asked for.

  4. 04

    It reports back

    It tells you what it did, in the same thread. If it could not do something, it says so rather than guessing.

43 tools it already has

What it can do in Zep

These are the ready-made tools your AI employee already has in Zep. It is not limited to them, but it never has to be taught these.

  • Add Fact TripleTool to add a manually specified fact triple (subject-predicate-object) to the Zep knowledge graph. Use when you need to add explicit relationships between entities. Returns a task
  • Add Session MemoryTool to add memory messages to a specified Zep session. Use when you need to store conversation history or context in a session.
  • Add Thread MessagesTool to add chat messages to a thread in Zep and ingest them into the user knowledge graph. Use when you need to add conversation history to a thread - for best results, add messag
  • Clone GraphTool to clone a user or group graph with new identifiers in Zep. Use when you need to create test copies of user data, migrate user graphs to new identifiers, or set up template gr
  • Create GraphTool to create a new graph by adding data to Zep. Use when you need to add text, message, or JSON data to a user's graph or a specific graph. The data is processed and an episode n
  • Create GroupTool to create a new group in Zep for multi-user graph management. Use when you need to create a namespace for shared context across multiple users.
  • Create SessionTool to create a new session in Zep for storing conversation memory. Use when you need to establish a new conversation context linked to an existing user. The user must be created
  • Create ThreadTool to create a new thread in Zep for a specific user. Use when you need to start a new conversation thread. The user must be created first before creating a thread. Zep automatic
  • Create UserTool to create a new user in Zep with properties like userid, email, and metadata. Use when you need to add a new user to the system. It is recommended to provide at least firstnam
  • Delete GraphTool to delete a graph from Zep. Use when you need to permanently remove a graph and all associated data.
  • Delete GroupTool to delete a group from Zep. Use when you need to permanently remove a group and its associated data.
  • Delete Session MemoryTool to delete a session and its memory from Zep. Use when you need to permanently remove all memory data associated with a specific session.
  • Delete ThreadTool to delete a thread and its messages from Zep. Note that deleting a thread removes the thread and its messages from the thread history but does not delete associated data in th
  • Delete UserTool to delete a user and all associated threads and artifacts from Zep. Use when you need to permanently remove a user and handle Right To Be Forgotten requests. Deleting a user w
  • Get Edge by UUIDTool to retrieve a specific edge by its UUID from the Zep knowledge graph. Use when you need to fetch detailed information about a relationship between nodes, including the semanti
  • Get Graph by IDTool to retrieve a graph by its unique identifier from Zep. Use when you need to fetch details about a specific graph including its name, description, and timestamps.
  • Get Group by IDTool to retrieve a group by ID from Zep. Use when you need to fetch detailed information about a specific group including its configuration and metadata.
  • Get Node Entity EdgesTool to retrieve all entity edges for a specific node in the Zep knowledge graph. Use when you need to fetch relationship information, facts, and connections for a given node UUID.
  • Get Project InfoTool to retrieve project information based on the provided API key. Use when you need to fetch project details including UUID, name, description, and creation timestamp.
  • Get Session by IDTool to retrieve a session by its unique identifier from Zep. Use when you need to fetch details about a specific session including user association, timestamps, classifications, a
  • Get Session MemoryTool to retrieve memory for a given session including relevant facts and entities. Use when you need contextual information and historical data from a session.
  • Get Session Message by UUIDTool to retrieve a specific message by UUID from a Zep session. Use when you need to fetch a single message's details by its unique identifier from a particular session.
  • Get Session MessagesTool to retrieve messages for a given session from Zep. Use when you need to fetch the message history for a specific session with optional pagination support.
  • Get Task StatusTool to check the status of asynchronous operations in Zep. Use when monitoring batch adds, clone operations, or fact triple additions. Returns comprehensive task information inclu
  • Get Thread MessagesTool to retrieve conversation history for a specific thread from Zep. Use when you need to fetch the chat message history with optional pagination support via limit, cursor, or las
  • Get Thread User ContextTool to retrieve the most relevant user context from the user graph based on thread messages. Use when you need to get context including memory from past threads that is most relev
  • Get User by IDTool to retrieve a user by their user ID from Zep. Use when you need to fetch detailed information about a specific user including their profile, metadata, and configuration settin
  • Get User NodeTool to retrieve a user's graph node and summary from Zep. Use when you need to access the user summary generated from instructions, build custom context blocks, or retrieve facts
  • Get User NodesTool to retrieve all nodes for a specific user from their graph in Zep. Use when you need to fetch entity information, preferences, and knowledge graph data for a user. Supports pa
  • Get User SessionsTool to retrieve all sessions for a user from Zep. Use when you need to fetch session history for a specific user ID. Returns an array of session objects with metadata, classificat
  • Get User ThreadsTool to retrieve all threads for a specific user from Zep. Use when you need to fetch thread history for a specific user ID. Returns an array of thread objects with identifiers and
  • Graph SearchTool to perform hybrid graph search combining semantic similarity and BM25 full-text search across the Zep knowledge graph. Use when you need to search for entities, relationships,
  • List All ThreadsTool to list all threads with pagination and ordering support. Use when you need to retrieve threads with optional pagination (pagenumber, pagesize) and ordering (orderby, asc) par
  • List GraphsTool to retrieve all graphs from Zep with pagination support. Use when you need to fetch a list of graphs with optional pagination via pagenumber and pagesize parameters.
  • List Groups OrderedTool to retrieve all groups from Zep with pagination support. Use when you need to fetch a list of groups with optional pagination via pageNumber and pageSize parameters.
  • List Sessions OrderedTool to retrieve all sessions from Zep with pagination and ordering support. Use when you need to fetch a list of sessions with optional pagination via pagenumber and pagesize para
  • List ThreadsTool to retrieve all threads from Zep with pagination support. Use when you need to fetch a list of threads with optional pagination and sorting via pagenumber, pagesize, orderby,
  • List Users OrderedTool to retrieve all users from Zep with pagination support. Use when you need to fetch a list of users with optional pagination via pageNumber and pageSize parameters.
  • Update GraphTool to update graph information in Zep including name and description. Use when you need to modify graph properties after creation.
  • Update GroupTool to update group information in Zep including name, description, and fact rating instructions. Use when you need to modify an existing group's properties.
  • Update MessageTool to update a message in a Zep thread. Use when you need to modify message content, metadata, role, or other properties of an existing message. Particularly useful for adding or
  • Update Session MetadataTool to update session metadata in Zep. Use when you need to modify or add metadata to an existing session. Metadata is merged, so existing keys are preserved unless explicitly ove
  • Update UserTool to update an existing user's information in Zep including email, metadata, and ontology settings. Use when you need to modify user properties after creation.
Access, and who is in charge of it

You stay the boss of your Zep account.

Nothing connects until you approve it. You grant access one app at a time, you can take it back the same way, and everything your AI employee does in there is written down where you can see it.

How we handle your data
  • It signs in to your own Zep account. You are not moving anything into ours.
  • You grant access one app at a time, and you can take it back the same way.
  • Everything it does in Zep is written down, with what it did and when.
  • Anything you tell it to check with you first, it checks with you first.
Other apps in the same corner of the business

It works in Zep and the rest of your software in the same job

A real job rarely stays in one place. Reading a message in one app, checking a record in another and writing the result in a third is one request to your AI employee, not three.

See every app

Questions people ask about Zep

Can an AI employee really work inside Zep?
Yes. It signs in to your own Zep account and works in it the way a new hire would, from the chat your team already has open. Nobody installs anything, and nobody learns a new screen.
Do I have to move anything out of Zep?
No. Nothing moves and nothing is replaced. Your records stay in Zep, your team carries on in the same screens they used yesterday, and your AI employee works alongside them in there.
How does it get into my Zep account?
You paste in a key from your own Zep account. It is kept encrypted, and you can withdraw it from inside Zep whenever you like. You approve it before anything connects, and you can take the access back the same way you gave it.
What can it actually do in Zep?
It has 43 ready-made tools in Zep today, among them Add Fact Triple, Add Session Memory and Add Thread Messages. The full list is on this page. It is not limited to those, but it never has to be taught them.
Can it use Zep and the rest of my software in the same job?
Yes, and that is usually the point. Reading a message in one app, checking a record in Zep and writing the result somewhere else is one request to your AI employee, not three separate ones you stitch together.
Who decides what it is allowed to do in Zep?
You do. You grant access one app at a time and can withdraw it at any time, anything you ask it to check with you first it checks with you first, and everything it does in Zep is written down with what it did and when.