Mem0 for AI agents

Agents read Mem0 at once. Changes and sends are held for a person's approval by default.

About Mem0

Mem0 is an universal, self-improving memory layer for LLM applications.

What an agent can do in Mem0

Every Mem0 action is classed by the platform as a read, a change or a send. Reads run at once. Changes and sends are held for a person by default.

Runs at once (reads)

Looks things up in Mem0 without asking first. 22 actions.

  • Get event status by event IDRetrieves 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 wi
  • Get memories by entityTool 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.
  • Perform semantic search on memoriesSearches 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 REQ
  • Retrieve memory by idRetrieves a complete memory entry by its unique identifier; `memory_id` must be valid and for an existing memory.
  • Search memories with filtersSemantically 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 resu
  • Export data based on filtersCreates 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 fo
  • List organizationsRetrieves 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 organizationFetches comprehensive details for an organization using its `org_id`; the `org_id` must be valid and for an existing organization.
  • Get list of entity filtersRetrieves predefined filter definitions for entities (e.g., by type, creation/modification date); returns definitions only, not filtered entity data.
  • Get entity by idFetches detailed information for an existing entity (user, agent, app, or run) identified by its type and unique ID.
  • Get memory exportRetrieves 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 ex
  • Get organization membersFetches a list of members for a specified, existing organization.
Show all 22
  • Get project detailsFetches comprehensive details for a specified project within an organization.
  • Get project membersRetrieves all members for a specified project within an organization.
  • Get projectsRetrieves all projects for a given organization `org_id` to which the caller has access.
  • Get project webhooksRetrieves all webhooks configured for a specific project. Use this to list webhook configurations including their event types, URLs, and active status.
  • Get user memory statsRetrieves 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 specifica
  • List entitiesRetrieves 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 li
  • Retrieve all events for the currently logged in userRetrieves 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
  • Retrieve list of memory eventsRetrieves 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 history by idRetrieves the complete version history for an existing memory, using its unique `memory_id`, to inspect its evolution or audit changes.
  • Retrieve memory listRetrieves 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 integ

Held for approval by default (changes and sends)

Held for a person's approval by default. The approval is recorded and the action is sent once, never twice, with 10 seconds to undo. 25 actions.

  • Add new memory recordsStores 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 memberAdds a new member, who must be a registered user, to an organization, assigning them a specific role.
  • Create a new organization entryCreates a new organization entry using the provided name and returns its details.
  • Create projectCreates a new project with a given name within an organization that must already exist.
  • Delete memoriesDeletes 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
  • Add member to projectAdds an existing user to a project (identified by `project_id` within organization `org_id`), assigning a valid system role.
  • Create a new agentCreates a new agent with a unique `agent_id` and an optional `name`; additional metadata may be assigned by the system.
  • Create a new agent runCreates a new agent run in the mem0.ai system.
  • Create a new applicationCreates 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
  • Create a new userCreates a new user with the specified unique `user_id` and supports associating `metadata` (not part of the request schema fields).
  • Create memory entryLists/searches existing memory entries with filtering and pagination; critically, this action retrieves memories and does *not* create new ones, despite its name.
  • Create webhookCreates 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.
Show all 25
  • Delete an organizationPermanently deletes an existing organization identified by its unique ID.
  • Delete memory by idPermanently deletes a specific memory by its unique ID; ensure the `memory_id` exists as this operation is irreversible.
  • Delete entity by type and idCall 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 memory batch with uuidsDeletes a batch of up to 1000 existing memories, identified by their UUIDs, in a single API call.
  • Delete projectPermanently 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 memberRemoves 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 webhookDeletes 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.
  • Remove a member from the organizationRemoves a member, specified by their username, from an existing organization of which they are currently a member.
  • Update memory batch with uuidUpdates text for up to 1000 memories in a single batch, using their UUIDs.
  • Update memory text contentUpdates the text content of an existing memory, identified by its `memory_id`.
  • Update organization member roleUpdates the role of an existing member to a new valid role within an existing organization.
  • Update projectUpdates 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 `[]`), othe
  • Update project member roleUpdates the role of a specific member within a designated project, ensuring the new role is valid and recognized by the system.

Changes wait in Needs you

Changes and sends in Mem0 are held for a person's approval by default. The approval is recorded, and the action is sent once, never twice, with 10 seconds to undo.

How approvals work

Mem0 questions

Can an agent change data in Mem0 on its own?

Not by default. Changes and sends in Mem0 are held for a person's approval. The approval is recorded, and the action is sent once, never twice, with 10 seconds to undo.

What can an agent read in Mem0?

This connector lists 22 read actions. Reads run at once, without waiting for approval.

How does Mem0 connect?

It connects with API key. Connectors are built and maintained by third-party developers; availability is confirmed during scoping.

Bring Mem0 to your agents.