QUICKSTART

Store → Retrieve → Verify → Prove in 5 minutes

Prerequisites

  • Google Chrome (or any Chromium browser)
  • A ChainMemory account — create one here
  • Your API Key — Extension → Settings → Connection → View

Option A — Chrome Extension (fastest)

1

Install & sign in

Download from the Chrome Web Store. Sign in with your account. The extension icon appears in your toolbar.

2

Store — save a memory

Open any AI chat (ChatGPT, Claude, Gemini). Have a conversation where you make a decision — e.g., "We'll use PostgreSQL for the user database." Click the ChainMemory icon and save. The extension extracts the content and creates a memory linked to your project.

3

Retrieve — inject into a new session

Open a different AI (or a new conversation in the same one). Click the ChainMemory icon → "Inject Context." Your previous decision arrives automatically — the AI now knows about the PostgreSQL choice without you repeating anything.

4

Verify — check the hash

In the Extension, open Project Brain. You will see your project state with decisions, risks and priorities, plus its on-chain anchor. The state carries a SHA3-256 hash computed over the canonical JSON of the state itself, domain-separated with CM_PROJECT_STATE_V<schema_version> — exactly what the open reference verifier recomputes.

5

Prove — anchor on-chain

There is nothing to click: your memories are anchored on-chain automatically, about 30 seconds after saving. To check it yourself, call GET /v1/project/:name/state/anchor — it returns the anchored state_hash with its transaction and block, and needs no API key. Making a single memory permanently immutable (seal) is available through the MCP server and the REST API; the extension does not seal.

Result You've stored a decision, retrieved it in a different AI, verified its hash, and created an immutable on-chain proof. All in under 5 minutes.

Option B — MCP Server (for Claude / Cursor)

1

Configure MCP

Add the ChainMemory MCP server to your Claude Desktop or Cursor configuration. See MCP Setup for the full config.

2

Store

In Claude, say: "Remember: we decided to use PostgreSQL for the user database". The MCP tool chainmemory_remember fires automatically.

3

Retrieve

In a new conversation: "What database did we choose?". Claude calls chainmemory_recall and returns the stored decision with its evidence chain.

4

Verify & Prove

Ask for the on-chain proof: verify_project_state returns every anchored version with its state_hash, anchor id, transaction and block — free, and verifiable by anyone without your API key. To make a single memory permanently immutable, chainmemory_seal takes the memory number and your ai_id.

Option C — REST API (full control)

bash
# 1. Store a memory
curl -X POST https://api.chainmemory.ai/v1/memory \
  -H "x-api-key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"summary":"Decided to use PostgreSQL for user DB","category":"decision","importance":8}'

# 2. Retrieve memories
curl https://api.chainmemory.ai/v1/memories/list?project=my-project \
  -H "x-api-key: YOUR_API_KEY"

# 3. Get project state (includes hash)
curl https://api.chainmemory.ai/v1/project/my-project/state \
  -H "x-api-key: YOUR_API_KEY"

# 4. Verify anchor (public — no auth needed)
curl https://api.chainmemory.ai/v1/project/my-project/state/anchor

Option D — Hermes Agent

Hermes Agent is an open-source AI agent framework. Use ChainMemory inside Hermes via the MCP server (native tools in chat) or the cm.py CLI wrapper (full terminal control).

Configure MCP

Edit ~/.hermes/config.yaml and add:

YAML
mcp_servers:
  chainmemory:
    command: "python"
    args: ["C:\\Users\\<user>\\.hermes\\skills\\chainmemory-mcp\\chainmemory_mcp_server.py"]
    env:
      CHAINMEMORY_API_KEY: "aic_..."

Restart Hermes. Tools appear as mcp_chainmemory_* in chat.

Or use cm.py CLI

Install the ChainMemory skill and use cm save, cm recall, cm state from terminal.

Verify

In Hermes chat: "Remember: we decided to use PostgreSQL". Or run cm whoami in terminal.

What's next Explore how event sourcing works, learn about the trust model, or dive into the full API reference.