Memories, collected with their labels.

Hosted long-term memory for AI agents. Every fact your agent recalls keeps the conversation it came from, and a correction is added on top, never written over.

2nd on the Agent Memory Leaderboard, October 2026.

Det. Prefers daily summaries
3 Aug 2026 · superseded

Det. Prefers weekly summaries
20 Aug 2026 · current

Memory
Prefers weekly summaries
Source
Conversation 184 · user-17
Collected
20 Aug 2026
Extractor
heuristic-v2
Confidence
0.96
Example record. Each memory carries its source and every earlier version.

Add evidence. Wait for it to settle. Recall what matters.

Three calls with your API key. Retrieval returns a bounded set of memories, each linked to the events it came from.

  1. 1 Save an event

    curl https://membraince.com/v1/events \
      -H "X-API-Key: YOUR_API_KEY" \
      -H "Content-Type: application/json" \
      -d '{
        "scope": {"tenant_id": "YOUR_TENANT_ID", "user_id": "user-17"},
        "content": "Send me a concise summary every Friday."
      }'
  2. 2 Check the job

    curl "https://membraince.com/v1/jobs/JOB_ID?tenant_id=YOUR_TENANT_ID&user_id=user-17" \
      -H "X-API-Key: YOUR_API_KEY"
    # Continue when status is "complete".
  3. 3 Retrieve memory

    curl https://membraince.com/v1/retrieve \
      -H "X-API-Key: YOUR_API_KEY" \
      -H "Content-Type: application/json" \
      -d '{
        "scope": {"tenant_id": "YOUR_TENANT_ID", "user_id": "user-17"},
        "query": "How should I send updates?",
        "limit": 5
      }'

Examples contain placeholders only. Keys are shown once in the portal; send them in headers, never in URLs or browser storage.

What every record keeps.

Provenance
Each memory links back to its source events, the extractor version that read them, and every lifecycle change. The memory trace API returns the whole trail.
History
When a fact changes, the new memory supersedes the old one. Nothing is silently overwritten.
Bounds
Results, token budgets, and graph traversal are capped by the request, so recall never floods a prompt.
Isolation
A key authorizes one tenant. Scope checks apply to events, jobs, memories, relations, traversal, and traces.
Guardrails
Per-key quotas, storage ceilings, immediate revocation, and audited cost controls are built in.

Give Claude a memory in one line.

The MemBraince plugin connects Claude Code to your memory. Claude recalls what matters when a session starts and with each prompt, and saves what you tell it when the session ends. It asks for your API key once and keeps it in your system's credential store.

On claude.ai or the Claude apps, add a custom connector with the URL https://membraince.com/v1/mcp and sign in with your MemBraince account. In the Claude Desktop app you can also download the Desktop extension and paste a key.

/plugin install membraince --marketplace danielflopez1/MemBraince
recall
Search memory for the task at hand.
remember
Save one durable fact or decision.
forget
Delete a memory by id.

Any MCP client can use the endpoint at https://membraince.com/v1/mcp with an X-API-Key header.

Pay per saved event.

Billing isn't live yet; these are the prices it will start with, billed monthly.

Standard

$0.0005 per save

Model-assisted extraction. Event content is sent to an OpenAI-compatible model to find the facts worth keeping.

Premium

$0.001 per save

Our best-scoring pipeline in internal benchmarks: local extraction and local reranking. No third-party model sees your saved content.

Know where memory goes.

Infrastructure is hosted on Fly.io in the United States. Approved offboarding revokes access immediately and purges live customer content within 7 calendar days. Volume snapshots are retained for 7 days, so purged content may remain in recovery copies until that window expires.

Model processing
On the Standard plan, event content is sent to the configured OpenAI-compatible endpoint for extraction. Premium never sends it to an outside model. Retrieval does not trigger paid extraction on either plan.
Encryption
Conversations and memories are encrypted with a key that only your API keys and your recovery code can unlock. MemBraince works with the plaintext only in memory while handling your requests, and can't read or recover what is stored.
Telemetry
No advertising trackers or browser analytics. Operational logs exclude request bodies, credentials, cookies, and raw query strings.
Control
Keys can be revoked immediately, tenants disabled, and quotas set, with every change in an append-only audit log.

Start a collection.

Create an account, make a key, and save your first memory in a few minutes.

Create an account