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/.

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]

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

Uploaded CPython 3.10+Windows x86-64

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

Uploaded CPython 3.10+musllinux: musl 1.2+ ARM64

memori-3.3.4-cp310-abi3-manylinux_2_28_x86_64.whl (8.0 MB view details)

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

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

Uploaded CPython 3.10+manylinux: glibc 2.28+ ARM64

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

Uploaded CPython 3.10+macOS 11.0+ ARM64

memori-3.3.4-cp310-abi3-android_24_x86_64.whl (8.4 MB view details)

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

memori-3.3.4-cp310-abi3-android_24_arm64_v8a.whl (8.8 MB view details)

Uploaded Android API level 24+ ARM64 v8aCPython 3.10+

File details

Details for the file memori-3.3.4.tar.gz.

File metadata

  • Download URL: memori-3.3.4.tar.gz
  • Upload date:
  • Size: 188.9 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.4.tar.gz
Algorithm Hash digest
SHA256 abea91f6dbcf5ea219df3d71f16cb7712a7b6e3f7ad55ad65ed1e2353607be14
MD5 87805bccf0e061bf393f68b62072e9a8
BLAKE2b-256 f67fde8bf32bdba0e9ef3255b837cc95551fd0e2685266e238c597a4c3ce16c6

See more details on using hashes here.

File details

Details for the file memori-3.3.4-cp310-abi3-win_amd64.whl.

File metadata

  • Download URL: memori-3.3.4-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.4-cp310-abi3-win_amd64.whl
Algorithm Hash digest
SHA256 fc6294fe6998f4d63aeaefced3bbb74069a88b0569891392d75297225500df8c
MD5 641315c9437274abb74432e39eb1754c
BLAKE2b-256 c883ceaddc779350779da88d03a65700ea9664ebf90ff9ae9affbc69e0a5cd8f

See more details on using hashes here.

File details

Details for the file memori-3.3.4-cp310-abi3-musllinux_1_2_x86_64.whl.

File metadata

File hashes

Hashes for memori-3.3.4-cp310-abi3-musllinux_1_2_x86_64.whl
Algorithm Hash digest
SHA256 afc6c34e8ec82cd2cc738a3dbac4e0e77e7480ce15775e78cb2103492a3e5811
MD5 7d8dd7077204b319bb3aa39ed7d91d33
BLAKE2b-256 d7ab0f89f63fc1425337128ce6ffd2403e8276226b463db8965b111e70a6564b

See more details on using hashes here.

File details

Details for the file memori-3.3.4-cp310-abi3-musllinux_1_2_aarch64.whl.

File metadata

File hashes

Hashes for memori-3.3.4-cp310-abi3-musllinux_1_2_aarch64.whl
Algorithm Hash digest
SHA256 f7c487d6cd0ecd21d83b96f5d6b768254554babe18806f3e310a56c0897a77dc
MD5 102e20ad66c17263b9fdff2ab64deec2
BLAKE2b-256 65993fbde655bb424e59612850148212e912fae5f4958ad82275d72c6c24e700

See more details on using hashes here.

File details

Details for the file memori-3.3.4-cp310-abi3-manylinux_2_28_x86_64.whl.

File metadata

File hashes

Hashes for memori-3.3.4-cp310-abi3-manylinux_2_28_x86_64.whl
Algorithm Hash digest
SHA256 e7721429b4b6c0107a6e6f0af08890b514530c0ad4f330919eaedaa49f040d1f
MD5 f8698e4ce5f5bbd335a201391bab15e5
BLAKE2b-256 6c8a226057f8160922cfc1c685c749c34100347cdda1eb6a3a03b29b30e60b70

See more details on using hashes here.

File details

Details for the file memori-3.3.4-cp310-abi3-manylinux_2_28_aarch64.whl.

File metadata

File hashes

Hashes for memori-3.3.4-cp310-abi3-manylinux_2_28_aarch64.whl
Algorithm Hash digest
SHA256 c42d4d88d639067a5c553e4b7ca6bfd874f7425e014c0f7185a75d479e4d45cd
MD5 c51bfe55a3d40a8439ac1682748194e3
BLAKE2b-256 2bb2a967c9f1df5da842b49d9707b648793492de7d494386bfccd1ea3473f424

See more details on using hashes here.

File details

Details for the file memori-3.3.4-cp310-abi3-macosx_11_0_x86_64.whl.

File metadata

File hashes

Hashes for memori-3.3.4-cp310-abi3-macosx_11_0_x86_64.whl
Algorithm Hash digest
SHA256 7e4911663a4a11b77adfe531a24da3358f437cc0acbdd7ca5bee7a0cbf38b50e
MD5 57f13579ffd76e44e5b39da3141b37f0
BLAKE2b-256 4056658bf1398df9dbf6a243133455a2a60d895ed4b1fefb9a4293f05116675d

See more details on using hashes here.

File details

Details for the file memori-3.3.4-cp310-abi3-macosx_11_0_arm64.whl.

File metadata

File hashes

Hashes for memori-3.3.4-cp310-abi3-macosx_11_0_arm64.whl
Algorithm Hash digest
SHA256 3130a6392d856c1b51c0d2ba24d13cafb0647e50b8ce52011170e664e9bffb87
MD5 8fe3aea2e625e820e3114c6300d28281
BLAKE2b-256 95fadb947fd9ce4b940b47da2d3ddb010e77fbae6c9b9370c0fcb27dc8f047e0

See more details on using hashes here.

File details

Details for the file memori-3.3.4-cp310-abi3-android_24_x86_64.whl.

File metadata

  • Download URL: memori-3.3.4-cp310-abi3-android_24_x86_64.whl
  • Upload date:
  • Size: 8.4 MB
  • Tags: Android API level 24+ x86-64, CPython 3.10+
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/6.1.0 CPython/3.13.12

File hashes

Hashes for memori-3.3.4-cp310-abi3-android_24_x86_64.whl
Algorithm Hash digest
SHA256 c4414bb02482ba301472126db565960cba353880d0b6e443606037ef5a7a447e
MD5 ea09eb966ef2ea972bd85172ce6d4d21
BLAKE2b-256 5d7be0c982df4f934b255ae55532652a46b295220abca7c724f60cfea94286ac

See more details on using hashes here.

File details

Details for the file memori-3.3.4-cp310-abi3-android_24_arm64_v8a.whl.

File metadata

File hashes

Hashes for memori-3.3.4-cp310-abi3-android_24_arm64_v8a.whl
Algorithm Hash digest
SHA256 76e814c0c9e7d34c98d717154a1deaaf02962341144909018ffe2c9e4ff067da
MD5 c5e617d4d509813941f21d1309b6118d
BLAKE2b-256 6be550d6ec20fc17fa50193dcdd6206752eceb8d73b78a839ccaf3adc99779a9

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