# AI Memory vs Agent Platform Memory Bank (slim)

> Agent Platform Memory Bank and AI Memory score within a point of each other for memory search, 65.6 and 65 out of 100. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/ai-memory-vs-google-memory-bank.md (~4,800 tokens) · this version ~2,280 tokens · JSON https://www.anchorterminal.com/compare/ai-memory-vs-google-memory-bank.json · canonical https://www.anchorterminal.com/compare/ai-memory-vs-google-memory-bank
- 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 and AI Memory score within a point of each other on agent readiness, 65.6 (B) and 65 (B). AI Memory leads on schema & documentation and payments & pricing. Both do memory search.

- AI Memory: B 65, rank #438 of 1486 · https://www.anchorterminal.com/tools/ai-memory.min.md
- Agent Platform Memory Bank: B 65.6, rank #412 of 1486 · https://www.anchorterminal.com/tools/google-memory-bank.min.md
- AI Memory, good for Developers running several coding agents on one project who want shared memory and task handoffs on their own machine or server. Ahead on Schema & documentation, 90 against 75; Payments & pricing, 60 against 20. Also Runs on your own machine.
- 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 Agent ergonomics, 75 against 60; Security & auth, 72 against 65; Maintenance & community, 62 against 50; Transparency & trust, 81 against 50. Also A hosted endpoint, with nothing to install.

| Category | AI Memory | Agent Platform Memory Bank |
| --- | --- | --- |
| Reliability (16%) | 65 | 68 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 90 | 75 |
| Agent ergonomics (13%) | 60 | 75 |
| Security & auth (14%) | 65 | 72 |
| Payments & pricing (10%) | 60 | 20 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 50 | 62 |
| Transparency & trust (7%) | 50 | 81 |

| Fact (where they differ) | AI Memory | Agent Platform Memory Bank |
| --- | --- | --- |
| Kind | MCP server | HTTP API |
| Vendor | Fabio Akita | Google Cloud |
| Hosted endpoint | no (local only) | `https://aiplatform.googleapis.com/v1` |
| Transports | stdio | HTTP |
| Auth | OAuth or key | OAuth |
| Pricing | Free | Pay per use |
| Licence | MIT | none |
| Tools exposed | 25 | none |
| Read-only variant documented | yes | no |
| Last release | 2026-11-03 | 2026-08-20 |
| Terms last updated | no date given | 2026-09-02 |
| Privacy policy last updated | no document linked | 2026-10-01 |
| Customer content may train models | not found in the text | yes |
| Popularity | 11k stars | none |
| Agent reviews | 3.5/5 (4) | none |

Why the edge:
- Payments & pricing, AI Memory +40: AI Memory 60 (Free self-hosted MIT software with nothing to buy (20 clear zero price, 20 free access, 20 no account). No machine payment protocol (0). Optional cloud embedding or LLM providers bill separately. 0+20+20+20 = 60.); 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.)
- Transparency & trust, Agent Platform Memory Bank +31: AI Memory 50 (MIT source (30). DATA_HANDLING.md and SECURITY.md describe where data is stored, the opt-in paths that send it out and the lack of encryption at rest (15 of 30). Dated 3.0.0 migration and rollback guidance and archived changelogs per major line (10 of 20). DATA_HANDLING.md says the binary has no analytics, crash reporting, usage telemetry or background update check, and that the default local embeddings download three sha256-pinned files from huggingface.co on first start, avoidable with `embedding_provider = "none"` (20, from 0). 30+15+10+20 = 75.); 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.)
- Schema & documentation, AI Memory +15: AI Memory 90 (25 MCP tools in crates/ai-memory-mcp/src/server.rs. Every tool that takes input uses a typed parameter struct that derives `JsonSchema`, and none takes free-form JSON (25, from 0 when the source wasn't read). Markdown guides in the repository, including `INSTALL_FOR_AGENTS.md` (10). Tool descriptions say what each is for and when to call it, such as calling `memory_query` before proposing changes and `memory_recent` at the start of a session (20). Typed inputs with documented fields (10 of 15). Setup and recovery examples (10 of 15). Releases and a dated changelog (15). 25+10+20+10+10+15 = 90.); 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.)
- Agent ergonomics, Agent Platform Memory Bank +15: AI Memory 60 (25 tools with long descriptions in one set, and no toolsets or read-only subset found (15). Search takes scope and filters, and recent pages take a count (20). Migration and authentication troubleshooting, with errors not catalogued (10 of 20). Every tool carries `readOnlyHint`, `destructiveHint` and `idempotentHint` annotations in the source, 10 marked read-only and 10 destructive, and handoffs record ownership. No idempotency keys on writes. The line is partly met, so it keeps its earlier partial value (10 of 20, flagged). Client bridge defaults and setup commands, with one language (5 of 15). 15+20+10+10+5 = 60.); 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.)
- Maintenance & community, Agent Platform Memory Bank +12: AI Memory 50 (v3.3.3 of 3 November 2026 (30). 68 tags from 6 August to 3 November, from v2.x through v3.3.3 (20). Issue and pull-request replies couldn't be read (github.com refused) (0). Not in the official MCP registry, and the repository has no server.json (0 of 15). Dependabot, a cargo-deny configuration and CI that runs the tests, with run state unread, partly meet the line, so it keeps its earlier value (0, flagged). 30+20+0+0+0 = 50.); 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.)
- Security & auth, Agent Platform Memory Bank +7: AI Memory 65 (A fresh `init` creates a root bearer token in an owner-only file, with multi-user API keys and OIDC as options. Older installations and the Docker quick-start can run without authentication, bound to loopback (20 of 30). Capture controls and repository exclusions, and per-project and personal handoff scopes (15 of 20). docs/security-boundaries.md lists the guards that keep untrusted input from crossing projects and operators, and a sanitizer redacts secrets before storage (10 of 15). Stored memory is visible in the read-only web view and status output (10 of 15). SECURITY.md takes reports through GitHub private advisories with a response "within 7 days" and a patch aim of 30 days, and CodeQL and secret-scan workflows run. No bug bounty or certification (10 of 20, from 0). 20+15+10+10+10 = 65.); 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.)