ebbmem-client
Python client for the Ebb memory HTTP API. Version 0.2.0. Homepage: https://ebbmem.ai.
The import name is ebbmem_client. The in-process engine wheel already owns the ebbmem import.
This package is not yet published. When it is, install it from the package registry:
pip install ebbmem-client
Quickstart
from ebbmem_client import EbbmemClient
client = EbbmemClient() # reads EBBMEM_ORIGIN and EBBMEM_TOKEN
stored = client.memory.remember("the harbor light is cobalt")
found = client.memory.recall("harbor light")
AsyncEbbmemClient is a native async client. It uses httpx for HTTP and the generated models for request and response bodies.
Auth
EBBMEM_ORIGIN is required. There is no default origin. EBBMEM_TOKEN is sent as Authorization: Bearer. EBBMEM_API_KEY is sent as X-API-Key. EBBMEM_NAMESPACE is sent as X-Ebb-Namespace. An explicit argument overrides the matching environment variable. The token is omitted from repr.
Methods
client.memory exposes remember, remember_batch, recall, recall_federated, get, list, update, forget, reinforce, reflect, why_not, and status. client.tasks exposes get, list, and cancel. client.events.stream reads the SSE event stream. client.health calls the health endpoint.
Errors and retries
Failures raise EbbmemError with status, code (EBB-… from the error envelope), message, details, and request_id. Subclasses are AuthError (401/403), NotFoundError (404), ValidationError (400/422), RateLimitError (429, retry_after), ServerError (5xx), and ConnectionError.
The client retries connection errors, 429 (honoring Retry-After), and 502/503/504. Retries apply to idempotent methods, and to remember / remember_batch when an idempotency key is set. max_retries defaults to 2. timeout defaults to 30 seconds. The user agent is ebbmem-client-python/0.2.0.
Pagination
memory.list() follows next_cursor until has_more is false and yields each row.
Events
client.events.stream() yields parsed SSE data objects. Pass token only when the stream must authenticate with the query parameter.
Raw API
client.raw is the generated client (memory, tasks, events, health).
License
Proprietary, (c) Spectrayan.
Metadata
Release files for ebbmem-client 0.2.0
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 | |
|---|---|---|---|---|
| ebbmem_client-0.2.0.tar.gz | 68.8 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| ebbmem_client-0.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 232.1 kB
Release files / ebbmem_client-0.2.0.tar.gz
| Download URL | ebbmem_client-0.2.0.tar.gz |
|---|---|
| Size | 68.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7031a912996fed7fefe70cc723f114fa7ec55414c194605f2c8b3fc99635ed96
|
|
BLAKE2b-256 checksum How to use checksums |
b2d015a950b6d19061339a2e005df1cf37ae1d28e024dd42e88fdd901f9516a6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.7
|
Release files / ebbmem_client-0.2.0-py3-none-any.whl
| Download URL | ebbmem_client-0.2.0-py3-none-any.whl |
|---|---|
| Size | 163.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
34f7ea6b410558d590710e999f4fdfba3c8dab5106677298f4f81d7fb33ed784
|
|
BLAKE2b-256 checksum How to use checksums |
bba7dac7828a1528b7719ed738006206f12ebe33667e9999800868122f5016d1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.7
|
Security for ebbmem-client 0.2.0
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A 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.