Zep Python Library
The Zep Python library provides convenient access to the Zep APIs from Python.
Table of Contents
- What Is Zep 💬
- Installation
- Reference
- Usage
- Environments
- Async Client
- Exception Handling
- Streaming
- Pagination
- Advanced
- Contributing
What is Zep? 💬
Zep is a context engineering platform for AI Assistant apps. With Zep, you can provide AI assistants with the ability to recall past conversations, no matter how distant, while also reducing hallucinations, latency, and cost.
Cloud Installation
You can install the Zep Cloud SDK by running:
pip install zep-cloud
How Zep works
Zep persists and recalls chat histories, and automatically generates summaries and other artifacts from these chat histories. It also embeds messages and summaries, enabling you to search Zep for relevant context from past conversations. Zep does all of this asynchronously, ensuring these operations don't impact your user's chat experience. Data is persisted to database, allowing you to scale out when growth demands.
Zep allows you to be more intentional about constructing your prompt:
- automatically adding a few recent messages, with the number customized for your app;
- a summary of recent conversations prior to the messages above;
- and/or contextually relevant summaries or messages surfaced from the entire chat session.
You will also need to provide a Zep Project API key to your zep client. You can find out about zep projects in our cloud docs
Installation
pip install zep-cloud
Reference
A full reference for this library is available here.
Usage
Instantiate and use the client with the following:
from zep_cloud import Zep
client = Zep(
api_key="<value>",
)
client.agent.create(
agent_id="payments-agent",
name="Refund a duplicate charge",
security_domain="customer:support",
)
Environments
This SDK allows you to configure different environments for API requests.
from zep_cloud import Zep
from zep_cloud.environment import ZepEnvironment
client = Zep(
environment=ZepEnvironment.DEFAULT,
)
Async Client
The SDK also exports an async client so that you can make non-blocking calls to our API. Note that if you are constructing an Async httpx client class to pass into this client, use httpx.AsyncClient() instead of httpx.Client() (e.g. for the httpx_client parameter of this client).
import asyncio
from zep_cloud import AsyncZep
client = AsyncZep(
api_key="<value>",
)
async def main() -> None:
await client.agent.create(
agent_id="payments-agent",
name="Refund a duplicate charge",
security_domain="customer:support",
)
asyncio.run(main())
Exception Handling
When the API returns a non-success status code (4xx or 5xx response), a subclass of the following error will be thrown.
from zep_cloud.core.api_error import ApiError
try:
client.agent.create(...)
except ApiError as e:
print(e.status_code)
print(e.body)
Streaming
The SDK supports streaming responses, as well, the response will be a generator that you can loop over.
from zep_cloud import Zep
client = Zep(
api_key="<value>",
)
client.graph.query_stream(
graph_uuids=[
"graph_uuids"
],
query="query",
)
Pagination
Paginated requests will return a SyncPager or AsyncPager, which can be used as generators for the underlying object.
from zep_cloud import Zep
client = Zep(
api_key="<value>",
)
client.agent.list()
# You can also iterate through pages and access the typed response per page
pager = client.agent.list(...)
for page in pager.iter_pages():
print(page.response) # access the typed response for each page
for item in page:
print(item)
Advanced
Access Raw Response Data
The SDK provides access to raw response data, including headers, through the .with_raw_response property.
The .with_raw_response property returns a "raw" client that can be used to access the .headers and .data attributes.
from zep_cloud import Zep
client = Zep(...)
response = client.agent.with_raw_response.create(...)
print(response.headers) # access the response headers
print(response.status_code) # access the response status code
print(response.data) # access the underlying object
Retries
The SDK is instrumented with automatic retries with exponential backoff. A request will be retried as long as the request is deemed retryable and the number of retry attempts has not grown larger than the configured retry limit (default: 2).
Which status codes are retried depends on the retryStatusCodes generator configuration:
legacy (current default): retries on
recommended: retries on
- 408 (Timeout)
- 409 (Conflict)
- 429 (Too Many Requests)
- 502 (Bad Gateway)
- 503 (Service Unavailable)
- 504 (Gateway Timeout)
Use the max_retries request option to configure this behavior.
client.agent.create(..., request_options={
"max_retries": 1
})
Timeouts
The SDK defaults to a 60 second timeout. You can configure this with a timeout option at the client or request level.
from zep_cloud import Zep
client = Zep(..., timeout=20.0)
# Override timeout for a specific method
client.agent.create(..., request_options={
"timeout": 1
})
Custom Client
You can override the httpx client to customize it for your use-case. Some common use-cases include support for proxies
and transports.
import httpx
from zep_cloud import Zep
client = Zep(
...,
httpx_client=httpx.Client(
proxy="http://my.test.proxy.example.com",
transport=httpx.HTTPTransport(local_address="0.0.0.0"),
),
)
Contributing
While we value open-source contributions to this SDK, this library is generated programmatically. Additions made directly to this library would have to be moved over to our generation code, otherwise they would be overwritten upon the next generated release. Feel free to open a PR as a proof of concept, but know that we will not be able to merge it as-is. We suggest opening an issue first to discuss with us!
On the other hand, contributions to the README are always very welcome!
1 maintainer
Metadata
1 maintainer
Release files for zep-cloud 4.0.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| zep_cloud-4.0.1.tar.gz | 304.8 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| zep_cloud-4.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 924.0 kB
Release files / zep_cloud-4.0.1.tar.gz
| Download URL | zep_cloud-4.0.1.tar.gz |
|---|---|
| Size | 304.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0c3cccfc7e1fe9868d8fecfded0c8a3a491827cbf72c947119ae6dd35f5a4ae0
|
|
BLAKE2b-256 checksum How to use checksums |
d9f29a249c73f198d863bfa2bf6bfe53d3e39f96eafd25624b74e47ceb75dd45
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 20, 2026.
Transparency logRelease files / zep_cloud-4.0.1-py3-none-any.whl
| Download URL | zep_cloud-4.0.1-py3-none-any.whl |
|---|---|
| Size | 619.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
53c1375569baef598309f2a3d96af2e4bb7ff1a3b4dc2506d5cbc5fe6269c309
|
|
BLAKE2b-256 checksum How to use checksums |
151283eecea93e0514e0183d01243e40ca24a035067ed693c7f5dd753b64ba2d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 20, 2026.
Transparency logSecurity for zep-cloud 4.0.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for zep_cloud-4.0.1.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 20, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
