ampup-memory

A thin Python client for an AmpUp Memory server: write what your team knows, search it, and read it back. One class, no codegen, and its only dependency is httpx.

pip install ampup-memory

Quickstart

from datetime import datetime, timezone
from ampup_memory import AmpUpMemory, micros

mem = AmpUpMemory.from_profile()  # the CLI's current context; or AmpUpMemory.from_profile("work")
# mem = AmpUpMemory("https://memory.example.com", "msk_...", org="acme")  # an explicit API key
# mem = AmpUpMemory("http://127.0.0.1:8080", None)  # a local `ampup-memory serve --local`

ep = mem.remember("note:acme", "The Acme renewal is owned by Priya.")
print(mem.episode(ep["episode_id"]))
print(mem.search("who owns the Acme renewal", k=5))
print(mem.query({"find": "passages", "text": "Acme renewal"})["results"])
mem.ingest([{"source": "email:1", "body": "...", "occurred_at": micros(datetime.now(timezone.utc)), "acl": ["group:sales"]}])

from_profile() uses the context and sign-in that ampup-memory-client join <server> --org <org> saved, in AMPUP_MEMORY_CONFIG_DIR (default ~/.ampup-memory). It picks the context from its argument, then AMPUP_MEMORY_CONTEXT, then the current one, and renews an expiring sign-in with the saved refresh token, writing it back where the CLI reads it.

Methods

Every failure raises AmpUpMemoryError with status, message and, on a 429, retry_after. An error the server reports inside a row (a bad query, say) raises it too, with status 200.

The TypeScript client with the same methods is @ampup/memory.

License

Apache-2.0.