Mem0
Mem0 is a memory infrastructure layer that gives AI agents and applications persistent context across sessions. The platform automatically condenses chat history into compact memories that reduce tokens and latency while preserving the right context for retrieval. Mem0 offers both a managed cloud platform and a permissively licensed open source project, with multi-tenant organizations, projects, users, and webhooks. It integrates with most popular agent frameworks including LangChain, LangGraph, CrewAI, AutoGen, LlamaIndex, the OpenAI Agents SDK, and the Vercel AI SDK. Enterprise features cover SOC 2, HIPAA, BYOK, auditable logging, and observability for production agent deployments.
Solid contracts, transparent operations, and an easy start — typically complete on four or five facets with one clear soft spot.
API Evangelist profiles Mem0 the way a machine reads it — 37 machine-readable artifacts across 1 API, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Mem0 scores 56.4/100 (strong), with a separate agent-readiness read of 22/100 (agent aware). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-09-08 · rubric v0.20.0
Put this on your own site. The badge is drawn live from Mem0's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/mem0/"
title="Mem0 on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/mem0.svg"
alt="Mem0 Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/mem0/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/mem0/"
title="Mem0 on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/mem0/card.svg"
alt="Mem0 Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile Mem0
Each block below is one kind of artifact we hold for Mem0. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 15
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Mem0 Platform API
The Mem0 Platform API provides hosted memory services for AI agents, exposing endpoints for adding, searching, retrieving, updating, and deleting memories, plus entities, events...
Mem0 agents API
The agents API from Mem0 — 1 operation(s) for agents.
Mem0 apps API
The apps API from Mem0 — 1 operation(s) for apps.
Mem0 entities API
The entities API from Mem0 — 3 operation(s) for entities.
Mem0 events API
The events API from Mem0 — 2 operation(s) for events.
Mem0 exports API
The exports API from Mem0 — 2 operation(s) for exports.
Mem0 feedback API
The feedback API from Mem0 — 1 operation(s) for feedback.
Mem0 memories API
The memories API from Mem0 — 12 operation(s) for memories.
Mem0 organizations API
The organizations API from Mem0 — 3 operation(s) for organizations.
Mem0 Project API
The Project API from Mem0 — 1 operation(s) for project.
Mem0 projects API
The projects API from Mem0 — 3 operation(s) for projects.
Mem0 runs API
The runs API from Mem0 — 1 operation(s) for runs.
Mem0 stats API
The stats API from Mem0 — 1 operation(s) for stats.
Mem0 users API
The users API from Mem0 — 1 operation(s) for users.
Mem0 webhooks API
The webhooks API from Mem0 — 2 operation(s) for webhooks.
Scroll within the panel for all 15 ·
Open Collections 16
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
API Collection
OPEN COLLECTIONMem0 API Docs agents API
OPEN COLLECTIONMem0 API Docs agents apps API
OPEN COLLECTIONMem0 API Docs agents entities API
OPEN COLLECTIONMem0 API Docs agents events API
OPEN COLLECTIONMem0 API Docs agents exports API
OPEN COLLECTIONMem0 API Docs agents feedback API
OPEN COLLECTIONMem0 API Docs agents memories API
OPEN COLLECTIONMem0 API Docs agents organizations API
OPEN COLLECTIONMem0 API Docs agents Project API
OPEN COLLECTIONMem0 API Docs agents projects API
OPEN COLLECTIONMem0 API Docs agents runs API
OPEN COLLECTIONMem0 API Docs agents stats API
OPEN COLLECTIONMem0 API Docs agents users API
OPEN COLLECTIONMem0 API Docs agents webhooks API
OPEN COLLECTIONMem0 API Docs
OPEN COLLECTIONScroll within the panel for all 16 ·
Pricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the things the Kin Score reads for access clarity — renamed from commercial clarity in rubric 0.12, because a free statutory interface has access terms and no commercial ones.
Published pricing tiers and plan structures.
Mem0 Plans Pricing
PLANSRate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Mem0 Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Mem0 Finops
FINOPSSecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Mem0 — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 2
MCP servers, agent skills, and machine-readable catalogs
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Operate 3
Status, limits, changes, and where to get help
Commercial 4
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/mem0 · machine-readable index on apis.io
This is an independent, third-party profile of Mem0, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.