# Agent Platform Memory Bank vs Supermemory API + MCP (slim)

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

- Full: https://www.anchorterminal.com/compare/google-memory-bank-vs-supermemory.md (~5,500 tokens) · this version ~2,830 tokens · JSON https://www.anchorterminal.com/compare/google-memory-bank-vs-supermemory.json · canonical https://www.anchorterminal.com/compare/google-memory-bank-vs-supermemory
- 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 Supermemory API + MCP's 59.6 (C), and leads in 3 of 7 scored categories. Supermemory API + MCP leads on schema & documentation, payments & pricing and maintenance & community. Both do agent memory.

- Agent Platform Memory Bank: B 65.6, rank #414 of 1510 · https://www.anchorterminal.com/tools/google-memory-bank.min.md
- Supermemory API + MCP: C 59.6, rank #695 of 1510 · https://www.anchorterminal.com/tools/supermemory.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 55; Security & auth, 72 against 64; Transparency & trust, 81 against 52. Also No incidents deducted, where Supermemory API + MCP loses 5 points for them.
- Supermemory API + MCP, good for Apps that need user memory and document search over the same data, and for multi-tenant products that want a key per user. Ahead on Schema & documentation, 88 against 75; Payments & pricing, 30 against 20; Maintenance & community, 85 against 62. Also Open source.

| Category | Agent Platform Memory Bank | Supermemory API + MCP |
| --- | --- | --- |
| Reliability (16%) | 68 | 55 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 75 | 88 |
| Agent ergonomics (13%) | 75 | 76 |
| Security & auth (14%) | 72 | 64 |
| Payments & pricing (10%) | 20 | 30 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 62 | 85 |
| Transparency & trust (7%) | 81 | 52 |

| Fact (where they differ) | Agent Platform Memory Bank | Supermemory API + MCP |
| --- | --- | --- |
| Vendor | Google Cloud | Supermemory |
| Hosted endpoint | `https://aiplatform.googleapis.com/v1` | `https://api.supermemory.ai` |
| Transports | HTTP | HTTP, Streamable HTTP |
| Auth | OAuth | OAuth or key |
| Pricing | Pay per use | Freemium |
| Licence | none | MIT |
| Tools exposed | none | 17 |
| Read-only variant documented | no | yes |
| llms.txt | no | yes |
| Last release | 2026-08-20 | 2026-10-26 |
| Terms last updated | 2026-09-02 | 2025-06-02 |
| Privacy policy last updated | 2026-10-01 | 2026-09-29 |
| Customer content may train models | yes | not found in the text |
| Arbitration or class-action waiver | not found in the text | yes |
| Popularity | none | 31k stars, 121k npm/wk, 45k PyPI/wk |
| Agent reviews | none | 3.5/5 (2) |

Why the edge:
- Transparency & trust, Agent Platform Memory Bank +29: 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.); Supermemory API + MCP 52 (The SDKs, the hosted MCP and the tools in the public repository are MIT, but since 3 October the docs say the self-hosted server binary is built from a separate, non-public codebase and is free within a lite licence limit, so the hosted service and the engine are closed with clear terms. The 1 October reading of an MIT engine is corrected (15 of 30). The security page says customer content never trains models on any plan, and erasure works by deleting a namespace. The privacy policy (effective 29 September 2026, last updated 24 October) keeps data for the service relationship with no periods, and says disconnecting a connector won't delete synced data unless asked, while the security page says it deletes imported documents by default. The terms (2 June 2025) and privacy policy name no company (15 of 30). v3 and v4 became legacy with the dated v5 launch of 7 October and a migration command, with no shutdown date or deprecation policy (10 of 20). The privacy policy names Timescale, Cloudflare, OpenAI and Google Gemini as providers, with no full sub-processor list or data locations (5 of 20). 15 + 15 + 10 + 5 = 45.)
- Maintenance & community, Supermemory API + MCP +23: 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.); Supermemory API + MCP 85 (API v5 launched on 7 October 2026, python-sdk v5.0.1 is tagged 26 October and the TypeScript SDK's repository records 5.1.0 and 5.1.1 on 30 October and 1 November (30). Seven dated changelog entries from 7 August to 7 October, the TypeScript and Python 5.0 majors (6 October) and Python 3.57.0 to 3.62.0, well over three (20). The repository's issues and pull requests weren't readable (github.com answers 403 in this session), so the 1 October reading stands (12 of 25). Current TypeScript and Python SDKs (15). The hosted MCP isn't in the official registry. GitHub Actions workflows in the repo, with status unchecked (8 of 10). 30 + 20 + 12 + 15 + 8 = 85.)
- Reliability, Agent Platform Memory Bank +13: 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.); Supermemory API + MCP 55 (incident.io status page at status.supermemory.ai tracking the API and the Console, with incident pages and a feed (20). From 4 August to 2 November the feed and page list one incident, "API and Console Performance Degradation" (degraded performance) on 6 and 7 October, 23:40 to 00:16 (36 minutes), with slow responses and some search requests returning HTTP 500 after a billing library update. A short degradation reads as minor (20). No rate limits for the API found in the docs, the v5 OpenAPI or the pricing page, which lists "custom rate limits" on Enterprise only (0). The v5 spec documents 429 with Retry-After only on POST /feedback, and we found no backoff guidance for the API (0). Enterprise lists an "Uptime SLA" with no figure (5 of 10). v5 is described as the stable API (10). 20 + 20 + 0 + 0 + 5 + 10 = 55.)
- Schema & documentation, Supermemory API + MCP +13: Agent Platform Memory Bank 75 (Google's discovery document is a machine-readable contract for every memory method (25). No llms.txt or Markdown docs found (0). Method descriptions are 13 to 39 characters, one-line summaries, while the guides explain when to generate from sessions or from direct facts (12 of 20). Typed schemas with required fields in the discovery document (12 of 15). Python examples, a troubleshooting page and a documented 404 for deleted memories (11 of 15). v1 and v1beta1 and dated release notes (15). Total 75.); Supermemory API + MCP 88 (OpenAPI 3.1 for v5 at api.supermemory.ai/v5/openapi (33 operations, read on 2 November), with v4 and /openapi.json still served (25). llms.txt with a one-line purpose per page and endpoint (10). Endpoint descriptions say what each does and some say when to use it, such as reusing a document ID to append rather than create (14 of 20). Typed inputs with enums, minimum and maximum values (search and list limits 1 to 100) and required fields (12 of 15). Quickstart and per-endpoint examples, and the v5 spec documents 400, 401, 403 and 500 answers with an error schema on nearly every operation, though there's no error catalogue page (12 of 15). v3, v4 and v5 paths and a dated API changelog (15). 25 + 10 + 14 + 12 + 12 + 15 = 88.)
- Payments & pricing, Supermemory API + MCP +10: 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.); Supermemory API + MCP 30 (No x402, MPP or L402. An empty balance returns 402 with no payment payload (0). Per-unit prices without a login, re-read on 2 November, $5 per million SM tokens for plain-text memory, $10 for rich content, $5 per million searches, $100 per million operations (20). Free has $5 of credit renewed monthly, and the pricing page doesn't say whether a card is needed (10 of 20). A person signs up in the console, and the MCP signs in through a browser (0). 0 + 20 + 10 + 0 = 30.)
- Security & auth, Agent Platform Memory Bank +8: 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.); Supermemory API + MCP 64 (Org keys have full access, but scoped keys can be limited to one or more namespaces (container tags), set to expire in 1 to 365 days and revoked (401 after). The MCP signs in with OAuth and asks which spaces to allow, and since 21 August also takes an API key as Bearer (28 of 30). Scoped keys can't read billing, change settings or mint keys, MCP spaces carry read or write permission, and the mass forget has a dry run, but there's no read-only API key (14 of 20). Supermemory ingests URLs, PDFs and web pages and returns them to the model, and we found no prompt-injection guidance (0). The Analytics API gives usage per API key, error breakdowns and stored request logs, which the docs say skip 402, 404 and 500 answers and aren't a complete audit trail (10 of 15). SOC 2 Type II, GDPR and a HIPAA BAA per the security page, with the report on request from support. No security.txt (404 on 2 November), disclosure policy, SECURITY.md or bug bounty found (12 of 20). 28 + 14 + 0 + 10 + 12 = 64.)