- Readable memory
- Encrypted
- Erased
Portable memory for AI agents.
Memory you can take with you. Forgetting it, provable.
Keep your agent's memory when you switch models. Sell what it knows. When someone asks to be forgotten, record a SHA-256 deletion attestation and a tombstone on-chain.
Encrypted at rest, not end-to-end. The hosted API can read memory while processing it. Self-host to control the server and its keys.
Free tier · 1,000 memories a month · no card
01
Portable memory
Memory lives in a vault with API-key access, not in a model vendor's memory silo. Export it as JSON and import it anywhere.
02
Provable erasure
Forgetting records a SHA-256 deletion attestation and a tombstone on Monad. Raw content never goes on-chain.
03
Sell what it knows
List curated knowledge packs on the Memory Market. Sellers keep 80% of every sale, settled in USDC.
How it works
From first write to a deletion receipt in four steps.
01
Create a vault
One vault per agent, owned by your wallet or identifier. You get an API key.
02
Connect your agent
Add the MCP server to Claude Desktop, Cursor or Windsurf, or call the REST API.
03
Write and recall
The agent stores memories and recalls them by meaning, using vector search.
04
Attest and forget
Writes are hashed on-chain. Deletions leave a tombstone you can show an auditor.
Deletion proof
Erasure you can show to an auditor.
When a user invokes GDPR Article 17, MNEME removes the memory from your vault, then records a hash of the deletion and a tombstone on Monad. The chain holds no personal data.
- SHA-256 deletion attestation, written by DeletionProver.sol
- Immutable tombstone, so the erasure cannot be quietly undone
- Not a zero-knowledge proof. It proves a deletion was recorded, not that no copy exists elsewhere.
- Request
- The erasure request, such as GDPR Art. 17
- Memory
- ID of the removed memory. The content is gone.
- Tombstone
- Hash of the on-chain tombstone transaction
- Contract
- DeletionProver.sol
- Network
- Monad
What every deletion receipt records
For developers
One config block and your agent has memory.
MNEME ships a Model Context Protocol server. It works with Claude Desktop, Cursor, Windsurf and any MCP client.
mcp.json (Cursor) / mcp_config.json (Windsurf Cascade)
{
"mcpServers": {
"mneme-memory": {
"url": "https://trymneme-api.onrender.com/mcp?vault=YOUR_VAULT_UUID",
"headers": {
"Authorization": "Bearer YOUR_API_KEY"
}
}
}
}Memory Market
Turn what your agent learned into a product.
List a curated pack of domain knowledge. Every submission is scanned for personal data before it goes live, and sellers keep 80% of each sale in USDC.
Knowledge pack · how a sale splits
You set the price in USDC.
List a pack of your agent's memories. Buyers pay on-chain and ingest the pack into their own vault.
Every listing is PII-scanned first
FAQ
Straight answers.
Can the hosted server read my memories?
Yes. Content is encrypted at rest, but the API holds the server secret used to derive vault keys and decrypts content while processing requests. This is not end-to-end encryption. Self-hosting lets you control that server and its secret.
Does my data go on-chain?
No. Only hashes and tombstones are written to Monad. Memory content stays in your vault.
Is the deletion proof a zero-knowledge proof?
No. It is a SHA-256 deletion attestation plus an on-chain tombstone. It shows a deletion was recorded at a point in time.
Which agents work with it?
Any MCP client, including Claude Desktop, Cursor and Windsurf. There is also a REST API and SDKs for TypeScript and Python.
What does it cost to start?
The free tier includes 1,000 memories a month and needs no credit card.
Can I leave?
Yes. Export the whole vault as JSON at any time and import it into another vault.
Start
Give your agent a memory it keeps.
Create a vault in under a minute. Free tier, 1,000 memories a month, no credit card.