“Trustless agents cannot work without trustless agentic memory.”
Verifiable memory for AI agents.
Persistent. Signed. Anchored on-chain. Memories your agents can carry across providers, sessions, and tools — and any third party can verify.
- Users
- — Distinct
- Memories
- — Saved
- On-chain
- — Anchored
- Bits / dim
- 2–4 TurboQuant
- Anchor
- Solana SPL Memo
- Storage
- Arweave Permanent
Quickstart · 5 steps
From zero to cross-device recall.
The whole loop — sign on Device A, recall on Device B — runs entirely through the webapp and your IDE of choice.
- 01~5sOpen
Open the install page
Go to mnemonik.xyz/install in your everyday browser. One page handles identity, IDE wiring, and OAuth in a single flow.
- 021 clickIdentity
Create your identity
Your browser generates an Ed25519 keypair locally. The private key never leaves the device. The public key is your identity across every IDE, every device, every model.
- 03Any MCP clientInstall
Install into the IDE of your choice
Cursor, Claude Desktop, VS Code, Windsurf — pick your tool, click install, finish OAuth. The Mnemonic tools appear in your IDE's tool list automatically.
- 04mnemonic_sign_memorySign
Ask your agent to store something
Just talk to it. "Remember that we shipped v0.2 on Tuesday with Alex as release owner." The agent calls mnemonic_sign_memory; the record is signed and anchored on-chain.
- 05mnemonic_recallRecall
Recall it from another device, another IDE
Re-import the same identity on a different device. Ask the agent: "What did we decide about the v0.2 release?" It searches by meaning, not keyword, and returns your signed memories — verifiable by anyone.
Next
Start with the install page. Generation, signing, and recall all happen behind the same OAuth handshake.
Under the hood · 4 parts
How it works.
Four moving parts. Each one inspectable, each one independently verifiable, no opaque vendor in the path.
- 01ed25519Identity
Generate an Ed25519 keypair
The keypair lives in your browser's local storage. The public key is your portable identity across providers; the secret never leaves the device.
- 02OAuth 2.1Install
Connect Mnemonic to your AI tool
Cursor and VS Code accept a deeplink; Claude.ai takes a custom connector URL; Windsurf takes a JSON snippet. All four negotiate OAuth 2.1 + PKCE against mcp.mnemonik.xyz.
- 03COSE_Sign1Sign
Sign memories from any tool
When the agent calls mnemonic_sign_memory, the server prepares the canonical-CBOR payload and redirects here; you approve in-browser, your keypair signs a COSE_Sign1 envelope, and the server persists the attestation.
- 04Arweave + SolanaRecall
Recall and verify across providers
Any tool authenticated with the same keypair can recall by semantic similarity and verify the Arweave + Solana anchors. Tampering is detectable; provenance is cryptographic.