Zep website screenshot

Zep

Zep is a context engineering and agent memory platform that assembles relevant context from chat history, business data, and user interactions for AI agents. It builds a temporal knowledge graph per user that evolves as new facts arrive, automatically extracts entities, and invalidates facts that are superseded. Zep exposes a Graph RAG layer with customizable context blocks for fast personalization. The platform offers Cloud and self-hosted community editions with Python, TypeScript, and Go SDKs and integrations with LangChain, LangGraph, LlamaIndex, CrewAI, and AutoGen. Zep targets sub-200ms p95 retrieval latency and is SOC 2 Type II and HIPAA aligned for enterprise deployments.

Zep publishes 1 API on the APIs.io network. Tagged areas include Memory, AI Agents, Knowledge Graph, Temporal Graph, and Graph RAG.

Zep’s developer surface includes documentation, engineering blog, pricing, and 15 more developer resources.

43.2/100 developing ▬ flat Agent 5/100 human only open core · Apache-2.0 Full breakdown ↓
scored 2026-09-08 · rubric v0.20.0
AccessFree
1 APIs
MemoryAI AgentsKnowledge GraphTemporal GraphGraph RAGContext EngineeringLangChainLlamaIndexCrewAILLMsPersonalizationRetrieval

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-09-08 · rubric v0.20.0
Open Source Surface applies to this provider. This product is open source and we read its repository directly, so Open Source Surface carries 10 points of the composite. It is scored from what the repository actually publishes — a security policy, a contribution guide, a release history, a code of conduct — read live from the provider rather than inferred from our own catalog pointers. This facet adds; nothing was taken away to make room for it. An open-source project is not excused from the commercial facets, because exemption would strip it of the points it does earn. If we have the wrong repository, or this product is not open source, say so on your provider repo and we will drop the facet rather than have you publish against it.
Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.
The six quality facets above are damped to 90 points between them, because the conditional facet above carries the other 10. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 90% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from github.com/api-evangelist/zep: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

APIs 1

Individual APIs this provider publishes, each with its own machine-readable definition.

Zep Cloud API

The Zep Cloud API delivers agent memory and temporal knowledge graph services over REST. It exposes endpoints for users, sessions, messages, memory retrieval, the per-user graph...

Pricing Plans 1

Published pricing tiers and plan structures.

Zep Plans Pricing

1 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Zep Rate Limits

2 limits

RATE LIMITS

FinOps 1

Cost, billing, and metering signals for API financial operations.

Zep Finops

FINOPS

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Zep Domain Security

TLSv1.3 · HSTS · DNSSEC · DMARC

SECURITY

Zep Trust Center

SOC 2, HIPAA

SECURITY

Resources

Documentation 2

Reference material describing how the API behaves

Build 2

SDKs, sample code, and the tooling you integrate with

Access & Security 3

Authentication, authorization, and security posture

Operate 3

Status, limits, changes, and where to get help

Commercial 4

Pricing, plans, and the legal terms of use

Company 3

The organization behind the API

Other 1

Properties that don't map to a standard resource type

Source (apis.yml)

apis.yml Raw ↑
aid: zep
name: Zep
description: Zep is a context engineering and agent memory platform that assembles relevant context from chat history, business
  data, and user interactions for AI agents. It builds a temporal knowledge graph per user that evolves as new facts arrive,
  automatically extracts entities, and invalidates facts that are superseded. Zep exposes a Graph RAG layer with customizable
  context blocks for fast personalization. The platform offers Cloud and self-hosted community editions with Python, TypeScript,
  and Go SDKs and integrations with LangChain, LangGraph, LlamaIndex, CrewAI, and AutoGen. Zep targets sub-200ms p95 retrieval
  latency and is SOC 2 Type II and HIPAA aligned for enterprise deployments.
type: Index
deliveryModel:
  model: open-core
  license: Apache-2.0
  open_source: true
  commercial: true
  callable_host: false
  label: Open core · an OSS project plus a commercial hosted product
  confidence: high
  source:
  - license
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: free
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Free
  confidence: medium
  source:
  - plans
  generated: '2026-07-22'
  method: derived
position: Producing
access: 3rd-Party
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/zep.png
tags:
- Memory
- AI Agents
- Knowledge Graph
- Temporal Graph
- Graph RAG
- Context Engineering
- LangChain
- LlamaIndex
- CrewAI
- LLMs
- Personalization
- Retrieval
url: https://raw.githubusercontent.com/api-evangelist/zep/refs/heads/main/apis.yml
created: '2026-05-23'
modified: '2026-05-23'
specificationVersion: '0.23'
apis:
- aid: zep:cloud-api
  name: Zep Cloud API
  description: The Zep Cloud API delivers agent memory and temporal knowledge graph services over REST. It exposes endpoints
    for users, sessions, messages, memory retrieval, the per-user graph, facts, summaries, and customizable context blocks
    for prompt assembly.
  humanURL: https://help.getzep.com
  baseURL: https://api.getzep.com/api/v2
  tags:
  - Memory
  - Graph
  - Sessions
  - User
  - Facts
  - Context
  - REST
  tags_raw:
  - Memory
  - Graph
  - Sessions
  - Users
  - Facts
  - Context
  - REST
  properties:
  - type: Documentation
    url: https://help.getzep.com
  - type: GettingStarted
    url: https://help.getzep.com/v2/quickstart
  - type: Signup
    url: https://app.getzep.com
  - type: SDKs
    url: https://github.com/getzep/zep-python
  - type: SDKs
    url: https://github.com/getzep/zep-js
  - type: SDKs
    url: https://github.com/getzep/zep-go
  - type: GitHubRepository
    url: https://github.com/getzep/zep
  - type: Pricing
    url: https://www.getzep.com/pricing
  - type: Authentication
    url: https://help.getzep.com/projects
  features:
  - name: Temporal Knowledge Graph
    description: Per-user knowledge graph that captures entities, relationships, and time-aware facts.
  - name: Memory and Sessions
    description: Manage users and chat sessions, with messages persisted for retrieval and summarization.
  - name: Automatic Fact Extraction
    description: Extract structured facts from messages and invalidate facts that are superseded.
  - name: Graph RAG
    description: Retrieve graph-grounded context for prompts using semantic and graph traversal queries.
  - name: Customizable Context Blocks
    description: Compose reusable, customizable blocks of context to inject into agent prompts.
  - name: Custom Entity Types
    description: Define domain-specific entity types to capture vertical-specific knowledge.
  - name: Multi-Source Ingestion
    description: Ingest from chat, documents, and structured JSON to enrich the graph.
  - name: Low-Latency Retrieval
    description: Sub-200ms p95 retrieval latency for use in real-time agent loops.
  - name: Enterprise Compliance
    description: SOC 2 Type II and HIPAA-aligned controls for regulated workloads.
  useCases:
  - name: Personal AI Assistants
    description: Maintain long-term user memory across conversations and devices.
  - name: Customer Support Copilots
    description: Provide agents with persistent customer history and account facts.
  - name: Sales Agents
    description: Track deal context, stakeholders, and prior interactions per account.
  - name: Healthcare Workflows
    description: Persist patient context with HIPAA-aligned controls and audit trails.
  - name: Voice Agents
    description: Inject low-latency context blocks into real-time voice agent prompts.
  integrations:
  - name: LangChain
  - name: LangGraph
  - name: LlamaIndex
  - name: CrewAI
  - name: AutoGen
  - name: OpenAI
  - name: Anthropic
  - name: Vercel AI SDK
  - name: Pipecat
  - name: LiveKit
  authentication:
  - type: API Key
    description: Zep Cloud uses an Api-Key header with project keys prefixed with z_; self-hosted uses Bearer tokens.
common:
- type: IssueTracker
  url: https://github.com/getzep/zep/issues
- type: Releases
  url: https://github.com/getzep/zep/releases
- type: SecurityPolicy
  url: https://github.com/getzep/zep/blob/main/SECURITY.md
- type: CodeOfConduct
  url: https://github.com/getzep/zep/blob/main/CODE_OF_CONDUCT.md
- type: ContributionGuide
  url: https://github.com/getzep/zep/blob/main/CONTRIBUTING.md
- type: License
  name: Apache-2.0
  url: https://github.com/getzep/zep/blob/main/LICENSE
- type: TrustCenter
  url: security/zep-trust-center.yml
- type: DomainSecurity
  url: security/zep-domain-security.yml
- type: Website
  url: https://www.getzep.com
- type: Documentation
  url: https://help.getzep.com
- type: Blog
  url: https://blog.getzep.com
- type: GitHubOrganization
  url: https://github.com/getzep
- type: Pricing
  url: https://www.getzep.com/pricing
- type: TermsOfService
  url: https://www.getzep.com/terms-of-service
- type: PrivacyPolicy
  url: https://www.getzep.com/privacy-policy
- type: Discord
  url: https://discord.com/invite/W8Kw6bsgXQ
- type: X
  url: https://x.com/zep_ai
- type: LinkedIn
  url: https://www.linkedin.com/company/zep-ai
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this
  • find_providersBrowse and filter every provider in the catalog.
  • get_provider_artifactsEvery artifact this provider publishes, grouped by type.
  • get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
  • get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
  • get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
  • get_provider_ratingPRO — composite, band, trend and facet scores.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This provider
curl "https://apis.io/api/v1/providers/zep"
All providers
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose
curl "https://apis.io/api/v1/providers/zep/operations?limit=25"
How their score was established
curl "https://apis.io/api/v1/providers/zep/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.