hippmem-py
Python bindings for HIPPMEM — native associative memory engine for AI agents.
Ecosystem: Rust engine · Python bindings · MCP server
Install
pip install hippmem
No GPU, API key, or network required — the deterministic fallback backend works offline.
Quick Start
from hippmem import Engine
# Hash embedder — offline, zero config (default)
engine = Engine.open()
engine.write("The user prefers Rust.", content_type="Preference")
engine.write("The user chose redb — pure Rust, fast compile.", content_type="Decision")
results = engine.retrieve("Why did the user choose redb?", top_k=3)
for r in results.results:
print(f"[{r.score:.3f}] {r.content}")
print(f" dimensions: {r.dimensions}")
engine.close()
Neural embedder (higher semantic accuracy)
engine = Engine.open(
embedder="neural",
api_base_url="https://api.openai.com/v1",
api_key="sk-...",
model="text-embedding-3-small",
)
Why associative memory?
Most memory solutions are vector databases — store embeddings, search by similarity. HIPPMEM discovers associations between memories at write time (entity, causal, temporal, semantic, topic) and retrieves via spreading activation over typed edges. The result: it remembers WHY, not just WHAT.
Documentation
| Document | Content |
|---|---|
| Quick Start | 5-minute setup and first run |
| API Reference | Method signatures and types |
| Configuration | Storage location, backend selection |
For deeper architecture and algorithm details, see the main HIPPMEM documentation.
Development
git clone https://github.com/hippmem/hippmem-py.git
cd hippmem-py
python3 -m venv .venv && source .venv/bin/activate
pip install maturin pytest
maturin develop
pytest
License
Apache 2.0. See LICENSE and COPYRIGHT.
The underlying hippmem-engine is AGPL-3.0-only. Importing hippmem-py does NOT subject your program to AGPL — only the engine crate itself is AGPL. See the HIPPMEM licensing overview.
Metadata
Release files for hippmem 0.4.5
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 | Actions |
|---|---|---|---|---|
| hippmem-0.4.5.tar.gz | 45.8 kB | Without provenance | Details for hippmem-0.4.5.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| hippmem-0.4.5-cp39-cp39-macosx_11_0_arm64.whl | CPython 3.9 | CPython 3.9 | macOS 11.0+ ARM64 | Details for hippmem-0.4.5-cp39-cp39-macosx_11_0_arm64.whl |
Total release size: 7.0 MB
Release files / hippmem-0.4.5.tar.gz
| Download URL | hippmem-0.4.5.tar.gz |
|---|---|
| Size | 45.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f5efec30f7e0bff6d64e21f466f155152af37f0f31e33aae4dccc60c4b23608a
|
|
BLAKE2b-256 checksum How to use checksums |
4b9b2f5feb456e685cf3b6084ee25f7d0f7b1f46324576ca78bb90b8f1a8c438
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
maturin/1.14.1
|
Release files / hippmem-0.4.5-cp39-cp39-macosx_11_0_arm64.whl
| Download URL | hippmem-0.4.5-cp39-cp39-macosx_11_0_arm64.whl |
|---|---|
| Size | 6.9 MB |
| Tags | CPython 3.9 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
22e0b040691c68e182e3a4569d012145d64021716c76979342855e46e7ad4fdc
|
|
BLAKE2b-256 checksum How to use checksums |
6a42777534542cbcab310738db45685e4da0c4fc3d57155a06290cc0a8b121d7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
maturin/1.14.1
|
Security for hippmem 0.4.5
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.