Get started

Zep for AI agents

Zep is a memory layer for AI agents, storing facts, sessions, and context graphs, used by developers building agents that need to remember past interactions. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.

Connect ZepSee the 41 actions ↓
AI and modelsAPI keyMCP + RESTgetzep.com
AUDIT LOG · ZEPPOLICY: acme-support
09:41:07 · claude · u_8f2read
zep.list_threads
List Threads✓ allowed · 212ms
09:41:08 · claude · u_8f2read
zep.get_edge
Get Edge by UUID✓ allowed · 164ms
09:41:09 · claude · u_8f2write
zep.create_user
Create User✓ approved · approved by user
09:41:12 · claude · u_8f2destructive
zep.delete_user
Delete User✕ blocked · policy: deny
EVERY ZEP CALL, ON THE RECORD
01 · USE CASES

What agents do in Zep.

01

Get a thread's messages

Pull the conversation history for a thread, a read-only context fetch.

02

Add a fact to the graph

Record a new fact tied to a user or session for future reference.

03

Confirm before deleting a user's memory

Check with the user before deleting a user's stored session memory, since that history can't be recovered.

02 · ACTIONS

41 Zep actions, graded by risk.

Every Zep action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.

read

21

Look things up. Allowed by default.

  • zep.get_edge
    Get Edge by UUID
  • zep.get_user
    Get User by ID
  • zep.get_group
    Get Group by ID
  • zep.get_session
    Get Session by ID
  • zep.list_threads
    List Threads
  • zep.get_user_node
    Get User Node
  • zep.get_node_edges
    Get Node Entity Edges
  • zep.get_user_nodes
    Get User Nodes
  • zep.get_graph_by_id
    Get Graph by ID
  • zep.get_task_status
    Get Task Status
  • zep.get_project_info
    Get Project Info
  • zep.get_user_threads
    Get User Threads
  • zep.get_user_sessions
    Get User Sessions
  • zep.get_session_memory
    Get Session Memory
  • zep.list_users_ordered
    List Users Ordered
  • zep.get_session_message
    Get Session Message by UUID
+ 5 MORE

write

15

Create and change things. Allow, or ask the user first.

  • zep.create_user
    Create User
  • zep.update_user
    Update User
  • zep.create_graph
    Create Graph
  • zep.create_group
    Create Group
  • zep.update_graph
    Update Graph
  • zep.update_group
    Update Group
  • zep.create_thread
    Create Thread
  • zep.create_session
    Create Session
  • zep.update_message
    Update Message
  • zep.update_session
    Update Session Metadata
  • zep.add_fact_triple
    Add Fact Triple
  • zep.add_session_memory
    Add Session Memory
  • zep.add_thread_messages
    Add Thread Messages
  • zep.clone_graph
    Clone Graph
  • zep.graph_search
    Graph Search

destructive

5

Delete, cancel or archive. Ask first, or deny outright.

  • zep.delete_user
    Delete User
  • zep.delete_graph
    Delete Graph
  • zep.delete_group
    Delete Group
  • zep.delete_thread
    Delete Thread
  • zep.delete_session
    Delete Session Memory
03 · HOW IT WORKS

Zep in three steps.

  1. 01Your users connect ZepThey add their Zep api key on Arc0 Connect, under your brand. It goes straight into the vault.
  2. 02You set the rulesReads run, writes like “create User” can wait for the user, and “delete User” can be denied outright.
  3. 03Any agent can actYour agent calls Zep through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
POLICY.TS
await arc0.policies.set('zep', {
  read: 'allow',
  write: 'ask',        // create_user
  destructive: 'deny',  // delete_user
})

# Claude Code: the same connection, one URL
$ claude mcp add --transport http arc0 \
    https://mcp.arc0.ai/u/u_8f2
04 · AUTH AND DATA

How Zep connects.

Users add their Zep api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.

The same Zep connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →

AUTH
API key
CREDENTIALS
Per-tenant encrypted vault
MODEL SEES
Results only, never credentials
AUDIT LOG
Every call, on every plan
05 · WORKS WITH

Use Zep from any agent.

Claude
ChatGPT
Cursor
Codex
VS Code
OpenAI Agents SDK
Claude Agent SDK
Vercel AI SDK
Mastra
LangGraph
06 · RELATED

More ai and models apps.

Perplexity AI9 actionsAffinda119 actionsAgent Mail5 actionsAI/ML API30 actionsAivoov1 actionsAll Images AI7 actionsAltText.ai10 actionsAltTextLab2 actions
ALL AI AND MODELS APPS →
07 · FAQ

Zep and Arc0, answered.

Q01

Can I use Zep with Claude, ChatGPT or Cursor?

Yes. Connect Zep to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the Zep actions you allow.

Q02

How do users connect Zep?

Users add their Zep api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.

Q03

Which Zep actions can my agent take?

41 in total: 21 read, 15 write and 5 destructive, such as “create User”. Your policies decide which of them each agent may call.

Q04

Can I stop my agent from deleting things in Zep?

Yes. Actions like “delete User” are graded destructive. Set destructive actions to deny, or to ask so the user approves each one, and blocked calls still show up on the audit log.

Q05

Can my own backend call Zep too?

Yes. The same Zep connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.

Get started

Plug Zep into your agent.

Your users connect Zep once, under your brand. Your agent gets 41 actions behind your policies, with every call on the record.

Connect ZepBrowse all apps →

Free to build · MCP + REST · Audit log on every plan