chore: add update project options (#3947 )

fix: add OpenClaw to docs navigation (#3965 )
Feature: Add OpenClaw plugin and documentation (#3964 )
2026-02-03 10:55:43 +05:30 · 2026-02-02 10:17:19 -08:00 · 2026-02-02 10:04:08 -08:00 · 2026-01-13 13:01:38 +05:30 · 2026-01-13 12:52:49 +05:30 · 2026-01-13 11:42:54 +05:30
558 changed files with 60025 additions and 12906 deletions
@@ -7,6 +7,8 @@ on:
      - 'mem0/**'
      - 'tests/**'
      - 'embedchain/**'
+      - '.github/workflows/**'
+      - 'pyproject.toml'
  pull_request:
    paths:
      - 'mem0/**'
@@ -28,6 +30,8 @@ jobs:
          mem0:
            - 'mem0/**'
            - 'tests/**'
+            - '.github/workflows/**'
+            - 'pyproject.toml'
          embedchain:
            - 'embedchain/**'

@@ -44,6 +48,13 @@ jobs:
        uses: actions/setup-python@v4
        with:
          python-version: ${{ matrix.python-version }}
+      - name: Clean up disk space
+        run: |
+          df -h
+          sudo rm -rf /usr/share/dotnet /usr/local/lib/android /opt/ghc /opt/hostedtoolcache/CodeQL
+          sudo docker image prune --all --force
+          sudo docker builder prune -a
+          df -h
      - name: Install Hatch
        run: pip install hatch
      - name: Load cached venv
@@ -86,7 +86,6 @@ const memory = new Memory({
 const result = await memory.add('My name is John', { userId: 'john' });
 ```

-
 ## Core API Reference

 ### Memory Class (Self-Hosted)
@@ -104,7 +103,7 @@ memory = Memory()
 # With custom configuration
 config = MemoryConfig(
    vector_store={"provider": "qdrant", "config": {"host": "localhost"}},
-    llm={"provider": "openai", "config": {"model": "gpt-4o-mini"}},
+    llm={"provider": "openai", "config": {"model": "gpt-4.1-nano-2025-04-14"}},
    embedder={"provider": "openai", "config": {"model": "text-embedding-3-small"}}
 )
 memory = Memory(config)
@@ -305,7 +304,7 @@ config = MemoryConfig(
 - **langchain** - LangChain embeddings
 - **aws_bedrock** - AWS Bedrock embeddings

-#### Vector Store Providers (17 supported)
+#### Vector Store Providers (19 supported)
 - **qdrant** - Qdrant vector database (default)
 - **chroma** - ChromaDB
 - **pinecone** - Pinecone vector database
@@ -323,11 +322,14 @@ config = MemoryConfig(
 - **supabase** - Supabase vector
 - **baidu** - Baidu vector database
 - **langchain** - LangChain vector stores
+- **s3_vectors** - Amazon S3 Vectors
+- **databricks** - Databricks vector stores

-#### Graph Store Providers (3 supported)
+#### Graph Store Providers (4 supported)
 - **neo4j** - Neo4j graph database
 - **memgraph** - Memgraph
 - **neptune** - AWS Neptune Analytics
+- **kuzu** - Kuzu Graph database

 ### Configuration Examples

@@ -337,7 +339,7 @@ config = MemoryConfig(
    llm={
        "provider": "openai",
        "config": {
-            "model": "gpt-4o-mini",
+            "model": "gpt-4.1-nano-2025-04-14",
            "temperature": 0.1,
            "max_tokens": 1000
        }
@@ -415,6 +417,54 @@ config = MemoryConfig(
 )
 ```

+#### LLM Providers
+- **OpenAI** - GPT-4, GPT-3.5-turbo, and structured outputs
+- **Anthropic** - Claude models with advanced reasoning
+- **Google AI** - Gemini models for multimodal applications
+- **AWS Bedrock** - Enterprise-grade AWS managed models
+- **Azure OpenAI** - Microsoft Azure hosted OpenAI models
+- **Groq** - High-performance LPU optimized models
+- **Together** - Open-source model inference platform
+- **Ollama** - Local model deployment for privacy
+- **vLLM** - High-performance inference framework
+- **LM Studio** - Local model management
+- **DeepSeek** - Advanced reasoning models
+- **Sarvam** - Indian language models
+- **XAI** - xAI models
+- **LiteLLM** - Unified LLM interface
+- **LangChain** - LangChain LLM integration
+
+#### Vector Store Providers
+- **Chroma** - AI-native open-source vector database
+- **Qdrant** - High-performance vector similarity search
+- **Pinecone** - Managed vector database with serverless options
+- **Weaviate** - Open-source vector search engine
+- **PGVector** - PostgreSQL extension for vector search
+- **Milvus** - Open-source vector database for scale
+- **Redis** - Real-time vector storage with Redis Stack
+- **Supabase** - Open-source Firebase alternative
+- **Upstash Vector** - Serverless vector database
+- **Elasticsearch** - Distributed search and analytics
+- **OpenSearch** - Open-source search and analytics
+- **FAISS** - Facebook AI Similarity Search
+- **MongoDB** - Document database with vector search
+- **Azure AI Search** - Microsoft's search service
+- **Vertex AI Vector Search** - Google Cloud vector search
+- **Databricks Vector Search** - Delta Lake integration
+- **Baidu** - Baidu vector database
+- **LangChain** - LangChain vector store integration
+
+#### Embedding Providers
+- **OpenAI** - High-quality text embeddings
+- **Azure OpenAI** - Enterprise Azure-hosted embeddings
+- **Google AI** - Gemini embedding models
+- **AWS Bedrock** - Amazon embedding models
+- **Hugging Face** - Open-source embedding models
+- **Vertex AI** - Google Cloud enterprise embeddings
+- **Ollama** - Local embedding models
+- **Together** - Open-source model embeddings
+- **LM Studio** - Local model embeddings
+- **LangChain** - LangChain embedder integration

 ## TypeScript/JavaScript SDK

@@ -477,7 +527,7 @@ const memory = new Memory({
  },
  llm: {
    provider: 'openai',
-    config: { model: 'gpt-4o-mini' }
+    config: { model: 'gpt-4.1-nano' }
  }
 });

@@ -569,6 +619,7 @@ print(result["relations"])   # Graph relationships
 - **Neo4j**: Full-featured graph database with Cypher queries
 - **Memgraph**: High-performance in-memory graph database
 - **Neptune**: AWS managed graph database service
+- **kuzu** - OSS Kuzu Graph database

 ### Multimodal Memory

@@ -0,0 +1,221 @@
+# Migration Guide: Upgrading to mem0 1.0.0
+
+## TL;DR
+
+**What changed?** We simplified the API by removing confusing version parameters. Now everything returns a consistent format: `{"results": [...]}`.
+
+**What you need to do:**
+1. Upgrade: `pip install mem0ai==1.0.0`
+2. Remove `version` and `output_format` parameters from your code
+3. Update response handling to use `result["results"]` instead of treating responses as lists
+
+**Time needed:** ~5-10 minutes for most projects
+
+---
+
+## Quick Migration Guide
+
+### 1. Install the Update
+
+```bash
+pip install mem0ai==1.0.0
+```
+
+### 2. Update Your Code
+
+**If you're using the Memory API:**
+
+```python
+# Before
+memory = Memory(config=MemoryConfig(version="v1.1"))
+result = memory.add("I like pizza")
+
+# After
+memory = Memory()  # That's it - version is automatic now
+result = memory.add("I like pizza")
+```
+
+**If you're using the Client API:**
+
+```python
+# Before
+client.add(messages, output_format="v1.1")
+client.search(query, version="v2", output_format="v1.1")
+
+# After
+client.add(messages)  # Just remove those extra parameters
+client.search(query)
+```
+
+### 3. Update How You Handle Responses
+
+All responses now use the same format: a dictionary with `"results"` key.
+
+```python
+# Before - you might have done this
+result = memory.add("I like pizza")
+for item in result:  # Treating it as a list
+    print(item)
+
+# After - do this instead
+result = memory.add("I like pizza")
+for item in result["results"]:  # Access the results key
+    print(item)
+
+# Graph relations (if you use them)
+if "relations" in result:
+    for relation in result["relations"]:
+        print(relation)
+```
+
+---
+
+## Enhanced Message Handling
+
+The platform client (MemoryClient) now supports the same flexible message formats as the OSS version:
+
+```python
+from mem0 import MemoryClient
+
+client = MemoryClient(api_key="your-key")
+
+# All three formats now work:
+
+# 1. Single string (automatically converted to user message)
+client.add("I like pizza", user_id="alice")
+
+# 2. Single message dictionary
+client.add({"role": "user", "content": "I like pizza"}, user_id="alice")
+
+# 3. List of messages (conversation)
+client.add([
+    {"role": "user", "content": "I like pizza"},
+    {"role": "assistant", "content": "I'll remember that!"}
+], user_id="alice")
+```
+
+### Async Mode Configuration
+
+The `async_mode` parameter now defaults to `True` but can be configured:
+
+```python
+# Default behavior (async_mode=True)
+client.add(messages, user_id="alice")
+
+# Explicitly set async mode
+client.add(messages, user_id="alice", async_mode=True)
+
+# Disable async mode if needed
+client.add(messages, user_id="alice", async_mode=False)
+```
+
+**Note:** `async_mode=True` provides better performance for most use cases. Only set it to `False` if you have specific synchronous processing requirements.
+
+---
+
+## That's It!
+
+For most users, that's all you need to know. The changes are:
+- ✅ No more `version` or `output_format` parameters
+- ✅ Consistent `{"results": [...]}` response format
+- ✅ Cleaner, simpler API
+
+---
+
+## Common Issues
+
+**Getting `KeyError: 'results'`?**
+
+Your code is still treating the response as a list. Update it:
+```python
+# Change this:
+for memory in response:
+
+# To this:
+for memory in response["results"]:
+```
+
+**Getting `TypeError: unexpected keyword argument`?**
+
+You're still passing old parameters. Remove them:
+```python
+# Change this:
+client.add(messages, output_format="v1.1")
+
+# To this:
+client.add(messages)
+```
+
+**Seeing deprecation warnings?**
+
+Remove any explicit `version="v1.0"` from your config:
+```python
+# Change this:
+memory = Memory(config=MemoryConfig(version="v1.0"))
+
+# To this:
+memory = Memory()
+```
+
+---
+
+## What's New in 1.0.0
+
+- **Better vector stores:** Fixed OpenSearch and improved reliability across all stores
+- **Cleaner API:** One way to do things, no more confusing options
+- **Enhanced GCP support:** Better Vertex AI configuration options
+- **Flexible message input:** Platform client now accepts strings, dicts, and lists (aligned with OSS)
+- **Configurable async_mode:** Now defaults to `True` but users can override if needed
+
+---
+
+## Need Help?
+
+- Check [GitHub Issues](https://github.com/mem0ai/mem0/issues)
+- Read the [documentation](https://docs.mem0.ai/)
+- Open a new issue if you're stuck
+
+---
+
+## Advanced: Configuration Changes
+
+**If you configured vector stores with version:**
+
+```python
+# Before
+config = MemoryConfig(
+    version="v1.1",
+    vector_store=VectorStoreConfig(...)
+)
+
+# After
+config = MemoryConfig(
+    vector_store=VectorStoreConfig(...)
+)
+```
+
+---
+
+## Testing Your Migration
+
+Quick sanity check:
+
+```python
+from mem0 import Memory
+
+memory = Memory()
+
+# Add should return a dict with "results"
+result = memory.add("I like pizza", user_id="test")
+assert "results" in result
+
+# Search should return a dict with "results"
+search = memory.search("food", user_id="test")
+assert "results" in search
+
+# Get all should return a dict with "results"
+all_memories = memory.get_all(user_id="test")
+assert "results" in all_memories
+
+print("✅ Migration successful!")
+```
@@ -13,7 +13,7 @@ install:
 install_all:
 	pip install ruff==0.6.9 groq together boto3 litellm ollama chromadb weaviate weaviate-client sentence_transformers vertexai \
 	            google-generativeai elasticsearch opensearch-py vecs "pinecone<7.0.0" pinecone-text faiss-cpu langchain-community \
-							upstash-vector azure-search-documents langchain-memgraph langchain-neo4j langchain-aws rank-bm25 pymochow pymongo psycopg
+							upstash-vector azure-search-documents langchain-memgraph langchain-neo4j langchain-aws rank-bm25 pymochow pymongo psycopg kuzu databricks-sdk valkey

 # Format code with ruff
 format:
@@ -21,7 +21,7 @@

 <p align="center">
  <a href="https://mem0.dev/DiG">
-    <img src="https://dcbadge.vercel.app/api/server/6PzXDgEjG5?style=flat" alt="Mem0 Discord">
+    <img src="https://img.shields.io/badge/Discord-%235865F2.svg?&logo=discord&logoColor=white" alt="Mem0 Discord">
  </a>
  <a href="https://pepy.tech/project/mem0ai">
    <img src="https://img.shields.io/pypi/dm/mem0ai" alt="Mem0 PyPI - Downloads">
@@ -47,6 +47,8 @@
  <strong>⚡ +26% Accuracy vs. OpenAI Memory • 🚀 91% Faster • 💰 90% Fewer Tokens</strong>
 </p>

+> **🎉 mem0ai v1.0.0 is now available!** This major release includes API modernization, improved vector store support, and enhanced GCP integration. [See migration guide →](MIGRATION_GUIDE_v1.0.md)
+
 ##  🔥 Research Highlights
 - **+26% Accuracy** over OpenAI Memory on the LOCOMO benchmark
 - **91% Faster Responses** than full-context, ensuring low-latency at scale
@@ -95,7 +97,7 @@ npm install mem0ai

 ### Basic Usage

-Mem0 requires an LLM to function, with `gpt-4o-mini` from OpenAI as the default. However, it supports a variety of LLMs; for details, refer to our [Supported LLMs documentation](https://docs.mem0.ai/components/llms/overview).
+Mem0 requires an LLM to function, with `gpt-4.1-nano-2025-04-14 from OpenAI as the default. However, it supports a variety of LLMs; for details, refer to our [Supported LLMs documentation](https://docs.mem0.ai/components/llms/overview).

 First step is to instantiate the memory:

@@ -114,7 +116,7 @@ def chat_with_memories(message: str, user_id: str = "default_user") -> str:
    # Generate Assistant response
    system_prompt = f"You are a helpful AI. Answer the question based on query and memories.\nUser Memories:\n{memories_str}"
    messages = [{"role": "system", "content": system_prompt}, {"role": "user", "content": message}]
-    response = openai_client.chat.completions.create(model="gpt-4o-mini", messages=messages)
+    response = openai_client.chat.completions.create(model="gpt-4.1-nano-2025-04-14", messages=messages)
    assistant_response = response.choices[0].message.content

    # Create new memories from the conversation
@@ -166,4 +168,4 @@ We now have a paper you can cite:

 ## ⚖️ License

-Apache 2.0 — see the [LICENSE](LICENSE) file for details.
+Apache 2.0 — see the [LICENSE](https://github.com/mem0ai/mem0/blob/main/LICENSE) file for details.
@@ -1,3 +1,3 @@
 <Note type="info">
-  📢 Announcing our research paper: Mem0 achieves <strong>26%</strong> higher accuracy than OpenAI Memory, <strong>91%</strong> lower latency, and <strong>90%</strong> token savings! [Read the paper](https://mem0.ai/research) to learn how we're revolutionizing AI agent memory.
+  <strong>🎉 Mem0 1.0.0 is here!</strong> Enhanced filtering, reranking, and smarter memory management.
 </Note>
@@ -1,3 +0,0 @@
-<Note type="info">
-  🔐 Mem0 is now <strong>SOC 2</strong> and <strong>HIPAA</strong> compliant! We're committed to the highest standards of data security and privacy, enabling secure memory for enterprises, healthcare, and beyond. [Learn more](https://mem0.ai/security)
-</Note>
@@ -1,193 +1,108 @@
 ---
-title: Overview
-icon: "info"
+title: "Overview"
+icon: "terminal"
 iconType: "solid"
+description: "REST APIs for memory management, search, and entity operations"
 ---

-<Snippet file="async-memory-add.mdx" />
+## Mem0 REST API

-Mem0 provides a powerful set of APIs that allow you to integrate advanced memory management capabilities into your applications. Our APIs are designed to be intuitive, efficient, and scalable, enabling you to create, retrieve, update, and delete memories across various entities such as users, agents, apps, and runs.
+Mem0 provides a comprehensive REST API for integrating advanced memory capabilities into your applications. Create, search, update, and manage memories across users, agents, and custom entities with simple HTTP requests.

-## Key Features
+<Info>
+**Quick start:** Get your API key from the [Mem0 Dashboard](https://app.mem0.ai/dashboard/api-keys) and make your first memory operation in minutes.
+</Info>

- **Memory Management**: Add, retrieve, update, and delete memories with ease.
- **Entity-based Operations**: Perform operations on memories associated with specific users, agents, apps, or runs.
- **Advanced Search**: Utilize our search API to find relevant memories based on various criteria.
- **History Tracking**: Access the history of memory interactions for comprehensive analysis.
- **User Management**: Manage user entities and their associated memories.
+---

-## API Structure
+## Quick Start Guide

-Our API is organized into several main categories:
+Get started with Mem0 API in three simple steps:

-1. **Memory APIs**: Core operations for managing individual memories and collections.
-2. **Entities APIs**: Manage different entity types (users, agents, etc.) and their associated memories.
-3. **Search API**: Advanced search functionality to retrieve relevant memories.
-4. **History API**: Track and retrieve the history of memory interactions.
+1. **[Add Memories](/api-reference/memory/add-memories)** - Store information and context from user conversations
+2. **[Search Memories](/api-reference/memory/v2-search-memories)** - Retrieve relevant memories using semantic search
+3. **[Get Memories](/api-reference/memory/v2-get-memories)** - Fetch all memories for a specific entity
+
+---
+
+## Core Operations
+
+<CardGroup cols={2}>
+  <Card title="Add Memories" icon="plus" href="/api-reference/memory/add-memories">
+    Store new memories from conversations and interactions
+  </Card>
+
+  <Card title="Search Memories" icon="magnifying-glass" href="/api-reference/memory/v2-search-memories">
+    Find relevant memories using semantic search with filters
+  </Card>
+
+  <Card title="Update Memory" icon="pen" href="/api-reference/memory/update-memory">
+    Modify existing memory content and metadata
+  </Card>
+
+  <Card title="Delete Memory" icon="trash" href="/api-reference/memory/delete-memory">
+    Remove specific memories or batch delete operations
+  </Card>
+</CardGroup>
+
+---
+
+## API Categories
+
+Explore the full API organized by functionality:
+
+<CardGroup cols={2}>
+  <Card title="Memory APIs" icon="microchip" href="/api-reference/memory/add-memories">
+    Core and advanced operations: CRUD, search, batch updates, history, and exports
+  </Card>
+
+  <Card title="Events APIs" icon="clock" href="/api-reference/events/get-events">
+    Track and monitor the status of asynchronous memory operations
+  </Card>
+
+  <Card title="Entities APIs" icon="users" href="/api-reference/entities/get-users">
+    Manage users, agents, and their associated memory data
+  </Card>
+
+  <Card title="Organizations & Projects" icon="building" href="/api-reference/organizations-projects">
+    Multi-tenant support, access control, and team collaboration
+  </Card>
+
+  <Card title="Webhooks" icon="webhook" href="/api-reference/webhook/create-webhook">
+    Real-time notifications for memory events and updates
+  </Card>
+</CardGroup>
+
+<Note>
+**Building multi-tenant apps?** Learn about [Organizations & Projects](/api-reference/organizations-projects) for team isolation and access control.
+</Note>
+
+---

 ## Authentication

-All API requests require authentication using HTTP Basic Auth. Ensure you include your API key in the Authorization header of each request.
+All API requests require authentication using Token-based authentication. Include your API key in the Authorization header:

-## Organizations and projects (optional)
-
-Organizations and projects provide the following capabilities:
-
- **Multi-org/project Support**: Specify organization and project when initializing the Mem0 client to attribute API usage appropriately
- **Member Management**: Control access to data through organization and project membership
- **Access Control**: Only members can access memories and data within their organization/project scope
- **Team Isolation**: Maintain data separation between different teams and projects for secure collaboration
-
-Example with the mem0 Python package:
-
-<Tabs>
-  <Tab title="Python">
-
-```python
-from mem0 import MemoryClient
-client = MemoryClient(org_id='YOUR_ORG_ID', project_id='YOUR_PROJECT_ID')
+```bash
+Authorization: Token <your-api-key>
 ```

-  </Tab>
+Get your API key from the [Mem0 Dashboard](https://app.mem0.ai/dashboard/api-keys).

-  <Tab title="Node.js">
+<Warning>
+**Keep your API key secure.** Never expose it in client-side code or public repositories. Use environment variables and server-side requests only.
+</Warning>

-```javascript
-import { MemoryClient } from "mem0ai";
-const client = new MemoryClient({organizationId: "YOUR_ORG_ID", projectId: "YOUR_PROJECT_ID"});
-```
+---

-  </Tab>
-</Tabs>
+## Next Steps

-### Project Management Methods
+<CardGroup cols={2}>
+  <Card title="Add Your First Memory" icon="rocket" href="/api-reference/memory/add-memories">
+    Start storing memories via the REST API
+  </Card>

-The Mem0 client provides comprehensive project management capabilities through the `client.project` interface:
-
-#### Get Project Details
-
-Retrieve information about the current project:
-
-```python
-# Get all project details
-project_info = client.project.get()
-
-# Get specific fields only
-project_info = client.project.get(fields=["name", "description", "custom_categories"])
-```
-
-#### Create a New Project
-
-Create a new project within your organization:
-
-```python
-# Create a project with name and description
-new_project = client.project.create(
-    name="My New Project",
-    description="A project for managing customer support memories"
-)
-```
-
-#### Update Project Settings
-
-Modify project configuration including custom instructions, categories, and graph settings:
-
-```python
-# Update project with custom categories
-client.project.update(
-    custom_categories=[
-        {"customer_preferences": "Customer likes, dislikes, and preferences"},
-        {"support_history": "Previous support interactions and resolutions"}
-    ]
-)
-
-# Update project with custom instructions
-client.project.update(
-    custom_instructions="..."
-)
-
-# Enable graph memory for the project
-client.project.update(enable_graph=True)
-
-# Update multiple settings at once
-client.project.update(
-    custom_instructions="...",
-    custom_categories=[
-        {"personal_info": "User personal information and preferences"},
-        {"work_context": "Professional context and work-related information"}
-    ],
-    enable_graph=True
-)
-```
-
-#### Delete Project
-
-<Note>
-This action will remove all memories, messages, and other related data in the project. This operation is irreversible.
-</Note>
-
-Remove a project and all its associated data:
-
-```python
-# Delete the current project (irreversible)
-result = client.project.delete()
-```
-
-#### Member Management
-
-Manage project members and their access levels:
-
-```python
-# Get all project members
-members = client.project.get_members()
-
-# Add a new member as a reader
-client.project.add_member(
-    email="colleague@company.com",
-    role="READER"  # or "OWNER"
-)
-
-# Update a member's role
-client.project.update_member(
-    email="colleague@company.com",
-    role="OWNER"
-)
-
-# Remove a member from the project
-client.project.remove_member(email="colleague@company.com")
-```
-
-#### Member Roles
-
- **READER**: Can view and search memories, but cannot modify project settings or manage members
- **OWNER**: Full access including project modification, member management, and all reader permissions
-
-#### Async Support
-
-All project methods are also available in async mode:
-
-```python
-from mem0 import AsyncMemoryClient
-
-async def manage_project():
-    client = AsyncMemoryClient(org_id='YOUR_ORG_ID', project_id='YOUR_PROJECT_ID')
-
-    # All methods support async/await
-    project_info = await client.project.get()
-    await client.project.update(enable_graph=True)
-    members = await client.project.get_members()
-
-# To call the async function properly
-import asyncio
-asyncio.run(manage_project())
-```
-
-## Getting Started
-
-To begin using the Mem0 API, you'll need to:
-
-1. Sign up for a [Mem0 account](https://app.mem0.ai) and obtain your API key.
-2. Familiarize yourself with the API endpoints and their functionalities.
-3. Make your first API call to add or retrieve a memory.
-
-Explore the detailed documentation for each API endpoint to learn more about request/response formats, parameters, and example usage.
+  <Card title="Search with Filters" icon="filter" href="/api-reference/memory/v2-search-memories">
+    Learn advanced search and filtering techniques
+  </Card>
+</CardGroup>
@@ -1,4 +1,4 @@
 ---
 title: 'Delete User'
-openapi: delete /v1/entities/{entity_type}/{entity_id}/
+openapi: delete /v2/entities/{entity_type}/{entity_id}/
 ---
@@ -0,0 +1,6 @@
+---
+title: 'Get Event'
+openapi: get /v1/event/{event_id}/
+---
+
+Retrieve details about a specific event by passing its `event_id`. This endpoint is particularly helpful for tracking the status, payload, and completion details of asynchronous memory operations.
@@ -0,0 +1,13 @@
+---
+title: 'Get Events'
+openapi: get /v1/events/
+---
+
+List recent events for your organization and project.
+
+## Use Cases
+
+- **Dashboards**: Summarize adds/searches over time by paging through events.
+- **Alerting**: Poll for `FAILED` events and trigger follow-up workflows.
+- **Audit**: Store the returned payload/metadata for compliance logs.
+
@@ -1,4 +1,97 @@
 ---
 title: 'Add Memories'
 openapi: post /v1/memories/
---
+---
+
+Add new facts, messages, or metadata to a user’s memory store. The Add Memories endpoint accepts either raw text or conversational turns and commits them asynchronously so the memory is ready for later search, retrieval, and graph queries.
+
+## Endpoint
+
+- **Method**: `POST`
+- **URL**: `/v1/memories/`
+- **Content-Type**: `application/json`
+
+Memories are processed asynchronously by default. The response contains queued events you can track while the platform finalizes enrichment.
+
+## Required headers
+
+| Header | Required | Description |
+| --- | --- | --- |
+| `Authorization: Token <MEM0_API_KEY>` | Yes | API key scoped to your workspace. |
+| `Accept: application/json` | Yes | Ensures a JSON response. |
+
+## Request body
+
+Provide at least one message or direct memory string. Most callers supply `messages` so Mem0 can infer structured memories as part of ingestion.
+
+<CodeGroup>
+```json Basic request
+{
+  "user_id": "alice",
+  "messages": [
+    { "role": "user", "content": "I moved to Austin last month." }
+  ],
+  "metadata": {
+    "source": "onboarding_form"
+  }
+}
+```
+</CodeGroup>
+
+### Common fields
+
+| Field | Type | Required | Description |
+| --- | --- | --- | --- |
+| `user_id` | string | No* | Associates the memory with a user. Provide when you want the memory scoped to a specific identity. |
+| `messages` | array | No* | Conversation turns for Mem0 to infer memories from. Each object should include `role` and `content`. |
+| `metadata` | object | Optional | Custom key/value metadata (e.g., `{"topic": "preferences"}`). |
+| `infer` | boolean (default `true`) | Optional | Set to `false` to skip inference and store the provided text as-is. |
+| `async_mode` | boolean (default `true`) | Optional | Controls asynchronous processing. Most clients leave this enabled. |
+| `output_format` | string (default `v1.1`) | Optional | Response format. `v1.1` wraps results in a `results` array. |
+
+> \* Provide at least one `messages` entry to describe what you are storing. For scoped memories, include `user_id`. You can also attach `agent_id`, `app_id`, `run_id`, `project_id`, or `org_id` to refine ownership.
+
+## Response
+
+Successful requests return an array of events queued for processing. Each event includes the generated memory text and an identifier you can persist for auditing.
+
+<CodeGroup>
+```json 200 response
+[
+  {
+    "id": "mem_01JF8ZS4Y0R0SPM13R5R6H32CJ",
+    "event": "ADD",
+    "data": {
+      "memory": "The user moved to Austin in 2025."
+    }
+  }
+]
+```
+
+```json 400 response
+{
+  "error": "400 Bad Request",
+  "details": {
+    "message": "Invalid input data. Please refer to the memory creation documentation at https://docs.mem0.ai/platform/quickstart#4-1-create-memories for correct formatting and required fields."
+  }
+}
+```
+</CodeGroup>
+
+## Graph relationships
+
+Add Memories can enrich the knowledge graph on write. Set `enable_graph: true` to create entity nodes and relationships for the stored memory. Use this when you want downstream `get_all` or search calls to traverse connected entities.
+
+<CodeGroup>
+```json Graph-aware request
+{
+  "user_id": "alice",
+  "messages": [
+    { "role": "user", "content": "I met with Dr. Lee at General Hospital." }
+  ],
+  "enable_graph": true
+}
+```
+</CodeGroup>
+
+The response follows the same format, and related entities become available in [Graph Memory](/platform/features/graph-memory) queries.
@@ -3,4 +3,4 @@ title: 'Create Memory Export'
 openapi: post /v1/exports/
 ---

-Submit a job to create a structured export of memories using a customizable Pydantic schema. This process may take some time to complete, especially if you’re exporting a large number of memories. You can tailor the export by applying various filters (e.g., user_id, agent_id, run_id, or session_id) and by modifying the Pydantic schema to ensure the final data matches your exact needs.
+Submit a job to create a structured export of memories using a customizable Pydantic schema. This process may take some time to complete, especially if you're exporting a large number of memories. You can tailor the export by applying various filters (e.g., `user_id`, `agent_id`, `run_id`, or `session_id`) and by modifying the Pydantic schema to ensure the final data matches your exact needs.
@@ -0,0 +1,99 @@
+---
+title: "Get Memories"
+openapi: post /v2/memories/
+---
+
+The v2 get memories API is powerful and flexible, allowing for more precise memory listing without the need for a search query. It supports complex logical operations (AND, OR, NOT) and comparison operators for advanced filtering capabilities. The comparison operators include:
+
+- `in`: Matches any of the values specified
+- `gte`: Greater than or equal to
+- `lte`: Less than or equal to
+- `gt`: Greater than
+- `lt`: Less than
+- `ne`: Not equal to
+- `icontains`: Case-insensitive containment check
+- `*`: Wildcard character that matches everything
+
+<CodeGroup>
+```python Code
+memories = client.get_all(
+    filters={
+        "AND": [
+            {
+                "user_id": "alex"
+            },
+            {
+                "created_at": {"gte": "2024-07-01", "lte": "2024-07-31"}
+            }
+        ]
+    }
+)
+```
+
+```python Output
+{
+    "results": [
+        {
+            "id": "f4cbdb08-7062-4f3e-8eb2-9f5c80dfe64c",
+            "memory": "Alex is planning a trip to San Francisco from July 1st to July 10th",
+            "created_at": "2024-07-01T12:00:00Z",
+            "updated_at": "2024-07-01T12:00:00Z"
+        },
+        {
+            "id": "a2b8c3d4-5e6f-7g8h-9i0j-1k2l3m4n5o6p",
+            "memory": "Alex prefers vegetarian restaurants",
+            "created_at": "2024-07-05T15:30:00Z",
+            "updated_at": "2024-07-05T15:30:00Z"
+        }
+    ],
+    "total": 2
+}
+```
+
+</CodeGroup>
+
+## Graph Memory
+
+To retrieve graph memory relationships between entities, pass `output_format="v1.1"` in your request. This will return memories with entity and relationship information from the knowledge graph.
+
+<CodeGroup>
+```python Code
+memories = client.get_all(
+    filters={
+        "user_id": "alex"
+    },
+    output_format="v1.1"
+)
+```
+
+```python Output
+{
+    "results": [
+        {
+            "id": "f4cbdb08-7062-4f3e-8eb2-9f5c80dfe64c",
+            "memory": "Alex is planning a trip to San Francisco",
+            "entities": [
+                {
+                    "id": "entity-1",
+                    "name": "Alex",
+                    "type": "person"
+                },
+                {
+                    "id": "entity-2",
+                    "name": "San Francisco",
+                    "type": "location"
+                }
+            ],
+            "relations": [
+                {
+                    "source": "entity-1",
+                    "target": "entity-2",
+                    "relationship": "traveling_to"
+                }
+            ]
+        }
+    ]
+}
+```
+
+</CodeGroup>
@@ -0,0 +1,104 @@
+---
+title: 'Search Memories'
+openapi: post /v2/memories/search/
+---
+
+The v2 search API is powerful and flexible, allowing for more precise memory retrieval. It supports complex logical operations (AND, OR, NOT) and comparison operators for advanced filtering capabilities. The comparison operators include:
+- `in`: Matches any of the values specified
+- `gte`: Greater than or equal to
+- `lte`: Less than or equal to
+- `gt`: Greater than
+- `lt`: Less than
+- `ne`: Not equal to
+- `icontains`: Case-insensitive containment check
+- `*`: Wildcard character that matches everything
+
+<CodeGroup>
+```python Platform API Example
+related_memories = client.search(
+    query="What are Alice's hobbies?",
+    filters={
+        "OR": [
+            {
+              "user_id": "alice"
+            },
+            {
+              "agent_id": {"in": ["travel-agent", "sports-agent"]}
+            }
+        ]
+    },
+)
+```
+
+```json Output
+{
+  "memories": [
+    {
+      "id": "ea925981-272f-40dd-b576-be64e4871429",
+      "memory": "Likes to play cricket and plays cricket on weekends.",
+      "metadata": {
+        "category": "hobbies"
+      },
+      "score": 0.32116443111457704,
+      "created_at": "2024-07-26T10:29:36.630547-07:00",
+      "updated_at": null,
+      "user_id": "alice",
+      "agent_id": "sports-agent"
+    }
+  ],
+}
+```
+</CodeGroup>
+
+<CodeGroup>
+```python Wildcard Example
+# Using wildcard to match all run_ids for a specific user
+all_memories = client.search(
+    query="What are Alice's hobbies?",
+    filters={
+        "AND": [
+            {
+                "user_id": "alice"
+            },
+            {
+                "run_id": "*"
+            }
+        ]
+    },
+)
+```
+</CodeGroup>
+
+<CodeGroup>
+```python Categories Filter Examples
+# Example 1: Using 'contains' for partial matching
+finance_memories = client.search(
+    query="What are my financial goals?",
+    filters={
+        "AND": [
+            { "user_id": "alice" },
+            {
+                "categories": {
+                    "contains": "finance"
+                }
+            }
+        ]
+    },
+)
+
+# Example 2: Using 'in' for exact matching
+personal_memories = client.search(
+    query="What personal information do you have?",
+    filters={
+        "AND": [
+            { "user_id": "alice" },
+            {
+                "categories": {
+                    "in": ["personal_information"]
+                }
+            }
+        ]
+    },
+)
+```
+</CodeGroup>
@@ -1,4 +0,0 @@
---
-title: 'Get Memories (v1 - Deprecated)'
-openapi: get /v1/memories/
---
@@ -1,4 +0,0 @@
---
-title: 'Search Memories (v1 - Deprecated)'
-openapi: post /v1/memories/search/
---
@@ -1,65 +0,0 @@
---
-title: 'Get Memories (v2)'
-openapi: post /v2/memories/
---
-
-The v2 get memories API is powerful and flexible, allowing for more precise memory listing without the need for a search query. It supports complex logical operations (AND, OR, NOT) and comparison operators for advanced filtering capabilities. The comparison operators include:
- `in`: Matches any of the values specified
- `gte`: Greater than or equal to
- `lte`: Less than or equal to
- `gt`: Greater than
- `lt`: Less than
- `ne`: Not equal to
- `icontains`: Case-insensitive containment check
- `*`: Wildcard character that matches everything
-
-<CodeGroup>
-```python Code
-memories = m.get_all(
-    filters={
-        "AND": [
-            {
-                "user_id": "alex"
-            },
-            {
-                "created_at": {"gte": "2024-07-01", "lte": "2024-07-31"}
-            }
-        ]
-    },
-    version="v2"
-)
-```
-
-```json Output
-[
-{
-    "id":"f38b689d-6b24-45b7-bced-17fbb4d8bac7",
-    "memory":"Name: Alex. Vegetarian. Allergic to nuts.",
-    "user_id":"alex",
-    "hash":"62bc074f56d1f909f1b4c2b639f56f6a",
-    "metadata":null,
-    "created_at":"2024-07-25T23:57:00.108347-07:00",
-    "updated_at":"2024-07-25T23:57:00.108367-07:00"
-}
-]
-```
-</CodeGroup>
-
-<CodeGroup>
-```python Wildcard Example
-# Using wildcard to get all memories for a specific user across all run_ids
-memories = m.get_all(
-    filters={
-        "AND": [
-            {
-                "user_id": "alex"
-            },
-            {
-                "run_id": "*"
-            }
-        ]
-    },
-    version="v2"
-)
-```
-</CodeGroup>
@@ -1,72 +0,0 @@
---
-title: 'Search Memories (v2)'
-openapi: post /v2/memories/search/
---
-
-The v2 search API is powerful and flexible, allowing for more precise memory retrieval. It supports complex logical operations (AND, OR, NOT) and comparison operators for advanced filtering capabilities. The comparison operators include:
- `in`: Matches any of the values specified
- `gte`: Greater than or equal to
- `lte`: Less than or equal to
- `gt`: Greater than
- `lt`: Less than
- `ne`: Not equal to
- `icontains`: Case-insensitive containment check
- `*`: Wildcard character that matches everything
-
-  <CodeGroup>
-  ```python Code
-  related_memories = m.search(
-      query="What are Alice's hobbies?",
-      version="v2",
-      filters={
-          "OR": [
-              {
-                "user_id": "alice"
-              },
-              {
-                "agent_id": {"in": ["travel-agent", "sports-agent"]}
-              }
-          ]
-      },
-  )
-  ```
-
-  ```json Output
-  {
-    "memories": [
-      {
-        "id": "ea925981-272f-40dd-b576-be64e4871429",
-        "memory": "Likes to play cricket and plays cricket on weekends.",
-        "metadata": {
-          "category": "hobbies"
-        },
-        "score": 0.32116443111457704,
-        "created_at": "2024-07-26T10:29:36.630547-07:00",
-        "updated_at": null,
-        "user_id": "alice",
-        "agent_id": "sports-agent"
-      }
-    ],
-  }
-  ```
-  </CodeGroup>
-
-  <CodeGroup>
-  ```python Wildcard Example
-  # Using wildcard to match all run_ids for a specific user
-  all_memories = m.search(
-      query="What are Alice's hobbies?",
-      version="v2",
-      filters={
-          "AND": [
-              {
-                  "user_id": "alice"
-              },
-              {
-                  "run_id": "*"
-              }
-          ]
-      },
-  )
-  ```
-  </CodeGroup>
@@ -1,4 +0,0 @@
---
-title: 'Delete Member'
-openapi: delete /api/v1/orgs/organizations/{org_id}/members/
---
@@ -1,9 +0,0 @@
---
-title: 'Update Member'
-openapi: put /api/v1/orgs/organizations/{org_id}/members/
---
-
-The API provides two roles for organization members:
-
- `READER`: Allows viewing of organization resources.
- `OWNER`: Grants full administrative access to manage the organization and its resources.
@@ -0,0 +1,197 @@
+---
+title: Organizations & Projects
+icon: "building"
+description: "Manage multi-tenant applications with organization and project APIs"
+---
+
+## Overview
+
+Organizations and projects provide multi-tenant support, access control, and team collaboration capabilities for Mem0 Platform. Use these APIs to build applications that support multiple teams, customers, or isolated environments.
+
+<Info>
+Organizations and projects are **optional** features. You can use Mem0 without them for single-user or simple multi-user applications.
+</Info>
+
+## Key Capabilities
+
+- **Multi-org/project Support**: Specify organization and project when initializing the Mem0 client to attribute API usage appropriately
+- **Member Management**: Control access to data through organization and project membership
+- **Access Control**: Only members can access memories and data within their organization/project scope
+- **Team Isolation**: Maintain data separation between different teams and projects for secure collaboration
+
+---
+
+## Using Organizations & Projects
+
+### Initialize with Org/Project Context
+
+Example with the mem0 Python package:
+
+<Tabs>
+  <Tab title="Python">
+
+```python
+from mem0 import MemoryClient
+client = MemoryClient(org_id='YOUR_ORG_ID', project_id='YOUR_PROJECT_ID')
+```
+
+  </Tab>
+
+  <Tab title="Node.js">
+
+```javascript
+import { MemoryClient } from "mem0ai";
+const client = new MemoryClient({
+  organizationId: "YOUR_ORG_ID",
+  projectId: "YOUR_PROJECT_ID"
+});
+```
+
+  </Tab>
+</Tabs>
+
+---
+
+## Project Management
+
+The Mem0 client provides comprehensive project management through the `client.project` interface:
+
+### Get Project Details
+
+Retrieve information about the current project:
+
+```python
+# Get all project details
+project_info = client.project.get()
+
+# Get specific fields only
+project_info = client.project.get(fields=["name", "description", "custom_categories"])
+```
+
+### Create a New Project
+
+Create a new project within your organization:
+
+```python
+# Create a project with name and description
+new_project = client.project.create(
+    name="My New Project",
+    description="A project for managing customer support memories"
+)
+```
+
+### Update Project Settings
+
+Modify project configuration including custom instructions, categories, and graph settings:
+
+```python
+# Update project with custom categories
+client.project.update(
+    custom_categories=[
+        {"customer_preferences": "Customer likes, dislikes, and preferences"},
+        {"support_history": "Previous support interactions and resolutions"}
+    ]
+)
+
+# Update project with custom instructions
+client.project.update(
+    custom_instructions="..."
+)
+
+# Enable graph memory for the project
+client.project.update(enable_graph=True)
+
+# Update multiple settings at once
+client.project.update(
+    custom_instructions="...",
+    custom_categories=[
+        {"personal_info": "User personal information and preferences"},
+        {"work_context": "Professional context and work-related information"}
+    ],
+    enable_graph=True
+)
+```
+
+### Delete Project
+
+<Warning>
+This action will remove all memories, messages, and other related data in the project. **This operation is irreversible.**
+</Warning>
+
+Remove a project and all its associated data:
+
+```python
+# Delete the current project (irreversible)
+result = client.project.delete()
+```
+
+---
+
+## Member Management
+
+Manage project members and their access levels:
+
+```python
+# Get all project members
+members = client.project.get_members()
+
+# Add a new member as a reader
+client.project.add_member(
+    email="colleague@company.com",
+    role="READER"  # or "OWNER"
+)
+
+# Update a member's role
+client.project.update_member(
+    email="colleague@company.com",
+    role="OWNER"
+)
+
+# Remove a member from the project
+client.project.remove_member(email="colleague@company.com")
+```
+
+### Member Roles
+
+| Role | Permissions |
+|------|-------------|
+| **READER** | Can view and search memories, but cannot modify project settings or manage members |
+| **OWNER** | Full access including project modification, member management, and all reader permissions |
+
+---
+
+## Async Support
+
+All project methods are available in async mode:
+
+```python
+from mem0 import AsyncMemoryClient
+
+async def manage_project():
+    client = AsyncMemoryClient(org_id='YOUR_ORG_ID', project_id='YOUR_PROJECT_ID')
+
+    # All methods support async/await
+    project_info = await client.project.get()
+    await client.project.update(enable_graph=True)
+    members = await client.project.get_members()
+
+# To call the async function properly
+import asyncio
+asyncio.run(manage_project())
+```
+
+---
+
+## API Reference
+
+For complete API specifications and additional endpoints, see:
+
+<CardGroup cols={2}>
+  <Card title="Organizations APIs" icon="building" href="/api-reference/organization/create-org">
+    Create, get, and manage organizations
+  </Card>
+
+  <Card title="Project APIs" icon="folder" href="/api-reference/project/create-project">
+    Full project CRUD and member management endpoints
+  </Card>
+</CardGroup>
@@ -1,4 +0,0 @@
---
-title: 'Delete Member'
-openapi: delete /api/v1/orgs/organizations/{org_id}/projects/{project_id}/members/
---
@@ -1,9 +0,0 @@
---
-title: 'Update Member'
-openapi: put /api/v1/orgs/organizations/{org_id}/projects/{project_id}/members/
---
-
-The API provides two roles for project members:
-
- `READER`: Allows viewing of project resources.
- `OWNER`: Grants full administrative access to manage the project and its resources.
@@ -1,4 +0,0 @@
---
-title: 'Update Project'
-openapi: patch /api/v1/orgs/organizations/{org_id}/projects/{project_id}/
---
@@ -3,7 +3,3 @@ title: 'Create Webhook'
 openapi: post /api/v1/webhooks/projects/{project_id}/
 ---

-## Create Webhook
-
-Create a webhook by providing the project ID and the webhook details.
-
@@ -2,7 +2,3 @@
 title: 'Delete Webhook'
 openapi: delete /api/v1/webhooks/{webhook_id}/
 ---
-
-## Delete Webhook
-
-Delete a webhook by providing the webhook ID.
@@ -3,7 +3,3 @@ title: 'Get Webhook'
 openapi: get /api/v1/webhooks/projects/{project_id}/
 ---

-## Get Webhook
-
-Get a webhook by providing the project ID.
-
@@ -3,7 +3,3 @@ title: 'Update Webhook'
 openapi: put /api/v1/webhooks/{webhook_id}/
 ---

-## Update Webhook
-
-Update a webhook by providing the webhook ID and the fields to update.
-
@@ -3,11 +3,207 @@ title: "Product Updates"
 mode: "wide"
 ---

-<Snippet file="blank-notif.mdx" />
-
+ 
 <Tabs>
 <Tab title="Python">

+<Update label="2026-01-29" description="v1.0.3">
+
+**New Features & Updates:**
+- **Project Settings:**
+  - Added inclusion prompt, exclusion prompt, memory depth, and usecase setting
+
+</Update>
+
+<Update label="2026-01-13" description="v1.0.2">
+
+**New Features & Updates:**
+- **Vector Stores:**
+  - Added DriverInfo metadata to MongoDB vector store
+
+</Update>
+
+<Update label="2025-11-14" description="v1.0.1">
+
+**New Features & Updates:**
+- **Vector Stores:**
+  - Added Apache Cassandra vector store support
+- **Embeddings:**
+  - Added FastEmbed embedding support for local embeddings
+- **Graph Store:**
+  - Added configurable embedding similarity threshold for graph store node matching
+
+**Bug Fixes:**
+- **Core:**
+  - Fixed condition check for memories_result type in Memory class
+  - Fixed list_memories endpoint Pydantic validation error
+  - Fixed memory deletion not removing from vector store
+
+</Update>
+
+<Update label="2025-10-16" description="v1.0.0">
+
+**New Features & Updates:**
+- **Vector Stores:**
+  - Added Azure MySQL support
+  - Added Azure AI Search Vector Store support
+- **LLMs:**
+  - Added Tool Call support for LangchainLLM
+  - Enabled custom model and parameters for Hugging Face with huggingface_base_url
+  - Updated default LLM configuration
+- **Rerankers:**
+  - Added reranker support: Cohere, ZeroEntropy, Hugging Face, Sentence Transformers, and LLMs
+- **Core:**
+  - Added metadata filtering for OSS
+  - Added Assistant memory retrieval
+  - Enabled async mode as default
+
+**Improvements:**
+- **Prompts:**
+  - Improved prompt for better memory retrieval
+- **Dependencies:**
+  - Updated dependency compatibility with OpenAI 2.x
+- **Validation:**
+  - Validated embedding_dims for Kuzu integration
+
+**Bug Fixes:**
+- **Vector Stores:**
+  - Fixed Databricks Vector Store integration
+  - Fixed Milvus DB bug and added test coverage
+  - Fixed Weaviate search method
+- **LLMs:**
+  - Fixed bug with thinking LLM in vLLM
+
+</Update>
+
+<Update label="2025-09-25" description="v0.1.118">
+
+**New Features & Updates:**
+- **Vector Stores:**
+  - Added Valkey vector store support
+  - Added support for ChromaDB Cloud
+  - Added Mem0 vector store backend integration for Neptune Analytics
+- **Graph Store:**
+  - Added Neptune-DB graph store with vector store
+- **Core:**
+  - Implemented structured exception classes with error codes and suggested actions
+
+**Improvements:**
+- **Dependencies:**
+  - Updated OpenAI dependency and improved Ollama compatibility
+- **Testing:**
+  - Added Weaviate DB test
+  - Added comprehensive test suite for SQLiteManager
+- **Documentation:**
+  - Updated category docs
+  - Updated Search V2 / Get All V2 filters documentation
+  - Refactored AWS example title
+  - Fixed Quickstart cURL example
+
+**Bug Fixes:**
+- **Vector Stores:**
+  - Databricks bug fixes
+  - Fixed S3 Vectors memory initialization issue from configuration
+- **Core:**
+  - Fixed JSON parsing with new memories
+  - Replaced hardcoded LLM provider with provider from configuration
+- **LLMs:**
+  - Fixed Bedrock Anthropic models to use system field
+
+</Update>
+
+<Update label="2025-09-03" description="v0.1.117">
+
+**New Features & Updates:**
+- **OpenMemory:**
+  - Added memory export / import feature
+  - Added vector store integrations: Weaviate, FAISS, PGVector, Chroma, Redis, Elasticsearch, Milvus
+  - Added `export_openmemory.sh` migration script
+- **Vector Stores:**
+  - Added Amazon S3 Vectors support
+  - Added Databricks Mosaic AI vector store support
+  - Added support for OpenAI Store
+- **Graph Memory:** Added support for graph memory using Kuzu
+- **Azure:** Added Azure Identity for Azure OpenAI and Azure AI Search authentication
+- **Elasticsearch:** Added headers configuration support
+
+**Improvements:**
+  - Added custom connection client to enable connecting to local containers for Weaviate
+  - Updated configuration AWS Bedrock
+  - Fixed dependency issues and tests; updated docstrings
+- **Documentation:**
+  - Fixed Graph Docs page missing in sidebar
+  - Updated integration documentation
+  - Added version param in Search V2 API documentation
+  - Updated Databricks documentation and refactored docs
+  - Updated favicon logo
+  - Fixed typos and Typescript docs
+
+**Bug Fixes:**
+- Baidu: Added missing provider for Baidu vector DB
+- MongoDB: Replaced `query_vector` args in search method
+- Fixed new memory mistaken for current
+- AsyncMemory._add_to_vector_store: handled edge case when no facts found
+- Fixed missing commas in Kuzu graph INSERT queries
+- Fixed inconsistent created and updated properties for Graph
+- Fixed missing `app_id` on client for Neptune Analytics
+- Correctly pick AWS region from environment variable
+- Fixed Ollama model existence check
+
+**Refactoring:**
+- **PGVector:** Use internal connection pools and context managers
+
+</Update>
+
+<Update label="2025-08-14" description="v0.1.116">
+
+**New Features & Updates:**
+- **Pinecone:** Added namespace support and improved type safety
+- **Milvus:** Added db_name field to MilvusDBConfig
+- **Vector Stores:** Added multi-id filters support
+- **Vercel AI SDK:** Migration to AI SDK V5.0
+- **Python Support:** Added Python 3.12 support
+- **Graph Memory:** Added sanitizer methods for nodes and relationships
+- **LLM Monitoring:** Added monitoring callback support
+
+**Improvements:**
+- **Performance:**
+  - Improved async handling in AsyncMemory class
+- **Documentation:**
+  - Added async add announcement
+  - Added personalized search docs
+  - Added Neptune examples
+  - Added V5 migration docs
+- **Configuration:**
+  - Refactored base class config for LLMs
+  - Added sslmode for pgvector
+- **Dependencies:**
+  - Updated psycopg to version 3
+  - Updated Docker compose
+
+**Bug Fixes:**
+- **Tests:**
+  - Fixed failing tests
+  - Restricted package versions
+- **Memgraph:**
+  - Fixed async attribute errors
+  - Fixed n_embeddings usage
+  - Fixed indexing issues
+- **Vector Stores:**
+  - Fixed Qdrant cloud indexing
+  - Fixed Neo4j Cypher syntax
+  - Fixed LLM parameters
+- **Graph Store:**
+  - Fixed LM config prioritization
+- **Dependencies:**
+  - Fixed JSON import for psycopg
+
+**Refactoring:**
+- **Google AI:** Refactored from Gemini to Google AI
+- **Base Classes:** Refactored LLM base class configuration
+
+</Update>
+
 <Update label="2025-07-24" description="v0.1.115">

 **New Features & Updates:**
@@ -153,7 +349,7 @@ mode: "wide"
 <Update label="2025-06-11" description="v0.1.107">

 **Improvements:**
- **Documentation:** 
+- **Documentation:**
  - Updated Livekit documentation migration
  - Updated OpenMemory hosted version documentation
 - **Core:** Updated categorization flow
@@ -190,7 +386,7 @@ mode: "wide"
 - **LLM:** Added support for OpenAI compatible LLM providers with baseUrl configuration

 **Improvements:**
- **Documentation:** 
+- **Documentation:**
  - Fixed broken links
  - Improved Graph Memory features documentation clarity
  - Updated enable_graph documentation
@@ -207,14 +403,14 @@ mode: "wide"
 - **OpenMemory:** Added LLM and Embedding Providers support

 **Improvements:**
- **Documentation:** 
+- **Documentation:**
  - Updated memory export documentation
  - Enhanced role-based memory attribution rules documentation
  - Updated API reference and messages documentation
  - Added Mastra and Raycast documentation
  - Added NOT filter documentation for Search and GetAll V2
  - Announced Claude 4 support
- **Core:** 
+- **Core:**
  - Removed support for passing string as input in client.add()
  - Added support for sarvam-m model
 - **TypeScript SDK:** Fixed types from message interface
@@ -231,7 +427,7 @@ mode: "wide"
 - **Neo4j:** Added base label configuration support

 **Improvements:**
- **Documentation:** 
+- **Documentation:**
  - Updated Healthcare example index
  - Enhanced collaborative task agent documentation clarity
  - Added criteria-based filtering documentation
@@ -327,7 +523,7 @@ mode: "wide"
 - **Vector Stores:** Added reset function for VectorDBs

 **Improvements:**
- **Documentation:** 
+- **Documentation:**
  - Updated timestamp and expiration_date documentation
  - Fixed v2 search documentation
  - Added "memory" in EC "Custom config" section
@@ -366,12 +562,12 @@ mode: "wide"

 **New Features:**
 - **LLM Integrations:** Added Azure OpenAI Embedding Model
- **Examples:** 
+- **Examples:**
  - Added movie recommendation using grok3
  - Added Voice Assistant using Elevenlabs

 **Improvements:**
- **Documentation:** 
+- **Documentation:**
  - Added keywords AI
  - Reformatted navbar page URLs
  - Updated changelog
@@ -386,7 +582,7 @@ mode: "wide"
 - **LLM Integrations:** Added Mistral AI as LLM provider

 **Improvements:**
- **Documentation:** 
+- **Documentation:**
  - Updated changelog
  - Fixed memory exclusion example
  - Updated xAI documentation
@@ -403,7 +599,7 @@ mode: "wide"

 **New Features:**
 - **Langchain Integration:** Added support for Langchain VectorStores
- **Examples:** 
+- **Examples:**
  - Added personal assistant example
  - Added personal study buddy example
  - Added YouTube assistant Chrome extension example
@@ -520,6 +716,41 @@ mode: "wide"

 <Tab title="TypeScript">

+<Update label="2026-01-29" description="v2.2.2">
+
+**New Features & Updates:**
+- **Project Settings:**
+  - Added inclusion prompt, exclusion prompt, memory depth, and usecase setting
+
+</Update>
+
+<Update label="2025-12-30" description="v2.2.1">
+
+**Improvements:**
+- **Client:** Added support for keyword arguments in `add` and `search` methods, allowing additional properties beyond defined options for experimental features
+
+</Update>
+
+<Update label="2025-12-29" description="v2.2.0">
+
+**New Features:**
+- **Vector Stores:** Added Azure AI Search vector store support
+
+**Improvements:**
+- **Config:** Fixed embedder config schema to support `embeddingDims` and `url` parameters
+- **Graph Memory:** Replaced hardcoded LLM provider with provider from configuration
+
+**Bug Fixes:**
+- **Embedders:** Fixed hardcoded `embeddingDims` values in embedders (OpenAI, Ollama, Google, Azure)
+- **Build:** Fixed TypeScript build errors
+
+</Update>
+
+<Update label="2025-09-04" description="v2.1.38">
+**New Features:**
+- **Client:** Added `metadata` param to `update` method.
+</Update>
+
 <Update label="2025-08-04" description="v2.1.37">
 **New Features:**
 - **OSS:** Added `RedisCloud` search module check
@@ -541,17 +772,17 @@ mode: "wide"
 </Update>

 <Update label="2025-06-24" description="v2.1.33">
-**Improvement :**
+**Improvement:**
 - **Client:** Added `immutable` param to `add` method.
 </Update>

 <Update label="2025-06-20" description="v2.1.32">
-**Improvement :**
+**Improvement:**
 - **Client:** Made `api_version` V2 as default.
 </Update>

 <Update label="2025-06-17" description="v2.1.31">
-**Improvement :**
+**Improvement:**
 - **Client:** Added param `filter_memories`.
 </Update>

@@ -577,7 +808,6 @@ mode: "wide"
 **Improvements:**
 - **OSS:** Added baseURL param in LLM Config.
 </Update>
-  
 <Update label="2025-05-23" description="v2.1.26">
 **Improvements:**
 - **Client:** Removed type `string` from `messages` interface
@@ -992,6 +1222,31 @@ mode: "wide"

 <Tab title="Vercel AI SDK">

+<Update label="2025-12-26" description="v2.0.5">
+**Bug Fix:**
+- **Vercel AI SDK:** Removed unnecessary dependencies to make the package lighter.
+</Update>
+
+<Update label="2025-09-25" description="v2.0.4">
+**Bug Fix:**
+- **Vercel AI SDK:** Fixed version parameter in the AI SDK to use V2 for addition.
+</Update>
+
+<Update label="2025-09-25" description="v2.0.3">
+**New Features:**
+- **Vercel AI SDK:** Added file support for multimodal capabilities with memory context
+</Update>
+
+<Update label="2025-09-03" description="v2.0.2">
+**Bug Fix:**
+- **Vercel AI SDK:** Fixed streaming response in the AI SDK.
+</Update>
+
+<Update label="2025-08-05" description="v2.0.1">
+**New Features:**
+- **Vercel AI SDK:** Added a new param `host` to the config.
+</Update>
+
 <Update label="2025-08-05" description="v2.0.0">
 **New Features:**
 - **Vercel AI SDK:** Migration to AI SDK V5.
@@ -1014,7 +1269,7 @@ mode: "wide"

 <Update label="2025-05-08" description="v1.0.3">
 **Improvements:**
- **Vercel AI SDK:** Added support for graceful failure in cases services are down. 
+- **Vercel AI SDK:** Added support for graceful failure in cases services are down.
 </Update>

 <Update label="2025-05-01" description="v1.0.1">
@@ -1,10 +1,7 @@
 ---
 title: Configurations
-icon: "gear"
-iconType: "solid"
 ---

-<Snippet file="blank-notif.mdx" />

 Config in mem0 is a dictionary that specifies the settings for your embedding models. It allows you to customize the behavior and connection details of your chosen embedder.

@@ -41,7 +41,7 @@ config = {
 m = Memory.from_config(config)
 messages = [
    {"role": "user", "content": "I'm planning to watch a movie tonight. Any recommendations?"},
-    {"role": "assistant", "content": "How about a thriller movies? They can be quite engaging."},
+    {"role": "assistant", "content": "How about thriller movies? They can be quite engaging."},
    {"role": "user", "content": "I'm not a big fan of thriller movies but I love sci-fi movies."},
    {"role": "assistant", "content": "Got it! I'll avoid thriller recommendations and suggest sci-fi movies in the future."}
 ]
@@ -23,7 +23,7 @@ config = {
    "embedder": {
        "provider": "azure_openai",
        "config": {
-            "model": "text-embedding-3-large"
+            "model": "text-embedding-3-large",
            "azure_kwargs": {
                  "api_version": "",
                  "azure_deployment": "",
@@ -40,7 +40,7 @@ config = {
 m = Memory.from_config(config)
 messages = [
    {"role": "user", "content": "I'm planning to watch a movie tonight. Any recommendations?"},
-    {"role": "assistant", "content": "How about a thriller movies? They can be quite engaging."},
+    {"role": "assistant", "content": "How about thriller movies? They can be quite engaging."},
    {"role": "user", "content": "I’m not a big fan of thriller movies but I love sci-fi movies."},
    {"role": "assistant", "content": "Got it! I'll avoid thriller recommendations and suggest sci-fi movies in the future."}
 ]
@@ -68,7 +68,7 @@ const memory = new Memory(config);

 const messages = [
    {"role": "user", "content": "I'm planning to watch a movie tonight. Any recommendations?"},
-    {"role": "assistant", "content": "How about a thriller movies? They can be quite engaging."},
+    {"role": "assistant", "content": "How about thriller movies? They can be quite engaging."},
    {"role": "user", "content": "I’m not a big fan of thriller movies but I love sci-fi movies."},
    {"role": "assistant", "content": "Got it! I'll avoid thriller recommendations and suggest sci-fi movies in the future."}
 ]
@@ -77,12 +77,60 @@ await memory.add(messages, { userId: "john" });
 ```
 </CodeGroup>

+As an alternative to using an API key, the Azure Identity credential chain can be used to authenticate with [Azure OpenAI role-based security](https://learn.microsoft.com/en-us/azure/ai-foundry/openai/how-to/role-based-access-control). 
+
+<Note> If an API key is provided, it will be used for authentication over an Azure Identity </Note>
+
+Below is a sample configuration for using Mem0 with Azure OpenAI and Azure Identity:
+
+```python
+import os
+from mem0 import Memory
+# You can set the values directly in the config dictionary or use environment variables
+
+os.environ["LLM_AZURE_DEPLOYMENT"] = "your-deployment-name"
+os.environ["LLM_AZURE_ENDPOINT"] = "your-api-base-url"
+os.environ["LLM_AZURE_API_VERSION"] = "version-to-use"
+
+config = {
+    "llm": {
+        "provider": "azure_openai_structured",
+        "config": {
+            "model": "your-deployment-name",
+            "temperature": 0.1,
+            "max_tokens": 2000,
+            "azure_kwargs": {
+                  "azure_deployment": "<your-deployment-name>",
+                  "api_version": "<version-to-use>",
+                  "azure_endpoint": "<your-api-base-url>",
+                  "default_headers": {
+                    "CustomHeader": "your-custom-header",
+                  }
+              }
+        }
+    }
+}
+```
+
+Refer to [Azure Identity troubleshooting tips](https://github.com/Azure/azure-sdk-for-python/blob/main/sdk/identity/azure-identity/TROUBLESHOOTING.md#troubleshoot-environmentcredential-authentication-issues) for setting up an Azure Identity credential.
+
 ### Config

 Here are the parameters available for configuring Azure OpenAI embedder:
-
+<Tabs>
+<Tab title="Python">
 | Parameter | Description | Default Value |
 | --- | --- | --- |
 | `model` | The name of the embedding model to use | `text-embedding-3-small` |
 | `embedding_dims` | Dimensions of the embedding model | `1536` |
 | `azure_kwargs` | The Azure OpenAI configs | `config_keys` |
+</Tab>
+<Tab title="TypeScript">
+| Parameter         | Description                                   | Default Value              |
+| ----------------- | --------------------------------------------- | -------------------------- |
+| `model`           | The name of the embedding model to use        | `text-embedding-3-small`   |
+| `embeddingDims`   | Dimensions of the embedding model             | `1536`                     |
+| `apiKey`          | Azure OpenAI API key                          | `None`                     |
+| `modelProperties` | Object containing endpoint and other settings | `{ endpoint: "",...rest   }`|
+</Tab>
+</Tabs>
@@ -6,7 +6,8 @@ To use Google AI embedding models, set the `GOOGLE_API_KEY` environment variable

 ### Usage

-```python
+<CodeGroup>
+```python Python
 import os
 from mem0 import Memory

@@ -25,19 +26,54 @@ config = {
 m = Memory.from_config(config)
 messages = [
    {"role": "user", "content": "I'm planning to watch a movie tonight. Any recommendations?"},
-    {"role": "assistant", "content": "How about a thriller movies? They can be quite engaging."},
-    {"role": "user", "content": "I’m not a big fan of thriller movies but I love sci-fi movies."},
+    {"role": "assistant", "content": "How about thriller movies? They can be quite engaging."},
+    {"role": "user", "content": "I'm not a big fan of thriller movies but I love sci-fi movies."},
    {"role": "assistant", "content": "Got it! I'll avoid thriller recommendations and suggest sci-fi movies in the future."}
 ]
 m.add(messages, user_id="john")
 ```

+```typescript TypeScript
+import { Memory } from 'mem0ai/oss';
+
+const config = {
+  embedder: {
+      provider: "google",
+      config: {
+        apiKey: process.env["GOOGLE_API_KEY"],
+        model: "gemini-embedding-001",
+        embeddingDims: 1536,
+      },
+    },
+};
+
+const memory = new Memory(config);
+const messages = [
+    {"role": "user", "content": "I'm planning to watch a movie tonight. Any recommendations?"},
+    {"role": "assistant", "content": "How about thriller movies? They can be quite engaging."},
+    {"role": "user", "content": "I'm not a big fan of thriller movies but I love sci-fi movies."},
+    {"role": "assistant", "content": "Got it! I'll avoid thriller recommendations and suggest sci-fi movies in the future."}
+]
+await memory.add(messages, { userId: "john" });
+```
+</CodeGroup>
+
 ### Config

 Here are the parameters available for configuring Gemini embedder:
-
-| Parameter | Description | Default Value |
-| --- | --- | --- |
-| `model` | The name of the embedding model to use | `models/text-embedding-004` |
-| `embedding_dims` | Dimensions of the embedding model (output_dimensionality will be considered as embedding_dims, so please set embedding_dims accordingly) | `768` |
-| `api_key` | The Google API key | `None` |
+<Tabs>
+<Tab title="Python">
+| Parameter        | Description                          | Default Value           |
+| ---------------- | ------------------------------------ | ----------------------- |
+| `model`          | The name of the embedding model to use| `models/text-embedding-004` |
+| `embedding_dims` | Dimensions of the embedding model     | `1536`                  |
+| `api_key`        | The Google API key                   | `None`                  |
+</Tab>
+<Tab title="TypeScript">
+| Parameter         | Description                                   | Default Value              |
+| ----------------- | --------------------------------------------- | -------------------------- |
+| `model`           | The name of the embedding model to use        | `gemini-embedding-001`     |
+| `embeddingDims`   | Dimensions of the embedding model             | `1536`                     |
+| `apiKey`          | Google API key                                | `None`                     |
+</Tab>
+</Tabs>
@@ -24,7 +24,7 @@ config = {
 m = Memory.from_config(config)
 messages = [
    {"role": "user", "content": "I'm planning to watch a movie tonight. Any recommendations?"},
-    {"role": "assistant", "content": "How about a thriller movies? They can be quite engaging."},
+    {"role": "assistant", "content": "How about thriller movies? They can be quite engaging."},
    {"role": "user", "content": "I'm not a big fan of thriller movies but I love sci-fi movies."},
    {"role": "assistant", "content": "Got it! I'll avoid thriller recommendations and suggest sci-fi movies in the future."}
 ]
@@ -36,7 +36,7 @@ config = {
 m = Memory.from_config(config)
 messages = [
    {"role": "user", "content": "I'm planning to watch a movie tonight. Any recommendations?"},
-    {"role": "assistant", "content": "How about a thriller movies? They can be quite engaging."},
+    {"role": "assistant", "content": "How about thriller movies? They can be quite engaging."},
    {"role": "user", "content": "I'm not a big fan of thriller movies but I love sci-fi movies."},
    {"role": "assistant", "content": "Got it! I'll avoid thriller recommendations and suggest sci-fi movies in the future."}
 ]
@@ -44,29 +44,33 @@ m.add(messages, user_id="alice", metadata={"category": "movies"})
 ```

 ```typescript TypeScript
-import { Memory } from "mem0ai";
+import { Memory } from 'mem0ai/oss';
 import { OpenAIEmbeddings } from "@langchain/openai";

-const embeddings = new OpenAIEmbeddings();
+// Initialize a LangChain embeddings model directly
+const openaiEmbeddings = new OpenAIEmbeddings({
+    modelName: "text-embedding-3-small",
+    dimensions: 1536,
+    apiKey: process.env.OPENAI_API_KEY,
+});
+
 const config = {
-    "embedder": {
-        "provider": "langchain",
-        "config": {
-            "model": embeddings
-        }
-    }
-}
+  embedder: {
+    provider: 'langchain',
+    config: {
+      model: openaiEmbeddings,
+    },
+  },
+};

 const memory = new Memory(config);
-
 const messages = [
-    { role: "user", content: "I'm planning to watch a movie tonight. Any recommendations?" },
-    { role: "assistant", content: "How about a thriller movies? They can be quite engaging." },
-    { role: "user", content: "I'm not a big fan of thriller movies but I love sci-fi movies." },
-    { role: "assistant", content: "Got it! I'll avoid thriller recommendations and suggest sci-fi movies in the future." }
+    {"role": "user", "content": "I'm planning to watch a movie tonight. Any recommendations?"},
+    {"role": "assistant", "content": "How about thriller movies? They can be quite engaging."},
+    {"role": "user", "content": "I'm not a big fan of thriller movies but I love sci-fi movies."},
+    {"role": "assistant", "content": "Got it! I'll avoid thriller recommendations and suggest sci-fi movies in the future."}
 ]
-
-memory.add(messages, user_id="alice", metadata={"category": "movies"})
+await memory.add(messages, { userId: "alice", metadata: { category: "movies" } });
 ```
 </CodeGroup>

@@ -96,9 +100,10 @@ When using LangChain as an embedder provider, you'll need to:

 ### Examples with Different Providers

+<CodeGroup>
 #### HuggingFace Embeddings

-```python
+```python Python
 from langchain_huggingface import HuggingFaceEmbeddings

 # Initialize a HuggingFace embeddings model
@@ -117,9 +122,33 @@ config = {
 }
 ```

+```typescript TypeScript
+import { Memory } from 'mem0ai/oss';
+import { HuggingFaceEmbeddings } from "@langchain/community/embeddings/hf";
+
+// Initialize a HuggingFace embeddings model
+const hfEmbeddings = new HuggingFaceEmbeddings({
+    modelName: "BAAI/bge-small-en-v1.5",
+    encode: {
+        normalize_embeddings: true,
+    },
+});
+
+const config = {
+  embedder: {
+    provider: 'langchain',
+    config: {
+      model: hfEmbeddings,
+    },
+  },
+};
+```
+</CodeGroup>
+
+<CodeGroup>
 #### Ollama Embeddings

-```python
+```python Python
 from langchain_ollama import OllamaEmbeddings

 # Initialize an Ollama embeddings model
@@ -137,6 +166,27 @@ config = {
 }
 ```

+```typescript TypeScript
+import { Memory } from 'mem0ai/oss';
+import { OllamaEmbeddings } from "@langchain/community/embeddings/ollama";
+
+// Initialize an Ollama embeddings model
+const ollamaEmbeddings = new OllamaEmbeddings({
+    model: "nomic-embed-text",
+    baseUrl: "http://localhost:11434", // Ollama server URL
+});
+
+const config = {
+  embedder: {
+    provider: 'langchain',
+    config: {
+      model: ollamaEmbeddings,
+    },
+  },
+};
+```
+</CodeGroup>
+
 <Note>
  Make sure to install the necessary LangChain packages and any provider-specific dependencies.
 </Note>
@@ -20,7 +20,7 @@ config = {
 m = Memory.from_config(config)
 messages = [
    {"role": "user", "content": "I'm planning to watch a movie tonight. Any recommendations?"},
-    {"role": "assistant", "content": "How about a thriller movies? They can be quite engaging."},
+    {"role": "assistant", "content": "How about thriller movies? They can be quite engaging."},
    {"role": "user", "content": "I’m not a big fan of thriller movies but I love sci-fi movies."},
    {"role": "assistant", "content": "Got it! I'll avoid thriller recommendations and suggest sci-fi movies in the future."}
 ]
@@ -29,10 +29,10 @@ m.add(messages, user_id="john")

 ### Config

-Here are the parameters available for configuring Ollama embedder:
+Here are the parameters available for configuring LM Studio embedder:

 | Parameter | Description | Default Value |
 | --- | --- | --- |
-| `model` | The name of the OpenAI model to use | `nomic-embed-text-v1.5-GGUF/nomic-embed-text-v1.5.f16.gguf` |
+| `model` | The name of the LM Studio model to use | `nomic-embed-text-v1.5-GGUF/nomic-embed-text-v1.5.f16.gguf` |
 | `embedding_dims` | Dimensions of the embedding model | `1536` |
 | `lmstudio_base_url` | Base URL for LM Studio connection | `http://localhost:1234/v1` |
@@ -2,7 +2,8 @@ You can use embedding models from Ollama to run Mem0 locally.

 ### Usage

-```python
+<CodeGroup>
+```python Python
 import os
 from mem0 import Memory

@@ -20,19 +21,54 @@ config = {
 m = Memory.from_config(config)
 messages = [
    {"role": "user", "content": "I'm planning to watch a movie tonight. Any recommendations?"},
-    {"role": "assistant", "content": "How about a thriller movies? They can be quite engaging."},
-    {"role": "user", "content": "I’m not a big fan of thriller movies but I love sci-fi movies."},
+    {"role": "assistant", "content": "How about thriller movies? They can be quite engaging."},
+    {"role": "user", "content": "I'm not a big fan of thriller movies but I love sci-fi movies."},
    {"role": "assistant", "content": "Got it! I'll avoid thriller recommendations and suggest sci-fi movies in the future."}
 ]
 m.add(messages, user_id="john")
 ```

+```typescript TypeScript
+import { Memory } from 'mem0ai/oss';
+
+const config = {
+  embedder: {
+    provider: 'ollama',
+    config: {
+      model: 'nomic-embed-text:latest', // or any other Ollama embedding model
+      url: 'http://localhost:11434', // Ollama server URL
+    },
+  },
+};
+
+const memory = new Memory(config);
+const messages = [
+    {"role": "user", "content": "I'm planning to watch a movie tonight. Any recommendations?"},
+    {"role": "assistant", "content": "How about thriller movies? They can be quite engaging."},
+    {"role": "user", "content": "I'm not a big fan of thriller movies but I love sci-fi movies."},
+    {"role": "assistant", "content": "Got it! I'll avoid thriller recommendations and suggest sci-fi movies in the future."}
+]
+await memory.add(messages, { userId: "john" });
+```
+</CodeGroup>
+
 ### Config

 Here are the parameters available for configuring Ollama embedder:

+<Tabs>
+<Tab title="Python">
 | Parameter | Description | Default Value |
 | --- | --- | --- |
-| `model` | The name of the OpenAI model to use | `nomic-embed-text` |
+| `model` | The name of the Ollama model to use | `nomic-embed-text` |
 | `embedding_dims` | Dimensions of the embedding model | `512` |
-| `ollama_base_url` | Base URL for ollama connection | `None` |
+| `ollama_base_url` | Base URL for ollama connection | `None` |
+</Tab>
+<Tab title="TypeScript">
+| Parameter | Description | Default Value |
+| --- | --- | --- |
+| `model` | The name of the Ollama model to use | `nomic-embed-text:latest` |
+| `url` | Base URL for Ollama server | `http://localhost:11434` |
+| `embeddingDims` | Dimensions of the embedding model | 768
+</Tab>
+</Tabs>
@@ -25,7 +25,7 @@ config = {
 m = Memory.from_config(config)
 messages = [
    {"role": "user", "content": "I'm planning to watch a movie tonight. Any recommendations?"},
-    {"role": "assistant", "content": "How about a thriller movies? They can be quite engaging."},
+    {"role": "assistant", "content": "How about thriller movies? They can be quite engaging."},
    {"role": "user", "content": "I’m not a big fan of thriller movies but I love sci-fi movies."},
    {"role": "assistant", "content": "Got it! I'll avoid thriller recommendations and suggest sci-fi movies in the future."}
 ]
@@ -27,7 +27,7 @@ config = {
 m = Memory.from_config(config)
 messages = [
    {"role": "user", "content": "I'm planning to watch a movie tonight. Any recommendations?"},
-    {"role": "assistant", "content": "How about a thriller movies? They can be quite engaging."},
+    {"role": "assistant", "content": "How about thriller movies? They can be quite engaging."},
    {"role": "user", "content": "I’m not a big fan of thriller movies but I love sci-fi movies."},
    {"role": "assistant", "content": "Got it! I'll avoid thriller recommendations and suggest sci-fi movies in the future."}
 ]
@@ -27,7 +27,7 @@ config = {
 m = Memory.from_config(config)
 messages = [
    {"role": "user", "content": "I'm planning to watch a movie tonight. Any recommendations?"},
-    {"role": "assistant", "content": "How about a thriller movies? They can be quite engaging."},
+    {"role": "assistant", "content": "How about thriller movies? They can be quite engaging."},
    {"role": "user", "content": "I’m not a big fan of thriller movies but I love sci-fi movies."},
    {"role": "assistant", "content": "Got it! I'll avoid thriller recommendations and suggest sci-fi movies in the future."}
 ]
@@ -1,11 +1,7 @@
 ---
 title: Overview
-icon: "info"
-iconType: "solid"
 ---

-<Snippet file="blank-notif.mdx" />
-
 Mem0 offers support for various embedding models, allowing users to choose the one that best suits their needs.

 ## Supported Embedders
@@ -31,6 +27,6 @@ See the list of supported embedders below.

 ## Usage

-To utilize a embedder, you must provide a configuration to customize its usage. If no configuration is supplied, a default configuration will be applied, and `OpenAI` will be used as the embedder.
+To utilize an embedding model, you must provide a configuration to customize its usage. If no configuration is supplied, a default configuration will be applied, and `OpenAI` will be used as the embedding model.

-For a comprehensive list of available parameters for embedder configuration, please refer to [Config](./config).
+For a comprehensive list of available parameters for embedding model configuration, please refer to [Config](./config).
@@ -1,11 +1,7 @@
 ---
 title: Configurations
-icon: "gear"
-iconType: "solid"
 ---

-<Snippet file="blank-notif.mdx" />
-
 ## How to define configurations?

 <Tabs>
@@ -2,7 +2,6 @@
 title: Anthropic
 ---

-<Snippet file="blank-notif.mdx" />

 To use Anthropic's models, please set the `ANTHROPIC_API_KEY` which you find on their [Account Settings Page](https://console.anthropic.com/account/keys).

@@ -30,7 +29,7 @@ config = {
 m = Memory.from_config(config)
 messages = [
    {"role": "user", "content": "I'm planning to watch a movie tonight. Any recommendations?"},
-    {"role": "assistant", "content": "How about a thriller movies? They can be quite engaging."},
+    {"role": "assistant", "content": "How about thriller movies? They can be quite engaging."},
    {"role": "user", "content": "I’m not a big fan of thriller movies but I love sci-fi movies."},
    {"role": "assistant", "content": "Got it! I'll avoid thriller recommendations and suggest sci-fi movies in the future."}
 ]
@@ -55,7 +54,7 @@ const config = {
 const memory = new Memory(config);
 const messages = [
    {"role": "user", "content": "I'm planning to watch a movie tonight. Any recommendations?"},
-    {"role": "assistant", "content": "How about a thriller movies? They can be quite engaging."},
+    {"role": "assistant", "content": "How about thriller movies? They can be quite engaging."},
    {"role": "user", "content": "I’m not a big fan of thriller movies but I love sci-fi movies."},
    {"role": "assistant", "content": "Got it! I'll avoid thriller recommendations and suggest sci-fi movies in the future."}
 ]
@@ -2,8 +2,6 @@
 title: AWS Bedrock
 ---

-<Snippet file="blank-notif.mdx" />
-
 ### Setup
 - Before using the AWS Bedrock LLM, make sure you have the appropriate model access from [Bedrock Console](https://us-east-1.console.aws.amazon.com/bedrock/home?region=us-east-1#/modelaccess).
 - You will also need to authenticate the `boto3` client by using a method in the [AWS documentation](https://boto3.amazonaws.com/v1/documentation/api/latest/guide/credentials.html#configuring-credentials)
@@ -33,7 +31,7 @@ config = {
 m = Memory.from_config(config)
 messages = [
    {"role": "user", "content": "I'm planning to watch a movie tonight. Any recommendations?"},
-    {"role": "assistant", "content": "How about a thriller movies? They can be quite engaging."},
+    {"role": "assistant", "content": "How about thriller movies? They can be quite engaging."},
    {"role": "user", "content": "I’m not a big fan of thriller movies but I love sci-fi movies."},
    {"role": "assistant", "content": "Got it! I'll avoid thriller recommendations and suggest sci-fi movies in the future."}
 ]
@@ -2,12 +2,12 @@
 title: Azure OpenAI
 ---

-<Snippet file="blank-notif.mdx" />
-
 <Note> Mem0 Now Supports Azure OpenAI Models in TypeScript SDK </Note>

 To use Azure OpenAI models, you have to set the `LLM_AZURE_OPENAI_API_KEY`, `LLM_AZURE_ENDPOINT`, `LLM_AZURE_DEPLOYMENT` and `LLM_AZURE_API_VERSION` environment variables. You can obtain the Azure API key from the [Azure](https://azure.microsoft.com/).

+Optionally, you can use Azure Identity to authenticate with Azure OpenAI, which allows you to use managed identities or service principals for production and Azure CLI login for development instead of an API key. If an Azure Identity is to be used, ***do not*** set the `LLM_AZURE_OPENAI_API_KEY` environment variable or the api_key in the config dictionary.
+
 > **Note**: The following are currently unsupported with reasoning models `Parallel tool calling`,`temperature`, `top_p`, `presence_penalty`, `frequency_penalty`, `logprobs`, `top_logprobs`, `logit_bias`, `max_tokens`


@@ -48,7 +48,7 @@ config = {
 m = Memory.from_config(config)
 messages = [
    {"role": "user", "content": "I'm planning to watch a movie tonight. Any recommendations?"},
-    {"role": "assistant", "content": "How about a thriller movies? They can be quite engaging."},
+    {"role": "assistant", "content": "How about thriller movies? They can be quite engaging."},
    {"role": "user", "content": "I’m not a big fan of thriller movies but I love sci-fi movies."},
    {"role": "assistant", "content": "Got it! I'll avoid thriller recommendations and suggest sci-fi movies in the future."}
 ]
@@ -77,7 +77,7 @@ const config = {
 const memory = new Memory(config);
 const messages = [
    {"role": "user", "content": "I'm planning to watch a movie tonight. Any recommendations?"},
-    {"role": "assistant", "content": "How about a thriller movies? They can be quite engaging."},
+    {"role": "assistant", "content": "How about thriller movies? They can be quite engaging."},
    {"role": "user", "content": "I’m not a big fan of thriller movies but I love sci-fi movies."},
    {"role": "assistant", "content": "Got it! I'll avoid thriller recommendations and suggest sci-fi movies in the future."}
 ]
@@ -118,6 +118,44 @@ config = {
 }
 ```

+As an alternative to using an API key, the Azure Identity credential chain can be used to authenticate with [Azure OpenAI role-based security](https://learn.microsoft.com/en-us/azure/ai-foundry/openai/how-to/role-based-access-control). 
+
+<Note> If an API key is provided, it will be used for authentication over an Azure Identity </Note>
+
+Below is a sample configuration for using Mem0 with Azure OpenAI and Azure Identity:
+
+```python
+import os
+from mem0 import Memory
+# You can set the values directly in the config dictionary or use environment variables
+
+os.environ["LLM_AZURE_DEPLOYMENT"] = "your-deployment-name"
+os.environ["LLM_AZURE_ENDPOINT"] = "your-api-base-url"
+os.environ["LLM_AZURE_API_VERSION"] = "version-to-use"
+
+config = {
+    "llm": {
+        "provider": "azure_openai_structured",
+        "config": {
+            "model": "your-deployment-name",
+            "temperature": 0.1,
+            "max_tokens": 2000,
+            "azure_kwargs": {
+                  "azure_deployment": "<your-deployment-name>",
+                  "api_version": "<version-to-use>",
+                  "azure_endpoint": "<your-api-base-url>",
+                  "default_headers": {
+                    "CustomHeader": "your-custom-header",
+                  }
+              }
+        }
+    }
+}
+```
+
+Refer to [Azure Identity troubleshooting tips](https://github.com/Azure/azure-sdk-for-python/blob/main/sdk/identity/azure-identity/TROUBLESHOOTING.md#troubleshoot-environmentcredential-authentication-issues) for setting up an Azure Identity credential.
+
+
 ## Config

 All available parameters for the `azure_openai` config are present in [Master List of All Params in Config](../config).
@@ -2,8 +2,6 @@
 title: DeepSeek
 ---

-<Snippet file="blank-notif.mdx" />
-
 To use DeepSeek LLM models, you have to set the `DEEPSEEK_API_KEY` environment variable. You can also optionally set `DEEPSEEK_API_BASE` if you need to use a different API endpoint (defaults to "https://api.deepseek.com").

 ## Usage
@@ -30,7 +28,7 @@ config = {
 m = Memory.from_config(config)
 messages = [
    {"role": "user", "content": "I'm planning to watch a movie tonight. Any recommendations?"},
-    {"role": "assistant", "content": "How about a thriller movies? They can be quite engaging."},
+    {"role": "assistant", "content": "How about thriller movies? They can be quite engaging."},
    {"role": "user", "content": "I’m not a big fan of thriller movies but I love sci-fi movies."},
    {"role": "assistant", "content": "Got it! I'll avoid thriller recommendations and suggest sci-fi movies in the future."}
 ]
@@ -2,8 +2,6 @@
 title: Google AI
 ---

-<Snippet file="blank-notif.mdx" />
-
 To use the Gemini model, set the `GOOGLE_API_KEY` environment variable. You can obtain the Google/Gemini API key from [Google AI Studio](https://aistudio.google.com/app/apikey).

 > **Note:** As of the latest release, Mem0 uses the new `google.genai` SDK instead of the deprecated `google.generativeai`. All message formatting and model interaction now use the updated `types` module from `google.genai`.
@@ -2,8 +2,6 @@
 title: Groq
 ---

-<Snippet file="blank-notif.mdx" />
-
 [Groq](https://groq.com/) is the creator of the world's first Language Processing Unit (LPU), providing exceptional speed performance for AI workloads running on their LPU Inference Engine.

 In order to use LLMs from Groq, go to their [platform](https://console.groq.com/keys) and get the API key. Set the API key as `GROQ_API_KEY` environment variable to use the model as given below in the example.
@@ -32,7 +30,7 @@ config = {
 m = Memory.from_config(config)
 messages = [
    {"role": "user", "content": "I'm planning to watch a movie tonight. Any recommendations?"},
-    {"role": "assistant", "content": "How about a thriller movies? They can be quite engaging."},
+    {"role": "assistant", "content": "How about thriller movies? They can be quite engaging."},
    {"role": "user", "content": "I’m not a big fan of thriller movies but I love sci-fi movies."},
    {"role": "assistant", "content": "Got it! I'll avoid thriller recommendations and suggest sci-fi movies in the future."}
 ]
@@ -57,7 +55,7 @@ const config = {
 const memory = new Memory(config);
 const messages = [
    {"role": "user", "content": "I'm planning to watch a movie tonight. Any recommendations?"},
-    {"role": "assistant", "content": "How about a thriller movies? They can be quite engaging."},
+    {"role": "assistant", "content": "How about thriller movies? They can be quite engaging."},
    {"role": "user", "content": "I’m not a big fan of thriller movies but I love sci-fi movies."},
    {"role": "assistant", "content": "Got it! I'll avoid thriller recommendations and suggest sci-fi movies in the future."}
 ]
@@ -2,7 +2,6 @@
 title: LangChain
 ---

-<Snippet file="blank-notif.mdx" />

 Mem0 supports LangChain as a provider to access a wide range of LLM models. LangChain is a framework for developing applications powered by language models, making it easy to integrate various LLM providers through a consistent interface.

@@ -21,7 +20,7 @@ os.environ["OPENAI_API_KEY"] = "your-api-key"

 # Initialize a LangChain model directly
 openai_model = ChatOpenAI(
-    model="gpt-4o",
+    model="gpt-4.1-nano-2025-04-14",
    temperature=0.2,
    max_tokens=2000
 )
@@ -39,7 +38,7 @@ config = {
 m = Memory.from_config(config)
 messages = [
    {"role": "user", "content": "I'm planning to watch a movie tonight. Any recommendations?"},
-    {"role": "assistant", "content": "How about a thriller movies? They can be quite engaging."},
+    {"role": "assistant", "content": "How about thriller movies? They can be quite engaging."},
    {"role": "user", "content": "I'm not a big fan of thriller movies but I love sci-fi movies."},
    {"role": "assistant", "content": "Got it! I'll avoid thriller recommendations and suggest sci-fi movies in the future."}
 ]
@@ -47,34 +46,34 @@ m.add(messages, user_id="alice", metadata={"category": "movies"})
 ```

 ```typescript TypeScript
-import { Memory } from "mem0ai";
+import { Memory } from 'mem0ai/oss';
 import { ChatOpenAI } from "@langchain/openai";

-const openai_model = new ChatOpenAI({
-    model: "gpt-4o",
+// Initialize a LangChain model directly
+const openaiModel = new ChatOpenAI({
+    modelName: "gpt-4",
    temperature: 0.2,
-    max_tokens: 2000
-})
+    maxTokens: 2000,
+    apiKey: process.env.OPENAI_API_KEY,
+});

 const config = {
-    "llm": {
-        "provider": "langchain",
-        "config": {
-            "model": openai_model
-        }
-    }
-}
+  llm: {
+    provider: 'langchain',
+    config: {
+      model: openaiModel,
+    },
+  },
+};

 const memory = new Memory(config);
-
 const messages = [
-    { role: "user", content: "I'm planning to watch a movie tonight. Any recommendations?" },
-    { role: "assistant", content: "How about a thriller movies? They can be quite engaging." },
-    { role: "user", content: "I'm not a big fan of thriller movies but I love sci-fi movies." },
-    { role: "assistant", content: "Got it! I'll avoid thriller recommendations and suggest sci-fi movies in the future." }
+    {"role": "user", "content": "I'm planning to watch a movie tonight. Any recommendations?"},
+    {"role": "assistant", "content": "How about thriller movies? They can be quite engaging."},
+    {"role": "user", "content": "I'm not a big fan of thriller movies but I love sci-fi movies."},
+    {"role": "assistant", "content": "Got it! I'll avoid thriller recommendations and suggest sci-fi movies in the future."}
 ]
-
-memory.add(messages, user_id="alice", metadata={"category": "movies"})
+await memory.add(messages, { userId: "alice", metadata: { category: "movies" } });
 ```
 </CodeGroup>

@@ -1,5 +1,3 @@
-<Snippet file="blank-notif.mdx" />
-
 [Litellm](https://litellm.vercel.app/docs/) is compatible with over 100 large language models (LLMs), all using a standardized input/output format. You can explore the [available models](https://litellm.vercel.app/docs/providers) to use with Litellm. Ensure you set the `API_KEY` for the model you choose to use.

 ## Usage
@@ -14,7 +12,7 @@ config = {
    "llm": {
        "provider": "litellm",
        "config": {
-            "model": "gpt-4o-mini",
+            "model": "gpt-4.1-nano-2025-04-14",
            "temperature": 0.2,
            "max_tokens": 2000,
        }
@@ -24,7 +22,7 @@ config = {
 m = Memory.from_config(config)
 messages = [
    {"role": "user", "content": "I'm planning to watch a movie tonight. Any recommendations?"},
-    {"role": "assistant", "content": "How about a thriller movies? They can be quite engaging."},
+    {"role": "assistant", "content": "How about thriller movies? They can be quite engaging."},
    {"role": "user", "content": "I’m not a big fan of thriller movies but I love sci-fi movies."},
    {"role": "assistant", "content": "Got it! I'll avoid thriller recommendations and suggest sci-fi movies in the future."}
 ]
@@ -2,8 +2,6 @@
 title: LM Studio
 ---

-<Snippet file="blank-notif.mdx" />
-
 To use LM Studio with Mem0, you'll need to have LM Studio running locally with its server enabled. LM Studio provides a way to run local LLMs with an OpenAI-compatible API.

 ## Usage
@@ -31,7 +29,7 @@ config = {
 m = Memory.from_config(config)
 messages = [
    {"role": "user", "content": "I'm planning to watch a movie tonight. Any recommendations?"},
-    {"role": "assistant", "content": "How about a thriller movies? They can be quite engaging."},
+    {"role": "assistant", "content": "How about thriller movies? They can be quite engaging."},
    {"role": "user", "content": "I'm not a big fan of thriller movies but I love sci-fi movies."},
    {"role": "assistant", "content": "Got it! I'll avoid thriller recommendations and suggest sci-fi movies in the future."}
 ]
@@ -59,7 +57,7 @@ config = {
 m = Memory.from_config(config)
 messages = [
    {"role": "user", "content": "I'm planning to watch a movie tonight. Any recommendations?"},
-    {"role": "assistant", "content": "How about a thriller movies? They can be quite engaging."},
+    {"role": "assistant", "content": "How about thriller movies? They can be quite engaging."},
    {"role": "user", "content": "I'm not a big fan of thriller movies but I love sci-fi movies."},
    {"role": "assistant", "content": "Got it! I'll avoid thriller recommendations and suggest sci-fi movies in the future."}
 ]
@@ -2,8 +2,6 @@
 title: Mistral AI
 ---

-<Snippet file="blank-notif.mdx" />
-
 To use mistral's models, please obtain the Mistral AI api key from their [console](https://console.mistral.ai/). Set the `MISTRAL_API_KEY` environment variable to use the model as given below in the example.

 ## Usage
@@ -30,7 +28,7 @@ config = {
 m = Memory.from_config(config)
 messages = [
    {"role": "user", "content": "I'm planning to watch a movie tonight. Any recommendations?"},
-    {"role": "assistant", "content": "How about a thriller movies? They can be quite engaging."},
+    {"role": "assistant", "content": "How about thriller movies? They can be quite engaging."},
    {"role": "user", "content": "I’m not a big fan of thriller movies but I love sci-fi movies."},
    {"role": "assistant", "content": "Got it! I'll avoid thriller recommendations and suggest sci-fi movies in the future."}
 ]
@@ -55,7 +53,7 @@ const config = {
 const memory = new Memory(config);
 const messages = [
    {"role": "user", "content": "I'm planning to watch a movie tonight. Any recommendations?"},
-    {"role": "assistant", "content": "How about a thriller movies? They can be quite engaging."},
+    {"role": "assistant", "content": "How about thriller movies? They can be quite engaging."},
    {"role": "user", "content": "I'm not a big fan of thriller movies but I love sci-fi movies."},
    {"role": "assistant", "content": "Got it! I'll avoid thriller recommendations and suggest sci-fi movies in the future."}
 ]
@@ -1,10 +1,13 @@
-<Snippet file="blank-notif.mdx" />
+---
+title: Ollama
+---

-You can use LLMs from Ollama to run Mem0 locally. These [models](https://ollama.com/search?c=tools) support tool support.
+You can use LLMs from Ollama to run Mem0 locally. These [models](https://ollama.com/search?c=tools) support tool calling.

 ## Usage

-```python
+<CodeGroup>
+```python Python
 import os
 from mem0 import Memory

@@ -24,13 +27,38 @@ config = {
 m = Memory.from_config(config)
 messages = [
    {"role": "user", "content": "I'm planning to watch a movie tonight. Any recommendations?"},
-    {"role": "assistant", "content": "How about a thriller movies? They can be quite engaging."},
-    {"role": "user", "content": "I’m not a big fan of thriller movies but I love sci-fi movies."},
+    {"role": "assistant", "content": "How about thriller movies? They can be quite engaging."},
+    {"role": "user", "content": "I'm not a big fan of thriller movies but I love sci-fi movies."},
    {"role": "assistant", "content": "Got it! I'll avoid thriller recommendations and suggest sci-fi movies in the future."}
 ]
 m.add(messages, user_id="alice", metadata={"category": "movies"})
 ```

+```typescript TypeScript
+import { Memory } from 'mem0ai/oss';
+
+const config = {
+  llm: {
+    provider: 'ollama',
+    config: {
+      model: 'llama3.1:8b', // or any other Ollama model
+      url: 'http://localhost:11434', // Ollama server URL
+      temperature: 0.1,
+    },
+  },
+};
+
+const memory = new Memory(config);
+const messages = [
+    {"role": "user", "content": "I'm planning to watch a movie tonight. Any recommendations?"},
+    {"role": "assistant", "content": "How about thriller movies? They can be quite engaging."},
+    {"role": "user", "content": "I'm not a big fan of thriller movies but I love sci-fi movies."},
+    {"role": "assistant", "content": "Got it! I'll avoid thriller recommendations and suggest sci-fi movies in the future."}
+]
+await memory.add(messages, { userId: "alice", metadata: { category: "movies" } });
+```
+</CodeGroup>
+
 ## Config

 All available parameters for the `ollama` config are present in [Master List of All Params in Config](../config).
@@ -2,8 +2,6 @@
 title: OpenAI
 ---

-<Snippet file="blank-notif.mdx" />
-
 To use OpenAI LLM models, you have to set the `OPENAI_API_KEY` environment variable. You can obtain the OpenAI API key from the [OpenAI Platform](https://platform.openai.com/account/api-keys).

 > **Note**: The following are currently unsupported with reasoning models `Parallel tool calling`,`temperature`, `top_p`, `presence_penalty`, `frequency_penalty`, `logprobs`, `top_logprobs`, `logit_bias`, `max_tokens`
@@ -21,7 +19,7 @@ config = {
    "llm": {
        "provider": "openai",
        "config": {
-            "model": "gpt-4o",
+            "model": "gpt-4.1-nano-2025-04-14",
            "temperature": 0.2,
            "max_tokens": 2000,
        }
@@ -42,7 +40,7 @@ config = {
 m = Memory.from_config(config)
 messages = [
    {"role": "user", "content": "I'm planning to watch a movie tonight. Any recommendations?"},
-    {"role": "assistant", "content": "How about a thriller movies? They can be quite engaging."},
+    {"role": "assistant", "content": "How about thriller movies? They can be quite engaging."},
    {"role": "user", "content": "I’m not a big fan of thriller movies but I love sci-fi movies."},
    {"role": "assistant", "content": "Got it! I'll avoid thriller recommendations and suggest sci-fi movies in the future."}
 ]
@@ -67,7 +65,7 @@ const config = {
 const memory = new Memory(config);
 const messages = [
    {"role": "user", "content": "I'm planning to watch a movie tonight. Any recommendations?"},
-    {"role": "assistant", "content": "How about a thriller movies? They can be quite engaging."},
+    {"role": "assistant", "content": "How about thriller movies? They can be quite engaging."},
    {"role": "user", "content": "I’m not a big fan of thriller movies but I love sci-fi movies."},
    {"role": "assistant", "content": "Got it! I'll avoid thriller recommendations and suggest sci-fi movies in the future."}
 ]
@@ -87,7 +85,7 @@ config = {
    "llm": {
        "provider": "openai_structured",
        "config": {
-            "model": "gpt-4o-2024-08-06",
+            "model": "gpt-4.1-nano-2025-04-14",
            "temperature": 0.0,
        }
    }
@@ -2,8 +2,6 @@
 title: Sarvam AI
 ---

-<Snippet file="blank-notif.mdx" />
-
 **Sarvam AI** is an Indian AI company developing language models with a focus on Indian languages and cultural context. Their latest model **Sarvam-M** is designed to understand and generate content in multiple Indian languages while maintaining high performance in English.

 To use Sarvam AI's models, please set the `SARVAM_API_KEY` which you can get from their [platform](https://dashboard.sarvam.ai/).
@@ -30,7 +28,7 @@ config = {
 m = Memory.from_config(config)
 messages = [
    {"role": "user", "content": "I'm planning to watch a movie tonight. Any recommendations?"},
-    {"role": "assistant", "content": "How about a thriller movies? They can be quite engaging."},
+    {"role": "assistant", "content": "How about thriller movies? They can be quite engaging."},
    {"role": "user", "content": "I'm not a big fan of thriller movies but I love sci-fi movies."},
    {"role": "assistant", "content": "Got it! I'll avoid thriller recommendations and suggest sci-fi movies in the future."}
 ]
@@ -1,6 +1,8 @@
-<Snippet file="blank-notif.mdx" />
+---
+title: Together
+---

-To use TogetherAI LLM models, you have to set the `TOGETHER_API_KEY` environment variable. You can obtain the TogetherAI API key from their [Account settings page](https://api.together.xyz/settings/api-keys).
+To use Together LLM models, you have to set the `TOGETHER_API_KEY` environment variable. You can obtain the Together API key from their [Account settings page](https://api.together.xyz/settings/api-keys).

 ## Usage

@@ -25,7 +27,7 @@ config = {
 m = Memory.from_config(config)
 messages = [
    {"role": "user", "content": "I'm planning to watch a movie tonight. Any recommendations?"},
-    {"role": "assistant", "content": "How about a thriller movies? They can be quite engaging."},
+    {"role": "assistant", "content": "How about thriller movies? They can be quite engaging."},
    {"role": "user", "content": "I’m not a big fan of thriller movies but I love sci-fi movies."},
    {"role": "assistant", "content": "Got it! I'll avoid thriller recommendations and suggest sci-fi movies in the future."}
 ]
@@ -34,4 +36,4 @@ m.add(messages, user_id="alice", metadata={"category": "movies"})

 ## Config

-All available parameters for the `togetherai` config are present in [Master List of All Params in Config](../config).
+All available parameters for the `together` config are present in [Master List of All Params in Config](../config).
@@ -2,8 +2,6 @@
 title: vLLM
 ---

-<Snippet file="blank-notif.mdx" />
-
 [vLLM](https://docs.vllm.ai/) is a high-performance inference engine for large language models that provides significant performance improvements for local inference. It's designed to maximize throughput and memory efficiency for serving LLMs.

 ## Prerequisites
@@ -2,8 +2,6 @@
 title: xAI
 ---

-<Snippet file="blank-notif.mdx" />
-
 [xAI](https://x.ai/) is a new AI company founded by Elon Musk that develops large language models, including Grok. Grok is trained on real-time data from X (formerly Twitter) and aims to provide accurate, up-to-date responses with a touch of wit and humor.

 In order to use LLMs from xAI, go to their [platform](https://console.x.ai) and get the API key. Set the API key as `XAI_API_KEY` environment variable to use the model as given below in the example.
@@ -31,7 +29,7 @@ config = {
 m = Memory.from_config(config)
 messages = [
    {"role": "user", "content": "I'm planning to watch a movie tonight. Any recommendations?"},
-    {"role": "assistant", "content": "How about a thriller movies? They can be quite engaging."},
+    {"role": "assistant", "content": "How about thriller movies? They can be quite engaging."},
    {"role": "user", "content": "I’m not a big fan of thriller movies but I love sci-fi movies."},
    {"role": "assistant", "content": "Got it! I'll avoid thriller recommendations and suggest sci-fi movies in the future."}
 ]
@@ -1,11 +1,7 @@
 ---
 title: Overview
-icon: "info"
-iconType: "solid"
 ---

-<Snippet file="blank-notif.mdx" />
-
 Mem0 includes built-in support for various popular large language models. Memory can utilize the LLM provided by the user, ensuring efficient use for specific needs.

 ## Usage
@@ -30,8 +26,8 @@ See the list of supported LLMs below.
  <Card title="Together" href="/components/llms/models/together" />
  <Card title="Groq" href="/components/llms/models/groq" />
  <Card title="Litellm" href="/components/llms/models/litellm" />
-  <Card title="Mistral AI" href="/components/llms/models/mistral_ai" />
-  <Card title="Google AI" href="/components/llms/models/google_ai" />
+  <Card title="Mistral AI" href="/components/llms/models/mistral_AI" />
+  <Card title="Google AI" href="/components/llms/models/google_AI" />
  <Card title="AWS bedrock" href="/components/llms/models/aws_bedrock" />
  <Card title="DeepSeek" href="/components/llms/models/deepseek" />
  <Card title="xAI" href="/components/llms/models/xAI" />
@@ -0,0 +1,105 @@
+---
+title: Config
+description: "Configuration options for rerankers in Mem0"
+---
+
+## Common Configuration Parameters
+
+All rerankers share these common configuration parameters:
+
+| Parameter  | Description                                         | Type  | Default  |
+| ---------- | --------------------------------------------------- | ----- | -------- |
+| `provider` | Reranker provider name                              | `str` | Required |
+| `top_k`    | Maximum number of results to return after reranking | `int` | `None`   |
+| `api_key`  | API key for the reranker service                    | `str` | `None`   |
+
+## Provider-Specific Configuration
+
+### Zero Entropy
+
+| Parameter | Description                                  | Type  | Default      |
+| --------- | -------------------------------------------- | ----- | ------------ |
+| `model`   | Model to use: `zerank-1` or `zerank-1-small` | `str` | `"zerank-1"` |
+| `api_key` | Zero Entropy API key                         | `str` | `None`       |
+
+### Cohere
+
+| Parameter            | Description                                  | Type   | Default                 |
+| -------------------- | -------------------------------------------- | ------ | ----------------------- |
+| `model`              | Cohere rerank model                          | `str`  | `"rerank-english-v3.0"` |
+| `api_key`            | Cohere API key                               | `str`  | `None`                  |
+| `return_documents`   | Whether to return document texts in response | `bool` | `False`                 |
+| `max_chunks_per_doc` | Maximum chunks per document                  | `int`  | `None`                  |
+
+### Sentence Transformer
+
+| Parameter           | Description                                  | Type   | Default                                  |
+| ------------------- | -------------------------------------------- | ------ | ---------------------------------------- |
+| `model`             | HuggingFace cross-encoder model name         | `str`  | `"cross-encoder/ms-marco-MiniLM-L-6-v2"` |
+| `device`            | Device to run model on (`cpu`, `cuda`, etc.) | `str`  | `None`                                   |
+| `batch_size`        | Batch size for processing                    | `int`  | `32`                                     |
+| `show_progress_bar` | Show progress during processing              | `bool` | `False`                                  |
+
+### Hugging Face
+
+| Parameter | Description                                  | Type  | Default                     |
+| --------- | -------------------------------------------- | ----- | --------------------------- |
+| `model`   | HuggingFace reranker model name              | `str` | `"BAAI/bge-reranker-large"` |
+| `api_key` | HuggingFace API token                        | `str` | `None`                      |
+| `device`  | Device to run model on (`cpu`, `cuda`, etc.) | `str` | `None`                      |
+
+### LLM-based
+
+| Parameter        | Description                                | Type    | Default                |
+| ---------------- | ------------------------------------------ | ------- | ---------------------- |
+| `model`          | LLM model to use for scoring               | `str`   | `"gpt-4o-mini"`        |
+| `provider`       | LLM provider (`openai`, `anthropic`, etc.) | `str`   | `"openai"`             |
+| `api_key`        | API key for LLM provider                   | `str`   | `None`                 |
+| `temperature`    | Temperature for LLM generation             | `float` | `0.0`                  |
+| `max_tokens`     | Maximum tokens for LLM response            | `int`   | `100`                  |
+| `scoring_prompt` | Custom prompt template for scoring         | `str`   | Default scoring prompt |
+
+### LLM Reranker
+
+| Parameter      | Description                 | Type   | Default  |
+| -------------- | --------------------------- | ------ | -------- |
+| `llm.provider` | LLM provider for reranking  | `str`  | Required |
+| `llm.config`   | LLM configuration object    | `dict` | Required |
+| `top_n`        | Number of results to return | `int`  | `None`   |
+
+## Environment Variables
+
+You can set API keys using environment variables:
+
+- `ZERO_ENTROPY_API_KEY` - Zero Entropy API key
+- `COHERE_API_KEY` - Cohere API key
+- `HUGGINGFACE_API_KEY` - HuggingFace API token
+- `OPENAI_API_KEY` - OpenAI API key (for LLM-based reranker)
+- `ANTHROPIC_API_KEY` - Anthropic API key (for LLM-based reranker)
+
+## Basic Configuration Example
+
+```python Python
+config = {
+    "vector_store": {
+        "provider": "chroma",
+        "config": {
+            "collection_name": "my_memories",
+            "path": "./chroma_db"
+        }
+    },
+    "llm": {
+        "provider": "openai",
+        "config": {
+            "model": "gpt-4.1-nano-2025-04-14"
+        }
+    },
+    "reranker": {
+        "provider": "zero_entropy",
+        "config": {
+            "model": "zerank-1",
+            "top_k": 5
+        }
+    }
+}
+```
@@ -0,0 +1,220 @@
+---
+title: Custom Prompts
+---
+
+When using LLM rerankers, you can customize the prompts used for ranking to better suit your specific use case and domain.
+
+## Default Prompt
+
+The default LLM reranker prompt is designed to be general-purpose:
+
+```
+Given a query and a list of memory entries, rank the memory entries based on their relevance to the query.
+Rate each memory on a scale of 1-10 where 10 is most relevant.
+
+Query: {query}
+
+Memory entries:
+{memories}
+
+Provide your ranking as a JSON array with scores for each memory.
+```
+
+## Custom Prompt Configuration
+
+You can provide a custom prompt template when configuring the LLM reranker:
+
+```python
+from mem0 import Memory
+
+custom_prompt = """
+You are an expert at ranking memories for a personal AI assistant.
+Given a user query and a list of memory entries, rank each memory based on:
+1. Direct relevance to the query
+2. Temporal relevance (recent memories may be more important)
+3. Emotional significance
+4. Actionability
+
+Query: {query}
+User Context: {user_context}
+
+Memory entries:
+{memories}
+
+Rate each memory from 1-10 and provide reasoning.
+Return as JSON: {{"rankings": [{{"index": 0, "score": 8, "reason": "..."}}]}}
+"""
+
+config = {
+    "reranker": {
+        "provider": "llm_reranker",
+        "config": {
+            "llm": {
+                "provider": "openai",
+                "config": {
+                    "model": "gpt-4.1-nano-2025-04-14",
+                    "api_key": "your-openai-key"
+                }
+            },
+            "custom_prompt": custom_prompt,
+            "top_n": 5
+        }
+    }
+}
+
+memory = Memory.from_config(config)
+```
+
+## Prompt Variables
+
+Your custom prompt can use the following variables:
+
+| Variable         | Description                           |
+| ---------------- | ------------------------------------- |
+| `{query}`        | The search query                      |
+| `{memories}`     | The list of memory entries to rank    |
+| `{user_id}`      | The user ID (if available)            |
+| `{user_context}` | Additional user context (if provided) |
+
+## Domain-Specific Examples
+
+### Customer Support
+
+```python
+customer_support_prompt = """
+You are ranking customer support conversation memories.
+Prioritize memories that:
+- Relate to the current customer issue
+- Show previous resolution patterns
+- Indicate customer preferences or constraints
+
+Query: {query}
+Customer Context: Previous interactions with this customer
+
+Memories:
+{memories}
+
+Rank each memory 1-10 based on support relevance.
+"""
+```
+
+### Educational Content
+
+```python
+educational_prompt = """
+Rank these learning memories for a student query.
+Consider:
+- Prerequisite knowledge requirements
+- Learning progression and difficulty
+- Relevance to current learning objectives
+
+Student Query: {query}
+Learning Context: {user_context}
+
+Available memories:
+{memories}
+
+Score each memory for educational value (1-10).
+"""
+```
+
+### Personal Assistant
+
+```python
+personal_assistant_prompt = """
+Rank personal memories for relevance to the user's query.
+Consider:
+- Recent vs. historical importance
+- Personal preferences and habits
+- Contextual relationships between memories
+
+Query: {query}
+Personal context: {user_context}
+
+Memories to rank:
+{memories}
+
+Provide relevance scores (1-10) with brief explanations.
+"""
+```
+
+## Advanced Prompt Techniques
+
+### Multi-Criteria Ranking
+
+```python
+multi_criteria_prompt = """
+Evaluate memories using multiple criteria:
+
+1. RELEVANCE (40%): How directly related to the query
+2. RECENCY (20%): How recent the memory is
+3. IMPORTANCE (25%): Personal or business significance
+4. ACTIONABILITY (15%): How useful for next steps
+
+Query: {query}
+Context: {user_context}
+
+Memories:
+{memories}
+
+For each memory, provide:
+- Overall score (1-10)
+- Breakdown by criteria
+- Final ranking recommendation
+
+Format: JSON with detailed scoring
+"""
+```
+
+### Contextual Ranking
+
+```python
+contextual_prompt = """
+Consider the following context when ranking memories:
+- Current user situation: {user_context}
+- Time of day: {current_time}
+- Recent activities: {recent_activities}
+
+Query: {query}
+
+Rank these memories considering both direct relevance and contextual appropriateness:
+{memories}
+
+Provide contextually-aware relevance scores (1-10).
+"""
+```
+
+## Best Practices
+
+1. **Be Specific**: Clearly define what makes a memory relevant for your use case
+2. **Use Examples**: Include examples in your prompt for better model understanding
+3. **Structure Output**: Specify the exact JSON format you want returned
+4. **Test Iteratively**: Refine your prompt based on actual ranking performance
+5. **Consider Token Limits**: Keep prompts concise while being comprehensive
+
+## Prompt Testing
+
+You can test different prompts by comparing ranking results:
+
+```python
+# Test multiple prompt variations
+prompts = [
+    default_prompt,
+    custom_prompt_v1,
+    custom_prompt_v2
+]
+
+for i, prompt in enumerate(prompts):
+    config["reranker"]["config"]["custom_prompt"] = prompt
+    memory = Memory.from_config(config)
+
+    results = memory.search("test query", user_id="test_user")
+    print(f"Prompt {i+1} results: {results}")
+```
+
+## Common Issues
+
+- **Too Long**: Keep prompts under token limits for your chosen LLM
+- **Too Vague**: Be specific about ranking criteria
+- **Inconsistent Format**: Ensure JSON output format is clearly specified
+- **Missing Context**: Include relevant variables for your use case
@@ -0,0 +1,145 @@
+---
+title: Cohere
+description: "Reranking with Cohere"
+---
+
+Cohere provides enterprise-grade reranking models with excellent multilingual support and production-ready performance.
+
+## Models
+
+Cohere offers several reranking models:
+
+- **`rerank-english-v3.0`**: Latest English reranker with best performance
+- **`rerank-multilingual-v3.0`**: Multilingual support for global applications
+- **`rerank-english-v2.0`**: Previous generation English reranker
+
+## Installation
+
+```bash
+pip install cohere
+```
+
+## Configuration
+
+```python Python
+from mem0 import Memory
+
+config = {
+    "vector_store": {
+        "provider": "chroma",
+        "config": {
+            "collection_name": "my_memories",
+            "path": "./chroma_db"
+        }
+    },
+    "llm": {
+        "provider": "openai",
+        "config": {
+            "model": "gpt-4.1-nano-2025-04-14"
+        }
+    },
+    "reranker": {
+        "provider": "cohere",
+        "config": {
+            "model": "rerank-english-v3.0",
+            "api_key": "your-cohere-api-key",  # or set COHERE_API_KEY
+            "top_k": 5,
+            "return_documents": False,
+            "max_chunks_per_doc": None
+        }
+    }
+}
+
+memory = Memory.from_config(config)
+```
+
+## Environment Variables
+
+Set your API key as an environment variable:
+
+```bash
+export COHERE_API_KEY="your-api-key"
+```
+
+## Usage Example
+
+```python Python
+import os
+from mem0 import Memory
+
+# Set API key
+os.environ["COHERE_API_KEY"] = "your-api-key"
+
+# Initialize memory with Cohere reranker
+config = {
+    "vector_store": {"provider": "chroma"},
+    "llm": {"provider": "openai", "config": {"model": "gpt-4o-mini"}},
+    "rerank": {
+        "provider": "cohere",
+        "config": {
+            "model": "rerank-english-v3.0",
+            "top_k": 3
+        }
+    }
+}
+
+memory = Memory.from_config(config)
+
+# Add memories
+messages = [
+    {"role": "user", "content": "I work as a data scientist at Microsoft"},
+    {"role": "user", "content": "I specialize in machine learning and NLP"},
+    {"role": "user", "content": "I enjoy playing tennis on weekends"}
+]
+
+memory.add(messages, user_id="bob")
+
+# Search with reranking
+results = memory.search("What is the user's profession?", user_id="bob")
+
+for result in results['results']:
+    print(f"Memory: {result['memory']}")
+    print(f"Vector Score: {result['score']:.3f}")
+    print(f"Rerank Score: {result['rerank_score']:.3f}")
+    print()
+```
+
+## Multilingual Support
+
+For multilingual applications, use the multilingual model:
+
+```python Python
+config = {
+    "rerank": {
+        "provider": "cohere",
+        "config": {
+            "model": "rerank-multilingual-v3.0",
+            "top_k": 5
+        }
+    }
+}
+```
+
+## Configuration Parameters
+
+| Parameter            | Description                      | Type   | Default                 |
+| -------------------- | -------------------------------- | ------ | ----------------------- |
+| `model`              | Cohere rerank model to use       | `str`  | `"rerank-english-v3.0"` |
+| `api_key`            | Cohere API key                   | `str`  | `None`                  |
+| `top_k`              | Maximum documents to return      | `int`  | `None`                  |
+| `return_documents`   | Whether to return document texts | `bool` | `False`                 |
+| `max_chunks_per_doc` | Maximum chunks per document      | `int`  | `None`                  |
+
+## Features
+
+- **High Quality**: Enterprise-grade relevance scoring
+- **Multilingual**: Support for 100+ languages
+- **Scalable**: Production-ready with high throughput
+- **Reliable**: SLA-backed service with 99.9% uptime
+
+## Best Practices
+
+1. **Model Selection**: Use `rerank-english-v3.0` for English, `rerank-multilingual-v3.0` for other languages
+2. **Batch Processing**: Process multiple queries efficiently
+3. **Error Handling**: Implement retry logic for production systems
+4. **Monitoring**: Track reranking performance and costs
@@ -0,0 +1,350 @@
+---
+title: Hugging Face Reranker
+description: 'Access thousands of reranking models from Hugging Face Hub'
+---
+
+## Overview
+
+The Hugging Face reranker provider gives you access to thousands of reranking models available on the Hugging Face Hub. This includes popular models like BAAI's BGE rerankers and other state-of-the-art cross-encoder models.
+
+## Configuration
+
+### Basic Setup
+
+```python
+from mem0 import Memory
+
+config = {
+    "reranker": {
+        "provider": "huggingface",
+        "config": {
+            "model": "BAAI/bge-reranker-base",
+            "device": "cpu"
+        }
+    }
+}
+
+m = Memory.from_config(config)
+```
+
+### Configuration Parameters
+
+| Parameter | Type | Default | Description |
+|-----------|------|---------|-------------|
+| `model` | str | Required | Hugging Face model identifier |
+| `device` | str | "cpu" | Device to run model on ("cpu", "cuda", "mps") |
+| `batch_size` | int | 32 | Batch size for processing |
+| `max_length` | int | 512 | Maximum input sequence length |
+| `trust_remote_code` | bool | False | Allow remote code execution |
+
+### Advanced Configuration
+
+```python
+config = {
+    "reranker": {
+        "provider": "huggingface",
+        "config": {
+            "model": "BAAI/bge-reranker-large",
+            "device": "cuda",
+            "batch_size": 16,
+            "max_length": 512,
+            "trust_remote_code": False,
+            "model_kwargs": {
+                "torch_dtype": "float16"
+            }
+        }
+    }
+}
+```
+
+## Popular Models
+
+### BGE Rerankers (Recommended)
+
+```python
+# Base model - good balance of speed and quality
+config = {
+    "reranker": {
+        "provider": "huggingface",
+        "config": {
+            "model": "BAAI/bge-reranker-base",
+            "device": "cuda"
+        }
+    }
+}
+
+# Large model - better quality, slower
+config = {
+    "reranker": {
+        "provider": "huggingface",
+        "config": {
+            "model": "BAAI/bge-reranker-large",
+            "device": "cuda"
+        }
+    }
+}
+
+# v2 models - latest improvements
+config = {
+    "reranker": {
+        "provider": "huggingface",
+        "config": {
+            "model": "BAAI/bge-reranker-v2-m3",
+            "device": "cuda"
+        }
+    }
+}
+```
+
+### Multilingual Models
+
+```python
+# Multilingual BGE reranker
+config = {
+    "reranker": {
+        "provider": "huggingface",
+        "config": {
+            "model": "BAAI/bge-reranker-v2-multilingual",
+            "device": "cuda"
+        }
+    }
+}
+```
+
+### Domain-Specific Models
+
+```python
+# For code search
+config = {
+    "reranker": {
+        "provider": "huggingface",
+        "config": {
+            "model": "microsoft/codebert-base",
+            "device": "cuda"
+        }
+    }
+}
+
+# For biomedical content
+config = {
+    "reranker": {
+        "provider": "huggingface",
+        "config": {
+            "model": "dmis-lab/biobert-base-cased-v1.1",
+            "device": "cuda"
+        }
+    }
+}
+```
+
+## Usage Examples
+
+### Basic Usage
+
+```python
+from mem0 import Memory
+
+m = Memory.from_config(config)
+
+# Add some memories
+m.add("I love hiking in the mountains", user_id="alice")
+m.add("Pizza is my favorite food", user_id="alice")
+m.add("I enjoy reading science fiction books", user_id="alice")
+
+# Search with reranking
+results = m.search(
+    "What outdoor activities do I enjoy?",
+    user_id="alice",
+    rerank=True
+)
+
+for result in results["results"]:
+    print(f"Memory: {result['memory']}")
+    print(f"Score: {result['score']:.3f}")
+```
+
+### Batch Processing
+
+```python
+# Process multiple queries efficiently
+queries = [
+    "What are my hobbies?",
+    "What food do I like?",
+    "What books interest me?"
+]
+
+results = []
+for query in queries:
+    result = m.search(query, user_id="alice", rerank=True)
+    results.append(result)
+```
+
+## Performance Optimization
+
+### GPU Acceleration
+
+```python
+# Use GPU for better performance
+config = {
+    "reranker": {
+        "provider": "huggingface",
+        "config": {
+            "model": "BAAI/bge-reranker-base",
+            "device": "cuda",
+            "batch_size": 64,  # Increase batch size for GPU
+        }
+    }
+}
+```
+
+### Memory Optimization
+
+```python
+# For limited memory environments
+config = {
+    "reranker": {
+        "provider": "huggingface",
+        "config": {
+            "model": "BAAI/bge-reranker-base",
+            "device": "cpu",
+            "batch_size": 8,   # Smaller batch size
+            "max_length": 256, # Shorter sequences
+            "model_kwargs": {
+                "torch_dtype": "float16"  # Half precision
+            }
+        }
+    }
+}
+```
+
+## Model Comparison
+
+| Model | Size | Quality | Speed | Memory | Best For |
+|-------|------|---------|-------|---------|----------|
+| bge-reranker-base | 278M | Good | Fast | Low | General use |
+| bge-reranker-large | 560M | Better | Medium | Medium | High quality needs |
+| bge-reranker-v2-m3 | 568M | Best | Medium | Medium | Latest improvements |
+| bge-reranker-v2-multilingual | 568M | Good | Medium | Medium | Multiple languages |
+
+## Error Handling
+
+```python
+try:
+    results = m.search(
+        "test query",
+        user_id="alice",
+        rerank=True
+    )
+except Exception as e:
+    print(f"Reranking failed: {e}")
+    # Fall back to vector search only
+    results = m.search(
+        "test query",
+        user_id="alice",
+        rerank=False
+    )
+```
+
+## Custom Models
+
+### Using Private Models
+
+```python
+# Use a private model from Hugging Face
+config = {
+    "reranker": {
+        "provider": "huggingface",
+        "config": {
+            "model": "your-org/custom-reranker",
+            "device": "cuda",
+            "use_auth_token": "your-hf-token"
+        }
+    }
+}
+```
+
+### Local Model Path
+
+```python
+# Use a locally downloaded model
+config = {
+    "reranker": {
+        "provider": "huggingface",
+        "config": {
+            "model": "/path/to/local/model",
+            "device": "cuda"
+        }
+    }
+}
+```
+
+## Best Practices
+
+1. **Choose the Right Model**: Balance quality vs speed based on your needs
+2. **Use GPU**: Significantly faster than CPU for larger models
+3. **Optimize Batch Size**: Tune based on your hardware capabilities
+4. **Monitor Memory**: Watch GPU/CPU memory usage with large models
+5. **Cache Models**: Download once and reuse to avoid repeated downloads
+
+## Troubleshooting
+
+### Common Issues
+
+**Out of Memory Error**
+```python
+# Reduce batch size and sequence length
+config = {
+    "reranker": {
+        "provider": "huggingface",
+        "config": {
+            "model": "BAAI/bge-reranker-base",
+            "batch_size": 4,
+            "max_length": 256
+        }
+    }
+}
+```
+
+**Model Download Issues**
+```python
+# Set cache directory
+import os
+os.environ["TRANSFORMERS_CACHE"] = "/path/to/cache"
+
+# Or use offline mode
+config = {
+    "reranker": {
+        "provider": "huggingface",
+        "config": {
+            "model": "BAAI/bge-reranker-base",
+            "local_files_only": True
+        }
+    }
+}
+```
+
+**CUDA Not Available**
+```python
+import torch
+
+config = {
+    "reranker": {
+        "provider": "huggingface",
+        "config": {
+            "model": "BAAI/bge-reranker-base",
+            "device": "cuda" if torch.cuda.is_available() else "cpu"
+        }
+    }
+}
+```
+
+## Next Steps
+
+<CardGroup cols={2}>
+  <Card title="Reranker Overview" icon="sort" href="/components/rerankers/overview">
+    Learn about reranking concepts
+  </Card>
+  <Card title="Configuration Guide" icon="gear" href="/components/rerankers/config">
+    Detailed configuration options
+  </Card>
+</CardGroup>
@@ -0,0 +1,226 @@
+---
+title: LLM as Reranker
+description: 'Flexible reranking using LLMs'
+---
+
+<Warning>
+**This page has been superseded.** Please see [LLM Reranker](/components/rerankers/models/llm_reranker) for the complete and up-to-date documentation on using LLMs for reranking.
+</Warning>
+
+LLM-based reranker provides maximum flexibility by using any Large Language Model to score document relevance. This approach allows for custom prompts and domain-specific scoring logic.
+
+## Supported LLM Providers
+
+Any LLM provider supported by Mem0 can be used for reranking:
+
+- **OpenAI**: GPT-4, GPT-3.5-turbo, etc.
+- **Anthropic**: Claude models
+- **Together**: Open-source models
+- **Groq**: Fast inference
+- **Ollama**: Local models
+- And more...
+
+## Configuration
+
+```python Python
+from mem0 import Memory
+
+config = {
+    "vector_store": {
+        "provider": "chroma",
+        "config": {
+            "collection_name": "my_memories",
+            "path": "./chroma_db"
+        }
+    },
+    "llm": {
+        "provider": "openai",
+        "config": {
+            "model": "gpt-4o-mini"
+        }
+    },
+    "reranker": {
+        "provider": "llm",
+        "config": {
+            "model": "gpt-4o-mini",
+            "provider": "openai",
+            "api_key": "your-openai-api-key",  # or set OPENAI_API_KEY
+            "top_k": 5,
+            "temperature": 0.0
+        }
+    }
+}
+
+memory = Memory.from_config(config)
+```
+
+## Custom Scoring Prompt
+
+You can provide a custom prompt for relevance scoring:
+
+```python Python
+custom_prompt = """You are a relevance scoring assistant. Rate how well this document answers the query.
+
+Query: "{query}"
+Document: "{document}"
+
+Score from 0.0 to 1.0 where:
+- 1.0: Perfect match, directly answers the query
+- 0.8-0.9: Highly relevant, good match  
+- 0.6-0.7: Moderately relevant, partial match
+- 0.4-0.5: Slightly relevant, limited useful information
+- 0.0-0.3: Not relevant or no useful information
+
+Provide only a single numerical score between 0.0 and 1.0."""
+
+config["reranker"]["config"]["scoring_prompt"] = custom_prompt
+```
+
+## Usage Example
+
+```python Python
+import os
+from mem0 import Memory
+
+# Set API key
+os.environ["OPENAI_API_KEY"] = "your-api-key"
+
+# Initialize memory with LLM reranker
+config = {
+    "vector_store": {"provider": "chroma"},
+    "llm": {"provider": "openai", "config": {"model": "gpt-4o-mini"}},
+    "reranker": {
+        "provider": "llm",
+        "config": {
+            "model": "gpt-4o-mini",
+            "provider": "openai",
+            "temperature": 0.0
+        }
+    }
+}
+
+memory = Memory.from_config(config)
+
+# Add memories
+messages = [
+    {"role": "user", "content": "I'm learning Python programming"},
+    {"role": "user", "content": "I find object-oriented programming challenging"}, 
+    {"role": "user", "content": "I love hiking in national parks"}
+]
+
+memory.add(messages, user_id="david")
+
+# Search with LLM reranking
+results = memory.search("What programming topics is the user studying?", user_id="david")
+
+for result in results['results']:
+    print(f"Memory: {result['memory']}")
+    print(f"Vector Score: {result['score']:.3f}")
+    print(f"Rerank Score: {result['rerank_score']:.3f}")
+    print()
+```
+
+```text Output
+Memory: I'm learning Python programming
+Vector Score: 0.856
+Rerank Score: 0.920
+
+Memory: I find object-oriented programming challenging
+Vector Score: 0.782
+Rerank Score: 0.850
+```
+
+## Domain-Specific Scoring
+
+Create specialized scoring for your domain:
+
+```python Python
+medical_prompt = """You are a medical relevance expert. Score how relevant this medical record is to the clinical query.
+
+Clinical Query: "{query}"
+Medical Record: "{document}"
+
+Consider:
+- Clinical relevance and accuracy
+- Patient safety implications
+- Diagnostic value
+- Treatment relevance
+
+Score from 0.0 to 1.0. Provide only the numerical score."""
+
+config = {
+    "reranker": {
+        "provider": "llm",
+        "config": {
+            "model": "gpt-4o-mini",
+            "provider": "openai",
+            "scoring_prompt": medical_prompt,
+            "temperature": 0.0
+        }
+    }
+}
+```
+
+## Multiple LLM Providers
+
+Use different LLM providers for reranking:
+
+```python Python
+# Using Anthropic Claude
+anthropic_config = {
+    "reranker": {
+        "provider": "llm",
+        "config": {
+            "model": "claude-3-haiku-20240307",
+            "provider": "anthropic",
+            "temperature": 0.0
+        }
+    }
+}
+
+# Using local Ollama model
+ollama_config = {
+    "reranker": {
+        "provider": "llm",
+        "config": {
+            "model": "llama2:7b",
+            "provider": "ollama",
+            "temperature": 0.0
+        }
+    }
+}
+```
+
+## Configuration Parameters
+
+| Parameter | Description | Type | Default |
+|-----------|-------------|------|---------|
+| `model` | LLM model to use for scoring | `str` | `"gpt-4o-mini"` |
+| `provider` | LLM provider name | `str` | `"openai"` |
+| `api_key` | API key for the LLM provider | `str` | `None` |
+| `top_k` | Maximum documents to return | `int` | `None` |
+| `temperature` | Temperature for LLM generation | `float` | `0.0` |
+| `max_tokens` | Maximum tokens for LLM response | `int` | `100` |
+| `scoring_prompt` | Custom prompt template | `str` | Default prompt |
+
+## Advantages
+
+- **Maximum Flexibility**: Custom prompts for any use case
+- **Domain Expertise**: Leverage LLM knowledge for specialized domains
+- **Interpretability**: Understand scoring through prompt engineering
+- **Multi-criteria**: Score based on multiple relevance factors
+
+## Considerations
+
+- **Latency**: Higher latency than specialized rerankers
+- **Cost**: LLM API costs per reranking operation
+- **Consistency**: May have slight variations in scoring
+- **Prompt Engineering**: Requires careful prompt design
+
+## Best Practices
+
+1. **Temperature**: Use 0.0 for consistent scoring
+2. **Prompt Design**: Be specific about scoring criteria
+3. **Token Efficiency**: Keep prompts concise to reduce costs
+4. **Caching**: Cache results for repeated queries when possible
+5. **Fallback**: Handle API errors gracefully
@@ -0,0 +1,489 @@
+---
+title: LLM Reranker
+description: 'Use any language model as a reranker with custom prompts'
+---
+
+## Overview
+
+The LLM reranker allows you to use any supported language model as a reranker. This approach uses prompts to instruct the LLM to score and rank memories based on their relevance to the query. While slower than specialized rerankers, it offers maximum flexibility and can be fine-tuned with custom prompts.
+
+## Configuration
+
+### Basic Setup
+
+```python
+from mem0 import Memory
+
+config = {
+    "reranker": {
+        "provider": "llm_reranker",
+        "config": {
+            "llm": {
+                "provider": "openai",
+                "config": {
+                    "model": "gpt-4",
+                    "api_key": "your-openai-api-key"
+                }
+            }
+        }
+    }
+}
+
+m = Memory.from_config(config)
+```
+
+### Configuration Parameters
+
+| Parameter | Type | Default | Description |
+|-----------|------|---------|-------------|
+| `llm` | dict | Required | LLM configuration object |
+| `top_k` | int | 10 | Number of results to rerank |
+| `temperature` | float | 0.0 | LLM temperature for consistency |
+| `custom_prompt` | str | None | Custom reranking prompt |
+| `score_range` | tuple | (0, 10) | Score range for relevance |
+
+### Advanced Configuration
+
+```python
+config = {
+    "reranker": {
+        "provider": "llm_reranker",
+        "config": {
+            "llm": {
+                "provider": "anthropic",
+                "config": {
+                    "model": "claude-3-sonnet-20240229",
+                    "api_key": "your-anthropic-api-key"
+                }
+            },
+            "top_k": 15,
+            "temperature": 0.0,
+            "score_range": (1, 5),
+            "custom_prompt": """
+            Rate the relevance of each memory to the query on a scale of 1-5.
+            Consider semantic similarity, context, and practical utility.
+            Only provide the numeric score.
+            """
+        }
+    }
+}
+```
+
+## Supported LLM Providers
+
+### OpenAI
+
+```python
+config = {
+    "reranker": {
+        "provider": "llm_reranker",
+        "config": {
+            "llm": {
+                "provider": "openai",
+                "config": {
+                    "model": "gpt-4",
+                    "api_key": "your-openai-api-key",
+                    "temperature": 0.0
+                }
+            }
+        }
+    }
+}
+```
+
+### Anthropic
+
+```python
+config = {
+    "reranker": {
+        "provider": "llm_reranker",
+        "config": {
+            "llm": {
+                "provider": "anthropic",
+                "config": {
+                    "model": "claude-3-sonnet-20240229",
+                    "api_key": "your-anthropic-api-key"
+                }
+            }
+        }
+    }
+}
+```
+
+### Ollama (Local)
+
+```python
+config = {
+    "reranker": {
+        "provider": "llm_reranker",
+        "config": {
+            "llm": {
+                "provider": "ollama",
+                "config": {
+                    "model": "llama2",
+                    "ollama_base_url": "http://localhost:11434"
+                }
+            }
+        }
+    }
+}
+```
+
+### Azure OpenAI
+
+```python
+config = {
+    "reranker": {
+        "provider": "llm_reranker",
+        "config": {
+            "llm": {
+                "provider": "azure_openai",
+                "config": {
+                    "model": "gpt-4",
+                    "api_key": "your-azure-api-key",
+                    "azure_endpoint": "https://your-resource.openai.azure.com/",
+                    "azure_deployment": "gpt-4-deployment"
+                }
+            }
+        }
+    }
+}
+```
+
+## Custom Prompts
+
+### Default Prompt Behavior
+
+The default prompt asks the LLM to score relevance on a 0-10 scale:
+
+```
+Given a query and a memory, rate how relevant the memory is to answering the query.
+Score from 0 (completely irrelevant) to 10 (perfectly relevant).
+Only provide the numeric score.
+
+Query: {query}
+Memory: {memory}
+Score:
+```
+
+### Custom Prompt Examples
+
+#### Domain-Specific Scoring
+
+```python
+custom_prompt = """
+You are a medical information specialist. Rate how relevant each memory is for answering the medical query.
+Consider clinical accuracy, specificity, and practical applicability.
+Rate from 1-10 where:
+- 1-3: Irrelevant or potentially harmful
+- 4-6: Somewhat relevant but incomplete
+- 7-8: Relevant and helpful
+- 9-10: Highly relevant and clinically useful
+
+Query: {query}
+Memory: {memory}
+Score:
+"""
+
+config = {
+    "reranker": {
+        "provider": "llm_reranker",
+        "config": {
+            "llm": {
+                "provider": "openai",
+                "config": {
+                    "model": "gpt-4",
+                    "api_key": "your-api-key"
+                }
+            },
+            "custom_prompt": custom_prompt
+        }
+    }
+}
+```
+
+#### Contextual Relevance
+
+```python
+contextual_prompt = """
+Rate how well this memory answers the specific question asked.
+Consider:
+- Direct relevance to the question
+- Completeness of information
+- Recency and accuracy
+- Practical usefulness
+
+Rate 1-5:
+1 = Not relevant
+2 = Slightly relevant
+3 = Moderately relevant
+4 = Very relevant
+5 = Perfectly answers the question
+
+Query: {query}
+Memory: {memory}
+Score:
+"""
+```
+
+#### Conversational Context
+
+```python
+conversation_prompt = """
+You are helping evaluate which memories are most useful for a conversational AI assistant.
+Rate how helpful this memory would be for generating a relevant response.
+
+Consider:
+- Direct relevance to user's intent
+- Emotional appropriateness
+- Factual accuracy
+- Conversation flow
+
+Rate 0-10:
+Query: {query}
+Memory: {memory}
+Score:
+"""
+```
+
+## Usage Examples
+
+### Basic Usage
+
+```python
+from mem0 import Memory
+
+m = Memory.from_config(config)
+
+# Add memories
+m.add("I'm allergic to peanuts", user_id="alice")
+m.add("I love Italian food", user_id="alice")
+m.add("I'm vegetarian", user_id="alice")
+
+# Search with LLM reranking
+results = m.search(
+    "What foods should I avoid?",
+    user_id="alice",
+    rerank=True
+)
+
+for result in results["results"]:
+    print(f"Memory: {result['memory']}")
+    print(f"LLM Score: {result['score']:.2f}")
+```
+
+### Batch Processing with Error Handling
+
+```python
+def safe_llm_rerank_search(query, user_id, max_retries=3):
+    for attempt in range(max_retries):
+        try:
+            return m.search(query, user_id=user_id, rerank=True)
+        except Exception as e:
+            print(f"Attempt {attempt + 1} failed: {e}")
+            if attempt == max_retries - 1:
+                # Fall back to vector search
+                return m.search(query, user_id=user_id, rerank=False)
+
+# Use the safe function
+results = safe_llm_rerank_search("What are my preferences?", "alice")
+```
+
+## Performance Considerations
+
+### Speed vs Quality Trade-offs
+
+| Model Type | Speed | Quality | Cost | Best For |
+|------------|-------|---------|------|----------|
+| GPT-3.5 Turbo | Fast | Good | Low | High-volume applications |
+| GPT-4 | Medium | Excellent | Medium | Quality-critical applications |
+| Claude 3 Sonnet | Medium | Excellent | Medium | Balanced performance |
+| Ollama Local | Variable | Good | Free | Privacy-sensitive applications |
+
+### Optimization Strategies
+
+```python
+# Fast configuration for high-volume use
+fast_config = {
+    "reranker": {
+        "provider": "llm_reranker",
+        "config": {
+            "llm": {
+                "provider": "openai",
+                "config": {
+                    "model": "gpt-3.5-turbo",
+                    "api_key": "your-api-key"
+                }
+            },
+            "top_k": 5,  # Limit candidates
+            "temperature": 0.0
+        }
+    }
+}
+
+# High-quality configuration
+quality_config = {
+    "reranker": {
+        "provider": "llm_reranker",
+        "config": {
+            "llm": {
+                "provider": "openai",
+                "config": {
+                    "model": "gpt-4",
+                    "api_key": "your-api-key"
+                }
+            },
+            "top_k": 15,
+            "temperature": 0.0
+        }
+    }
+}
+```
+
+## Advanced Use Cases
+
+### Multi-Step Reasoning
+
+```python
+reasoning_prompt = """
+Evaluate this memory's relevance using multi-step reasoning:
+
+1. What is the main intent of the query?
+2. What key information does the memory contain?
+3. How directly does the memory address the query?
+4. What additional context might be needed?
+
+Based on this analysis, rate relevance 1-10:
+
+Query: {query}
+Memory: {memory}
+
+Analysis:
+Step 1 (Intent):
+Step 2 (Information):
+Step 3 (Directness):
+Step 4 (Context):
+Final Score:
+"""
+```
+
+### Comparative Ranking
+
+```python
+comparative_prompt = """
+You will see a query and multiple memories. Rank them in order of relevance.
+Consider which memories best answer the question and would be most helpful.
+
+Query: {query}
+
+Memories to rank:
+{memories}
+
+Provide scores 1-10 for each memory, considering their relative usefulness.
+"""
+```
+
+### Emotional Intelligence
+
+```python
+emotional_prompt = """
+Consider both factual relevance and emotional appropriateness.
+Rate how suitable this memory is for responding to the user's query.
+
+Factors to consider:
+- Factual accuracy and relevance
+- Emotional tone and sensitivity
+- User's likely emotional state
+- Appropriateness of response
+
+Query: {query}
+Memory: {memory}
+Emotional Context: {context}
+Score (1-10):
+"""
+```
+
+## Error Handling and Fallbacks
+
+```python
+class RobustLLMReranker:
+    def __init__(self, primary_config, fallback_config=None):
+        self.primary = Memory.from_config(primary_config)
+        self.fallback = Memory.from_config(fallback_config) if fallback_config else None
+
+    def search(self, query, user_id, max_retries=2):
+        # Try primary LLM reranker
+        for attempt in range(max_retries):
+            try:
+                return self.primary.search(query, user_id=user_id, rerank=True)
+            except Exception as e:
+                print(f"Primary reranker attempt {attempt + 1} failed: {e}")
+
+        # Try fallback reranker
+        if self.fallback:
+            try:
+                return self.fallback.search(query, user_id=user_id, rerank=True)
+            except Exception as e:
+                print(f"Fallback reranker failed: {e}")
+
+        # Final fallback: vector search only
+        return self.primary.search(query, user_id=user_id, rerank=False)
+
+# Usage
+primary_config = {
+    "reranker": {
+        "provider": "llm_reranker",
+        "config": {"llm": {"provider": "openai", "config": {"model": "gpt-4"}}}
+    }
+}
+
+fallback_config = {
+    "reranker": {
+        "provider": "llm_reranker",
+        "config": {"llm": {"provider": "openai", "config": {"model": "gpt-3.5-turbo"}}}
+    }
+}
+
+reranker = RobustLLMReranker(primary_config, fallback_config)
+results = reranker.search("What are my preferences?", "alice")
+```
+
+## Best Practices
+
+1. **Use Specific Prompts**: Tailor prompts to your domain and use case
+2. **Set Temperature to 0**: Ensure consistent scoring across runs
+3. **Limit Top-K**: Don't rerank too many candidates to control costs
+4. **Implement Fallbacks**: Always have a backup plan for API failures
+5. **Monitor Costs**: Track API usage, especially with expensive models
+6. **Cache Results**: Consider caching reranking results for repeated queries
+7. **Test Prompts**: Experiment with different prompts to find what works best
+
+## Troubleshooting
+
+### Common Issues
+
+**Inconsistent Scores**
+- Set temperature to 0.0
+- Use more specific prompts
+- Consider using multiple calls and averaging
+
+**API Rate Limits**
+- Implement exponential backoff
+- Use cheaper models for high-volume scenarios
+- Add retry logic with delays
+
+**Poor Ranking Quality**
+- Refine your custom prompt
+- Try different LLM models
+- Add examples to your prompt
+
+## Next Steps
+
+<CardGroup cols={2}>
+  <Card title="Custom Prompts Guide" icon="pencil" href="/components/rerankers/custom-prompts">
+    Learn to craft effective reranking prompts
+  </Card>
+  <Card title="Performance Optimization" icon="bolt" href="/components/rerankers/optimization">
+    Optimize LLM reranker performance
+  </Card>
+</CardGroup>
@@ -0,0 +1,159 @@
+---
+title: Sentence Transformer
+description: 'Local reranking with HuggingFace cross-encoder models'
+---
+
+Sentence Transformer reranker provides local reranking using HuggingFace cross-encoder models, perfect for privacy-focused deployments where you want to keep data on-premises.
+
+## Models
+
+Any HuggingFace cross-encoder model can be used. Popular choices include:
+
+- **`cross-encoder/ms-marco-MiniLM-L-6-v2`**: Default, good balance of speed and accuracy
+- **`cross-encoder/ms-marco-TinyBERT-L-2-v2`**: Fastest, smaller model size
+- **`cross-encoder/ms-marco-electra-base`**: Higher accuracy, larger model
+- **`cross-encoder/stsb-distilroberta-base`**: Good for semantic similarity tasks
+
+## Installation
+
+```bash
+pip install sentence-transformers
+```
+
+## Configuration
+
+```python Python
+from mem0 import Memory
+
+config = {
+    "vector_store": {
+        "provider": "chroma",
+        "config": {
+            "collection_name": "my_memories",
+            "path": "./chroma_db"
+        }
+    },
+    "llm": {
+        "provider": "openai",
+        "config": {
+            "model": "gpt-4o-mini"
+        }
+    },
+    "rerank": {
+        "provider": "sentence_transformer",
+        "config": {
+            "model": "cross-encoder/ms-marco-MiniLM-L-6-v2",
+            "device": "cpu",  # or "cuda" for GPU
+            "batch_size": 32,
+            "show_progress_bar": False,
+            "top_k": 5
+        }
+    }
+}
+
+memory = Memory.from_config(config)
+```
+
+## GPU Acceleration
+
+For better performance, use GPU acceleration:
+
+```python Python
+config = {
+    "rerank": {
+        "provider": "sentence_transformer",
+        "config": {
+            "model": "cross-encoder/ms-marco-MiniLM-L-6-v2",
+            "device": "cuda",  # Use GPU
+            "batch_size": 64   # high batch size for high memory GPUs
+        }
+    }
+}
+```
+
+## Usage Example
+
+```python Python
+from mem0 import Memory
+
+# Initialize memory with local reranker
+config = {
+    "vector_store": {"provider": "chroma"},
+    "llm": {"provider": "openai", "config": {"model": "gpt-4o-mini"}},
+    "rerank": {
+        "provider": "sentence_transformer",
+        "config": {
+            "model": "cross-encoder/ms-marco-MiniLM-L-6-v2",
+            "device": "cpu"
+        }
+    }
+}
+
+memory = Memory.from_config(config)
+
+# Add memories
+messages = [
+    {"role": "user", "content": "I love reading science fiction novels"},
+    {"role": "user", "content": "My favorite author is Isaac Asimov"},
+    {"role": "user", "content": "I also enjoy watching sci-fi movies"}
+]
+
+memory.add(messages, user_id="charlie")
+
+# Search with local reranking
+results = memory.search("What books does the user like?", user_id="charlie")
+
+for result in results['results']:
+    print(f"Memory: {result['memory']}")
+    print(f"Vector Score: {result['score']:.3f}")
+    print(f"Rerank Score: {result['rerank_score']:.3f}")
+    print()
+```
+
+## Custom Models
+
+You can use any HuggingFace cross-encoder model:
+
+```python Python
+# Using a different model
+config = {
+    "rerank": {
+        "provider": "sentence_transformer", 
+        "config": {
+            "model": "cross-encoder/stsb-distilroberta-base",
+            "device": "cpu"
+        }
+    }
+}
+```
+
+## Configuration Parameters
+
+| Parameter | Description | Type | Default |
+|-----------|-------------|------|---------|
+| `model` | HuggingFace cross-encoder model name | `str` | `"cross-encoder/ms-marco-MiniLM-L-6-v2"` |
+| `device` | Device to run model on (`cpu`, `cuda`, etc.) | `str` | `None` |
+| `batch_size` | Batch size for processing documents | `int` | `32` |
+| `show_progress_bar` | Show progress bar during processing | `bool` | `False` |
+| `top_k` | Maximum documents to return | `int` | `None` |
+
+## Advantages
+
+- **Privacy**: Complete local processing, no external API calls
+- **Cost**: No per-token charges after initial model download
+- **Customization**: Use any HuggingFace cross-encoder model
+- **Offline**: Works without internet connection after model download
+
+## Performance Considerations
+
+- **First Run**: Model download may take time initially
+- **Memory Usage**: Models require GPU/CPU memory
+- **Batch Size**: Optimize batch size based on available memory
+- **Device**: GPU acceleration significantly improves speed
+
+## Best Practices
+
+1. **Model Selection**: Choose model based on accuracy vs speed requirements
+2. **Device Management**: Use GPU when available for better performance
+3. **Batch Processing**: Process multiple documents together for efficiency
+4. **Memory Monitoring**: Monitor system memory usage with larger models
@@ -0,0 +1,117 @@
+---
+title: Zero Entropy
+description: 'Neural reranking with Zero Entropy'
+---
+
+[Zero Entropy](https://www.zeroentropy.dev) provides neural reranking models that significantly improve search relevance with fast performance.
+
+## Models
+
+Zero Entropy offers two reranking models:
+
+- **`zerank-1`**: Flagship state-of-the-art reranker (non-commercial license)
+- **`zerank-1-small`**: Open-source model (Apache 2.0 license)
+
+## Installation
+
+```bash
+pip install zeroentropy
+```
+
+## Configuration
+
+```python Python
+from mem0 import Memory
+
+config = {
+    "vector_store": {
+        "provider": "chroma",
+        "config": {
+            "collection_name": "my_memories",
+            "path": "./chroma_db"
+        }
+    },
+    "llm": {
+        "provider": "openai",
+        "config": {
+            "model": "gpt-4o-mini"
+        }
+    },
+    "rerank": {
+        "provider": "zero_entropy",
+        "config": {
+            "model": "zerank-1",  # or "zerank-1-small"
+            "api_key": "your-zero-entropy-api-key",  # or set ZERO_ENTROPY_API_KEY
+            "top_k": 5
+        }
+    }
+}
+
+memory = Memory.from_config(config)
+```
+
+## Environment Variables
+
+Set your API key as an environment variable:
+
+```bash
+export ZERO_ENTROPY_API_KEY="your-api-key"
+```
+
+## Usage Example
+
+```python Python
+import os
+from mem0 import Memory
+
+# Set API key
+os.environ["ZERO_ENTROPY_API_KEY"] = "your-api-key"
+
+# Initialize memory with Zero Entropy reranker
+config = {
+    "vector_store": {"provider": "chroma"},
+    "llm": {"provider": "openai", "config": {"model": "gpt-4o-mini"}},
+    "rerank": {"provider": "zero_entropy", "config": {"model": "zerank-1"}}
+}
+
+memory = Memory.from_config(config)
+
+# Add memories
+messages = [
+    {"role": "user", "content": "I love Italian pasta, especially carbonara"},
+    {"role": "user", "content": "Japanese sushi is also amazing"},
+    {"role": "user", "content": "I enjoy cooking Mediterranean dishes"}
+]
+
+memory.add(messages, user_id="alice")
+
+# Search with reranking
+results = memory.search("What Italian food does the user like?", user_id="alice")
+
+for result in results['results']:
+    print(f"Memory: {result['memory']}")
+    print(f"Vector Score: {result['score']:.3f}")
+    print(f"Rerank Score: {result['rerank_score']:.3f}")
+    print()
+```
+
+## Configuration Parameters
+
+| Parameter | Description | Type | Default |
+|-----------|-------------|------|---------|
+| `model` | Model to use: `"zerank-1"` or `"zerank-1-small"` | `str` | `"zerank-1"` |
+| `api_key` | Zero Entropy API key | `str` | `None` |
+| `top_k` | Maximum documents to return after reranking | `int` | `None` |
+
+## Performance
+
+- **Fast**: Optimized neural architecture for low latency
+- **Accurate**: State-of-the-art relevance scoring
+- **Cost-effective**: ~$0.025/1M tokens processed
+
+## Best Practices
+
+1. **Model Selection**: Use `zerank-1` for best quality, `zerank-1-small` for faster processing
+2. **Batch Size**: Process multiple queries together when possible
+3. **Top-k Limiting**: Set reasonable `top_k` values (5-20) for best performance
+4. **API Key Management**: Use environment variables for secure key storage
@@ -0,0 +1,310 @@
+---
+title: Performance Optimization
+---
+
+Optimizing reranker performance is crucial for maintaining fast search response times while improving result quality. This guide covers best practices for different reranker types.
+
+## General Optimization Principles
+
+### Candidate Set Size
+The number of candidates sent to the reranker significantly impacts performance:
+
+```python
+# Optimal candidate sizes for different rerankers
+config_map = {
+    "cohere": {"initial_candidates": 100, "top_n": 10},
+    "sentence_transformer": {"initial_candidates": 50, "top_n": 10},
+    "huggingface": {"initial_candidates": 30, "top_n": 5},
+    "llm_reranker": {"initial_candidates": 20, "top_n": 5}
+}
+```
+
+### Batching Strategy
+Process multiple queries efficiently:
+
+```python
+# Configure for batch processing
+config = {
+    "reranker": {
+        "provider": "sentence_transformer",
+        "config": {
+            "model": "cross-encoder/ms-marco-MiniLM-L-6-v2",
+            "batch_size": 16,  # Process multiple candidates at once
+            "top_n": 10
+        }
+    }
+}
+```
+
+## Provider-Specific Optimizations
+
+### Cohere Optimization
+
+```python
+# Optimized Cohere configuration
+config = {
+    "reranker": {
+        "provider": "cohere",
+        "config": {
+            "model": "rerank-english-v3.0",
+            "top_n": 10,
+            "max_chunks_per_doc": 10,  # Limit chunk processing
+            "return_documents": False   # Reduce response size
+        }
+    }
+}
+```
+
+**Best Practices:**
+- Use v3.0 models for better speed/accuracy balance
+- Limit candidates to 100 or fewer
+- Cache API responses when possible
+- Monitor API rate limits
+
+### Sentence Transformer Optimization
+
+```python
+# Performance-optimized configuration
+config = {
+    "reranker": {
+        "provider": "sentence_transformer",
+        "config": {
+            "model": "cross-encoder/ms-marco-MiniLM-L-6-v2",
+            "device": "cuda",  # Use GPU when available
+            "batch_size": 32,
+            "top_n": 10,
+            "max_length": 512  # Limit input length
+        }
+    }
+}
+```
+
+**Device Optimization:**
+```python
+import torch
+
+# Auto-detect best device
+device = "cuda" if torch.cuda.is_available() else "mps" if torch.backends.mps.is_available() else "cpu"
+
+config = {
+    "reranker": {
+        "provider": "sentence_transformer",
+        "config": {
+            "device": device,
+            "model": "cross-encoder/ms-marco-MiniLM-L-6-v2"
+        }
+    }
+}
+```
+
+### Hugging Face Optimization
+
+```python
+# Optimized for Hugging Face models
+config = {
+    "reranker": {
+        "provider": "huggingface",
+        "config": {
+            "model": "BAAI/bge-reranker-base",
+            "use_fp16": True,  # Half precision for speed
+            "max_length": 512,
+            "batch_size": 8,
+            "top_n": 10
+        }
+    }
+}
+```
+
+### LLM Reranker Optimization
+
+```python
+# Optimized LLM reranker configuration
+config = {
+    "reranker": {
+        "provider": "llm_reranker",
+        "config": {
+            "llm": {
+                "provider": "openai",
+                "config": {
+                    "model": "gpt-3.5-turbo",  # Faster than gpt-4
+                    "temperature": 0,  # Deterministic results
+                    "max_tokens": 500  # Limit response length
+                }
+            },
+            "batch_ranking": True,  # Rank multiple at once
+            "top_n": 5,  # Fewer results for faster processing
+            "timeout": 10  # Request timeout
+        }
+    }
+}
+```
+
+## Performance Monitoring
+
+### Latency Tracking
+```python
+import time
+from mem0 import Memory
+
+def measure_reranker_performance(config, queries, user_id):
+    memory = Memory.from_config(config)
+
+    latencies = []
+    for query in queries:
+        start_time = time.time()
+        results = memory.search(query, user_id=user_id)
+        latency = time.time() - start_time
+        latencies.append(latency)
+
+    return {
+        "avg_latency": sum(latencies) / len(latencies),
+        "max_latency": max(latencies),
+        "min_latency": min(latencies)
+    }
+```
+
+### Memory Usage Monitoring
+```python
+import psutil
+import os
+
+def monitor_memory_usage():
+    process = psutil.Process(os.getpid())
+    return {
+        "memory_mb": process.memory_info().rss / 1024 / 1024,
+        "memory_percent": process.memory_percent()
+    }
+```
+
+## Caching Strategies
+
+### Result Caching
+```python
+from functools import lru_cache
+import hashlib
+
+class CachedReranker:
+    def __init__(self, config):
+        self.memory = Memory.from_config(config)
+        self.cache_size = 1000
+
+    @lru_cache(maxsize=1000)
+    def search_cached(self, query_hash, user_id):
+        return self.memory.search(query, user_id=user_id)
+
+    def search(self, query, user_id):
+        query_hash = hashlib.md5(f"{query}_{user_id}".encode()).hexdigest()
+        return self.search_cached(query_hash, user_id)
+```
+
+### Model Caching
+```python
+# Pre-load models to avoid initialization overhead
+config = {
+    "reranker": {
+        "provider": "sentence_transformer",
+        "config": {
+            "model": "cross-encoder/ms-marco-MiniLM-L-6-v2",
+            "cache_folder": "/path/to/model/cache",
+            "device": "cuda"
+        }
+    }
+}
+```
+
+## Parallel Processing
+
+### Async Configuration
+```python
+import asyncio
+from mem0 import Memory
+
+async def parallel_search(config, queries, user_id):
+    memory = Memory.from_config(config)
+
+    # Process multiple queries concurrently
+    tasks = [
+        memory.search_async(query, user_id=user_id)
+        for query in queries
+    ]
+
+    results = await asyncio.gather(*tasks)
+    return results
+```
+
+## Hardware Optimization
+
+### GPU Configuration
+```python
+# Optimize for GPU usage
+import torch
+
+if torch.cuda.is_available():
+    torch.cuda.set_per_process_memory_fraction(0.8)  # Reserve GPU memory
+
+config = {
+    "reranker": {
+        "provider": "sentence_transformer",
+        "config": {
+            "device": "cuda",
+            "model": "cross-encoder/ms-marco-electra-base",
+            "batch_size": 64,  # Larger batch for GPU
+            "fp16": True  # Half precision
+        }
+    }
+}
+```
+
+### CPU Optimization
+```python
+import torch
+
+# Optimize CPU threading
+torch.set_num_threads(4)  # Adjust based on your CPU
+
+config = {
+    "reranker": {
+        "provider": "sentence_transformer",
+        "config": {
+            "device": "cpu",
+            "model": "cross-encoder/ms-marco-MiniLM-L-6-v2",
+            "num_workers": 4  # Parallel processing
+        }
+    }
+}
+```
+
+## Benchmarking Different Configurations
+
+```python
+def benchmark_rerankers():
+    configs = [
+        {"provider": "cohere", "model": "rerank-english-v3.0"},
+        {"provider": "sentence_transformer", "model": "cross-encoder/ms-marco-MiniLM-L-6-v2"},
+        {"provider": "huggingface", "model": "BAAI/bge-reranker-base"}
+    ]
+
+    test_queries = ["sample query 1", "sample query 2", "sample query 3"]
+
+    results = {}
+    for config in configs:
+        provider = config["provider"]
+        performance = measure_reranker_performance(
+            {"reranker": {"provider": provider, "config": config}},
+            test_queries,
+            "test_user"
+        )
+        results[provider] = performance
+
+    return results
+```
+
+## Production Best Practices
+
+1. **Model Selection**: Choose the right balance of speed vs. accuracy
+2. **Resource Allocation**: Monitor CPU/GPU usage and memory consumption
+3. **Error Handling**: Implement fallbacks for reranker failures
+4. **Load Balancing**: Distribute reranking load across multiple instances
+5. **Monitoring**: Track latency, throughput, and error rates
+6. **Caching**: Cache frequent queries and model predictions
+7. **Batch Processing**: Group similar queries for efficient processing
@@ -0,0 +1,78 @@
+---
+title: Overview
+description: 'Pick the right reranker path to boost Mem0 search relevance.'
+---
+
+Mem0 rerankers rescore vector search hits so your agents surface the most relevant memories. Use this hub to decide when reranking helps, configure a provider, and fine-tune performance.
+
+<Info>
+Reranking trades extra latency for better precision. Start once you have baseline search working and measure before/after relevance.
+</Info>
+
+<CardGroup cols={3}>
+  <Card
+    title="Understand Reranking"
+    description="See how reranker-enhanced search changes your retrieval flow."
+    icon="search"
+    href="/open-source/features/reranker-search"
+  />
+  <Card
+    title="Configure Providers"
+    description="Add reranker blocks to your memory configuration."
+    icon="settings"
+    href="/components/rerankers/config"
+  />
+  <Card
+    title="Optimize Performance"
+    description="Balance relevance, latency, and cost with tuning tactics."
+    icon="speedometer"
+    href="/components/rerankers/optimization"
+  />
+  <Card
+    title="Custom Prompts"
+    description="Shape LLM-based reranking with tailored instructions."
+    icon="code"
+    href="/components/rerankers/custom-prompts"
+  />
+  <Card
+    title="Zero Entropy Guide"
+    description="Adopt the managed neural reranker for production workloads."
+    icon="sparkles"
+    href="/components/rerankers/models/zero_entropy"
+  />
+  <Card
+    title="Sentence Transformers"
+    description="Keep reranking on-device with cross-encoder models."
+    icon="cpu"
+    href="/components/rerankers/models/sentence_transformer"
+  />
+</CardGroup>
+
+## Picking the Right Reranker
+
+- **API-first** when you need top quality and can absorb request costs (Cohere, Zero Entropy).  
+- **Self-hosted** for privacy-sensitive deployments that must stay on your hardware (Sentence Transformer, Hugging Face).  
+- **LLM-driven** when you need bespoke scoring logic or complex prompts.  
+- **Hybrid** by enabling reranking only on premium journeys to control spend.
+
+## Implementation Checklist
+
+1. Confirm baseline search KPIs so you can measure uplift.  
+2. Select a provider and add the `reranker` block to your config.  
+3. Test latency impact with production-like query batches.  
+4. Decide whether to enable reranking globally or per-search via the `rerank` flag.
+
+<CardGroup cols={2}>
+  <Card
+    title="Set Up Reranking"
+    description="Walk through the configuration fields and defaults."
+    icon="settings"
+    href="/components/rerankers/config"
+  />
+  <Card
+    title="Example: Reranker Search"
+    description="Follow the feature guide to see reranking in action."
+    icon="rocket"
+    href="/open-source/features/reranker-search"
+  />
+</CardGroup>
@@ -1,16 +1,12 @@
 ---
 title: Configurations
-icon: "gear"
-iconType: "solid"
 ---

-<Snippet file="blank-notif.mdx" />
-
 ## How to define configurations?

 The `config` is defined as an object with two main keys:
 - `vector_store`: Specifies the vector database provider and its configuration
-  - `provider`: The name of the vector database (e.g., "chroma", "pgvector", "qdrant", "milvus", "upstash_vector", "azure_ai_search", "vertex_ai_vector_search")
+  - `provider`: The name of the vector database (e.g., "chroma", "pgvector", "qdrant", "milvus", "upstash_vector", "azure_ai_search", "vertex_ai_vector_search", "valkey")
  - `config`: A nested dictionary containing provider-specific settings


@@ -16,8 +16,8 @@ config = {
    "vector_store": {
        "provider": "azure_ai_search",
        "config": {
-            "service_name": "ai-search-test",
-            "api_key": "*****",
+            "service_name": "<your-azure-ai-search-service-name>",
+            "api_key": "<your-api-key>",
            "collection_name": "mem0", 
            "embedding_model_dims": 1536
        }
@@ -27,7 +27,7 @@ config = {
 m = Memory.from_config(config)
 messages = [
    {"role": "user", "content": "I'm planning to watch a movie tonight. Any recommendations?"},
-    {"role": "assistant", "content": "How about a thriller movies? They can be quite engaging."},
+    {"role": "assistant", "content": "How about thriller movies? They can be quite engaging."},
    {"role": "user", "content": "I'm not a big fan of thriller movies but I love sci-fi movies."},
    {"role": "assistant", "content": "Got it! I'll avoid thriller recommendations and suggest sci-fi movies in the future."}
 ]
@@ -41,8 +41,8 @@ config = {
    "vector_store": {
        "provider": "azure_ai_search",
        "config": {
-            "service_name": "ai-search-test",
-            "api_key": "*****",
+            "service_name": "<your-azure-ai-search-service-name>",
+            "api_key": "<your-api-key>",
            "collection_name": "mem0", 
            "embedding_model_dims": 1536,
            "compression_type": "binary",
@@ -59,8 +59,8 @@ config = {
    "vector_store": {
        "provider": "azure_ai_search",
        "config": {
-            "service_name": "ai-search-test",
-            "api_key": "*****",
+            "service_name": "<your-azure-ai-search-service-name>",
+            "api_key": "<your-api-key>",
            "collection_name": "mem0", 
            "embedding_model_dims": 1536,
            "hybrid_search": True,
@@ -70,12 +70,92 @@ config = {
 }
 ```

+## Using Azure Identity for Authentication
+As an alternative to using an API key, the Azure Identity credential chain can be used to authenticate with Azure OpenAI. The list below shows the order of precedence for credential application:
+
+1. **Environment Credential:**
+Azure client ID, secret, tenant ID, or certificate in environment variables for service principal authentication.
+
+2. **Workload Identity Credential:**
+Utilizes Azure Workload Identity (relevant for Kubernetes and Azure workloads).
+
+3. **Managed Identity Credential:**
+Authenticates as a Managed Identity (for apps/services hosted in Azure with Managed Identity enabled), this is the most secure production credential.
+
+4. **Shared Token Cache Credential / Visual Studio Credential (Windows only):**
+Uses cached credentials from Visual Studio sign-ins (and sometimes VS Code if SSO is enabled).
+
+5. **Azure CLI Credential:**
+Uses the currently logged-in user from the Azure CLI (`az login`), this is the most common development credential.
+
+6. **Azure PowerShell Credential:**
+Uses the identity from Azure PowerShell (`Connect-AzAccount`).
+
+7. **Azure Developer CLI Credential:**
+Uses the session from Azure Developer CLI (`azd auth login`).
+
+<Note> If an API is provided, it will be used for authentication over an Azure Identity </Note>
+To enable Role-Based Access Control (RBAC) for Azure AI Search, follow these steps:
+
+1. In the Azure Portal, navigate to your **Azure AI Search** service.
+2. In the left menu, select **Settings** > **Keys**.
+3. Change the authentication setting to **Role-based access control**, or **Both** if you need API key compatibility. The default is “Key-based authentication”—you must switch it to use Azure roles.
+4. **Go to Access Control (IAM):**
+    - In the Azure Portal, select your Search service.
+    - Click **Access Control (IAM)** on the left.
+5. **Add a Role Assignment:**
+    - Click **Add** > **Add role assignment**.
+6. **Choose Role:**
+    - Mem0 requires the **Search Index Data Contributor** and **Search Service Contributor** role.
+7. **Choose Member**
+    - To assign to a User, Group, Service Principal or Managed Identity:
+        - For production it is recommended to use a service principal or managed identity.
+            - For a service principal: select **User, group, or service principal** and search for the service principal.
+            - For a managed identity: select **Managed identity** and choose the managed identity.
+        - For development, you can assign the role to a user account.
+            - For development: select **User, group, or service principal** and pick an Azure Entra ID account (the same used with `az login`).
+8. **Complete the Assignment:**
+    - Click **Review + Assign**.
+
+If you are using Azure Identity, do not set the `api_key` in the configuration.
+```python
+config = {
+    "vector_store": {
+        "provider": "azure_ai_search",
+        "config": {
+            "service_name": "<your-azure-ai-search-service-name>",
+            "collection_name": "mem0", 
+            "embedding_model_dims": 1536,
+            "compression_type": "binary",
+            "use_float16": True  # Use half precision for storage efficiency
+        }
+    }
+}
+```
+
+### Environment Variables to Use Azure Identity Credential
+* For an Environment Credential, you will need to setup a Service Principal and set the following environment variables:
+  - `AZURE_TENANT_ID`: Your Azure Active Directory tenant ID.
+  - `AZURE_CLIENT_ID`: The client ID of your service principal or managed identity.
+  - `AZURE_CLIENT_SECRET`: The client secret of your service principal.
+* For a User-Assigned Managed Identity, you will need to set the following environment variable:
+  - `AZURE_CLIENT_ID`: The client ID of the user-assigned managed identity.
+* For a System-Assigned Managed Identity, no additional environment variables are needed.
+
+### Developer Logins for Azure Identity Credential
+* For an Azure CLI Credential, you need to have the Azure CLI installed and logged in with `az login`.
+* For an Azure PowerShell Credential, you need to have the Azure PowerShell module installed and logged in with `Connect-AzAccount`.
+* For an Azure Developer CLI Credential, you need to have the Azure Developer CLI installed and logged in with `azd auth login`.
+
+Troubleshooting tips for [Azure Identity](https://github.com/Azure/azure-sdk-for-python/blob/main/sdk/identity/azure-identity/TROUBLESHOOTING.md#troubleshoot-environmentcredential-authentication-issues).
+
+
 ## Configuration Parameters

 | Parameter | Description | Default Value | Options |
 | --- | --- | --- | --- |
 | `service_name` | Azure AI Search service name | Required | - |
-| `api_key` | API key of the Azure AI Search service | Required | - |
+| `api_key` | API key of the Azure AI Search service | Optional | If not present, the [Azure Identity](#using-azure-identity-for-authentication) credential chain will be used |
 | `collection_name` | The name of the collection/index to store vectors | `mem0` | Any valid index name |
 | `embedding_model_dims` | Dimensions of the embedding model | `1536` | Any integer value |
 | `compression_type` | Type of vector compression to use | `none` | `none`, `scalar`, `binary` |
@@ -0,0 +1,128 @@
+---
+title: Azure MySQL
+---
+
+[Azure Database for MySQL](https://azure.microsoft.com/products/mysql) is a fully managed relational database service that provides enterprise-grade reliability and security. It supports JSON-based vector storage for semantic search capabilities in AI applications.
+
+### Usage
+
+```python
+import os
+from mem0 import Memory
+
+os.environ["OPENAI_API_KEY"] = "sk-xx"
+
+config = {
+    "vector_store": {
+        "provider": "azure_mysql",
+        "config": {
+            "host": "your-server.mysql.database.azure.com",
+            "port": 3306,
+            "user": "your_username",
+            "password": "your_password",
+            "database": "mem0_db",
+            "collection_name": "memories",
+        }
+    }
+}
+
+m = Memory.from_config(config)
+messages = [
+    {"role": "user", "content": "I'm planning to watch a movie tonight. Any recommendations?"},
+    {"role": "assistant", "content": "How about thriller movies? They can be quite engaging."},
+    {"role": "user", "content": "I'm not a big fan of thriller movies but I love sci-fi movies."},
+    {"role": "assistant", "content": "Got it! I'll avoid thriller recommendations and suggest sci-fi movies in the future."}
+]
+m.add(messages, user_id="alice", metadata={"category": "movies"})
+```
+
+#### Using Azure Managed Identity
+
+For production deployments, use Azure Managed Identity instead of passwords:
+
+```python
+config = {
+    "vector_store": {
+        "provider": "azure_mysql",
+        "config": {
+            "host": "your-server.mysql.database.azure.com",
+            "user": "your_username",
+            "database": "mem0_db",
+            "collection_name": "memories",
+            "use_azure_credential": True,  # Uses DefaultAzureCredential
+            "ssl_disabled": False
+        }
+    }
+}
+```
+
+<Note>
+When `use_azure_credential` is enabled, the password is obtained via Azure DefaultAzureCredential (supports Managed Identity, Azure CLI, etc.)
+</Note>
+
+### Config
+
+Here are the parameters available for configuring Azure MySQL:
+
+| Parameter | Description | Default Value |
+| --- | --- | --- |
+| `host` | MySQL server hostname | Required |
+| `port` | MySQL server port | `3306` |
+| `user` | Database user | Required |
+| `password` | Database password (optional with Azure credential) | `None` |
+| `database` | Database name | Required |
+| `collection_name` | Table name for storing vectors | `"mem0"` |
+| `embedding_model_dims` | Dimensions of embedding vectors | `1536` |
+| `use_azure_credential` | Use Azure DefaultAzureCredential | `False` |
+| `ssl_ca` | Path to SSL CA certificate | `None` |
+| `ssl_disabled` | Disable SSL (not recommended) | `False` |
+| `minconn` | Minimum connections in pool | `1` |
+| `maxconn` | Maximum connections in pool | `5` |
+
+### Setup
+
+#### Create MySQL Flexible Server using Azure CLI:
+
+```bash
+# Create resource group
+az group create --name mem0-rg --location eastus
+
+# Create MySQL Flexible Server
+az mysql flexible-server create \
+    --resource-group mem0-rg \
+    --name mem0-mysql-server \
+    --location eastus \
+    --admin-user myadmin \
+    --admin-password <YourPassword> \
+    --version 8.0.21
+
+# Create database
+az mysql flexible-server db create \
+    --resource-group mem0-rg \
+    --server-name mem0-mysql-server \
+    --database-name mem0_db
+
+# Configure firewall
+az mysql flexible-server firewall-rule create \
+    --resource-group mem0-rg \
+    --name mem0-mysql-server \
+    --rule-name AllowMyIP \
+    --start-ip-address <YourIP> \
+    --end-ip-address <YourIP>
+```
+
+#### Enable Azure AD Authentication:
+
+1. In Azure Portal, navigate to your MySQL Flexible Server
+2. Go to **Security** > **Authentication** and enable Azure AD
+3. Add your application's managed identity as a MySQL user:
+
+```sql
+CREATE AADUSER 'your-app-identity' IDENTIFIED BY 'your-client-id';
+GRANT ALL PRIVILEGES ON mem0_db.* TO 'your-app-identity'@'%';
+FLUSH PRIVILEGES;
+```
+
+<Tip>
+For production, use [Managed Identity](https://learn.microsoft.com/azure/active-directory/managed-identities-azure-resources/) to eliminate password management.
+</Tip>
@@ -37,7 +37,7 @@ m.add(messages, user_id="alice", metadata={"category": "movies"})

 ### Config

-Here are the available parameters for the `mochow` config:
+Here are the parameters available for configuring Baidu VectorDB:

 | Parameter | Description | Default Value |
 | --- | --- | --- |
@@ -0,0 +1,181 @@
+---
+title: Apache Cassandra
+---
+
+[Apache Cassandra](https://cassandra.apache.org/) is a highly scalable, distributed NoSQL database designed for handling large amounts of data across many commodity servers with no single point of failure. It supports vector storage for semantic search capabilities in AI applications and can scale to massive datasets with linear performance improvements.
+
+### Usage
+
+```python
+import os
+from mem0 import Memory
+
+os.environ["OPENAI_API_KEY"] = "sk-xx"
+
+config = {
+    "vector_store": {
+        "provider": "cassandra",
+        "config": {
+            "contact_points": ["127.0.0.1"],
+            "port": 9042,
+            "username": "cassandra",
+            "password": "cassandra",
+            "keyspace": "mem0",
+            "collection_name": "memories",
+        }
+    }
+}
+
+m = Memory.from_config(config)
+messages = [
+    {"role": "user", "content": "I'm planning to watch a movie tonight. Any recommendations?"},
+    {"role": "assistant", "content": "How about thriller movies? They can be quite engaging."},
+    {"role": "user", "content": "I'm not a big fan of thriller movies but I love sci-fi movies."},
+    {"role": "assistant", "content": "Got it! I'll avoid thriller recommendations and suggest sci-fi movies in the future."}
+]
+m.add(messages, user_id="alice", metadata={"category": "movies"})
+```
+
+#### Using DataStax Astra DB
+
+For managed Cassandra with DataStax Astra DB:
+
+```python
+config = {
+    "vector_store": {
+        "provider": "cassandra",
+        "config": {
+            "contact_points": ["dummy"],  # Not used with secure connect bundle
+            "username": "token",
+            "password": "AstraCS:...",  # Your Astra DB application token
+            "keyspace": "mem0",
+            "collection_name": "memories",
+            "secure_connect_bundle": "/path/to/secure-connect-bundle.zip"
+        }
+    }
+}
+```
+
+<Note>
+When using DataStax Astra DB, provide the secure connect bundle path. The contact_points parameter is ignored when a secure connect bundle is provided.
+</Note>
+
+### Config
+
+Here are the parameters available for configuring Apache Cassandra:
+
+| Parameter | Description | Default Value |
+| --- | --- | --- |
+| `contact_points` | List of contact point IP addresses | Required |
+| `port` | Cassandra port | `9042` |
+| `username` | Database username | `None` |
+| `password` | Database password | `None` |
+| `keyspace` | Keyspace name | `"mem0"` |
+| `collection_name` | Table name for storing vectors | `"memories"` |
+| `embedding_model_dims` | Dimensions of embedding vectors | `1536` |
+| `secure_connect_bundle` | Path to Astra DB secure connect bundle | `None` |
+| `protocol_version` | CQL protocol version | `4` |
+| `load_balancing_policy` | Custom load balancing policy | `None` |
+
+### Setup
+
+#### Option 1: Local Cassandra Setup using Docker:
+
+```bash
+# Pull and run Cassandra container
+docker run --name mem0-cassandra \
+    -p 9042:9042 \
+    -e CASSANDRA_CLUSTER_NAME="Mem0Cluster" \
+    -d cassandra:latest
+
+# Wait for Cassandra to start (may take 1-2 minutes)
+docker exec -it mem0-cassandra cqlsh
+
+# Create keyspace
+CREATE KEYSPACE IF NOT EXISTS mem0
+WITH replication = {'class': 'SimpleStrategy', 'replication_factor': 1};
+```
+
+#### Option 2: DataStax Astra DB (Managed Cloud):
+
+1. Sign up at [DataStax Astra](https://astra.datastax.com/)
+2. Create a new database
+3. Download the secure connect bundle
+4. Generate an application token
+
+<Tip>
+For production deployments, use DataStax Astra DB for fully managed Cassandra with automatic scaling, backups, and security.
+</Tip>
+
+#### Option 3: Install Cassandra Locally:
+
+**Ubuntu/Debian:**
+```bash
+# Add Apache Cassandra repository
+echo "deb https://downloads.apache.org/cassandra/debian 40x main" | sudo tee -a /etc/apt/sources.list.d/cassandra.sources.list
+curl https://downloads.apache.org/cassandra/KEYS | sudo apt-key add -
+
+# Install Cassandra
+sudo apt-get update
+sudo apt-get install cassandra
+
+# Start Cassandra
+sudo systemctl start cassandra
+
+# Verify installation
+nodetool status
+```
+
+**macOS:**
+```bash
+# Using Homebrew
+brew install cassandra
+
+# Start Cassandra
+brew services start cassandra
+
+# Connect to CQL shell
+cqlsh
+```
+
+### Python Client Installation
+
+Install the required Python package:
+
+```bash
+pip install cassandra-driver
+```
+
+### Performance Considerations
+
+- **Replication Factor**: For production, use replication factor of at least 3
+- **Consistency Level**: Balance between consistency and performance (QUORUM recommended)
+- **Partitioning**: Cassandra automatically distributes data across nodes
+- **Scaling**: Add nodes to linearly increase capacity and performance
+
+### Advanced Configuration
+
+```python
+from cassandra.policies import DCAwareRoundRobinPolicy
+
+config = {
+    "vector_store": {
+        "provider": "cassandra",
+        "config": {
+            "contact_points": ["node1.example.com", "node2.example.com", "node3.example.com"],
+            "port": 9042,
+            "username": "mem0_user",
+            "password": "secure_password",
+            "keyspace": "mem0_prod",
+            "collection_name": "memories",
+            "protocol_version": 4,
+            "load_balancing_policy": DCAwareRoundRobinPolicy(local_dc='DC1')
+        }
+    }
+}
+```
+
+<Warning>
+For production use, configure appropriate replication strategies and consistency levels based on your availability and consistency requirements.
+</Warning>
+
@@ -1,7 +1,9 @@
-[Chroma](https://www.trychroma.com/) is an AI-native open-source vector database that simplifies building LLM apps by providing tools for storing, embedding, and searching embeddings with a focus on simplicity and speed.
+[Chroma](https://www.trychroma.com/) is an AI-native open-source vector database that simplifies building LLM apps by providing tools for storing, embedding, and searching embeddings with a focus on simplicity and speed. It supports both local deployment and cloud hosting through ChromaDB Cloud.

 ### Usage

+#### Local Installation
+
 ```python
 import os
 from mem0 import Memory
@@ -14,6 +16,9 @@ config = {
        "config": {
            "collection_name": "test",
            "path": "db",
+            # Optional: ChromaDB Cloud configuration
+            # "api_key": "your-chroma-cloud-api-key",
+            # "tenant": "your-chroma-cloud-tenant-id",
        }
    }
 }
@@ -21,7 +26,7 @@ config = {
 m = Memory.from_config(config)
 messages = [
    {"role": "user", "content": "I'm planning to watch a movie tonight. Any recommendations?"},
-    {"role": "assistant", "content": "How about a thriller movies? They can be quite engaging."},
+    {"role": "assistant", "content": "How about thriller movies? They can be quite engaging."},
    {"role": "user", "content": "I’m not a big fan of thriller movies but I love sci-fi movies."},
    {"role": "assistant", "content": "Got it! I'll avoid thriller recommendations and suggest sci-fi movies in the future."}
 ]
@@ -38,4 +43,6 @@ Here are the parameters available for configuring Chroma:
 | `client` | Custom client for Chroma | `None` |
 | `path` | Path for the Chroma database | `db` |
 | `host` | The host where the Chroma server is running | `None` |
-| `port` | The port where the Chroma server is running | `None` |
+| `port` | The port where the Chroma server is running | `None` |
+| `api_key` | ChromaDB Cloud API key (for cloud usage) | `None` |
+| `tenant` | ChromaDB Cloud tenant ID (for cloud usage) | `None` |
@@ -0,0 +1,130 @@
+[Databricks Vector Search](https://docs.databricks.com/en/generative-ai/vector-search.html) is a serverless similarity search engine that allows you to store a vector representation of your data, including metadata, in a vector database. With Vector Search, you can create auto-updating vector search indexes from Delta tables managed by Unity Catalog and query them with a simple API to return the most similar vectors.
+
+### Usage
+
+```python
+import os
+from mem0 import Memory
+
+config = {
+    "vector_store": {
+        "provider": "databricks",
+        "config": {
+            "workspace_url": "https://your-workspace.databricks.com",
+            "access_token": "your-access-token",
+            "endpoint_name": "your-vector-search-endpoint",
+            "index_name": "catalog.schema.index_name",
+            "source_table_name": "catalog.schema.source_table",
+            "embedding_dimension": 1536
+        }
+    }
+}
+
+m = Memory.from_config(config)
+messages = [
+    {"role": "user", "content": "I'm planning to watch a movie tonight. Any recommendations?"},
+    {"role": "assistant", "content": "How about thriller movies? They can be quite engaging."},
+    {"role": "user", "content": "I'm not a big fan of thriller movies but I love sci-fi movies."},
+    {"role": "assistant", "content": "Got it! I'll avoid thriller recommendations and suggest sci-fi movies in the future."}
+]
+m.add(messages, user_id="alice", metadata={"category": "movies"})
+```
+
+### Config
+
+Here are the parameters available for configuring Databricks Vector Search:
+
+| Parameter | Description | Default Value |
+| --- | --- | --- |
+| `workspace_url` | The URL of your Databricks workspace | **Required** |
+| `access_token` | Personal Access Token for authentication | `None` |
+| `service_principal_client_id` | Service principal client ID (alternative to access_token) | `None` |
+| `service_principal_client_secret` | Service principal client secret (required with client_id) | `None` |
+| `endpoint_name` | Name of the Vector Search endpoint | **Required** |
+| `index_name` | Name of the vector index (Unity Catalog format: catalog.schema.index) | **Required** |
+| `source_table_name` | Name of the source Delta table (Unity Catalog format: catalog.schema.table) | **Required** |
+| `embedding_dimension` | Dimension of self-managed embeddings | `1536` |
+| `embedding_source_column` | Column name for text when using Databricks-computed embeddings | `None` |
+| `embedding_model_endpoint_name` | Databricks serving endpoint for embeddings | `None` |
+| `embedding_vector_column` | Column name for self-managed embedding vectors | `embedding` |
+| `endpoint_type` | Type of endpoint (`STANDARD` or `STORAGE_OPTIMIZED`) | `STANDARD` |
+| `sync_computed_embeddings` | Whether to sync computed embeddings automatically | `True` |
+
+### Authentication
+
+Databricks Vector Search supports two authentication methods:
+
+#### Service Principal (Recommended for Production)
+```python
+config = {
+    "vector_store": {
+        "provider": "databricks",
+        "config": {
+            "workspace_url": "https://your-workspace.databricks.com",
+            "service_principal_client_id": "your-service-principal-id",
+            "service_principal_client_secret": "your-service-principal-secret",
+            "endpoint_name": "your-endpoint",
+            "index_name": "catalog.schema.index_name",
+            "source_table_name": "catalog.schema.source_table"
+        }
+    }
+}
+```
+
+#### Personal Access Token (for Development)
+```python
+config = {
+    "vector_store": {
+        "provider": "databricks",
+        "config": {
+            "workspace_url": "https://your-workspace.databricks.com",
+            "access_token": "your-personal-access-token",
+            "endpoint_name": "your-endpoint",
+            "index_name": "catalog.schema.index_name",
+            "source_table_name": "catalog.schema.source_table"
+        }
+    }
+}
+```
+
+### Embedding Options
+
+#### Self-Managed Embeddings (Default)
+Use your own embedding model and provide vectors directly:
+
+```python
+config = {
+    "vector_store": {
+        "provider": "databricks",
+        "config": {
+            # ... authentication config ...
+            "embedding_dimension": 768,  # Match your embedding model
+            "embedding_vector_column": "embedding"
+        }
+    }
+}
+```
+
+#### Databricks-Computed Embeddings
+Let Databricks compute embeddings from text using a serving endpoint:
+
+```python
+config = {
+    "vector_store": {
+        "provider": "databricks",
+        "config": {
+            # ... authentication config ...
+            "embedding_source_column": "text",
+            "embedding_model_endpoint_name": "e5-small-v2"
+        }
+    }
+}
+```
+
+### Important Notes
+
+- **Delta Sync Index**: This implementation uses Delta Sync Index, which automatically syncs with your source Delta table. Direct vector insertion/deletion/update operations will log warnings as they're not supported with Delta Sync.
+- **Unity Catalog**: Both the source table and index must be in Unity Catalog format (`catalog.schema.table_name`).
+- **Endpoint Auto-Creation**: If the specified endpoint doesn't exist, it will be created automatically.
+- **Index Auto-Creation**: If the specified index doesn't exist, it will be created automatically with the provided configuration.
+- **Filter Support**: Supports filtering by metadata fields, with different syntax for STANDARD vs STORAGE_OPTIMIZED endpoints.
@@ -31,7 +31,7 @@ config = {
 m = Memory.from_config(config)
 messages = [
    {"role": "user", "content": "I'm planning to watch a movie tonight. Any recommendations?"},
-    {"role": "assistant", "content": "How about a thriller movies? They can be quite engaging."},
+    {"role": "assistant", "content": "How about thriller movies? They can be quite engaging."},
    {"role": "user", "content": "I’m not a big fan of thriller movies but I love sci-fi movies."},
    {"role": "assistant", "content": "Got it! I'll avoid thriller recommendations and suggest sci-fi movies in the future."}
 ]
@@ -40,7 +40,7 @@ m.add(messages, user_id="alice", metadata={"category": "movies"})

 ### Config

-Let's see the available parameters for the `elasticsearch` config:
+Here are the parameters available for configuring Elasticsearch:

 | Parameter              | Description                                        | Default Value |
 | ---------------------- | -------------------------------------------------- | ------------- |
@@ -54,7 +54,8 @@ Let's see the available parameters for the `elasticsearch` config:
 | `password`             | Password for basic authentication                  | `None`        |
 | `verify_certs`         | Whether to verify SSL certificates                 | `True`        |
 | `auto_create_index`    | Whether to automatically create the index          | `True`        |
-| `custom_search_query`  | Function returning a custom search query            | `None`        |
+| `custom_search_query`  | Function returning a custom search query           | `None`        |
+| `headers`              | Custom headers to include in requests              | `None`        |

 ### Features

@@ -22,7 +22,7 @@ config = {
 m = Memory.from_config(config)
 messages = [
    {"role": "user", "content": "I'm planning to watch a movie tonight. Any recommendations?"},
-    {"role": "assistant", "content": "How about a thriller movies? They can be quite engaging."},
+    {"role": "assistant", "content": "How about thriller movies? They can be quite engaging."},
    {"role": "user", "content": "I'm not a big fan of thriller movies but I love sci-fi movies."},
    {"role": "assistant", "content": "Got it! I'll avoid thriller recommendations and suggest sci-fi movies in the future."}
 ]
@@ -38,7 +38,7 @@ config = {
 m = Memory.from_config(config)
 messages = [
    {"role": "user", "content": "I'm planning to watch a movie tonight. Any recommendations?"},
-    {"role": "assistant", "content": "How about a thriller movies? They can be quite engaging."},
+    {"role": "assistant", "content": "How about thriller movies? They can be quite engaging."},
    {"role": "user", "content": "I'm not a big fan of thriller movies but I love sci-fi movies."},
    {"role": "assistant", "content": "Got it! I'll avoid thriller recommendations and suggest sci-fi movies in the future."}
 ]
@@ -64,12 +64,12 @@ const memory = new Memory(config);

 const messages = [
    { role: "user", content: "I'm planning to watch a movie tonight. Any recommendations?" },
-    { role: "assistant", content: "How about a thriller movies? They can be quite engaging." },
+    { role: "assistant", content: "How about thriller movies? They can be quite engaging." },
    { role: "user", content: "I'm not a big fan of thriller movies but I love sci-fi movies." },
    { role: "assistant", content: "Got it! I'll avoid thriller recommendations and suggest sci-fi movies in the future." }
 ]

-memory.add(messages, user_id="alice", metadata={"category": "movies"})
+await memory.add(messages, { userId: "alice", metadata: { category: "movies" } });
 ```
 </CodeGroup>

@@ -1,4 +1,4 @@
-[Milvus](https://milvus.io/) Milvus is an open-source vector database that suits AI applications of every size from running a demo chatbot in Jupyter notebook to building web-scale search that serves billions of users.
+[Milvus](https://milvus.io/) is an open-source vector database that suits AI applications of every size, from running a demo chatbot in a Jupyter notebook to building web-scale search that serves billions of users.

 ### Usage

@@ -11,7 +11,7 @@ config = {
        "provider": "milvus",
        "config": {
            "collection_name": "test",
-            "embedding_model_dims": "123",
+            "embedding_model_dims": 1536,
            "url": "127.0.0.1",
            "token": "8e4b8ca8cf2c67",
            "db_name": "my_database",
@@ -22,7 +22,7 @@ config = {
 m = Memory.from_config(config)
 messages = [
    {"role": "user", "content": "I'm planning to watch a movie tonight. Any recommendations?"},
-    {"role": "assistant", "content": "How about a thriller movies? They can be quite engaging."},
+    {"role": "assistant", "content": "How about thriller movies? They can be quite engaging."},
    {"role": "user", "content": "I’m not a big fan of thriller movies but I love sci-fi movies."},
    {"role": "assistant", "content": "Got it! I'll avoid thriller recommendations and suggest sci-fi movies in the future."}
 ]
@@ -31,7 +31,7 @@ m.add(messages, user_id="alice", metadata={"category": "movies"})

 ### Config

-Here's the parameters available for configuring Milvus Database:
+Here are the parameters available for configuring Milvus:

 | Parameter | Description | Default Value |
 | --- | --- | --- |
@@ -24,7 +24,7 @@ config = {
 m = Memory.from_config(config)
 messages = [
    {"role": "user", "content": "I'm planning to watch a movie tonight. Any recommendations?"},
-    {"role": "assistant", "content": "How about a thriller movies? They can be quite engaging."},
+    {"role": "assistant", "content": "How about thriller movies? They can be quite engaging."},
    {"role": "user", "content": "I’m not a big fan of thriller movies but I love sci-fi movies."},
    {"role": "assistant", "content": "Got it! I'll avoid thriller recommendations and suggest sci-fi movies in the future."}
 ]
@@ -40,6 +40,6 @@ Here are the parameters available for configuring MongoDB:
 | db_name | Name of the MongoDB database | `"mem0_db"` |
 | collection_name | Name of the MongoDB collection | `"mem0_collection"` |
 | embedding_model_dims | Dimensions of the embedding vectors | `1536` |
-| mongo_uri | The mongo URI connection string | mongodb://username:password@localhost:27017 |
+| mongo_uri | The MongoDB URI connection string | `mongodb://username:password@localhost:27017` |

-> **Note**: If Mongo_uri is not provided it will default to mongodb://username:password@localhost:27017.
+> **Note**: If `mongo_uri` is not provided, it will default to `mongodb://username:password@localhost:27017`.
@@ -0,0 +1,42 @@
+# Neptune Analytics Vector Store
+
+[Neptune Analytics](https://docs.aws.amazon.com/neptune-analytics/latest/userguide/what-is-neptune-analytics.html/) is a memory-optimized graph database engine for analytics. With Neptune Analytics, you can get insights and find trends by processing large amounts of graph data in seconds, including vector search.
+
+
+## Installation
+
+```bash
+pip install mem0ai[vector_stores]
+```
+
+## Usage
+
+```python
+config = {
+    "vector_store": {
+        "provider": "neptune",
+        "config": {
+            "collection_name": "mem0",
+            "endpoint": f"neptune-graph://my-graph-identifier",
+        },
+    },
+}
+
+m = Memory.from_config(config)
+messages = [
+    {"role": "user", "content": "I'm planning to watch a movie tonight. Any recommendations?"},
+    {"role": "assistant", "content": "How about a thriller movies? They can be quite engaging."},
+    {"role": "user", "content": "I'm not a big fan of thriller movies but I love sci-fi movies."},
+    {"role": "assistant", "content": "Got it! I'll avoid thriller recommendations and suggest sci-fi movies in the future."}
+]
+m.add(messages, user_id="alice", metadata={"category": "movies"})
+```
+
+## Parameters
+
+Let's see the available parameters for the `neptune` config:
+
+| Parameter | Description | Default Value |
+| --- | --- | --- |
+| `collection_name` | The name of the collection to store the vectors | `mem0` |
+| `endpoint` | Connection URL for the Neptune Analytics service | `neptune-graph://my-graph-identifier` |
@@ -58,7 +58,7 @@ config = {
 m = Memory.from_config(config)
 messages = [
    {"role": "user", "content": "I'm planning to watch a movie tonight. Any recommendations?"},
-    {"role": "assistant", "content": "How about a thriller movies? They can be quite engaging."},
+    {"role": "assistant", "content": "How about thriller movies? They can be quite engaging."},
    {"role": "user", "content": "I'm not a big fan of thriller movies but I love sci-fi movies."},
    {"role": "assistant", "content": "Got it! I'll avoid thriller recommendations and suggest sci-fi movies in the future."}
 ]
@@ -74,8 +74,8 @@ results = m.search("What kind of movies does Alice like?", user_id="alice")
 ### Features

 - Fast and Efficient Vector Search
- Can be deployed on-premises, in containers, or on cloud platforms like AWS OpenSearch Service.
- Multiple Authentication and Security Methods (Basic Authentication, API Keys, LDAP, SAML, and OpenID Connect)
+- Can be deployed on-premises, in containers, or on cloud platforms like AWS OpenSearch Service
+- Multiple authentication and security methods (Basic Authentication, API Keys, LDAP, SAML, and OpenID Connect)
 - Automatic index creation with optimized mappings for vector search
- Memory Optimization through Disk-Based Vector Search and Quantization
- Real-Time Analytics and Observability
+- Memory optimization through disk-based vector search and quantization
+- Real-time analytics and observability
@@ -1,8 +1,9 @@
-[pgvector](https://github.com/pgvector/pgvector) is open-source vector similarity search for Postgres. After connecting with postgres run `CREATE EXTENSION IF NOT EXISTS vector;` to create the vector extension.
+[pgvector](https://github.com/pgvector/pgvector) is an open-source vector similarity search extension for Postgres. After connecting to Postgres, run `CREATE EXTENSION IF NOT EXISTS vector;` to create the vector extension.

 ### Usage

-```python
+<CodeGroup>
+```python Python
 import os
 from mem0 import Memory

@@ -23,16 +24,47 @@ config = {
 m = Memory.from_config(config)
 messages = [
    {"role": "user", "content": "I'm planning to watch a movie tonight. Any recommendations?"},
-    {"role": "assistant", "content": "How about a thriller movies? They can be quite engaging."},
-    {"role": "user", "content": "I’m not a big fan of thriller movies but I love sci-fi movies."},
+    {"role": "assistant", "content": "How about thriller movies? They can be quite engaging."},
+    {"role": "user", "content": "I'm not a big fan of thriller movies but I love sci-fi movies."},
    {"role": "assistant", "content": "Got it! I'll avoid thriller recommendations and suggest sci-fi movies in the future."}
 ]
 m.add(messages, user_id="alice", metadata={"category": "movies"})
 ```

+```typescript TypeScript
+import { Memory } from 'mem0ai/oss';
+
+const config = {
+  vectorStore: {
+    provider: 'pgvector',
+    config: {
+      collectionName: 'memories',
+      embeddingModelDims: 1536,
+      user: 'test',
+      password: '123',
+      host: '127.0.0.1',
+      port: 5432,
+      dbname: 'vector_store', // Optional, defaults to 'postgres'
+      diskann: false, // Optional, requires pgvectorscale extension
+      hnsw: false, // Optional, for HNSW indexing
+    },
+  },
+};
+
+const memory = new Memory(config);
+const messages = [
+    {"role": "user", "content": "I'm planning to watch a movie tonight. Any recommendations?"},
+    {"role": "assistant", "content": "How about thriller movies? They can be quite engaging."},
+    {"role": "user", "content": "I'm not a big fan of thriller movies but I love sci-fi movies."},
+    {"role": "assistant", "content": "Got it! I'll avoid thriller recommendations and suggest sci-fi movies in the future."}
+]
+await memory.add(messages, { userId: "alice", metadata: { category: "movies" } });
+```
+</CodeGroup>
+
 ### Config

-Here's the parameters available for configuring pgvector:
+Here are the parameters available for configuring pgvector:

 | Parameter | Description | Default Value |
 | --- | --- | --- |
@@ -33,7 +33,7 @@ config = {
 m = Memory.from_config(config)
 messages = [
    {"role": "user", "content": "I'm planning to watch a movie tonight. Any recommendations?"},
-    {"role": "assistant", "content": "How about a thriller movies? They can be quite engaging."},
+    {"role": "assistant", "content": "How about thriller movies? They can be quite engaging."},
    {"role": "user", "content": "I'm not a big fan of thriller movies but I love sci-fi movies."},
    {"role": "assistant", "content": "Got it! I'll avoid thriller recommendations and suggest sci-fi movies in the future."}
 ]
@@ -23,7 +23,7 @@ config = {
 m = Memory.from_config(config)
 messages = [
    {"role": "user", "content": "I'm planning to watch a movie tonight. Any recommendations?"},
-    {"role": "assistant", "content": "How about a thriller movies? They can be quite engaging."},
+    {"role": "assistant", "content": "How about thriller movies? They can be quite engaging."},
    {"role": "user", "content": "I’m not a big fan of thriller movies but I love sci-fi movies."},
    {"role": "assistant", "content": "Got it! I'll avoid thriller recommendations and suggest sci-fi movies in the future."}
 ]
@@ -48,7 +48,7 @@ const config = {
 const memory = new Memory(config);
 const messages = [
    {"role": "user", "content": "I'm planning to watch a movie tonight. Any recommendations?"},
-    {"role": "assistant", "content": "How about a thriller movies? They can be quite engaging."},
+    {"role": "assistant", "content": "How about thriller movies? They can be quite engaging."},
    {"role": "user", "content": "I’m not a big fan of thriller movies but I love sci-fi movies."},
    {"role": "assistant", "content": "Got it! I'll avoid thriller recommendations and suggest sci-fi movies in the future."}
 ]
@@ -34,7 +34,7 @@ config = {
 m = Memory.from_config(config)
 messages = [
    {"role": "user", "content": "I'm planning to watch a movie tonight. Any recommendations?"},
-    {"role": "assistant", "content": "How about a thriller movies? They can be quite engaging."},
+    {"role": "assistant", "content": "How about thriller movies? They can be quite engaging."},
    {"role": "user", "content": "I’m not a big fan of thriller movies but I love sci-fi movies."},
    {"role": "assistant", "content": "Got it! I'll avoid thriller recommendations and suggest sci-fi movies in the future."}
 ]
@@ -60,7 +60,7 @@ const config = {
 const memory = new Memory(config);
 const messages = [
    {"role": "user", "content": "I'm planning to watch a movie tonight. Any recommendations?"},
-    {"role": "assistant", "content": "How about a thriller movies? They can be quite engaging."},
+    {"role": "assistant", "content": "How about thriller movies? They can be quite engaging."},
    {"role": "user", "content": "I’m not a big fan of thriller movies but I love sci-fi movies."},
    {"role": "assistant", "content": "Got it! I'll avoid thriller recommendations and suggest sci-fi movies in the future."}
 ]
@@ -0,0 +1,78 @@
+---
+title: Amazon S3 Vectors
+---
+
+[Amazon S3 Vectors](https://aws.amazon.com/s3/features/vectors/) is a purpose-built, cost-optimized vector storage and query service for semantic search and AI applications. It provides S3-level elasticity and durability with sub-second query performance.
+
+### Installation
+
+S3 Vectors support requires additional dependencies. Install them with:
+
+```bash
+pip install boto3
+```
+
+### Usage
+
+To use Amazon S3 Vectors with Mem0, you need to have an AWS account and the necessary IAM permissions (`s3vectors:*`). Ensure your environment is configured with AWS credentials (e.g., via `~/.aws/credentials` or environment variables).
+
+```python
+import os
+from mem0 import Memory
+
+# Ensure your AWS credentials are configured in your environment
+# e.g., by setting AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, and AWS_DEFAULT_REGION
+
+config = {
+    "vector_store": {
+        "provider": "s3_vectors",
+        "config": {
+            "vector_bucket_name": "my-mem0-vector-bucket",
+            "collection_name": "my-memories-index",
+            "embedding_model_dims": 1536,
+            "distance_metric": "cosine",
+            "region_name": "us-east-1"
+        }
+    }
+}
+
+m = Memory.from_config(config)
+messages = [
+    {"role": "user", "content": "I'm planning to watch a movie tonight. Any recommendations?"},
+    {"role": "assistant", "content": "How about a thriller movie? They can be quite engaging."},
+    {"role": "user", "content": "I'm not a big fan of thriller movies but I love sci-fi movies."},
+    {"role": "assistant", "content": "Got it! I'll avoid thriller recommendations and suggest sci-fi movies in the future."}
+]
+m.add(messages, user_id="alice", metadata={"category": "movies"})
+```
+
+### Config
+
+Here are the parameters available for configuring Amazon S3 Vectors:
+
+| Parameter              | Description                                                                      | Default Value                         |
+| ---------------------- | -------------------------------------------------------------------------------- | ------------------------------------- |
+| `vector_bucket_name`   | The name of the S3 Vector bucket to use. It will be created if it doesn't exist. | Required                              |
+| `collection_name`      | The name of the vector index within the bucket.                                  | `mem0`                                |
+| `embedding_model_dims` | Dimensions of the embedding model. Must match your embedder.                     | `1536`                                |
+| `distance_metric`      | Distance metric for similarity search. Options: `cosine`, `euclidean`.           | `cosine`                              |
+| `region_name`          | The AWS region where the bucket and index reside.                                | `None` (uses default from AWS config) |
+
+### IAM Permissions
+
+Your AWS identity (user or role) needs permissions to perform actions on S3 Vectors. A minimal policy would look like this:
+
+```json
+{
+  "Version": "2012-10-17",
+  "Statement": [
+    {
+      "Effect": "Allow",
+      "Action": "s3vectors:*",
+      "Resource": "*"
+    }
+  ]
+}
+```
+
+For production, it is recommended to scope down the resource ARN to your specific buckets and indexes.
@@ -26,7 +26,7 @@ config = {
 m = Memory.from_config(config)
 messages = [
    {"role": "user", "content": "I'm planning to watch a movie tonight. Any recommendations?"},
-    {"role": "assistant", "content": "How about a thriller movies? They can be quite engaging."},
+    {"role": "assistant", "content": "How about thriller movies? They can be quite engaging."},
    {"role": "user", "content": "I'm not a big fan of thriller movies but I love sci-fi movies."},
    {"role": "assistant", "content": "Got it! I'll avoid thriller recommendations and suggest sci-fi movies in the future."}
 ]
@@ -53,7 +53,7 @@ const memory = new Memory(config);

 const messages = [
    {"role": "user", "content": "I'm planning to watch a movie tonight. Any recommendations?"},
-    {"role": "assistant", "content": "How about a thriller movies? They can be quite engaging."},
+    {"role": "assistant", "content": "How about thriller movies? They can be quite engaging."},
    {"role": "user", "content": "I'm not a big fan of thriller movies but I love sci-fi movies."},
    {"role": "assistant", "content": "Got it! I'll avoid thriller recommendations and suggest sci-fi movies in the future."}
 ]
@@ -109,7 +109,7 @@ end;
 $$;
 ```

-Goto [Supabase](https://supabase.com/dashboard/projects) and run the above SQL migrations inside the SQL Editor.
+Go to [Supabase](https://supabase.com/dashboard/projects) and run the above SQL migrations in the SQL Editor.

 ### Config

@@ -0,0 +1,49 @@
+# Valkey Vector Store
+
+[Valkey](https://valkey.io/) is an open source (BSD) high-performance key/value datastore that supports a variety of workloads and rich datastructures including vector search.
+
+## Installation
+
+```bash
+pip install mem0ai[vector_stores]
+```
+
+## Usage
+
+```python
+config = {
+    "vector_store": {
+        "provider": "valkey",
+        "config": {
+            "collection_name": "test",
+            "valkey_url": "valkey://localhost:6379",
+            "embedding_model_dims": 1536,
+            "index_type": "flat"
+        }
+    }
+}
+
+m = Memory.from_config(config)
+messages = [
+    {"role": "user", "content": "I'm planning to watch a movie tonight. Any recommendations?"},
+    {"role": "assistant", "content": "How about thriller movies? They can be quite engaging."},
+    {"role": "user", "content": "I'm not a big fan of thriller movies but I love sci-fi movies."},
+    {"role": "assistant", "content": "Got it! I'll avoid thriller recommendations and suggest sci-fi movies in the future."}
+]
+m.add(messages, user_id="alice", metadata={"category": "movies"})
+```
+
+## Parameters
+
+Here are the parameters available for configuring Valkey:
+
+| Parameter | Description | Default Value |
+| --- | --- | --- |
+| `collection_name` | The name of the collection to store the vectors | `mem0` |
+| `valkey_url` | Connection URL for the Valkey server | `valkey://localhost:6379` |
+| `embedding_model_dims` | Dimensions of the embedding model | `1536` |
+| `index_type` | Vector index algorithm (`hnsw` or `flat`) | `hnsw` |
+| `hnsw_m` | Number of bi-directional links for HNSW | `16` |
+| `hnsw_ef_construction` | Size of dynamic candidate list for HNSW | `200` |
+| `hnsw_ef_runtime` | Size of dynamic candidate list for search | `10` |
+| `distance_metric` | Distance metric for vector similarity | `cosine` |
@@ -31,7 +31,7 @@ await memory.add(messages, { userId: "bob", metadata: { interest: "books" } });

 ### Config

-Let's see the available parameters for the `vectorize` config:
+Here are the parameters available for configuring Vectorize:

 <Tabs>
 <Tab title="TypeScript">
@@ -37,7 +37,7 @@ m.add(messages, user_id="alice", metadata={"category": "movies"})

 ### Config

-Let's see the available parameters for the `weaviate` config:
+Here are the parameters available for configuring Weaviate:

 | Parameter | Description | Default Value |
 | --- | --- | --- |
@@ -1,11 +1,7 @@
 ---
 title: Overview
-icon: "info"
-iconType: "solid"
 ---

-<Snippet file="blank-notif.mdx" />
-
 Mem0 includes built-in support for various popular databases. Memory can utilize the database provided by the user, ensuring efficient use for specific needs.

 ## Supported Vector Databases
@@ -13,19 +9,20 @@ Mem0 includes built-in support for various popular databases. Memory can utilize
 See the list of supported vector databases below.

 <Note>
-  The following vector databases are supported in the Python implementation. The TypeScript implementation currently only supports Qdrant, Redis,Vectorize and in-memory vector database.
+  The following vector databases are supported in the Python implementation. The TypeScript implementation currently only supports Qdrant, Redis, Valkey, Vectorize and in-memory vector database.
 </Note>

 <CardGroup cols={3}>
  <Card title="Qdrant" href="/components/vectordbs/dbs/qdrant"></Card>
  <Card title="Chroma" href="/components/vectordbs/dbs/chroma"></Card>
-  <Card title="Pgvector" href="/components/vectordbs/dbs/pgvector"></Card>
+  <Card title="PGVector" href="/components/vectordbs/dbs/pgvector"></Card>
  <Card title="Upstash Vector" href="/components/vectordbs/dbs/upstash-vector"></Card>
  <Card title="Milvus" href="/components/vectordbs/dbs/milvus"></Card>
  <Card title="Pinecone" href="/components/vectordbs/dbs/pinecone"></Card>
  <Card title="MongoDB" href="/components/vectordbs/dbs/mongodb"></Card>
  <Card title="Azure" href="/components/vectordbs/dbs/azure"></Card>
  <Card title="Redis" href="/components/vectordbs/dbs/redis"></Card>
+  <Card title="Valkey" href="/components/vectordbs/dbs/valkey"></Card>
  <Card title="Elasticsearch" href="/components/vectordbs/dbs/elasticsearch"></Card>
  <Card title="OpenSearch" href="/components/vectordbs/dbs/opensearch"></Card>
  <Card title="Supabase" href="/components/vectordbs/dbs/supabase"></Card>
@@ -33,6 +30,8 @@ See the list of supported vector databases below.
  <Card title="Weaviate" href="/components/vectordbs/dbs/weaviate"></Card>
  <Card title="FAISS" href="/components/vectordbs/dbs/faiss"></Card>
  <Card title="LangChain" href="/components/vectordbs/dbs/langchain"></Card>
+  <Card title="Amazon S3 Vectors" href="/components/vectordbs/dbs/s3_vectors"></Card>
+  <Card title="Databricks" href="/components/vectordbs/dbs/databricks"></Card>
 </CardGroup>

 ## Usage
@@ -43,12 +42,10 @@ For a comprehensive list of available parameters for vector database configurati

 ## Common issues

-### Using model with different dimensions
+### Using Model with Different Dimensions

-If you are using customized model, which is having different dimensions other than 1536
-for example 768, you may encounter below error:
+If you are using a customized model with different dimensions other than 1536 (for example, 768), you may encounter the following error:

 `ValueError: shapes (0,1536) and (768,) not aligned: 1536 (dim 1) != 768 (dim 0)`

-you could add `"embedding_model_dims": 768,` to the config of the vector_store to overcome this issue.
-
+You can add `"embedding_model_dims": 768,` to the config of the vector_store to resolve this issue.
@@ -3,8 +3,6 @@ title: Development
 icon: "code"
 ---

-<Snippet file="blank-notif.mdx" />
-
 # Development Contributions

 We strive to make contributions **easy, collaborative, and enjoyable**. Follow the steps below to ensure a smooth contribution process.
@@ -21,25 +19,25 @@ To contribute, follow these steps:
 4. **Code Quality Checks**:
   - Run **linting** to catch style issues
   - Ensure **all tests pass**
-5. **Submit a Pull Request** 🚀
+5. **Submit a Pull Request**

 For detailed guidance on pull requests, refer to [GitHub's documentation](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request).

 ---

-## 📦 Dependency Management
+## Dependency Management

 We use `hatch` as our package manager. Install it by following the [official instructions](https://hatch.pypa.io/latest/install/).

-⚠️ **Do NOT use `pip` or `conda` for dependency management.** Instead, follow these steps in order:
+**Do NOT use `pip` or `conda` for dependency management.** Instead, follow these steps in order:

 ```bash
 # 1. Install base dependencies
 make install

-# 2. Activate virtual environment (this will install deps.)
-hatch shell (for default env)
-hatch -e dev_py_3_11 shell (for dev_py_3_11) (differences are mentioned in pyproject.toml)
+# 2. Activate virtual environment (this will install dependencies)
+hatch shell  # For default environment
+hatch -e dev_py_3_11 shell  # For dev_py_3_11 (differences are mentioned in pyproject.toml)

 # 3. Install all optional dependencies
 make install_all
@@ -47,9 +45,9 @@ make install_all

 ---

-## 🛠️ Development Standards
+## Development Standards

-### ✅ Pre-commit Hooks
+### Pre-commit Hooks

 Ensure `pre-commit` is installed before contributing:

@@ -57,7 +55,7 @@ Ensure `pre-commit` is installed before contributing:
 pre-commit install
 ```

-### 🔍 Linting with `ruff`
+### Linting with `ruff`

 Run the linter and fix any reported issues before submitting your PR:

@@ -65,7 +63,7 @@ Run the linter and fix any reported issues before submitting your PR:
 make lint
 ```

-### 🎨 Code Formatting
+### Code Formatting

 To maintain a consistent code style, format your code:

@@ -73,7 +71,7 @@ To maintain a consistent code style, format your code:
 make format
 ```

-### 🧪 Testing with `pytest`
+### Testing with `pytest`

 Run tests to verify functionality before submitting your PR:

@@ -81,14 +79,14 @@ Run tests to verify functionality before submitting your PR:
 make test
 ```

-💡 **Note:** Some dependencies have been removed from the main dependencies to reduce package size. Run `make install_all` to install necessary dependencies before running tests.
+**Note:** Some dependencies have been removed from the main dependencies to reduce package size. Run `make install_all` to install necessary dependencies before running tests.

 ---

-## 🚀 Release Process
+## Release Process

 Currently, releases are handled manually. We aim for frequent releases, typically when new features or bug fixes are introduced.

 ---

-Thank you for contributing to Mem0! 🎉
+Thank you for contributing to Mem0!
@@ -3,17 +3,15 @@ title: Documentation
 icon: "book"
 ---

-<Snippet file="blank-notif.mdx" />
-
 # Documentation Contributions

-## 📌 Prerequisites
+## Prerequisites

 Before getting started, ensure you have **Node.js (version 23.6.0 or higher)** installed on your system.

 ---

-## 🚀 Setting Up Mintlify
+## Setting Up Mintlify

 ### Step 1: Install Mintlify

@@ -43,7 +41,7 @@ The documentation website will be available at: [http://localhost:3000](http://l

 ---

-## 🔧 Custom Ports
+## Custom Ports

 By default, Mintlify runs on **port 3000**. To use a different port, add the `--port` flag:

@@ -53,5 +51,5 @@ mintlify dev --port 3333

 ---

-By following these steps, you can efficiently contribute to **Mem0's documentation**. Happy documenting! ✍️
+By following these steps, you can efficiently contribute to Mem0's documentation.

@@ -0,0 +1,125 @@
+---
+title: Personalized AI Tutor
+description: "Keep student progress and preferences persistent across tutoring sessions."
+---
+
+
+You can create a personalized AI Tutor using Mem0. This guide will walk you through the necessary steps and provide the complete code to get you started.
+
+## Overview
+
+The Personalized AI Tutor leverages Mem0 to retain information across interactions, enabling a tailored learning experience. By integrating with OpenAI's GPT-4 model, the tutor can provide detailed and context-aware responses to user queries.
+
+## Setup
+
+Before you begin, ensure you have the required dependencies installed. You can install the necessary packages using pip:
+
+```bash
+pip install openai mem0ai
+```
+
+## Full Code Example
+
+Below is the complete code to create and interact with a Personalized AI Tutor using Mem0:
+
+```python
+import os 
+from openai import OpenAI
+from mem0 import Memory
+
+# Set the OpenAI API key
+os.environ['OPENAI_API_KEY'] = 'sk-xxx'
+
+# Initialize the OpenAI client
+client = OpenAI()
+
+class PersonalAITutor:
+    def __init__(self):
+        """
+        Initialize the PersonalAITutor with memory configuration and OpenAI client.
+        """
+        config = {
+            "vector_store": {
+                "provider": "qdrant",
+                "config": {
+                    "host": "localhost",
+                    "port": 6333,
+                }
+            },
+        }
+        self.memory = Memory.from_config(config)
+        self.client = client
+        self.app_id = "app-1"
+
+    def ask(self, question, user_id=None):
+        """
+        Ask a question to the AI and store the relevant facts in memory
+
+        :param question: The question to ask the AI.
+        :param user_id: Optional user ID to associate with the memory.
+        """
+        # Start a streaming response request to the AI
+        response = self.client.responses.create(
+            model="gpt-4.1-nano-2025-04-14",
+            instructions="You are a personal AI Tutor.",
+            input=question,
+            stream=True
+        )
+
+        # Store the question in memory
+        self.memory.add(question, user_id=user_id, metadata={"app_id": self.app_id})
+
+        # Print the response from the AI in real-time
+        for event in response:
+            if event.type == "response.output_text.delta":
+                print(event.delta, end="")
+
+    def get_memories(self, user_id=None):
+        """
+        Retrieve all memories associated with the given user ID.
+
+        :param user_id: Optional user ID to filter memories.
+        :return: List of memories.
+        """
+        return self.memory.get_all(user_id=user_id)
+
+# Instantiate the PersonalAITutor
+ai_tutor = PersonalAITutor()
+
+# Define a user ID
+user_id = "john_doe"
+
+# Ask a question
+ai_tutor.ask("I am learning introduction to CS. What is queue? Briefly explain.", user_id=user_id)
+```
+
+### Fetching Memories
+
+You can fetch all the memories at any point in time using the following code:
+
+```python
+memories = ai_tutor.get_memories(user_id=user_id)
+for m in memories['results']:
+    print(m['memory'])
+```
+
+## Key Points
+
+- **Initialization**: The PersonalAITutor class is initialized with the necessary memory configuration and OpenAI client setup
+- **Asking Questions**: The ask method sends a question to the AI and stores the relevant information in memory
+- **Retrieving Memories**: The get_memories method fetches all stored memories associated with a user
+
+## Conclusion
+
+As the conversation progresses, Mem0's memory automatically updates based on the interactions, providing a continuously improving personalized learning experience. This setup ensures that the AI Tutor can offer contextually relevant and accurate responses, enhancing the overall educational process.
+
+---
+
+<CardGroup cols={2}>
+  <Card title="Build a Mem0 Companion" icon="users" href="/cookbooks/essentials/building-ai-companion">
+    Learn the foundations of memory-powered companions with production-ready patterns.
+  </Card>
+  <Card title="Travel Assistant with Mem0" icon="plane" href="/cookbooks/companions/travel-assistant">
+    Build a travel companion that remembers preferences and past conversations.
+  </Card>
+</CardGroup>
@@ -0,0 +1,83 @@
+---
+title: Self-Hosted AI Companion
+description: "Run Mem0 end-to-end on your machine using Ollama-powered LLMs and embedders."
+---
+
+
+Mem0 can be utilized entirely locally by leveraging Ollama for both the embedding model and the language model (LLM). This guide will walk you through the necessary steps and provide the complete code to get you started.
+
+## Overview
+
+By using Ollama, you can run Mem0 locally, which allows for greater control over your data and models. This setup uses Ollama for both the embedding model and the language model, providing a fully local solution.
+
+## Setup
+
+Before you begin, ensure you have Mem0 and Ollama installed and properly configured on your local machine.
+
+## Full Code Example
+
+Below is the complete code to set up and use Mem0 locally with Ollama:
+
+```python
+from mem0 import Memory
+
+config = {
+    "vector_store": {
+        "provider": "qdrant",
+        "config": {
+            "collection_name": "test",
+            "host": "localhost",
+            "port": 6333,
+            "embedding_model_dims": 768,  # Change this according to your local model's dimensions
+        },
+    },
+    "llm": {
+        "provider": "ollama",
+        "config": {
+            "model": "llama3.1:latest",
+            "temperature": 0,
+            "max_tokens": 2000,
+            "ollama_base_url": "http://localhost:11434",  # Ensure this URL is correct
+        },
+    },
+    "embedder": {
+        "provider": "ollama",
+        "config": {
+            "model": "nomic-embed-text:latest",
+            # Alternatively, you can use "snowflake-arctic-embed:latest"
+            "ollama_base_url": "http://localhost:11434",
+        },
+    },
+}
+
+# Initialize Memory with the configuration
+m = Memory.from_config(config)
+
+# Add a memory
+m.add("I'm visiting Paris", user_id="john")
+
+# Retrieve memories
+memories = m.get_all(user_id="john")
+```
+
+## Key Points
+
+- **Configuration**: The setup involves configuring the vector store, language model, and embedding model to use local resources
+- **Vector Store**: Qdrant is used as the vector store, running on localhost
+- **Language Model**: Ollama is used as the LLM provider, with the `llama3.1:latest` model
+- **Embedding Model**: Ollama is also used for embeddings, with the `nomic-embed-text:latest` model
+
+## Conclusion
+
+This local setup of Mem0 using Ollama provides a fully self-contained solution for memory management and AI interactions. It allows for greater control over your data and models while still leveraging the powerful capabilities of Mem0.
+
+---
+
+<CardGroup cols={2}>
+  <Card title="Configure Open Source" icon="gear" href="/open-source/configuration">
+    Explore advanced configuration options for vector stores, LLMs, and embedders.
+  </Card>
+  <Card title="Build a Mem0 Companion" icon="users" href="/cookbooks/essentials/building-ai-companion">
+    Learn core companion patterns that work with any LLM provider.
+  </Card>
+</CardGroup>
@@ -0,0 +1,139 @@
+---
+title: Build a Node.js Companion
+description: "Build a JavaScript fitness coach that remembers user goals run after run."
+---
+
+
+You can create a personalized AI Companion using Mem0. This guide will walk you through the necessary steps and provide the complete code to get you started.
+
+## Overview
+
+The Personalized AI Companion leverages Mem0 to retain information across interactions, enabling a tailored learning experience. It creates memories for each user interaction and integrates with OpenAI's GPT models to provide detailed and context-aware responses to user queries.
+
+## Setup
+
+Before you begin, ensure you have Node.js installed and create a new project. Install the required dependencies using npm:
+
+```bash
+npm install openai mem0ai
+```
+
+## Full Code Example
+
+Below is the complete code to create and interact with an AI Companion using Mem0:
+
+```javascript
+import { OpenAI } from 'openai';
+import { Memory } from 'mem0ai/oss';
+import * as readline from 'readline';
+
+const openaiClient = new OpenAI();
+const memory = new Memory();
+
+async function chatWithMemories(message, userId = "default_user") {
+  const relevantMemories = await memory.search(message, { userId: userId });
+  
+  const memoriesStr = relevantMemories.results
+    .map(entry => `- ${entry.memory}`)
+    .join('\n');
+  
+  const systemPrompt = `You are a helpful AI. Answer the question based on query and memories.
+User Memories:
+${memoriesStr}`;
+  
+  const messages = [
+    { role: "system", content: systemPrompt },
+    { role: "user", content: message }
+  ];
+  
+  const response = await openaiClient.chat.completions.create({
+    model: "gpt-4.1-nano-2025-04-14",
+    messages: messages
+  });
+  
+  const assistantResponse = response.choices[0].message.content || "";
+  
+  messages.push({ role: "assistant", content: assistantResponse });
+  await memory.add(messages, { userId: userId });
+  
+  return assistantResponse;
+}
+
+async function main() {
+  const rl = readline.createInterface({
+    input: process.stdin,
+    output: process.stdout
+  });
+  
+  console.log("Chat with AI (type 'exit' to quit)");
+  
+  const askQuestion = () => {
+    return new Promise((resolve) => {
+      rl.question("You: ", (input) => {
+        resolve(input.trim());
+      });
+    });
+  };
+  
+  try {
+    while (true) {
+      const userInput = await askQuestion();
+      
+      if (userInput.toLowerCase() === 'exit') {
+        console.log("Goodbye!");
+        rl.close();
+        break;
+      }
+      
+      const response = await chatWithMemories(userInput, "sample_user");
+      console.log(`AI: ${response}`);
+    }
+  } catch (error) {
+    console.error("An error occurred:", error);
+    rl.close();
+  }
+}
+
+main().catch(console.error);
+```
+
+### Key Components
+
+1. **Initialization**
+   - The code initializes both OpenAI and Mem0 Memory clients
+   - Uses Node.js's built-in readline module for command-line interaction
+
+2. **Memory Management (chatWithMemories function)**
+   - Retrieves relevant memories using Mem0's search functionality
+   - Constructs a system prompt that includes past memories
+   - Makes API calls to OpenAI for generating responses
+   - Stores new interactions in memory
+
+3. **Interactive Chat Interface (main function)**
+   - Creates a command-line interface for user interaction
+   - Handles user input and displays AI responses
+   - Includes graceful exit functionality
+
+### Environment Setup
+
+Make sure to set up your environment variables:
+```bash
+export OPENAI_API_KEY=your_api_key
+```
+
+### Conclusion
+
+This implementation demonstrates how to create an AI Companion that maintains context across conversations using Mem0's memory capabilities. The system automatically stores and retrieves relevant information, creating a more personalized and context-aware interaction experience.
+
+As users interact with the system, Mem0's memory system continuously learns and adapts, making future responses more relevant and personalized. This setup is ideal for creating long-term learning AI assistants that can maintain context and provide increasingly personalized responses over time.
+
+---
+
+<CardGroup cols={2}>
+  <Card title="Partition Memories by Entity" icon="layers" href="/cookbooks/essentials/entity-partitioning-playbook">
+    Separate user, agent, and session context to keep your companion consistent.
+  </Card>
+  <Card title="Quickstart Demo with Mem0" icon="rocket" href="/cookbooks/companions/quickstart-demo">
+    Run the full showcase app to see memory-powered companions in action.
+  </Card>
+</CardGroup>
@@ -0,0 +1,80 @@
+---
+title: Interactive Memory Demo
+description: "Spin up the showcase companion app to see Mem0 memories in action."
+---
+
+
+You can create a personalized AI Companion using Mem0. This guide will walk you through the necessary steps and provide the complete setup instructions to get you started.
+
+<video
+  autoPlay
+  muted
+  loop
+  playsInline
+  className="w-full aspect-video rounded-lg"
+  src="https://github.com/user-attachments/assets/cebc4f8e-bdb9-4837-868d-13c5ab7bb433"
+></video>
+
+You can try the [Mem0 Demo](https://mem0-4vmi.vercel.app) live here.
+
+## Overview
+
+The Personalized AI Companion leverages Mem0 to retain information across interactions, enabling a tailored learning experience. It creates memories for each user interaction and integrates with OpenAI's GPT models to provide detailed and context-aware responses to user queries.
+
+## Setup
+
+Before you begin, follow these steps to set up the demo application:
+
+1. Clone the Mem0 repository:
+   ```bash
+   git clone https://github.com/mem0ai/mem0.git
+   ```
+
+2. Navigate to the demo application folder:
+   ```bash
+   cd mem0/examples/mem0-demo
+   ```
+
+3. Install dependencies:
+   ```bash
+   pnpm install
+   ```
+
+4. Set up environment variables by creating a `.env` file in the project root with the following content:
+   ```bash
+   OPENAI_API_KEY=your_openai_api_key
+   MEM0_API_KEY=your_mem0_api_key
+   ```
+   You can obtain your `MEM0_API_KEY` by signing up at [Mem0 API Dashboard](https://app.mem0.ai/dashboard/api-keys).
+
+5. Start the development server:
+   ```bash
+   pnpm run dev
+   ```
+
+## Enhancing the Next.js Application
+
+Once the demo is running, you can customize and enhance the Next.js application by modifying the components in the `mem0-demo` folder. Consider:
+- Adding new memory features to improve contextual retention
+- Customizing the UI to better suit your application needs
+- Integrating additional APIs or third-party services to extend functionality
+
+## Full Code
+
+You can find the complete source code for this demo on GitHub:
+[Mem0 Demo GitHub](https://github.com/mem0ai/mem0/tree/main/examples/mem0-demo)
+
+## Conclusion
+
+This setup demonstrates how to build an AI Companion that maintains memory across interactions using Mem0. The system continuously adapts to user interactions, making future responses more relevant and personalized. Experiment with the application and enhance it further to suit your use case!
+
+---
+
+<CardGroup cols={2}>
+  <Card title="Build a Mem0 Companion" icon="users" href="/cookbooks/essentials/building-ai-companion">
+    Deep dive into production patterns for fitness coaches, tutors, and assistants.
+  </Card>
+  <Card title="Node.js Companion with Mem0" icon="code" href="/cookbooks/companions/nodejs-companion">
+    Implement a command-line companion using the Node.js SDK.
+  </Card>
+</CardGroup>
--- a/Show More
+++ b/Show More
Author	SHA1	Message	Date
Saket Aryan	69a832dc58	chore: add update project options (#3947 )	2026-02-03 10:55:43 +05:30
Deshraj Yadav	70baa46cb1	fix: add OpenClaw to docs navigation (#3965 )	2026-02-02 10:17:19 -08:00
Deshraj Yadav	3d3e875d21	Feature: Add OpenClaw plugin and documentation (#3964 )	2026-02-02 10:04:08 -08:00
Saket Aryan	dba7f0458a	(version-bump): update the project version to v1.0.2 (#3902 )	2026-01-13 13:01:38 +05:30
Saket Aryan	27e5db5831	(fix): mongodb distribution name, azure ai search, and workflow trigger (#3900 )	2026-01-13 12:52:49 +05:30
Saket Aryan	2c90eedfff	chore: do a disk cleanup in gh actions to fix memo build (#3899 )	2026-01-13 11:42:54 +05:30
Noah Stapp	a1db0f6362	Add DriverInfo metadata to MongoDB vector store (#3648 )	2026-01-12 21:07:42 -08:00
Saket Aryan	90a7b1afa0	feat(ts-sdk): add support for keyword arguments in add and search methods (#3895 )	2026-01-10 21:19:55 +05:30
Saket Aryan	69a552d8a8	fix(docs): Improve light mode support for introduction page and organize thumbnails (#3880 )	2026-01-03 21:21:24 +05:30
Saket Aryan	417ebffadd	(ts-sdk-update): Update for TypeScript SDK v2.2. (#3865 )	2025-12-29 15:01:18 +05:30
Saket Aryan	1dc07d3550	(docs): update to use the v2 URL Patterns in delete user route (#3864 )	2025-12-29 14:51:42 +05:30
Saket Aryan	65e22e34d9	chore: remove unnecessary dependencies from Vercel AI SDK to reduce package size (#3856 )	2025-12-26 22:24:40 +05:30
Parth Sharma	e08f44c5f2	[docs] link to fix api key redirect (#3843 )	2025-12-18 00:20:29 +05:30
Parth Sharma	16d989bbcd	[docs] Series of docs for mem0-mcp (#3831 )	2025-12-15 22:03:23 +05:30
Swarnaprakash Udayakumar	0f8654bd40	Add Strands agent (with AWS ElastiCache and Neptune) example mention in Joint blog post by Mem0 and AWS (#3824 )	2025-12-13 14:00:29 +05:30
Parth Sharma	654089fcfc	[docs] Filters fix in docs (#3815 )	2025-12-11 18:38:08 +05:30
Parth Sharma	222c6ceea1	(docs-fix): fix broken redirect in python and node quickstart (#3826 )	2025-12-11 15:50:20 +05:30
Parth Sharma	84bd6e3b97	fix(docs): Correct API authentication header from Bearer to Token (#3820 )	2025-12-11 00:32:59 +05:30
Parth Sharma	5676bebd5f	docs: migration guide v1 (#3822 )	2025-12-10 23:45:19 +05:30
Parth Sharma	f14132db44	[docs] Gemini-3 demo with mem0-mcp (#3810 )	2025-12-09 23:43:49 +05:30
Parth Sharma	903c3635cc	[docs] Add memory and v2 docs fixup (#3792 )	2025-11-27 23:41:51 +05:30
Parth Sharma	cc2894aaec	[docs] Docs redirect to platform (#3769 )	2025-11-22 10:17:58 +05:30
Deshraj Yadav	97cbff77ef	Add events API docs and spec updates (#3752 )	2025-11-14 20:53:31 -08:00
Parth Sharma	e29220efda	[docs] new redirect for entity doc (#3750 )	2025-11-14 08:51:25 -08:00
Prateek Chhikara	3b84a234e1	Updates to python sdk (#3749 )	2025-11-13 14:22:39 -08:00
Parth Sharma	2bca30ebe6	[docs] Minor Docs fixes ( enhancements , restructure ) (#3748 )	2025-11-13 11:58:36 -08:00
Parth Sharma	3297ec1a46	[doc] Partition Memories by Entity , features doc and cookbook (#3735 )	2025-11-13 10:26:41 -08:00
Parth Sharma	61e2a40d55	[docs] python quickstart fix (#3742 )	2025-11-13 10:18:55 -08:00
Parth Sharma	9f921e27cb	[docs] add callouts and comparision to clear the problem of when to use Infer=True/False (#3738 )	2025-11-10 14:23:49 -08:00
Parth Sharma	568e97d013	[docs] graph memory docs fix (#3728 )	2025-11-07 09:41:35 -08:00
Parth Sharma	ac5660e26d	[docs] LLM.txt + Context menu to make our Docs LLM friendly (#3726 )	2025-11-07 09:38:12 -08:00
Parth Sharma	76abd5117d	[docs] API References and search Doc fix (#3712 )	2025-11-04 13:53:37 -08:00
Prateek Chhikara	978babd3db	Docs Update (#3706 )	2025-11-03 11:03:33 -08:00
Parth Sharma	2b0a457198	[docs] Custom categories Documentation fix (#3702 )	2025-11-03 10:11:04 -08:00
Parth Sharma	6a7277070f	[docs] Add Redirects to the new docs to fix broken links (#3701 )	2025-11-01 06:19:47 -07:00
Parth Sharma	4c53930e47	[docs] complete redirects (#3700 )	2025-10-31 20:26:30 -07:00
Parth Sharma	84687fc3d2	[fix] list' object has no attribute 'id' - Id fault with chroma pinecone and other providers (#3693 )	2025-10-31 16:46:10 +05:30
Parth Sharma	3ca939e210	[docs] redirect with fixed ci fails - langchain (#3699 )	2025-10-31 16:45:15 +05:30
Parth Sharma	5f5e64b44b	[docs] tab icon cleanup (#3679 )	2025-10-28 09:42:19 +01:00
Parth Sharma	5cb6b31690	[docs] Cookbook name cleanup (#3678 )	2025-10-28 09:20:23 +01:00
Parth Sharma	ee8955d08b	[docs] OSS Features , Overview , Brushup (#3676 )	2025-10-27 12:31:40 -07:00
Parth Sharma	80c9139c5b	[docs] zoom effect fix (#3670 )	2025-10-27 08:56:32 +05:30
Parth Sharma	7be32641c7	[docs] Essential cookbook added and overall revamp to the structure of cookbooks (#3668 )	2025-10-27 00:19:29 +05:30
Parth Sharma	2c18355dd2	[docs] platform core concept revamp and overview update (#3664 )	2025-10-26 15:15:13 +05:30
Parth Sharma	61faf71064	[docs] Template moulding in docs/platform and index improvement (#3663 )	2025-10-25 14:05:18 -07:00
Parth Sharma	ac9598a67f	[docs] Added Templates and Contribution Guidelines (#3662 )	2025-10-25 12:58:40 -07:00
Parth Sharma	f98a17c716	[docs] Welcome page thumbnail and reranker fix (#3660 )	2025-10-25 12:20:52 -07:00
Vedant Thakkar	639d26e1ac	feat(api): add vector store configuration endpoints (#3583 )	2025-10-23 18:36:25 +05:30
Parth Sharma	f7d7c53001	Added improved docs index and overview pages and quickstart (#3603 )	2025-10-22 10:30:45 -07:00
Frederik Berg	ec1a60bf8d	Add delete_memories MCP tool for targeted deletion (#3616 )	2025-10-22 10:08:28 -07:00
Frederik Berg	77c71a134a	Fix REST API infer parameter ignored (#3607 )	2025-10-22 10:08:15 -07:00
Frederik Berg	2692e49d50	Fix: Add missing filter methods to AsyncMemory (#3624 ) Co-authored-by: Claude <noreply@anthropic.com>	2025-10-22 16:08:04 +05:30
Ronak Bhalgami	eb2f8a3738	fix: Prevent Mock object issues in graph memory tests (#3627 ) Co-authored-by: parshvadaftari <daftariparshva@gmail.com>	2025-10-22 03:53:12 +05:30
Prateek Chhikara	4a30745592	Add redirect to new apis doc page (#3639 )	2025-10-21 13:55:14 -07:00
Rahul Sharma	3b1a4c2e68	Fix condition check for memories_result type in AsyncMemory class (#3621 )	2025-10-22 01:55:28 +05:30
Mrinank Bhowmick	5227b0a062	Fix embedder config schema to support embeddingDims and url parameters (#3633 )	2025-10-21 09:30:44 -07:00
Prateek Chhikara	8031f0bf8f	Changes to docs (#3637 )	2025-10-20 16:13:34 -07:00
Prateek Chhikara	dd3e5363dd	Update docs (#3636 )	2025-10-20 16:12:11 -07:00
Frederik Berg	d5a130b785	Fix memory deletion not removing from vector store (#3610 )	2025-10-18 14:17:03 -07:00
Frederik Berg	8ede1df10a	Fix list_memories endpoint Pydantic validation error (#3608 )	2025-10-18 14:16:49 -07:00
Parshva Daftari	8ba18bf8bc	[fix] docs for search memories (#3622 )	2025-10-18 13:27:15 -07:00
Ronak Bhalgami	de224dd26d	feat: Add configurable embedding similarity threshold for graph store node matching (#3593 )	2025-10-18 13:03:30 -07:00
Faizan Habib	9ef644b95e	Add Apache Cassandra vector store support (#3578 )	2025-10-17 23:48:49 +05:30
Aashis kumar	7afbaae7a3	Fix condition check for memories_result type in Memory class (#3596 )	2025-10-17 02:17:18 +05:30
Tarun Jain	1090784302	[feat add]FastEmbed embedding for local embeddings (#3552 )	2025-10-16 22:52:22 +05:30
Parshva Daftari	394203d1b5	Mem0 1.0.0 (#3545 )	2025-10-16 15:50:20 +05:30
Kabir Kohli	8f5151c344	asycn mode default change (#3585 )	2025-10-16 04:58:53 +05:30
Parshva Daftari	41cfb3ab1a	[Update] Default LLM (#3587 )	2025-10-15 11:19:52 -07:00
G Karthik Koundinya	a40314c971	feat: Add Azure AI Search vector store support for TypeScript SDK (#3549 )	2025-10-15 11:19:10 -07:00
Vedant Thakkar	ea22e8d9cd	feat: Allow custom model and params with huggingface_base_url (#3574 )	2025-10-14 17:33:18 +05:30
Alex Kondratev	ce8a285003	Validate embedding_dims in kuzu, fix #3556 (#3558 )	2025-10-11 03:55:03 +05:30
Parshva Daftari	4559623501	[fix] milvus db bug and added tests (#3566 )	2025-10-11 02:21:35 +05:30
Deshraj Yadav	37c86aa3c0	Update main script and remove stale code (#3561 )	2025-10-09 15:30:20 -07:00
Mrinank Bhowmick	335a7d7862	Fix TypeScript build error (#3535 )	2025-10-09 11:09:31 -07:00
Mrinank Bhowmick	64571002f5	fixed hardcoded embeddingDims (#3537 )	2025-10-09 11:09:20 -07:00
Vishaal LS	9000576173	fix: handle non-serializable objects in config deepcopy (#3464 ) (#3544 )	2025-10-09 19:35:08 +05:30
Josh Hayes	922471f43b	fix: Databricks Vector Store (#3546 )	2025-10-09 19:19:07 +05:30
Saket Aryan	b93ce5548b	(docs): add v2 filter documentations (#3469 )	2025-10-07 14:12:58 +05:30
Alex Kondratev	ee0202764b	Tool call support for LangchainLLM (#3542 )	2025-10-06 00:03:44 +05:30
Saket Aryan	8ba032e029	(fix): added version=v2 as default param in ai sdk add calls (#3540 )	2025-10-05 02:16:02 +05:30
yashikabadaya	fbf3bd640c	support dependency openai 2.x (#3533 )	2025-10-03 21:50:49 +05:30
dog-last	51ce6f1347	Bug fix of thinking llm in vllm (#3510 )	2025-10-03 19:13:08 +05:30
Parshva Daftari	346d89d244	Added azure mysql for mem0 (#3531 )	2025-10-02 21:41:03 +05:30
Vishaal LS	1104b52d99	docs: add detailed explanation for output_format v1.1 parameter (#3517 )	2025-10-01 14:19:34 -07:00
Parshva Daftari	e19b748ad0	Refactor docs and fix get memories playground (#3527 )	2025-10-01 10:40:27 -07:00
Matan Cohen	517a266d74	Fix bug in weaviate search method (#3521 )	2025-10-01 14:24:03 +05:30
Frederik Berg	cbf56477be	Fix: Serialize response to JSON in add_memories MCP tool (#3523 )	2025-09-30 15:28:50 -07:00
Vishaal LS	58cc44ff38	fix: handle missing 'data' key in memory payload during search operations (#3524 )	2025-09-30 15:10:43 -07:00
Vishaal LS	445286a138	fix: update license information in README and pyproject.toml (#3522 )	2025-09-30 13:58:08 -07:00
Deshraj Yadav	d68ed11d58	Update Docs (#3520 )	2025-09-30 08:41:36 -07:00
Parshva Daftari	135883935f	refactor: v2 search and update examples (#3508 )	2025-09-26 22:55:53 +05:30
Parshva Daftari	ed5a1e9fc6	Update version to 0.1.118 (#3505 )	2025-09-26 02:03:37 +05:30
Karthikeya Kollu	dc883b0f9e	[test] Add comprehensive test suite for SQLiteManager (#3494 )	2025-09-25 22:30:03 +05:30
Saket Aryan	5616844b9c	docs-fix: Quickstart cURL example fixed (#3503 )	2025-09-25 20:44:39 +05:30
Saket Aryan	6e1d02c137	feat(ai-sdk): added file support for multimodal capabilities with memory context (#3500 )	2025-09-25 10:32:06 +05:30
Parshva Daftari	a199ee4ff8	Refactored example title for aws (#3492 )	2025-09-22 18:28:28 +05:30
Parshva Daftari	88ae952483	[DOCS] Changing 1.0 to 1.0.0 (#3486 )	2025-09-20 20:07:23 +05:30
Abdullah Irfan	9df392b26a	Fixed s3 vectors memory initialization issue from configuration (#3481 )	2025-09-20 12:43:18 +05:30
Parshva Daftari	ead210ffe4	Added weaviate db test (#3483 )	2025-09-18 14:40:44 -07:00
Andrew Carbonetto	a015e2ff4a	Add Neptune-DB graph store with vector store (#3443 ) Signed-off-by: Andrew Carbonetto <andrew.carbonetto@improving.com> Co-authored-by: Siddhartha Sahu <dev@sdht.in>	2025-09-19 02:54:33 +05:30
Brinlee Kidd	d4e98dba38	feat: implement structured exception classes with error codes and sug… (#3279 )	2025-09-19 02:31:35 +05:30
Parshva Daftari	ac72eb5ecc	Aspen theme for 1.x (#3473 )	2025-09-18 21:03:17 +05:30
Andy Kwok	6b5582f474	Feat: Mem0 vector store backend integration for Neptune Analytics (#3453 ) Signed-off-by: Andy Kwok <andy.kwok@improving.com>	2025-09-17 19:26:03 +05:30
Parshva Daftari	d38e3f1962	Fix json parsing with new memories (#3456 )	2025-09-12 17:29:34 +05:30
◢ 徇 ◤	a0685f3e8c	fix: correct typo in knowledge graph extraction guidelines (#3449 )	2025-09-12 15:07:37 +05:30
Parshva Daftari	d48b1832c7	Fixes ollama and updates openai dependency (#3452 )	2025-09-12 01:39:39 +05:30
Saket Aryan	21d69307dc	docs: Update Search V2/Get All V2 Filters (#3450 )	2025-09-11 19:10:19 +05:30
Andrew Carbonetto	9e5810dfb7	Fix bedrock anthropic models to use system field (#3438 ) Signed-off-by: Andrew Carbonetto <andrew.carbonetto@improving.com>	2025-09-11 02:55:45 +05:30
Swarnaprakash Udayakumar	e3f0277cb9	feat(vector-store): Add Valkey vector store support (#3272 )	2025-09-10 04:01:53 +05:30
Prateek Chhikara	e64488b598	updates to the category docs (#3437 )	2025-09-09 11:47:09 -07:00
Parshva Daftari	f5e0fb9e4b	Added support for chromadb cloud (#3436 )	2025-09-09 22:22:09 +05:30
Ranjith kumar	77b4b6a2b9	fix: 🐛 replace hardcoded llm provider with provider from config (#3423 )	2025-09-05 22:38:04 +05:30
Josh Hayes	9477184582	databricks bug fixes (#3416 )	2025-09-05 16:22:09 +05:30
Gabe Goodhart	b27879bfd4	fix: Use ConfigDict instead of class-based Config (#3409 ) Signed-off-by: Gabe Goodhart <ghart@us.ibm.com>	2025-09-04 20:18:25 +05:30
Saket Aryan	f0e8c3f760	feat: Add metadata param to TS-SDK in client.update (#3415 )	2025-09-04 03:22:12 +05:30
Parshva Daftari	5e8d5e4664	Release 0.1.117 (#3411 )	2025-09-03 23:09:00 +05:30
Shili Cao	c8d864c1b6	fix: add missing provider for baidu vector db (#3405 )	2025-09-03 15:24:33 +05:30
Prateek Chhikara	617aabe5b3	[FIX] Graph Docs page was missing on the side bar (#3402 )	2025-09-02 13:32:23 -07:00
Prateek Chhikara	163dafb216	Add version param in search v2 API documentation (#3401 )	2025-09-02 13:24:22 -07:00
Srishti Gureja	cc15a22bf9	support `store` for openai (#3399 )	2025-09-02 21:23:59 +05:30
Parshva Daftari	64cbe84089	Updated favicon logo (#3398 )	2025-09-02 21:10:04 +05:30
Parshva Daftari	c8f9f20dff	Updated integration docs (#3392 )	2025-09-02 04:26:43 +05:30
John Lockwood	97fd320bbf	Fix/new mem mistaken for current fixing #2875 (#2876 )	2025-09-01 19:46:01 +05:30
Saket Aryan	748620f29b	fix(Vercel AI SDK): Streaming not working properly (#3386 )	2025-08-30 21:58:30 +05:30
Srishti Gureja	0b2aa36e98	Bugfix: Pick AWS region from the environment variable correctly (#3384 )	2025-08-30 01:43:02 +05:30
Sheharyar Ahmad	3d0ece1bcf	Refactor PGVector to Use Internal Connection Pools and Context Managers (#3373 )	2025-08-29 19:06:39 +05:30
Rupam Jana	458d7ab8a3	replace query_vector args in search method of mongodb vector_stores (#3379 )	2025-08-29 19:05:25 +05:30
Tushar Chandra	84af5ad265	docs: fix typo in docs/platform/advanced-memory-operations.mdx (#3348 )	2025-08-27 17:35:45 -07:00
VikramIyer125	6237a6acb9	Adding weaviate, faiss, pgvector, chroma, redis, elasticsearch, milvus vector store to openmemory (#3366 ) Co-authored-by: Vikram Iyer <vikramiyer@mac.local.meter>	2025-08-27 01:47:39 +05:30
VikramIyer125	8c8368781d	Adding custom connection to weaviate connection client to enable client connection to local container (#3360 ) Co-authored-by: Vikram Iyer <vikramiyer@Vikrams-MacBook-Pro.local>	2025-08-25 23:54:02 +05:30
Padarn Wilson	3b2d0ad0eb	Fix missing commas in Kuzu graph INSERT queries (#3358 )	2025-08-24 12:33:51 +05:30
Andy Kwok	9337a873ec	Fix: Missing app_id on Neptune Analytics client (#3278 ) Signed-off-by: Andy Kwok <andy.kwok@improving.com>	2025-08-23 21:06:19 +05:30
Srishti Gureja	76411e2591	docs fix: remove `user_id` from `from_config` (#3320 )	2025-08-23 17:11:56 +05:30
Andy Kwok	d523070cbc	fix: Inconsistent `created` and `updated` properties on graph (#3220 ) Signed-off-by: Andy Kwok <andy.kwok@improving.com>	2025-08-23 16:51:13 +05:30
Enzo Biondo	c72bfc3285	Add Amazon S3 Vectors Support (#3237 )	2025-08-23 16:44:42 +05:30
Parshva Daftari	ee00bd5731	Fix typescript docs (#3357 )	2025-08-22 14:23:26 -07:00
VikramIyer125	f914dca659	Add export_openmemory.sh migration script (#3352 ) Co-authored-by: Vikram Iyer <vikramiyer@Vikrams-MacBook-Pro.local>	2025-08-22 20:19:41 +05:30
VikramIyer125	b64792590e	Add memory export / import feature (#3345 ) Co-authored-by: Vikram Iyer <vikramiyer@Vikrams-MacBook-Pro.local>	2025-08-21 23:27:28 +05:30
Parshva Daftari	a7ac8bf13b	Updated discord and dashboard image (#3344 )	2025-08-20 14:11:26 -07:00
David A. Torres	4487785cec	feature: add Azure Identity for Azure OpenAI and Azure AI Search authentication (#3262 )	2025-08-21 02:00:27 +05:30
NiLAy	e4c5582808	fix-migration-collection-override (#3100 ) Co-authored-by: parshvadaftari <daftariparshva@gmail.com>	2025-08-21 00:11:28 +05:30
Vương Hữu Hưng (Hans)	ff399e5528	Fix: Ollama checking model exists (#2682 )	2025-08-19 16:29:26 +05:30
Parshva Daftari	e7013764f7	Update aws bedrock (#3334 )	2025-08-19 02:20:34 +05:30
Parshva Daftari	c8ee17b884	Fix dependency and tests and updated docstring (#3337 )	2025-08-19 02:12:24 +05:30
AkisAya	346b913ace	feat: add es headers config (#3088 )	2025-08-19 01:15:23 +05:30
Parshva Daftari	49ad64708b	Updated databricks docs (#3336 )	2025-08-18 13:24:32 -05:00
Josh Hayes	3a1eff425b	feat(vector-store): Add Databricks Mosaic AI vector store support (#3325 )	2025-08-18 22:20:33 +05:30
Parshva Daftari	ebb411b11a	Refactor docs (#3335 )	2025-08-18 20:45:09 +05:30
Archie Sengupta	8e8f13a48e	feat(Vercel AI SDK): add a param in config called `host` (#2634 ) Co-authored-by: Saket Aryan <94069182+whysosaket@users.noreply.github.com>	2025-08-17 16:21:06 +05:30
Siddhartha Sahu	a6a3928091	Add support for graph memory using Kuzu (#2934 )	2025-08-16 02:22:31 +05:30
Ankush Malaker	a883b56aa8	AsyncMemory._add_to_vector_store bugfix when no facts found (#3313 )	2025-08-15 22:15:00 +05:30
Deshraj Yadav	246d9e8f69	Update llms.txt file (#3321 )	2025-08-14 14:51:03 -07:00
Deshraj Yadav	192db1844c	Update Docs (#3315 )	2025-08-13 21:37:15 -07:00