OpenViSTAI · Agents · Blockchain · Crypto
Submit a project
Menu
Agent Memory & RAG

Zep

Zep is a public developer repository of examples, agent-framework integrations and tools for building agent memory with Zep Cloud. It includes sample apps in Python, TypeScript and Go, bulk ingestion utilities, ontology definitions, benchmarks and an evaluation harness.

Explore the practical guide ↓

Independent OpenViST project profile, based on linked sources.

Zep — OpenViST project profile in Agent Memory & RAG.
OpenViST project illustration. See the linked sources for product details.
Understand the project

Practical overview

When it fits

Use the repository when you need implementation examples or supporting tools for agent memory with Zep Cloud; use its integration listings to identify packages by framework and language.

Who it is for

  • Developers integrating Zep Cloud with an agent framework.
  • Teams building bulk ingestion workflows for agent-memory data.
  • Developers evaluating memory ingestion and retrieval.

Documented uses

  • Find an integration package for an agent framework and programming language.
  • Explore sample apps and snippets for connecting agent code with Zep Cloud.
  • Bulk-ingest Slack data, documents, email, JSON/CSV or fact triples.
  • Structure memory data with ontology definitions.
  • Benchmark or evaluate memory ingestion and retrieval.
Before you choose

Requirements & limits

The repository is public and licensed under Apache-2.0. Zep Cloud is a separate managed service; the README directs users to sign up and provides separate SDK package references. Zep Community Edition is deprecated and unsupported.

  • Integration packages are grouped by framework and language, and are built, tested and released independently; consult the integrations README for package and release details.
  • The repository’s examples use Python, TypeScript and Go, while integration coverage varies by framework and language.
  • This repository is distinct from Zep Cloud, and the deprecated Community Edition is not supported.

Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.

Source-based practical guide

Choose a Zep framework integration package

Locate an integration package for a supported agent framework and language.

Before you start

  • Choose a framework and language listed in the repository README.

Steps

  1. Open the integrations directory.

  2. Browse to the framework-first, language-second package path: integrations//.

  3. Consult integrations/README.md for package details, release status, and links.

Expected outcome

You can identify the repository package and its listed release information for the selected framework and language.

Guide limitations

  • Packages are built, tested, and released independently; the README does not establish compatibility for a particular setup.
Documentation 1 ↗
Source-based practical guide

Install an official Zep Cloud SDK

Install the SDK for Python, TypeScript/JavaScript, or Go to connect to Zep Cloud.

Before you start

  • A Zep Cloud account; the README directs users to sign up at getzep.com.

Steps

  1. Choose the SDK for your language.

  2. For Python, run the command below; for TypeScript/JavaScript, run the command below; or for Go, run the command below.

    Documented command
    pip install zep-cloud
    Documented command
    npm install @getzep/zep-cloud
    Documented command
    go get github.com/getzep/zep-go/v3

  3. Read the Zep Cloud documentation at help.getzep.com.

Expected outcome

The selected SDK installation command is provided, and the README points to the service documentation for next steps.

Guide limitations

  • The repository contains examples and tools, not the Zep Cloud product or service.
Documentation 1 ↗
Evidence and transparency

Sources & review

Official repository ↗
Source record details
Source availability
Active
Sources checked
7 October 2026
Original website title
getzep/zep · Official homepage title · retained in its source language
How we review sourcesSuggest a correction