Connect Mem0 to your AI agent
Mem0 is an universal, self-improving memory layer for LLM applications.
We set up the connection using your own Mem0 account, with keys you control, and keep it running. Your agent picks it up and starts doing the work.
Actions
What your agent can do in Mem0
Each one is a real action the agent can take on its own, the same things a person clicking around Mem0 could do. Read-only by default; write actions are confirmed against your policy.
- Add member to project Adds an existing user to a project (identified by `project_id` within organization `org_id`), assigning a valid system role.
- Add new memory records Stores new memory records from a list of messages, optionally inferring structured content; requires association via `agent_id`, `user_id`, `app_id`, or `run_id`.
- Add organization member Adds a new member, who must be a registered user, to an organization, assigning them a specific role.
- Create a new agent Creates a new agent with a unique `agent_id` and an optional `name`; additional metadata may be assigned by the system.
- Create a new agent run Creates a new agent run in the mem0.ai system.
- Create a new application Creates a new application, allowing metadata to be passed in the request body (not an explicit field in this action's request model); ensure `app_id` is unique to avoid potential errors or unintended updates.
- Create a new organization entry Creates a new organization entry using the provided name and returns its details.
- Create a new user Creates a new user with the specified unique `user_id` and supports associating `metadata` (not part of the request schema fields).
- Create memory entry Lists/searches existing memory entries with filtering and pagination; critically, this action retrieves memories and does *not* create new ones, despite its name.
- Create project Creates a new project with a given name within an organization that must already exist.
- Create webhook Creates a new webhook for a specific project to receive real-time notifications. Use when you need to set up event-driven integrations that trigger on memory operations.
- Delete an organization Permanently deletes an existing organization identified by its unique ID.
- Delete memory by id Permanently deletes a specific memory by its unique ID; ensure the `memory_id` exists as this operation is irreversible.
- Delete entity by type and id Call to permanently and irreversibly hard-delete an existing entity (user, agent, app, or run) and all its associated data, using its type and ID.
- Delete memories Deletes all memories matching specified filter criteria. IMPORTANT: At least one filter (agent_id, user_id, app_id, or run_id) must be provided to prevent accidental deletion of all memories. Requires delete permissions…
- Delete memory batch with uuids Deletes a batch of up to 1000 existing memories, identified by their UUIDs, in a single API call.
- Delete project Permanently deletes a specific project and all its associated data from an organization; this action cannot be undone and requires the project to exist within the specified organization.
- Delete project member Removes an existing member, specified by email address, from a project, immediately revoking their project-specific access; the user is not removed from the organization.
- Delete webhook Deletes a webhook and stops receiving notifications for the specified webhook ID. Use this when you no longer need webhook notifications or want to remove a specific webhook configuration.
- Export data based on filters Creates a new memory export job with optional entity filters (user_id, agent_id, app_id, run_id). Returns export job ID and confirmation message. Requires org_id and project_id. Uses default schema for memory structure…
- List organizations Retrieves a summary list of organizations for administrative oversight; returns summary data (names, IDs), not exhaustive details, despite 'detailed' in the name.
- Fetch details of a specific organization Fetches comprehensive details for an organization using its `org_id`; the `org_id` must be valid and for an existing organization.
- Get list of entity filters Retrieves predefined filter definitions for entities (e.g., by type, creation/modification date); returns definitions only, not filtered entity data.
- Get entity by id Fetches detailed information for an existing entity (user, agent, app, or run) identified by its type and unique ID.
- Get event status by event ID Retrieves a single async event by ID to check its current status and results. Use this after operations that return event IDs (e.g., add_new_memory_records) to poll for completion before proceeding with dependent operat…
- Get memories by entity Tool to retrieve all memories associated with a specific entity (user, agent, app, or run). Use when you need to fetch memories for a known entity type and ID combination.
- Get memory export Retrieves the status and results of a memory export job by its ID. Use this after creating an export job to fetch the processed memory data. The response structure matches the schema defined during export creation.
- Get organization members Fetches a list of members for a specified, existing organization.
- Get project details Fetches comprehensive details for a specified project within an organization.
- Get project members Retrieves all members for a specified project within an organization.
- Get projects Retrieves all projects for a given organization `org_id` to which the caller has access.
- Get project webhooks Retrieves all webhooks configured for a specific project. Use this to list webhook configurations including their event types, URLs, and active status.
- Get user memory stats Retrieves a summary of the authenticated user's memory activity, including total memories created, search events, and add events. Note: This endpoint is undocumented in the official mem0 API specification but is functio…
- List entities Retrieves a list of entities, optionally filtered by organization or project (prefer `org_id`/`project_id` over deprecated `org_name`/`project_name`), noting results may be summaries and subject to limits.
- Perform semantic search on memories Searches memories semantically using a natural language query and metadata filters. IMPORTANT: - At least one of 'user_id', 'agent_id', or 'run_id' MUST be provided - A non-empty 'query' string is REQUIRED for semantic…
- Remove a member from the organization Removes a member, specified by their username, from an existing organization of which they are currently a member.
- Retrieve all events for the currently logged in user Retrieves a paginated list of events for the authenticated user, filterable and paginable via URL query parameters. This is a read-only operation that does not modify data. Supported Query Parameters (applied directly t…
- Retrieve list of memory events Retrieves a chronological list of all memory events (e.g., user inputs, AI responses) from the Mem0 platform, providing interaction history and context for AI assistants.
- Retrieve memory by id Retrieves a complete memory entry by its unique identifier; `memory_id` must be valid and for an existing memory.
- Retrieve memory history by id Retrieves the complete version history for an existing memory, using its unique `memory_id`, to inspect its evolution or audit changes.
- Retrieve memory list Retrieves a list of memories, supporting pagination and diverse filtering (e.g., by IDs, metadata, keywords, date ranges); ensure dates are ISO 8601 and `page`/`page_size` (if used) are positive integers. REQUIRED: At l…
- Search memories with filters Semantically searches memories using structured filters with an optional natural language query. If query is omitted, defaults to '*' (wildcard) for filter-only searches. Offers options to rerank results, select specifi…
- Update memory batch with uuid Updates text for up to 1000 memories in a single batch, using their UUIDs.
- Update memory text content Updates the text content of an existing memory, identified by its `memory_id`.
- Update organization member role Updates the role of an existing member to a new valid role within an existing organization.
- Update project Updates a project by `project_id` within an `org_id`, modifying only provided fields (name, description, custom_instructions, custom_categories); list fields are fully replaced (cleared by `[]`), other omitted/null fiel…
- Update project member role Updates the role of a specific member within a designated project, ensuring the new role is valid and recognized by the system.
Setup
How we connect it
- 1
Connect your account
You create a key in Mem0, a key you create and control, and paste it in once. It lives in a secrets store on your server, not with us.
- 2
Set the guardrails
Read-only by default. You choose which write actions the agent may take, and anything outside that policy gets confirmed with you first.
- 3
We keep it running
Health checks on every connection, updates handled for you, and we watch the first week of activity to make sure the work lands.
FAQ
Mem0 questions, answered.
With a key you create and control. You paste it in once, it is stored in a secrets store on your server, permissions are scoped to the minimum the agent needs, and you can revoke it at any time.
The actions Mem0's API allows, the same things a person clicking around the app could do. Connections start read-only by default; write actions are confirmed against the policy you set before the agent takes them.
Connections are priced per tool on top of the base plan. Some are included, some are premium. See pricing for how connection charges work.
Standard tools are ready inside 7 business days of the setup call. We test the connection end to end, walk you through how the agent uses it, and watch the first week of activity.
Ready to put Mem0 to work?
Tell us what your team runs on. We set up the connection, secure it, and your agent takes it from there.
All product names, logos, and brands are property of their respective owners; used for identification only. ZeroToClaw is not affiliated with or endorsed by Mem0.