Skip to content

Start building

Integration · Developer

AI agents for Zep

Long-term memory and context for agents with Zep: keep each person's conversations in threads, get a ready-made context block of what matters about them before answering.

Actions
10
Read
6
Write
4

Actions

What your agents can do in Zep

Long-term memory and context for agents with Zep: keep each person's conversations in threads, get a ready-made context block of what matters about them before answering, search the facts Zep has learned in their knowledge graph, and add business data or documents to a graph.

Read 6

Look things up. Nothing changes.

  • Find a user

    Looks up a person by the ID your own system gives them (user_id) and returns Zep's record.

  • List threads

    Lists conversation threads, newest first, optionally only one person's (user_uuid), each with its uuid and when it was made.

  • Get context for a thread

    Returns, in context, a ready-to-use text block of what matters for the thread's latest messages: the relevant facts and entities from the person's knowledge graph with their dates.

  • Read a thread's messages

    Returns a thread's messages, newest first by default, each with role, name, content and when it was said.

  • Search facts in a graph

    Searches a knowledge graph (a person's, by their graph_uuid, or a shared one) for the facts most relevant to a question, like "Where does Jane work?".

  • Get context from a graph

    Builds, in context, a text block of what a knowledge graph knows about a question (facts, entities, episodes and summaries), up to max_characters, for a person's graph or a shared one.

Write 4

Create, change or send.

  • Create a user

    Adds a person to Zep under the ID your own system gives them, with an optional name, email and metadata, and creates their knowledge graph.

  • Start a thread

    Starts a conversation thread for a person (by the user's Zep uuid from find_user or create_user).

  • Add messages to a thread

    Saves new messages of a conversation to a thread; Zep learns facts about the person from them in the background (a task follows it).

  • Add data to a graph

    Adds text, a JSON record or a chat message to a knowledge graph (a person's, by graph_uuid, or a shared one), from which Zep extracts entities and facts in the background.

A person can approve first

Any write action can be set to wait for a person's approval before it runs, so an agent asks before it changes anything.

Connection

How it connects

Connect it once in the console, then give it to the agents and workflows that need it.

API key

Paste an API key from your Zep account.

What you enter

  • Project API key

Kept safe

  • Credentials are stored encrypted with your organization's own keys.
  • They are opened only by the process that makes the call, at the moment it runs, and never go into a prompt or the browser.
  • Calls go only to the tool's own servers.

How we protect your data

Ideas

Ideas to start with

Starting points made only from the actions above. Mix them with any other tool your agents can use.

  • 01

    Ask about your Zep data

    Ask a question in plain words. The agent can find a user, list threads or get context for a thread in Zep, then answers with what it found.

  • 02

    Let an agent update Zep

    Have the agent create a user or start a thread in Zep as part of a larger task. Turn on approval and a person signs off on each change first.

  • 03

    Share what it finds in Slack

    Give one agent Zep and Slack: it can find a user in Zep and post a summary to a Slack channel in the same run.

FAQ

Zep and MyDeepAgents

Can MyDeepAgents connect to Zep?

Yes. The Zep connector has 10 actions: 6 read and 4 make changes. Your agents can call them as tools, and your workflows can run them as steps.

How do I connect Zep?

Paste an API key from your Zep account. You'll need: Project API key. Credentials are stored encrypted with your organization's own keys and are opened only at the moment of a call.

Can an agent change data in Zep without asking?

Only if you let it. Each of the 4 actions that change data can be set to wait for a person's approval before it runs.

Can I use Zep in workflows as well as agents?

Yes. Every Zep action also works as a step in a workflow, and the same connection serves your agents and your workflows.

Early access

Put Zep to work

Connect it in a few minutes, give an agent the actions it needs, and decide which changes wait for a person.