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

Uploaded CPython 3.10+Windows x86-64

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

Uploaded CPython 3.10+musllinux: musl 1.2+ ARM64

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

Uploaded CPython 3.10+manylinux: glibc 2.28+ ARM64

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

Uploaded CPython 3.10+macOS 11.0+ ARM64

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

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

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

File metadata

  • Download URL: memori-3.3.6.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.6.tar.gz
Algorithm Hash digest
SHA256 211147974495218feafb8e236083e629bfa9be30b0da3e6099e4215d0f97f9b0
MD5 f723711660af77d8eb22f593d6a31ae5
BLAKE2b-256 cb6ecc8327c01683b499423ea09d173aef5bcba813c88e6f06ee47c10deacff7

See more details on using hashes here.

File details

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

File metadata

  • Download URL: memori-3.3.6-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.6-cp310-abi3-win_amd64.whl
Algorithm Hash digest
SHA256 06166319ee3dd867cf7ed655cb05055212c528d4f6dffe3f74b624669c6c5858
MD5 45d3b4dd114e0cd6099129f388fb2a4f
BLAKE2b-256 ec15b0afb2426eef2f95f6d074ae68e686909b87653d404feb8d601fa129f84e

See more details on using hashes here.

File details

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

File metadata

File hashes

Hashes for memori-3.3.6-cp310-abi3-musllinux_1_2_x86_64.whl
Algorithm Hash digest
SHA256 169d2742e881846f29e3257f657934426e8e1418464a46e2d1f212d53aec02aa
MD5 763bacbecc87c0585207efd1fb7a3490
BLAKE2b-256 4068a3fb1b8b519211d778009bcbbb11789df122f327bda5286bf742dc9e5b8d

See more details on using hashes here.

File details

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

File metadata

File hashes

Hashes for memori-3.3.6-cp310-abi3-musllinux_1_2_aarch64.whl
Algorithm Hash digest
SHA256 e1d3f5992688edf094cdc5cc31effdefa00dafb2415ff7bc48d0743f411e5121
MD5 3ff4a65c6c3b5b6edffa832070098aad
BLAKE2b-256 68ab73069ebb036cef89dfa63dd8a4aacd6945f5f4ccc4e6963d31f362d6bdca

See more details on using hashes here.

File details

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

File metadata

File hashes

Hashes for memori-3.3.6-cp310-abi3-manylinux_2_28_x86_64.whl
Algorithm Hash digest
SHA256 96405cd5095f51cbc69b565726a9938bf5cb6adc16d8834652be35e58586e483
MD5 f377f114c390e46fe1f08283fd64db08
BLAKE2b-256 efc170cd163eaf1983695a5f6fe92af79d19f3ff90561d16cfcd6847b23b8512

See more details on using hashes here.

File details

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

File metadata

File hashes

Hashes for memori-3.3.6-cp310-abi3-manylinux_2_28_aarch64.whl
Algorithm Hash digest
SHA256 85e216a3b264a78693e11498d794c92dabdefaf55f78fa031dc834366f337a5b
MD5 84d72d3c08787db4cb008689c586e3b1
BLAKE2b-256 e84542a8ab0face6187a2afae6cf9f75cc9317c2aa8e69915a4a57e53ce60ad6

See more details on using hashes here.

File details

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

File metadata

File hashes

Hashes for memori-3.3.6-cp310-abi3-macosx_11_0_x86_64.whl
Algorithm Hash digest
SHA256 dc7a48c980cf42856d6f6e72871b949e2d4f72a449a233303378c60dc4b7b0ac
MD5 4e6c12dda1c09bd4e7167165e50ca5b3
BLAKE2b-256 320b131a4e512d7670d14ce164602bf32523f7d42a7a4bd93deb674572f3c099

See more details on using hashes here.

File details

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

File metadata

File hashes

Hashes for memori-3.3.6-cp310-abi3-macosx_11_0_arm64.whl
Algorithm Hash digest
SHA256 0a3cca4de7d28a0fefae0812b124d7c187a6b19ce31b9fc820f58bbf0d3233e3
MD5 03ca626cb2bc9446dfc7d1eb60ad176f
BLAKE2b-256 d35e6b68aecdad37de5bfb9d3ed9a5f2ec35427ed353374bee4e0227dedc70e0

See more details on using hashes here.

File details

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

File metadata

  • Download URL: memori-3.3.6-cp310-abi3-android_24_x86_64.whl
  • Upload date:
  • Size: 8.5 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.6-cp310-abi3-android_24_x86_64.whl
Algorithm Hash digest
SHA256 46f40b61d6c6dcf4a7a094bbaa18ca062cf7fae0021a16c44435279a425d12c8
MD5 8c3d9d6f0c3541d4db41322efefe7439
BLAKE2b-256 c76be2beb7e32f5c3a0fe9939e0992b25e54ce66936b8f17e14405d2c61a653b

See more details on using hashes here.

File details

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

File metadata

File hashes

Hashes for memori-3.3.6-cp310-abi3-android_24_arm64_v8a.whl
Algorithm Hash digest
SHA256 4395287573fb6eebd6020ed932af1f4c95094f6f4b56072685fe4ad8ef14213c
MD5 99b453e77861a4697a05b4282adc12b5
BLAKE2b-256 fa848584493ffd0bd3f99987106346331224afc6896a886234a20fff984670a7

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