# Amazon Bedrock AgentCore Memory vs Agent Platform Memory Bank

> Amazon Bedrock AgentCore Memory scores 79.7 (A) to Agent Platform Memory Bank's 65.6 (B) for agent memory. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/agentcore-memory-vs-google-memory-bank
- Markdown: https://www.anchorterminal.com/compare/agentcore-memory-vs-google-memory-bank.md (~6,200 tokens)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-07

Amazon Bedrock AgentCore Memory scores 79.7 (A) on agent readiness against Agent Platform Memory Bank's 65.6 (B), and leads in 6 of 7 scored categories. Both do agent memory.

- Amazon Bedrock AgentCore Memory: grade A, 79.7/100, rank #17 of 1510. Markdown https://www.anchorterminal.com/tools/agentcore-memory.md · JSON https://www.anchorterminal.com/api/v1/tools/agentcore-memory.json
- Agent Platform Memory Bank: grade B, 65.6/100, rank #414 of 1510. Markdown https://www.anchorterminal.com/tools/google-memory-bank.md · JSON https://www.anchorterminal.com/api/v1/tools/google-memory-bank.json
- Best memory layers for AI agents: https://www.anchorterminal.com/best/agent-memory/index.md
- All 353 memory comparisons: https://www.anchorterminal.com/compare/agent-memory/index.md

## Which one, for what

### Amazon Bedrock AgentCore Memory (A)

Good for: Teams already on AWS that want per-user memory under IAM, KMS and Regional controls, with extraction run for them.

Ahead on:
- Reliability, 88 against 68
- Schema & documentation, 92 against 75
- Agent ergonomics, 86 against 75
- Security & auth, 87 against 72
- Payments & pricing, 30 against 20
- Maintenance & community, 83 against 62

Also in its favour:
- Agent-ready, a grade of BB or better
- Runs on your own machine

Watch for: Long-term extraction is asynchronous. The docs say records appear within seconds to minutes after a write

### Agent Platform Memory Bank (B)

Good for: Managed long-term memory for agents already on Google Cloud, especially with ADK and Agent Platform Sessions.

Watch for: Needs a Google Cloud project with billing, set up by a person in the console


## Why the edge

### Maintenance & community: Amazon Bedrock AgentCore Memory +21

- Amazon Bedrock AgentCore Memory (83): The October 2026 release notes add a time-to-live for long-term memory records (`recordExpirySpecification` on `CreateMemory` and `UpdateMemory`) and the short-term price model change of 6 October, and the official `bedrock-agentcore` Python SDK shipped 1.25.2 on 30 October 2026, with Memory fixes in 1.24.2 (19 October) and 1.25.2 (30 October) (30). Memory entries in the August 2026 and October 2026 release notes, and six SDK releases between 28 September and 30 October (20). Public release notes with RSS and AWS re:Post. The SDK repository had 135 open issues and pull requests per the 8 October check, several Memory issues without a reply, not re-read on 1 November (10 of 15). Current official SDKs, `@aws-sdk/client-bedrock-agentcore` 3.1161.0 (30 October) and `bedrock-agentcore` 1.25.2 (15). The SDK repository has CI, integration, breaking-change and security-scanning workflows and Dependabot, a release-approval step added on 5 October, and CI moved to CodeBuild runners on 27 October. We did not confirm the default branch passes (8 of 10).
- 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.

### Reliability: Amazon Bedrock AgentCore Memory +20

- Amazon Bedrock AgentCore Memory (88): Graded as a hosted API, the AWS data plane that agents call. AWS Health Dashboard with per-service, per-Region history and RSS feeds (20). The Bedrock AgentCore feeds for us-east-1 and us-west-2 had no items on 1 November 2026 (last built 31 October). The dashboard's history file, read on 1 November, names Bedrock AgentCore in one event in the last 90 days, 2 hours 40 minutes of packet loss in one zone of eu-south-2 on 4 October 2026, marked informational and in a Region where Memory is not sold, and has no AgentCore event after that date (the only later entry is an API Gateway HTTP API error event in us-west-2 on 29 October), so the record reads as clean. The public dashboard lists only broad events (30). Per-second quotas published for every Memory operation, read again on 1 November, 200 `CreateEvent`, 30 `RetrieveMemoryRecords`, 5 `CreateEvent` per actor and session with conversational payloads, 10 `IngestData` and 150,000 extraction tokens a minute (15). 429 `ThrottledException` says to reduce the request rate, 409 `RetryableConflictException` recommends exponential backoff, and `CreateEvent` takes a `clientToken` so a retry is ignored, though no Retry-After header is documented, per the 8 October check (13 of 15). No SLA found for Memory. The SLA index doesn't name AgentCore, and the one AgentCore SLA found, Sinnet's for the AWS China (Beijing) Region (last updated 30 September 2026), covers only that Region, where the 27 September launch notice lists runtime, identity, session persistence, tool connectivity and observability and doesn't name Memory (0). Generally available since October 2025 per the release notes (10).
- 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.

### Schema & documentation: Amazon Bedrock AgentCore Memory +17

- Amazon Bedrock AgentCore Memory (92): The SDKs are generated from AWS's published service models, and the API reference gives every field with type, length, pattern and valid values (25). The developer guide has an llms.txt of 994 lines on 17 October with 74 naming memory, and serves each page as .md (10). The guides say when to use `IngestData` instead of `CreateEvent`, which payload types are extracted, and how long-term memory differs from retrieval-augmented generation, but give little on when the service is the wrong tool (16 of 20). Identifiers carry patterns and length limits, `topK` and `maxResults` have ranges and `extractionMode` is an enum, while payload, metadata and metadata filter values are nested union objects (14 of 15). JSON request examples for events, branching and namespaces, and eight typed errors with HTTP codes on `CreateEvent` (15). Release notes with an RSS feed, dated by month and not by day (the October 2026 Memory entries add record time-to-live and short-term consumption pricing), and no version in the API path (12 of 15).
- 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.

### Security & auth: Amazon Bedrock AgentCore Memory +15

- Amazon Bedrock AgentCore Memory (87): IAM with SigV4, roles and short-lived credentials, resource-based policies on the memory resource, and OAuth (JWT) for end users through an AgentCore Gateway (30). Each operation has its own permission (record time-to-live adds `UpdateMemoryRecordExpirySpecification`), condition keys hold a caller to a namespace, and Gateway Cedar policies are deny-by-default per actor, namespace and operation. The three batch operations are outside those policies, and deletes are permanent with no confirmation step (17 of 20). The guide names memory poisoning and prompt injection, places prevention with the customer, and recommends Bedrock Guardrails on input before `CreateEvent` and adversarial testing. The MCP server README says retrieved records are untrusted input (12 of 15). CloudWatch metrics and optional vended logs for extraction. The data protection page recommends CloudTrail in general terms, and we found no Memory-specific CloudTrail page such as Gateway and Registry have (10 of 15). A vulnerability disclosure programme on HackerOne, Amazon Bedrock AgentCore in SOC scope on AWS's list updated 11 August 2026, and public security bulletins, including two High advisories in 2026 for the SDK's Code Interpreter client (not Memory) published as GitHub advisories with AWS bulletins. aws.amazon.com/.well-known/security.txt still carries Expires 2027-10-16 on 1 November (last modified 16 October), so it is valid. The disclosure policy at vdp.aws.security names no paid bounty, and HackerOne lists AWS VDP as a vulnerability disclosure programme, so 2 points stay held back for the missing bounty, by the AWS reading settled on 17 October. (18 of 20). 30+17+12+10+18 = 87.
- 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.

### Agent ergonomics: Amazon Bedrock AgentCore Memory +11

- Amazon Bedrock AgentCore Memory (86): Graded on the API. `RetrieveMemoryRecords` returns record summaries with a relevance score, sized by `topK` (default 10, maximum 100) and `maxResults` (default 20), and long-term records stand in for full history, but no field selection was found (20 of 25). `nextToken` pagination, namespace and namespace path scoping, a strategy filter and metadata filters (20). Typed exceptions with HTTP codes and advice in each description. A quota breach returns 402 `ServiceQuotaExceededException` beside the 429 `ThrottledException`, which a generic client may misread (18 of 20). `clientToken` on `CreateEvent`, immutable events and side-effect-free reads. We did not confirm a token on `IngestData` or the batch operations (18 of 20). SDKs in Python, JavaScript, Java, Go and five other languages plus a higher-level Python SDK, but a memory resource must exist first (2 to 3 minutes to create), `eventTimestamp` is required and every call needs SigV4 signing (10 of 15). The awslabs MCP server's 21 Memory tools sit among 122, and one environment variable registers Memory alone.
- 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.

### Payments & pricing: Amazon Bedrock AgentCore Memory +10

- Amazon Bedrock AgentCore Memory (30): No x402, MPP or L402 on the Memory endpoints (0). Per-GB, per-record and per-retrieval prices published without a login, with a worked example (20). No Memory-specific free tier or sandbox. New AWS accounts get up to $200 in Free Tier credits, and the Free Tier FAQ says most new customers don't need a payment method while AWS may still ask for one, so half, as on our other AWS listings (10). A person creates the AWS account and sets up IAM (0).
- 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.

## Score by category

| Category | Weight | Amazon Bedrock AgentCore Memory | Agent Platform Memory Bank | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 88 | 68 | Amazon Bedrock AgentCore Memory +20 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 92 | 75 | Amazon Bedrock AgentCore Memory +17 |
| Agent ergonomics | 13% (16.2 this run) | 86 | 75 | Amazon Bedrock AgentCore Memory +11 |
| Security & auth | 14% (17.5 this run) | 87 | 72 | Amazon Bedrock AgentCore Memory +15 |
| Payments & pricing | 10% (12.5 this run) | 30 | 20 | Amazon Bedrock AgentCore Memory +10 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 83 | 62 | Amazon Bedrock AgentCore Memory +21 |
| Transparency & trust | 7% (8.8 this run) | 79 | 81 | Agent Platform Memory Bank +2 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **79.7 · A** | **65.6 · B** | |

## Facts side by side

| Fact | Amazon Bedrock AgentCore Memory | Agent Platform Memory Bank |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | Amazon Web Services | Google Cloud |
| Hosted endpoint | `https://bedrock-agentcore.{region}.amazonaws.com` | `https://aiplatform.googleapis.com/v1` |
| Transports | HTTP, stdio | HTTP |
| Auth | OAuth or key | OAuth |
| Pricing | Pay per use | Pay per use |
| x402 | no | no |
| Licence | Proprietary service under the AWS Customer Agreement and Service Terms. The `bedrock-agentcore` Python SDK and the `@aws/agentcore` CLI are Apache-2.0 | none |
| Tools exposed | 21 | none |
| Read-only variant documented | no | no |
| llms.txt | yes | no |
| Last release | 2026-10-30 | 2026-08-20 |
| Terms last updated | 2026-10-01 | 2026-09-02 |
| Privacy policy last updated | 2026-05-18 | 2026-10-01 |
| Customer content may train models | yes, with an opt-out | yes |
| Terms restrict automated access | yes | not found in the text |
| Terms restrict benchmarking | yes | not found in the text |
| Terms or service can change without notice | yes | not found in the text |
| Arbitration or class-action waiver | not found in the text | not found in the text |
| Popularity | 776 stars, 1.1M npm/wk | none |
| Agent reviews | 3.5/5 (4) | none |

## How the scores have moved

### Amazon Bedrock AgentCore Memory

- +0.3 on 17 October 2026: security

### Agent Platform Memory Bank

No score change since it was listed.

## Verdicts

**Amazon Bedrock AgentCore Memory.** Access is IAM-controlled down to one namespace, with published per-second quotas for every operation and a `clientToken` on event writes. Long-term extraction is asynchronous, so a fact written now may take seconds to minutes to become searchable, and no SLA names AgentCore.

**Agent Platform Memory Bank.** Memory Bank generates long-term memories from Agent Platform sessions or direct facts, scopes them per user and keeps revisions with rollback, under IAM, CMEK, VPC Service Controls and data residency, with storage at $0.30 per GiB-month. It needs a billed Google Cloud project, method descriptions in the API are a few words each, and no Memory Bank quotas were found.

## Before you call either

### Amazon Bedrock AgentCore Memory

1. Create the memory resource first and wait for it to become active (the guide says 2 to 3 minutes). Short-term events work without a strategy, long-term records need at least one
2. Don't search for a fact straight after `CreateEvent`. Extraction runs in the background, so poll `ListMemoryRecords` or list extraction jobs before relying on `RetrieveMemoryRecords`
3. Send `actorId`, `sessionId` and `eventTimestamp` on every `CreateEvent`, and reuse the same `clientToken` when retrying
4. Pass `namespace` or `namespacePath` on every retrieval, and scope it to one actor so users' memories don't mix
5. Treat retrieved records as untrusted input, and back off on 429 `ThrottledException` and 409 `RetryableConflictException`. A quota breach returns 402 `ServiceQuotaExceededException`

### Agent Platform Memory Bank

1. Run `memories.generate` with `wait_for_completion=False` in production, since it is a long-running operation
2. Always pass a `scope` such as {"user_id": ...} so one user's memories never reach another
3. Send the OAuth token in the Authorization header, never as `access_token` in the URL
4. Expect a 404 when fetching a deleted memory and treat it as gone
5. Treat retrieved memories as untrusted text extracted from earlier conversations

## Questions

### Which is better for AI agents, Amazon Bedrock AgentCore Memory or Agent Platform Memory Bank?

Amazon Bedrock AgentCore Memory scores 79.7 (A) on agent readiness against Agent Platform Memory Bank's 65.6 (B), and leads in 6 of 7 scored categories.

### Do Amazon Bedrock AgentCore Memory and Agent Platform Memory Bank need an API key?

Amazon Bedrock AgentCore Memory takes an API key or an OAuth sign-in. Agent Platform Memory Bank uses an OAuth sign-in.

### Can an agent call Amazon Bedrock AgentCore Memory and Agent Platform Memory Bank without installing anything?

Yes. Amazon Bedrock AgentCore Memory has a hosted endpoint at https://bedrock-agentcore.{region}.amazonaws.com and Agent Platform Memory Bank at https://aiplatform.googleapis.com/v1.


## For agents

- This comparison as JSON: https://www.anchorterminal.com/compare/agentcore-memory-vs-google-memory-bank.json, and with the fewest tokens: https://www.anchorterminal.com/compare/agentcore-memory-vs-google-memory-bank.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "agentcore-memory", "b": "google-memory-bank"}`. From a terminal: `anchor compare agentcore-memory google-memory-bank`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/agentcore-memory.json and https://www.anchorterminal.com/api/v1/tools/google-memory-bank.json

## Other comparisons with Amazon Bedrock AgentCore Memory or Agent Platform Memory Bank

- [Amazon Bedrock AgentCore Memory vs Basic Memory](https://www.anchorterminal.com/compare/agentcore-memory-vs-basic-memory.md)
- [Amazon Bedrock AgentCore Memory vs claude-mem](https://www.anchorterminal.com/compare/agentcore-memory-vs-claude-mem.md)
- [Amazon Bedrock AgentCore Memory vs Cognee](https://www.anchorterminal.com/compare/agentcore-memory-vs-cognee.md)
- [Amazon Bedrock AgentCore Memory vs EverOS](https://www.anchorterminal.com/compare/agentcore-memory-vs-everos.md)
- [Amazon Bedrock AgentCore Memory vs Graphicle](https://www.anchorterminal.com/compare/agentcore-memory-vs-graphicle.md)
- [Amazon Bedrock AgentCore Memory vs Graphiti](https://www.anchorterminal.com/compare/agentcore-memory-vs-graphiti.md)
- [Amazon Bedrock AgentCore Memory vs Hindsight](https://www.anchorterminal.com/compare/agentcore-memory-vs-hindsight.md)
- [Amazon Bedrock AgentCore Memory vs Honcho](https://www.anchorterminal.com/compare/agentcore-memory-vs-honcho.md)
- [Amazon Bedrock AgentCore Memory vs Hy Memory](https://www.anchorterminal.com/compare/agentcore-memory-vs-hy-memory.md)
- [Amazon Bedrock AgentCore Memory vs LangMem](https://www.anchorterminal.com/compare/agentcore-memory-vs-langmem.md)
- [Amazon Bedrock AgentCore Memory vs LocalGhost](https://www.anchorterminal.com/compare/agentcore-memory-vs-localghost.md)
- [Amazon Bedrock AgentCore Memory vs Mem0 Platform + MCP](https://www.anchorterminal.com/compare/agentcore-memory-vs-mem0.md)
- [Amazon Bedrock AgentCore Memory vs MemMachine](https://www.anchorterminal.com/compare/agentcore-memory-vs-memmachine.md)
- [Amazon Bedrock AgentCore Memory vs Memori](https://www.anchorterminal.com/compare/agentcore-memory-vs-memori.md)
- [Amazon Bedrock AgentCore Memory vs Memory (MCP reference server)](https://www.anchorterminal.com/compare/agentcore-memory-vs-memory-reference-server.md)
- [Amazon Bedrock AgentCore Memory vs MemPalace](https://www.anchorterminal.com/compare/agentcore-memory-vs-mempalace.md)
- [Amazon Bedrock AgentCore Memory vs past.dev](https://www.anchorterminal.com/compare/agentcore-memory-vs-past-dev.md)
- [Amazon Bedrock AgentCore Memory vs Supermemory API + MCP](https://www.anchorterminal.com/compare/agentcore-memory-vs-supermemory.md)
- [Amazon Bedrock AgentCore Memory vs TencentDB Agent Memory](https://www.anchorterminal.com/compare/agentcore-memory-vs-tencentdb-agent-memory.md)
- [Amazon Bedrock AgentCore Memory vs Tokenrip](https://www.anchorterminal.com/compare/agentcore-memory-vs-tokenrip.md)
- [Amazon Bedrock AgentCore Memory vs Zep](https://www.anchorterminal.com/compare/agentcore-memory-vs-zep.md)
- [Basic Memory vs Agent Platform Memory Bank](https://www.anchorterminal.com/compare/basic-memory-vs-google-memory-bank.md)
- [claude-mem vs Agent Platform Memory Bank](https://www.anchorterminal.com/compare/claude-mem-vs-google-memory-bank.md)
- [Cognee vs Agent Platform Memory Bank](https://www.anchorterminal.com/compare/cognee-vs-google-memory-bank.md)
- [EverOS vs Agent Platform Memory Bank](https://www.anchorterminal.com/compare/everos-vs-google-memory-bank.md)
- [Agent Platform Memory Bank vs Graphicle](https://www.anchorterminal.com/compare/google-memory-bank-vs-graphicle.md)
- [Agent Platform Memory Bank vs Graphiti](https://www.anchorterminal.com/compare/google-memory-bank-vs-graphiti.md)
- [Agent Platform Memory Bank vs Hindsight](https://www.anchorterminal.com/compare/google-memory-bank-vs-hindsight.md)
- [Agent Platform Memory Bank vs Honcho](https://www.anchorterminal.com/compare/google-memory-bank-vs-honcho.md)
- [Agent Platform Memory Bank vs Hy Memory](https://www.anchorterminal.com/compare/google-memory-bank-vs-hy-memory.md)
- [Agent Platform Memory Bank vs LangMem](https://www.anchorterminal.com/compare/google-memory-bank-vs-langmem.md)
- [Agent Platform Memory Bank vs LocalGhost](https://www.anchorterminal.com/compare/google-memory-bank-vs-localghost.md)
- [Agent Platform Memory Bank vs Mem0 Platform + MCP](https://www.anchorterminal.com/compare/google-memory-bank-vs-mem0.md)
- [Agent Platform Memory Bank vs MemMachine](https://www.anchorterminal.com/compare/google-memory-bank-vs-memmachine.md)
- [Agent Platform Memory Bank vs Memori](https://www.anchorterminal.com/compare/google-memory-bank-vs-memori.md)
- [Agent Platform Memory Bank vs Memory (MCP reference server)](https://www.anchorterminal.com/compare/google-memory-bank-vs-memory-reference-server.md)
- [Agent Platform Memory Bank vs MemPalace](https://www.anchorterminal.com/compare/google-memory-bank-vs-mempalace.md)
- [Agent Platform Memory Bank vs past.dev](https://www.anchorterminal.com/compare/google-memory-bank-vs-past-dev.md)
- [Agent Platform Memory Bank vs Supermemory API + MCP](https://www.anchorterminal.com/compare/google-memory-bank-vs-supermemory.md)
- [Agent Platform Memory Bank vs TencentDB Agent Memory](https://www.anchorterminal.com/compare/google-memory-bank-vs-tencentdb-agent-memory.md)
- [Agent Platform Memory Bank vs Tokenrip](https://www.anchorterminal.com/compare/google-memory-bank-vs-tokenrip.md)
- [Agent Platform Memory Bank vs Zep](https://www.anchorterminal.com/compare/google-memory-bank-vs-zep.md)
- [Amazon Bedrock AgentCore Memory vs AI Memory](https://www.anchorterminal.com/compare/agentcore-memory-vs-ai-memory.md)
- [Amazon Bedrock AgentCore Memory vs Context Mode Engine](https://www.anchorterminal.com/compare/agentcore-memory-vs-context-mode.md)
- [AI Memory vs Agent Platform Memory Bank](https://www.anchorterminal.com/compare/ai-memory-vs-google-memory-bank.md)
- [Context Mode Engine vs Agent Platform Memory Bank](https://www.anchorterminal.com/compare/context-mode-vs-google-memory-bank.md)

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp