# Agent Platform Memory Bank vs Mem0 Platform + MCP (slim)

> Agent Platform Memory Bank scores 65.6 (B) to Mem0 Platform's 40.1 (E) for agent memory. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/google-memory-bank-vs-mem0.md (~5,400 tokens) · this version ~2,780 tokens · JSON https://www.anchorterminal.com/compare/google-memory-bank-vs-mem0.json · canonical https://www.anchorterminal.com/compare/google-memory-bank-vs-mem0
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-07
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Agent Platform Memory Bank scores 65.6 (B) on agent readiness against Mem0 Platform + MCP's 40.1 (E), and leads in 4 of 7 scored categories. Mem0 Platform + MCP leads on schema & documentation, payments & pricing and maintenance & community. Both do agent memory.

- Agent Platform Memory Bank: B 65.6, rank #412 of 1486 · https://www.anchorterminal.com/tools/google-memory-bank.min.md
- Mem0 Platform + MCP: E 40.1, rank #1310 of 1486 · https://www.anchorterminal.com/tools/mem0.min.md
- Agent Platform Memory Bank, good for Managed long-term memory for agents already on Google Cloud, especially with ADK and Agent Platform Sessions. Ahead on Reliability, 68 against 25; Agent ergonomics, 75 against 63; Security & auth, 72 against 45; Transparency & trust, 81 against 62. Also No incidents deducted, where Mem0 Platform + MCP loses 13 points for them.
- Mem0 Platform + MCP, good for Chat products that want per-user facts back with one search call and little setup, and teams willing to connect their own LLM key for higher free limits. Ahead on Schema & documentation, 80 against 75; Payments & pricing, 40 against 20; Maintenance & community, 75 against 62. Also Free to start without a card; Open source.

| Category | Agent Platform Memory Bank | Mem0 Platform + MCP |
| --- | --- | --- |
| Reliability (16%) | 68 | 25 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 75 | 80 |
| Agent ergonomics (13%) | 75 | 63 |
| Security & auth (14%) | 72 | 45 |
| Payments & pricing (10%) | 20 | 40 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 62 | 75 |
| Transparency & trust (7%) | 81 | 62 |

| Fact (where they differ) | Agent Platform Memory Bank | Mem0 Platform + MCP |
| --- | --- | --- |
| Vendor | Google Cloud | Mem0 |
| Hosted endpoint | `https://aiplatform.googleapis.com/v1` | `https://api.mem0.ai` |
| Transports | HTTP | HTTP, Streamable HTTP |
| Auth | OAuth | API key |
| Pricing | Pay per use | Freemium |
| Licence | none | Apache-2.0 |
| Tools exposed | none | 11 |
| llms.txt | no | yes |
| MCP registry | not listed | `io.github.mem0ai/mem0` |
| Last release | 2026-08-20 | 2026-09-25 |
| Terms last updated | 2026-09-02 | no date given |
| Privacy policy last updated | 2026-10-01 | no date given |
| Terms restrict automated access | not found in the text | yes |
| Terms restrict benchmarking | not found in the text | yes |
| Arbitration or class-action waiver | not found in the text | yes |
| Popularity | none | 66k stars, 168k npm/wk, 502k PyPI/wk |
| Agent reviews | none | 2.5/5 (2) |

Why the edge:
- Reliability, Agent Platform Memory Bank +43: Agent Platform Memory Bank 68 (Hosted lines. Google Cloud status dashboard with per-product history (20). Its incident feed, read on 6 November 2026, holds four incidents since 8 August (20 August, 27 products; 1 September, us-central1-b; 8 October, Cloud Storage; 20 October, europe-west2, 38 products), and none names Agent Platform, Vertex or Memory Bank (30). No Memory Bank quotas or rate limits were found; the platform quotas path guessed returned 404 (0, unchecked). Generation is a long-running operation with wait and cancel methods, and Google's retry guidance wasn't re-read for this API (8 of 15). No SLA for Memory Bank was found in the pages read (0, unchecked). Memory profiles, IngestEvents and multi-regional endpoints are GA (10). Total 68.); Mem0 Platform + MCP 25 (A status page exists at status.mem0.ai. On 1 October it refused automated readers, so its components weren't seen (10 of 20, a partial value kept and flagged) and it had no readable history (5). Mem0's terms bar automated download from its service and documentation, so the page wasn't requested on 4 November. No Platform rate limits with numbers. The docs say only "Managed quotas per workspace" (0). The OpenAPI file in the repository documents 429 on one operation, a profile-job cooldown with `retry_after_seconds`, and no general retry guidance was found (0). The October pricing FAQ says an SLA comes only by talking to sales, and the platform comparison page says a support SLA "is not documented as a Platform benefit today" (0, from 5). The v3 API and the hosted MCP server are generally available (10). 10+5+0+0+0+10 = 25.)
- Security & auth, Agent Platform Memory Bank +27: Agent Platform Memory Bank 72 (OAuth 2.0 with IAM and service accounts (30), less 10, as for the other Google API listings, because the v1 discovery document lists `access_token`, `oauth_token` and `key` as query parameters (20 of 30). IAM Conditions can restrict access by memory scope; purge and delete have no confirmation (15 of 20). Memories are written by an LLM from conversation content and returned to agents, with no injection guidance found (5 of 15). Access Transparency and Access Approval are listed; Cloud Audit Logs coverage for Memory Bank wasn't read (12 of 15). Google's valid security.txt, vulnerability reward programme and certifications, with HIPAA listed for Memory Bank (20). Total 72.); Mem0 Platform + MCP 45 (Plain revocable API keys in an `Authorization: Token` header, and browser OAuth on the MCP server with no scopes documented (20 of 30). No read-only key or MCP mode, and delete_all_memories and delete_entities sit in the default MCP tool list. Bulk deletes need at least one filter (3 of 20). The tool returns stored memories that came from user text, and no prompt-injection guidance was found (0). An events API lists memory operations, and audit logs are an Enterprise item (10 of 15). SECURITY.md takes private reports by GitHub advisory or email with a 72-hour acknowledgement, and Mem0 published its first repository advisory (GHSA-5324-3w58-qpp2) on 28 October 2026. SOC 2 Type I claimed per the 1 October check, no security.txt and no bug bounty (12 of 20). 20+3+0+10+12 = 45.)
- Payments & pricing, Mem0 Platform + MCP +20: Agent Platform Memory Bank 20 (No x402, MPP or L402 (0). Storage, read and write prices are published without a login (20). No Memory Bank free tier found (0). A person creates the project, enables billing and sets up IAM in the console (0). Total 20.); Mem0 Platform + MCP 40 (No x402, MPP or L402 (0). Since 26 October 2026 the Starter, Growth and Pro plans are no longer sold to new accounts, per the pricing FAQ. Above the free limits a customer turns on usage-based billing, whose rate "is shown when you turn it on" in the dashboard, or talks to sales, so no per-unit price is published (0, from 10). The free plan needs no card. For the first 30 days Mem0 pays for the model calls (10,000 adds and 1,000 retrievals a month), then adds need the customer's own LLM key, with 50,000 adds and 10,000 retrievals a month (20). `mem0 init --agent` creates an unclaimed free account with no email, capped at 5 sign-ups a day per IP address (20). 0+0+20+20 = 40.)
- Transparency & trust, Agent Platform Memory Bank +19: Agent Platform Memory Bank 81 (Closed service under the Google Cloud terms (15). Data residency at rest, CMEK and the Cloud Data Processing Addendum apply; no Memory Bank retention period or time-to-live was read (20 of 30). The rename was announced in the release notes with old and new names listed, and Google's deprecation policy covers GA services (14 of 20). Google Cloud's subprocessor list and regional endpoints are published (16 of 20). Total 65.); Mem0 Platform + MCP 62 (The extraction library is Apache-2.0, but the Platform, the product listed here, is closed (20 of 30). Per the 1 October check (privacy policy of 22 August 2026, not re-read on 4 November), Free Plan interactions train Mem0's models and paid ones don't, memories are kept for the life of the account, and retention after closure is "a limited period" (18 of 30). Migration guides and changelogs that name removals, and the October pricing change gave existing free accounts until 25 November 2026 to connect a key. No written deprecation policy (10 of 20). The privacy policy names OpenAI and Anthropic as AI providers and US transfers. No full subprocessor list was found (8 of 20). The SDKs send usage telemetry to PostHog by default with a documented `MEM0_TELEMETRY` opt-out. The hosted client sends events under the account email, which the plugin pages disclose. No term. 20+18+10+8 = 56.)
- Maintenance & community, Mem0 Platform + MCP +13: Agent Platform Memory Bank 62 (The newest Memory Bank release notes are of 20 August 2026 (IngestEvents GA, metadata, Gemini Embedding 2), 78 days before the check, and billing started on 1 September (20). Three Memory Bank entries in the 90 days, all on 20 August (10 of 20). Public release notes and Cloud Customer Care (12 of 15). `google-cloud-agentplatform` 2.7.0 on 28 October 2026, twelve releases in 90 days per its PyPI release feed, plus ADK (15). SDK test status not checked (5 of 10). Total 62.); Mem0 Platform + MCP 75 (The newest releases are Python mem0ai 2.2.1 and npm mem0ai 3.3.1 of 25 September 2026 (tags v2.2.1 and ts-v3.3.1), 40 days ago, and no package, CLI or plugin tag is newer (20, from 30, cause time). In the 90 days from 6 August, Python v2.0.18 (12 August), v2.0.19 (24 August), v2.0.20 (2 September), v2.1.0 (18 September), v2.2.0 (24 September) and v2.2.1, with the matching TypeScript releases (20). Issues and pull requests weren't re-read (github.com refused). 15 of 25 per the 1 October check. Current Python and TypeScript SDKs, and the hosted MCP server is in the official registry as io.github.mem0ai/mem0 per the 1 October check (15). CI workflows run on pull requests, with run state unread (5 of 10). 20+20+15+15+5 = 75.)
- Agent ergonomics, Agent Platform Memory Bank +12: Agent Platform Memory Bank 75 (Retrieval takes a scope and similarity search with a result limit (20 of 25). List methods page with page tokens and filters (16 of 20). Google's standard error model with status codes (15 of 20). Revisions and rollback make a bad write recoverable, and generation can run in the background (14 of 20). Python SDK and ADK integration, with REST for other languages (10 of 15). Total 75.); Mem0 Platform + MCP 63 (The hosted MCP server has 11 tools, unchanged in the docs source (15), with no toolsets or read-only subset to add back. Pagination with page and page_size up to 200 and structured filters on list and search (20). Errors are thin. Few operations document 401, 403 or 429 and there's no error catalogue (8 of 20). No idempotency keys, and no readOnlyHint or destructiveHint documented on the MCP tools. Writes return an event ID that get_event_status can check (5 of 20). Python and TypeScript SDKs and a short required set (user_id plus messages) on add (15). 15+20+8+5+15 = 63.)