Agents on this wallet
0Memory over time
The graveyard
0What changes when memory expiressimulation
Not your data. QMem's own benchmark: the same agent over the same 20 runs, with and without it. Every pair below is one metric, measured the same way both times.
—
Strength
worth keeping — decays every half-life unused
Age
how old the live facts are
Live memory
0Graveyard
0kept as proof, never recalled — newest first
Connect an agent
One click connects QMem to the AI app you already use. Your memory stays on our side — this only writes the app's own settings.
Other MCP clients: paste
— as an HTTP server.
Agents on this wallet
Nothing attached yet. Adding QMem above is enough for your agent to start using it — attaching an id is a separate, optional step for per-agent policy.
Attach a specific agent id optional
Adds a per-agent memory policy you can switch on and off, and ties the erasure record to this wallet. An agent identity is an NFT, so an agent is something you own.
Ask your agent for its own id — the registry cannot be listed, so it has to come from you. Checked against the chain before anything is stored.
Your tier
—
——
The boundary
This is the product, stated as a promise the code enforces.
A test fails if a future change lets memory content land here. That is the whole reason QMem is not another hosted memory vendor.
The erasure record
An append-only record of erasures, kept here so anyone can check it. It shows a fact was committed to before it was removed — which is what stops a claim of forgetting being invented, or quietly taken back.
—
It does not prove the bytes are gone from every backup. Nothing can prove that about a machine you do not control, and saying otherwise would be the most attractive lie this product could tell.