Skip to main content

Memori Python SDK

Project description

Memori Labs

Memory from what agents do, not just what they say.

Memori plugs into the software and infrastructure you already use. It is LLM, datastore and framework agnostic and seamlessly integrates into the architecture you've already designed.

Memori Cloud — Zero config. Get an API key and start building in minutes.

MemoriLabs%2FMemori | Trendshift

PyPI version NPM version Downloads License Discord

Give a Star

Choose memory that performs

Memori Labs


Getting Started

Installation

TypeScript SDK
npm install @memorilabs/memori
Python SDK
pip install memori

Quickstart

Sign up at app.memorilabs.ai, get a Memori API key, and start building. Full docs: memorilabs.ai/docs/memori-cloud/.

Set MEMORI_API_KEY and your LLM API key (e.g. OPENAI_API_KEY), then:

TypeScript SDK
import { OpenAI } from 'openai';
import { Memori } from '@memorilabs/memori';

// Requires MEMORI_API_KEY and OPENAI_API_KEY in your environment
const client = new OpenAI();
const mem = new Memori().llm
  .register(client)
  .attribution('user_123', 'support_agent');

async function main() {
  await client.chat.completions.create({
    model: 'gpt-4o-mini',
    messages: [{ role: 'user', content: 'My favorite color is blue.' }],
  });
  // Conversations are persisted and recalled automatically in the background.

  const response = await client.chat.completions.create({
    model: 'gpt-4o-mini',
    messages: [{ role: 'user', content: "What's my favorite color?" }],
  });
  // Memori recalls that your favorite color is blue.
}
Python SDK
from memori import Memori
from openai import OpenAI

# Requires MEMORI_API_KEY and OPENAI_API_KEY in your environment
client = OpenAI()
mem = Memori().llm.register(client)

mem.attribution(entity_id="user_123", process_id="support_agent")

response = client.chat.completions.create(
    model="gpt-4o-mini",
    messages=[{"role": "user", "content": "My favorite color is blue."}]
)
# Conversations are persisted and recalled automatically.

response = client.chat.completions.create(
    model="gpt-4o-mini",
    messages=[{"role": "user", "content": "What's my favorite color?"}]
)
# Memori recalls that your favorite color is blue.

Explore the Memories

Use the Dashboard — Memories, Analytics, Playground, and API Keys.

[!TIP] Want to use your own database? Check out docs for Memori BYODB here: https://memorilabs.ai/docs/memori-byodb/. For disposable BYODB development databases, see the TiDB Zero provisioning guide: docs/memori-byodb/databases/tidb.mdx.

LoCoMo Benchmark

Memori was evaluated on the LoCoMo benchmark for long-conversation memory and achieved 81.95% overall accuracy while using an average of 1,294 tokens per query. That is just 4.97% of the full-context footprint, showing that structured memory can preserve reasoning quality without forcing large prompts into every request.

Compared with other retrieval-based memory systems, Memori outperformed Zep, LangMem, and Mem0 while reducing prompt size by roughly 67% vs. Zep and lowering context cost by more than 20x vs. full-context prompting.

Read the benchmark overview, see the results, or download the paper.

"Memori's average accuracy along with the standard deviation"

OpenClaw (Persistent Memory for Your Gateway)

By default, OpenClaw agents forget everything between sessions. The Memori plugin fixes that. It automatically captures structured memory from conversation and agent execution after each turn — including tool calls, decisions, and outcomes — and makes it available for agents to recall on demand.

No changes to your agent code or prompts are required. The plugin hooks into OpenClaw's lifecycle, so you get structured memory, agent-controlled recall, and Advanced Augmentation with a drop-in plugin.

openclaw plugins install @memorilabs/openclaw-memori
openclaw plugins enable openclaw-memori

openclaw memori init \
  --api-key "YOUR_MEMORI_API_KEY" \
  --entity-id "your-app-user-id" \
  --project-id "my-project"

openclaw gateway restart

For setup and configuration, see the OpenClaw Quickstart. For architecture and lifecycle details, see the OpenClaw Overview.

Hermes Agent (Persistent Memory Provider)

Memori also ships as a Hermes Agent memory provider. It captures completed conversations in the background and gives Hermes explicit memori_recall and memori_recall_summary tools for agent-controlled recall.

pip install hermes-memori
hermes-memori install

hermes config set memory.provider memori
HERMES_HOME="${HERMES_HOME:-$HOME/.hermes}"
mkdir -p "$HERMES_HOME"
echo "MEMORI_API_KEY=YOUR_MEMORI_API_KEY" >> "$HERMES_HOME/.env"
echo "MEMORI_ENTITY_ID=your-app-user-id" >> "$HERMES_HOME/.env"

MEMORI_PROJECT_ID is optional; when omitted, the provider uses Hermes' active project context for scoping.

For setup and configuration, see the Hermes Quickstart. For architecture and lifecycle details, see the Hermes Overview.

MCP (Connect Your Agent in One Command)

Your agent forgets everything between sessions. Memori fixes that. It remembers your stack, your conventions, and how you like things done so you stop repeating yourself.

Works for solo developers and teams. Your agent learns coding patterns, reviewer preferences, and project conventions over time. For teams, that means shared context that new engineers pick up on day one instead of absorbing tribal knowledge over months.

If you use Claude Code, Cursor, Codex, Warp, or Antigravity, you can connect Memori with no SDK integration needed:

claude mcp add --transport http memori https://api.memorilabs.ai/mcp/ \
  --header "X-Memori-API-Key: ${MEMORI_API_KEY}" \
  --header "X-Memori-Entity-Id: your_username" \
  --header "X-Memori-Process-Id: claude-code"

For Cursor, Codex, Warp, and other clients, see the MCP client setup guide.

Attribution

To get the most out of Memori, you want to attribute your LLM interactions to an entity (think person, place or thing; like a user) and a process (think your agent, LLM interaction or program).

If you do not provide any attribution, Memori cannot make memories for you.

TypeScript SDK
mem.attribution("12345", "my-ai-bot");
Python SDK
mem.attribution(entity_id="12345", process_id="my-ai-bot")

Session Management

Memori uses sessions to group your LLM interactions together. For example, if you have an agent that executes multiple steps you want those to be recorded in a single session.

By default, Memori handles setting the session for you but you can start a new session or override the session by executing the following:

TypeScript SDK
mem.resetSession();
// or
mem.setSession(sessionId);
Python SDK
mem.new_session()
# or
mem.set_session(session_id)

Supported LLMs

  • Anthropic
  • Bedrock
  • DeepSeek
  • Gemini
  • Grok (xAI)
  • OpenAI (Chat Completions & Responses API)

(unstreamed, streamed, synchronous and asynchronous)

Supported Frameworks

  • Agno
  • LangChain
  • Pydantic AI

Supported Platforms

  • DeepSeek
  • Nebius AI Studio

Examples

For more examples and demos, check out the Memori Cookbook.

Memori Advanced Augmentation

Memories are tracked at several different levels:

  • entity: think person, place, or thing; like a user
  • process: think your agent, LLM interaction or program
  • session: the current interactions between the entity, process and the LLM

Memori's Advanced Augmentation enhances memories at each of these levels with:

  • attributes
  • events
  • facts
  • people
  • preferences
  • relationships
  • rules
  • skills

Memori knows who your user is, what tasks your agent handles and creates unparalleled context between the two. Augmentation occurs in the background incurring no latency.

By default, Memori Advanced Augmentation is available without an account but rate limited. When you need increased limits, sign up for Memori Advanced Augmentation or use the Memori CLI:

# Install the CLI via pip to manage your account
python -m memori sign-up <email_address>

Memori Advanced Augmentation is always free for developers!

Once you've obtained an API key, set the following environment variable (used by both Python and TypeScript SDKs):

export MEMORI_API_KEY=[api_key]

The Memori CLI uses your exported environment first, then fills missing values from a .env file in the directory where you run the command.

Managing Your Quota

At any time, you can check your quota using the Memori CLI (works for both SDKs):

python -m memori quota

Or by checking your account at https://app.memorilabs.ai/. If you have reached your IP address quota, sign up and get an API key for increased limits.

If your API key exceeds its quota limits we will email you and let you know.

Command Line Interface (CLI)

The Memori CLI is the unified tool for managing your account, keys, and quotas across all SDKs. To use it, execute the following from the command line:

# Requires Python installed
python -m memori

This will display a menu of the available options. For more information about what you can do with the Memori CLI, please reference Command Line Interface.

Contributing

We welcome contributions from the community! Please see our Contributing Guidelines for details on:

  • Setting up your development environment
  • Code style and standards
  • Submitting pull requests
  • Reporting issues

Support


License

Apache 2.0 - see LICENSE

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

memori-3.3.6rc1.tar.gz (195.3 kB view details)

Uploaded Source

Built Distributions

If you're not sure about the file name format, learn more about wheel file names.

memori-3.3.6rc1-cp310-abi3-win_amd64.whl (4.8 MB view details)

Uploaded CPython 3.10+Windows x86-64

memori-3.3.6rc1-cp310-abi3-musllinux_1_2_x86_64.whl (9.3 MB view details)

Uploaded CPython 3.10+musllinux: musl 1.2+ x86-64

memori-3.3.6rc1-cp310-abi3-musllinux_1_2_aarch64.whl (9.5 MB view details)

Uploaded CPython 3.10+musllinux: musl 1.2+ ARM64

memori-3.3.6rc1-cp310-abi3-manylinux_2_28_x86_64.whl (8.1 MB view details)

Uploaded CPython 3.10+manylinux: glibc 2.28+ x86-64

memori-3.3.6rc1-cp310-abi3-manylinux_2_28_aarch64.whl (8.5 MB view details)

Uploaded CPython 3.10+manylinux: glibc 2.28+ ARM64

memori-3.3.6rc1-cp310-abi3-macosx_11_0_x86_64.whl (5.4 MB view details)

Uploaded CPython 3.10+macOS 11.0+ x86-64

memori-3.3.6rc1-cp310-abi3-macosx_11_0_arm64.whl (5.2 MB view details)

Uploaded CPython 3.10+macOS 11.0+ ARM64

memori-3.3.6rc1-cp310-abi3-android_24_x86_64.whl (8.5 MB view details)

Uploaded Android API level 24+ x86-64CPython 3.10+

memori-3.3.6rc1-cp310-abi3-android_24_arm64_v8a.whl (8.9 MB view details)

Uploaded Android API level 24+ ARM64 v8aCPython 3.10+

File details

Details for the file memori-3.3.6rc1.tar.gz.

File metadata

  • Download URL: memori-3.3.6rc1.tar.gz
  • Upload date:
  • Size: 195.3 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/6.1.0 CPython/3.13.12

File hashes

Hashes for memori-3.3.6rc1.tar.gz
Algorithm Hash digest
SHA256 781e6ef5de84fef5d95be8e8ee0d1d7c1b6ab7587ab1968bf26e5bde2897f461
MD5 1c950982922d3f6a526d9f3e03c2c984
BLAKE2b-256 321783f5302825784bda8acfc6395bad188c7f7881147e2b7837fae5fbf4b93c

See more details on using hashes here.

File details

Details for the file memori-3.3.6rc1-cp310-abi3-win_amd64.whl.

File metadata

  • Download URL: memori-3.3.6rc1-cp310-abi3-win_amd64.whl
  • Upload date:
  • Size: 4.8 MB
  • Tags: CPython 3.10+, Windows x86-64
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/6.1.0 CPython/3.13.12

File hashes

Hashes for memori-3.3.6rc1-cp310-abi3-win_amd64.whl
Algorithm Hash digest
SHA256 54360af84c35d2d725901ce7b49a5a055b4691078f719b7cd5edbf163c4781d5
MD5 1d28bd6a6697434662789e00acd6e47e
BLAKE2b-256 5a708429c04d322da1e1a3a76e8a555a8a21b03d4715f9aaa47affca6a79b2ec

See more details on using hashes here.

File details

Details for the file memori-3.3.6rc1-cp310-abi3-musllinux_1_2_x86_64.whl.

File metadata

File hashes

Hashes for memori-3.3.6rc1-cp310-abi3-musllinux_1_2_x86_64.whl
Algorithm Hash digest
SHA256 a04fa5caf7033eee052b8a7c931d39b962a53d64891240dbef4d6f2e76489528
MD5 c9136e99cede8d509705178e072a40c2
BLAKE2b-256 a95404a8ad50aba9ee33212da7bd98f28e148a1ee295409bfaa5dc3c740ff6a5

See more details on using hashes here.

File details

Details for the file memori-3.3.6rc1-cp310-abi3-musllinux_1_2_aarch64.whl.

File metadata

File hashes

Hashes for memori-3.3.6rc1-cp310-abi3-musllinux_1_2_aarch64.whl
Algorithm Hash digest
SHA256 1a29ee8b14bbe8bcc081c1f4d6b9c418c677510bfab8c9b14aaa109a72639a38
MD5 0c7575c8c841a705f31e5e8997e8f492
BLAKE2b-256 d8c6ef76dc0435c4e36a85cbebb19704dad5f4b2a5b5e20b8294b6aa38b3af59

See more details on using hashes here.

File details

Details for the file memori-3.3.6rc1-cp310-abi3-manylinux_2_28_x86_64.whl.

File metadata

File hashes

Hashes for memori-3.3.6rc1-cp310-abi3-manylinux_2_28_x86_64.whl
Algorithm Hash digest
SHA256 d58a4586361703ff8a323e3738ea47cc7be90bb5787f17a1b10f0bd023a072b2
MD5 bc231196160921b8e8da7533065f5779
BLAKE2b-256 6aea0beb2caf7fde2eaac814fd8889a19154cbfec195275d6e5433519aedb40c

See more details on using hashes here.

File details

Details for the file memori-3.3.6rc1-cp310-abi3-manylinux_2_28_aarch64.whl.

File metadata

File hashes

Hashes for memori-3.3.6rc1-cp310-abi3-manylinux_2_28_aarch64.whl
Algorithm Hash digest
SHA256 789027e85914dcee9c69bd2306f833c09f4bd0956ff1a6ac09dca8c7e62c4692
MD5 2e013b96cdcb99189a94ddc3eae60a33
BLAKE2b-256 c057a75b8131b1097fd9c7a03bb745cc4b26ce52add5a74becdf55587b9bb237

See more details on using hashes here.

File details

Details for the file memori-3.3.6rc1-cp310-abi3-macosx_11_0_x86_64.whl.

File metadata

File hashes

Hashes for memori-3.3.6rc1-cp310-abi3-macosx_11_0_x86_64.whl
Algorithm Hash digest
SHA256 192e0e45c187361fade656e557062e24eeb7903e41c61d4307a6dc8e5e63614e
MD5 c7f2e5b1211837a4efe65df0f3997804
BLAKE2b-256 3318a6bc9d7591fbf449b7b8ea82793d5a18a4f07dcefa31c48f30d55765e007

See more details on using hashes here.

File details

Details for the file memori-3.3.6rc1-cp310-abi3-macosx_11_0_arm64.whl.

File metadata

File hashes

Hashes for memori-3.3.6rc1-cp310-abi3-macosx_11_0_arm64.whl
Algorithm Hash digest
SHA256 24223a2e8ad730aa7ee6e130d2e5dc120b42fccb449b70bbbd17dbe3c56efb1f
MD5 131d1f664bf923ae9ae698eebc167322
BLAKE2b-256 3eea246952b892a030413254010c3a8aba67ca69672511d07798a021b65283db

See more details on using hashes here.

File details

Details for the file memori-3.3.6rc1-cp310-abi3-android_24_x86_64.whl.

File metadata

File hashes

Hashes for memori-3.3.6rc1-cp310-abi3-android_24_x86_64.whl
Algorithm Hash digest
SHA256 b2d8e0965b9427ff1894c76dfb198b0d17b29139c6ccdc186cca5cf0bc571ae4
MD5 012c093401ca90bb4425c24ba3d89772
BLAKE2b-256 727ed2980ebc4af8382d4adbcbacb986078b517d1f14f1111af8d81269c0ce89

See more details on using hashes here.

File details

Details for the file memori-3.3.6rc1-cp310-abi3-android_24_arm64_v8a.whl.

File metadata

File hashes

Hashes for memori-3.3.6rc1-cp310-abi3-android_24_arm64_v8a.whl
Algorithm Hash digest
SHA256 7e36a7dd45744dc16f4e0d70fcfe72cca9826e5f60fc469cf91ee7efdde50dce
MD5 2a163da342ad7ff998197ce99e3252eb
BLAKE2b-256 3d42dfbdbb7d28d72cce421edcb3eb19395974d6f3479b3704b51a41cfe9e808

See more details on using hashes here.

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Pingdom Monitoring Sentry Error logging StatusPage Status page