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.6rc2.tar.gz (195.5 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.6rc2-cp310-abi3-win_amd64.whl (4.8 MB view details)

Uploaded CPython 3.10+Windows x86-64

memori-3.3.6rc2-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.6rc2-cp310-abi3-musllinux_1_2_aarch64.whl (9.5 MB view details)

Uploaded CPython 3.10+musllinux: musl 1.2+ ARM64

memori-3.3.6rc2-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.6rc2-cp310-abi3-manylinux_2_28_aarch64.whl (8.5 MB view details)

Uploaded CPython 3.10+manylinux: glibc 2.28+ ARM64

memori-3.3.6rc2-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.6rc2-cp310-abi3-macosx_11_0_arm64.whl (5.2 MB view details)

Uploaded CPython 3.10+macOS 11.0+ ARM64

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

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

memori-3.3.6rc2-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.6rc2.tar.gz.

File metadata

  • Download URL: memori-3.3.6rc2.tar.gz
  • Upload date:
  • Size: 195.5 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.6rc2.tar.gz
Algorithm Hash digest
SHA256 f8df9a99938c745378e9dbd911be4cef8f9030a4f22c755c4f81683aab0f397b
MD5 6743855ea72965ced839855e58d66052
BLAKE2b-256 685be548d592d3e1af88e82a75599ffb1ebe1f83d337703c021e314bf645001d

See more details on using hashes here.

File details

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

File metadata

  • Download URL: memori-3.3.6rc2-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.6rc2-cp310-abi3-win_amd64.whl
Algorithm Hash digest
SHA256 8458c24ad837c77819d2e666a95a6eaf3c187fe66476fdc214ecbc72b4ed5ee1
MD5 79e40ed694fc3e855f643f5b57f8db81
BLAKE2b-256 a0625b982d69d264163eb54a4d13d73a7c944cda38afffaee8ea47a6c82e23ad

See more details on using hashes here.

File details

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

File metadata

File hashes

Hashes for memori-3.3.6rc2-cp310-abi3-musllinux_1_2_x86_64.whl
Algorithm Hash digest
SHA256 76b29ba6054f2acdff8a4ee5e3adbb55a8774b6afb68a4afcfef75377c752491
MD5 c46a82ecad43395600f9729bfe3cde0f
BLAKE2b-256 73c8546c810c903f348a83dbeb5a3d49987468b520ceb6aa4f499e54a5b67102

See more details on using hashes here.

File details

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

File metadata

File hashes

Hashes for memori-3.3.6rc2-cp310-abi3-musllinux_1_2_aarch64.whl
Algorithm Hash digest
SHA256 4ac07ccaebdd0652fc3d5e170b8d06cfbd6023f854573f2e3725bc1233dd731a
MD5 27cd1e8eb246bdc0354630e4baefe53e
BLAKE2b-256 777444c962c818839f3bc9d60681b8a0dd6f5f11cfc5ac36bbed1cb1817b9700

See more details on using hashes here.

File details

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

File metadata

File hashes

Hashes for memori-3.3.6rc2-cp310-abi3-manylinux_2_28_x86_64.whl
Algorithm Hash digest
SHA256 4e843da4bbd3f92f8297825bc47831be0d918d0490d75f12286a73c94c2f2677
MD5 5bafb78fe9614b7eefd28e4a3b53149b
BLAKE2b-256 44f93ca85a58a6a1645c842c160563ed47563bb35e924a0b360bc075620b43d1

See more details on using hashes here.

File details

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

File metadata

File hashes

Hashes for memori-3.3.6rc2-cp310-abi3-manylinux_2_28_aarch64.whl
Algorithm Hash digest
SHA256 8dfd194b18ece72245e3fd1ffd0e848b55b110487ad6ba7dca49dafbcfdef43a
MD5 0de600aa25dbf3c08b09c6bb314bb55d
BLAKE2b-256 75e816415901125c91f8ca2cfb241ce7dbbf36d5e43a68021204ac6a59c86938

See more details on using hashes here.

File details

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

File metadata

File hashes

Hashes for memori-3.3.6rc2-cp310-abi3-macosx_11_0_x86_64.whl
Algorithm Hash digest
SHA256 2f5a38573d9ab857b842942dc81aeeeb21046dd2558c08278cb81b9c9a38fb2f
MD5 65143dcccf8a4e0e4903cfddae410ab8
BLAKE2b-256 53385b700c0b2bf65e6b4ada631fa8820ee43d49f6d73a85c0061f137913bcfd

See more details on using hashes here.

File details

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

File metadata

File hashes

Hashes for memori-3.3.6rc2-cp310-abi3-macosx_11_0_arm64.whl
Algorithm Hash digest
SHA256 0226fd6507dee38324aa0b722e788c4450c88ed4aba6eac8c32c2f246ce2ecd2
MD5 32e56ac93a4d49ffa2227ca178f25d75
BLAKE2b-256 563c354716c3e41c0194d640678f8b28f137b34429ceeb0187c5c1c737afcb65

See more details on using hashes here.

File details

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

File metadata

File hashes

Hashes for memori-3.3.6rc2-cp310-abi3-android_24_x86_64.whl
Algorithm Hash digest
SHA256 610a26f31b368af7abefb31d890ca93f43830fd3278015b431abb84bdd050fa2
MD5 2795ab0377bc672bac07645e25f4fc02
BLAKE2b-256 33f7470008b545505986599c357ff9c1d97ed310759fe4875c78ba4015a1a56a

See more details on using hashes here.

File details

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

File metadata

File hashes

Hashes for memori-3.3.6rc2-cp310-abi3-android_24_arm64_v8a.whl
Algorithm Hash digest
SHA256 8b8b2bf146c7d4757c7fd2d80b4bc61c501523c04606bfdb600d73095dfe4273
MD5 1d8789cbb1a34c7ff2e8ea3df6f6961b
BLAKE2b-256 96a5dd45db36304c2780e995857e5452beb9d52fe4a8bf3297f432bb2b0df077

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