{ "data": { "a": { "slug": "agentcore-memory", "name": "Amazon Bedrock AgentCore Memory", "vendor": "Amazon Web Services", "vendorUrl": "https://aws.amazon.com/bedrock/agentcore/", "kind": "http-api", "category": "agent-memory", "summary": "Managed memory service for AI agents on AWS. It stores conversation events as short-term memory and extracts facts, preferences, summaries and episodes into searchable long-term records, through the AWS API, SDKs and an MCP server.", "url": "https://www.anchorterminal.com/tools/agentcore-memory", "markdownUrl": "https://www.anchorterminal.com/tools/agentcore-memory.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/agentcore-memory.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/agentcore-memory.json", "dns": "agentcore-memory.grade.anchorterminal.com", "repo": "https://github.com/aws/bedrock-agentcore-sdk-python", "license": "Proprietary service under the AWS Customer Agreement and Service Terms. The `bedrock-agentcore` Python SDK and the `@aws/agentcore` CLI are Apache-2.0", "transports": [ "http", "stdio" ], "remoteUrl": "https://bedrock-agentcore.{region}.amazonaws.com", "packages": [ { "registry": "pypi", "name": "bedrock-agentcore" }, { "registry": "pypi", "name": "boto3" }, { "registry": "npm", "name": "@aws-sdk/client-bedrock-agentcore" }, { "registry": "npm", "name": "@aws/agentcore" }, { "registry": "pypi", "name": "awslabs.amazon-bedrock-agentcore-mcp-server" } ], "auth": "mixed", "authNotes": "AWS Signature Version 4 with IAM access keys or a role, and a policy that allows actions such as `bedrock-agentcore:CreateEvent` and `bedrock-agentcore:RetrieveMemoryRecords` on the memory resource. The data plane accepts SigV4 only. Resource-based policies and the condition keys `bedrock-agentcore:namespace` and `bedrock-agentcore:namespacePath` narrow access further. For end users, an AgentCore Gateway with the `agentcore-memory` connector accepts OAuth (JWT) tokens and applies Cedar policies. Access is self-serve once a person has created an AWS account.", "pricing": "usage", "pricingNotes": "Usage-priced with no minimum fee. Short-term memory, as of 6 October 2026, is $1.00 per GB ingested, $0.20 per GB retrieved and $0.10 per GB-month stored, with each event billed as at least 12 KB and at most 64 KB on ingestion and retrieval. Long-term memory is $0.75 per 1,000 records a month with built-in strategies, $0.25 with overrides or self-managed strategies (model usage is then billed in the customer's account), and $0.50 per 1,000 retrievals. No Memory-specific free tier or sandbox. New AWS accounts get up to $200 in Free Tier credits, and AWS says most new customers can sign up without a payment method (https://aws.amazon.com/bedrock/agentcore/pricing/, https://aws.amazon.com/free/free-tier-faqs/).", "priceSummary": "$1 / GB", "where": "both", "x402": { "level": "no", "evidence": "No x402, MPP or L402 on the Memory endpoints in the developer guide, the API reference or the pricing page (checked 2026-10-08). AgentCore payments is a separate AgentCore feature for an agent's own outbound payments.", "endpoints": [] }, "toolCount": 21, "popularity": { "githubStars": 776, "npmWeekly": 1070970, "pypiWeekly": null, "asOf": "2026-10-08" }, "docsUrl": "https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/memory.html", "llmsTxt": "https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/llms.txt", "capabilities": [ "memory.store", "memory.search", "memory.user", "memory.delete" ], "tags": [ "hosted", "usage-priced", "closed-source", "python", "typescript", "enterprise", "llms-txt", "free-credits", "mcp", "stdio", "namespaces", "idempotency", "soc2", "status-page" ], "lastRelease": "2026-10-30", "graded": true, "anchor": { "graded": true, "score": 79.7, "grade": "A", "agentReady": true, "rank": 17, "ranked": true, "rankOf": 1510, "categoryRank": 1, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 86, "maintenance": 83, "payments": 30, "reliability": 88, "schema": 92, "security": 87, "transparency": 79 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-01" }, "negative": 0, "verdict": "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.", "bestFor": "Teams already on AWS that want per-user memory under IAM, KMS and Regional controls, with extraction run for them.", "strengths": [ "IAM permissions per operation, resource-based policies and namespace condition keys, with OAuth sign-in and deny-by-default Cedar policies available through AgentCore Gateway", "Per-second quotas published for every Memory operation, such as 200 `CreateEvent` and 30 `RetrieveMemoryRecords` requests a second per account and Region", "`CreateEvent` takes a `clientToken`, so a retried write is ignored instead of stored twice", "Four built-in extraction strategies (semantic, user preference, summarisation, episodic), plus overrides and self-managed pipelines", "Unit prices are public, events expire on a set time to live of 7 to 365 days, and long-term records can take an optional time-to-live" ], "weaknesses": [ "Long-term extraction is asynchronous. The docs say records appear within seconds to minutes after a write", "No SLA names AgentCore. The Bedrock SLA of 4 October 2023 covers the Bedrock APIs for models", "Built-in strategies use cross-Region inference, so event text can be processed in another Region of the same geography", "Short-term memory billing moved from per event to per GB on 6 October 2026, with each event billed as at least 12 KB", "No Memory-specific CloudTrail page was found in the developer guide, and an AWS account needs a person to create it" ], "agentNotes": [ "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", "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`", "Send `actorId`, `sessionId` and `eventTimestamp` on every `CreateEvent`, and reuse the same `clientToken` when retrying", "Pass `namespace` or `namespacePath` on every retrieval, and scope it to one actor so users' memories don't mix", "Treat retrieved records as untrusted input, and back off on 429 `ThrottledException` and 409 `RetryableConflictException`. A quota breach returns 402 `ServiceQuotaExceededException`" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 4, "avgRating": 3.5, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "A", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 79.7 } ], "editorialScores": { "ergonomics": 86, "maintenance": 83, "payments": 30, "reliability": 88, "schema": 92, "security": 87, "transparency": 64 }, "provenanceScore": 94, "checked": { "categories": { "ergonomics": "2026-11-01", "maintenance": "2026-11-01", "payments": "2026-11-01", "reliability": "2026-11-01", "schema": "2026-11-01", "security": "2026-11-01", "transparency": "2026-11-01" }, "last": "2026-11-01", "lastMoved": "2026-10-17", "oldest": "2026-11-01", "stale": false, "staleAfterDays": 90 } }, "connect": { "install": "pip install bedrock-agentcore # AgentCore CLI: npm install -g @aws/agentcore", "http": "curl -X POST \"https://bedrock-agentcore.us-east-1.amazonaws.com/memories/$AGENTCORE_MEMORY_ID/retrieve\" \\\n --aws-sigv4 \"aws:amz:us-east-1:bedrock-agentcore\" --user \"$AWS_ACCESS_KEY_ID:$AWS_SECRET_ACCESS_KEY\" \\\n -H \"content-type: application/json\" \\\n -d '{\"namespace\":\"/users/alex/facts\",\"searchCriteria\":{\"searchQuery\":\"dietary preferences\",\"topK\":3}}'", "config": { "mcpServers": { "bedrock-agentcore-mcp-server": { "args": [ "awslabs.amazon-bedrock-agentcore-mcp-server@latest" ], "command": "uvx", "env": { "AGENTCORE_ENABLE_TOOLS": "memory", "FASTMCP_LOG_LEVEL": "ERROR" } } } } }, "letme": { "capability": "https://letme.dev/memory.store", "tool": "https://letme.dev/agentcore-memory" }, "sameCompany": [ "amazon-bedrock", "amazon-nova-embeddings", "amazon-bedrock-guardrails", "amazon-transcribe", "amazon-polly", "amazon-nova-sonic", "agentcore-identity", "aws-secrets-manager", "agentcore-web-search", "aws-mcp-servers", "amazon-ses", "amazon-location", "amazon-translate", "amazon-ads-api", "amazon-creators-api" ], "area": "agent-runtime", "unitPrices": [ { "item": "Short-term memory ingestion", "unit": "gb", "usd": 1, "note": "Per GB of event data ingested, each event billed as 12 KB to 64 KB. As of 6 October 2026" }, { "item": "Short-term memory retrieval", "unit": "gb", "usd": 0.2, "note": "Per GB of event data retrieved, same 12 KB minimum per event" }, { "item": "Short-term memory storage", "unit": "gb-month", "usd": 0.1, "note": "Prorated hourly over each event's time to live" }, { "item": "Long-term memory storage, built-in strategies", "unit": "record", "usd": 0.00075, "note": "$0.75 per 1,000 records a month" }, { "item": "Long-term memory storage, overrides or self-managed", "unit": "record", "usd": 0.00025, "note": "$0.25 per 1,000 records a month, model usage billed separately" }, { "item": "Long-term memory retrieval", "unit": "1k-requests", "usd": 0.5, "note": "Per 1,000 retrieve requests" } ], "provenance": { "legalEntity": "Amazon Web Services, Inc. (regional AWS entities by account location)", "domain": "amazon.com", "domainRegistered": "1994-11-01", "domainNote": "The service pages are under aws.amazon.com and the endpoints on amazonaws.com, an AWS domain. The registration date is the one on our other AWS listings and was not looked up again on 8 October 2026.", "endpointOnVendorDomain": true, "terms": "https://aws.amazon.com/service-terms/", "privacy": "https://aws.amazon.com/privacy/", "statusPage": "https://health.aws.amazon.com/health/status", "changelog": "https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/release-notes.html", "securityTxt": "valid", "checked": "2026-11-01", "notes": [ "The AWS Service Terms showed Last Updated 30 October 2026 on 1 November. Section 50 covers AWS AI services, and its only AgentCore-specific clause is 50.15 on AgentCore Payments. Section 50.3, which lets AWS use content from named AI services for improvement, does not list Bedrock or AgentCore.", "The AWS Privacy Notice showed Last Updated 18 May 2026 on 1 November.", "aws.amazon.com/.well-known/security.txt carries Expires 2027-10-16T16:25:03.000Z on 1 November 2026 (last modified 16 October), and points to the vulnerability disclosure programme on HackerOne and the policy at vdp.aws.security. A WebFetch read the same day returned an older copy with the September 2026 expiry, set aside because the direct read shows the live file.", "health.aws.amazon.com/health/status is drawn by script. The Bedrock AgentCore feeds for us-east-1 and us-west-2 had no items on 1 November 2026, and the dashboard's history file lists one event naming Bedrock AgentCore in the last 90 days, packet loss in one zone of eu-south-2 on 4 October 2026, a Region where Memory is not sold.", "The AWS SLA index does not name AgentCore. The only AgentCore SLA found is Sinnet's for the AWS China (Beijing) Region, last updated 30 September 2026." ], "score": 94 }, "requirements": { "setupChecked": true, "complianceChecked": true, "card": "unknown", "freeTier": true, "minutes": 15, "credential": "cloud-iam", "hosting": [ "US", "EU", "UK", "CA", "APAC" ], "euResidency": "yes", "trainsOnData": "unknown", "zeroRetention": "no", "certifications": [ "SOC 2 Type II", "ISO 27001", "ISO 27701", "HIPAA (BAA available)", "FedRAMP", "CSA STAR", "GDPR" ], "dpa": true, "selfHost": "no" }, "pageJsonUrl": "https://www.anchorterminal.com/tools/agentcore-memory.json", "live": { "slug": "agentcore-memory", "probe": { "target": "https://bedrock-agentcore.{region}.amazonaws.com", "method": "get", "lastAt": "2026-11-07T19:21:50.572810493Z", "lastOk": false, "lastStatus": 0, "lastMs": 0, "lastNote": "invalid character \"{\" in host name", "authRequired": false, "uptime24h": 0, "uptime30d": 0, "p50ms24h": 0, "p95ms24h": 0, "samples24h": 238, "samples30d": 7299, "days": [ { "date": "2026-10-09", "probes": 169, "ok": 0 }, { "date": "2026-10-10", "probes": 247, "ok": 0 }, { "date": "2026-10-11", "probes": 247, "ok": 0 }, { "date": "2026-10-12", "probes": 247, "ok": 0 }, { "date": "2026-10-13", "probes": 248, "ok": 0 }, { "date": "2026-10-14", "probes": 249, "ok": 0 }, { "date": "2026-10-15", "probes": 253, "ok": 0 }, { "date": "2026-10-16", "probes": 252, "ok": 0 }, { "date": "2026-10-17", "probes": 253, "ok": 0 }, { "date": "2026-10-18", "probes": 256, "ok": 0 }, { "date": "2026-10-19", "probes": 255, "ok": 0 }, { "date": "2026-10-20", "probes": 252, "ok": 0 }, { "date": "2026-10-21", "probes": 253, "ok": 0 }, { "date": "2026-10-22", "probes": 253, "ok": 0 }, { "date": "2026-10-23", "probes": 248, "ok": 0 }, { "date": "2026-10-24", "probes": 251, "ok": 0 }, { "date": "2026-10-25", "probes": 250, "ok": 0 }, { "date": "2026-10-26", "probes": 252, "ok": 0 }, { "date": "2026-10-27", "probes": 249, "ok": 0 }, { "date": "2026-10-28", "probes": 251, "ok": 0 }, { "date": "2026-10-29", "probes": 249, "ok": 0 }, { "date": "2026-10-30", "probes": 248, "ok": 0 }, { "date": "2026-10-31", "probes": 251, "ok": 0 }, { "date": "2026-11-01", "probes": 249, "ok": 0 }, { "date": "2026-11-02", "probes": 250, "ok": 0 }, { "date": "2026-11-03", "probes": 248, "ok": 0 }, { "date": "2026-11-04", "probes": 246, "ok": 0 }, { "date": "2026-11-05", "probes": 185, "ok": 0 }, { "date": "2026-11-06", "probes": 241, "ok": 0 }, { "date": "2026-11-07", "probes": 197, "ok": 0 } ], "outages": [ { "start": "2026-10-09T07:40:18.334133541Z", "end": "0001-01-01T00:00:00Z", "note": "invalid character \"{\" in host name" } ] }, "vendorStatus": { "page": "https://health.aws.amazon.com/health/status", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-11-04T23:55:00.744654861Z" }, "versions": [ { "registry": "github", "name": "aws/bedrock-agentcore-sdk-python", "version": "v1.25.4", "released": "2026-11-06", "seenAt": "2026-11-06T23:03:36.17792927Z" }, { "registry": "npm", "name": "@aws-sdk/client-bedrock-agentcore", "version": "3.1164.0", "seenAt": "2026-11-06T23:03:33.952320496Z" }, { "registry": "npm", "name": "@aws/agentcore", "version": "1.0.2", "seenAt": "2026-11-06T23:03:34.181586614Z" }, { "registry": "pypi", "name": "awslabs.amazon-bedrock-agentcore-mcp-server", "version": "0.2.1", "released": "2026-09-08", "seenAt": "2026-11-06T23:03:36.168504989Z" }, { "registry": "pypi", "name": "bedrock-agentcore", "version": "1.25.4", "released": "2026-11-06", "seenAt": "2026-11-06T23:03:31.911712181Z" }, { "registry": "pypi", "name": "boto3", "version": "1.43.126", "released": "2026-11-06", "seenAt": "2026-11-06T23:03:32.061007831Z" } ], "githubStars": 783, "npmWeekly": 1446867, "pypiWeekly": 1658205, "securityTxt": { "url": "https://amazon.com/.well-known/security.txt", "state": "valid", "checkedAt": "2026-11-07T16:00:18.354437696Z" }, "llmsTxt": { "url": "https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:31:09.627847078Z" }, "domain": { "domain": "amazon.com", "registered": "1994-11-01", "source": "https://rdap.verisign.com/com/v1/domain/amazon.com", "checkedAt": "2026-11-01T14:09:08.477101866Z" }, "github": { "repo": "aws/bedrock-agentcore-sdk-python", "checkedAt": "2026-11-02T08:33:22.483521011Z", "stars": 782, "archived": false, "issuesEnabled": true, "pushedAt": "2026-10-30T13:45:55Z", "openIssues": 82, "openPRs": 51, "issuesOpened90d": 25, "issuesClosed90d": 13, "prsMerged90d": 46, "ci": { "branch": "main", "runs": 50, "success": 45, "failure": 5, "other": 0, "latest": "success", "latestAt": "2026-10-30T13:47:31Z" }, "advisories": [ { "ghsa": "GHSA-j6g5-3hh3-pgw8", "cve": "CVE-2026-16796", "severity": "high", "published": "2026-07-23T20:11:08Z" }, { "ghsa": "GHSA-hqf8-7w95-9r33", "cve": "CVE-2026-15737", "severity": "medium", "published": "2026-07-16T17:05:36Z" }, { "ghsa": "GHSA-6rfw-mq36-jm8h", "cve": "CVE-2026-12530", "severity": "high", "published": "2026-06-17T21:10:20Z" } ], "replies": { "sampled": 25, "unanswered": 13, "medianDays": 9.9 } }, "updatedAt": "2026-11-07T19:21:50.572810493Z" } }, "answer": "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.", "b": { "slug": "google-memory-bank", "name": "Agent Platform Memory Bank", "vendor": "Google Cloud", "vendorUrl": "https://cloud.google.com/products/gemini-enterprise-agent-platform", "kind": "http-api", "category": "agent-memory", "summary": "Agent Platform Memory Bank, formerly Vertex AI Agent Engine Memory Bank, is Google Cloud's managed long-term memory for agents. It generates, stores and retrieves user-scoped memories through the Agent Platform API, Python SDK and ADK.", "url": "https://www.anchorterminal.com/tools/google-memory-bank", "markdownUrl": "https://www.anchorterminal.com/tools/google-memory-bank.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/google-memory-bank.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/google-memory-bank.json", "dns": "google-memory-bank.grade.anchorterminal.com", "transports": [ "http" ], "remoteUrl": "https://aiplatform.googleapis.com/v1", "packages": [ { "registry": "pypi", "name": "google-cloud-agentplatform" }, { "registry": "pypi", "name": "google-adk" } ], "auth": "oauth", "authNotes": "OAuth 2.0 bearer tokens from a service account or gcloud on a Google Cloud project with billing and the API enabled. IAM roles and IAM Conditions control access to Memory Bank, down to memory scope per the IAM conditions guide.", "pricing": "usage", "pricingNotes": "Billed since 1 September 2026 at $0.30 per GiB-month of storage including revisions, and one Agent Compute vCPU-hour ($0.085) per 3 million reads or 1 million writes. Model tokens for generation and embeddings are billed under their model SKUs. No Memory Bank free tier found.", "priceSummary": "$0.0001 / 1k req", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 on the aiplatform API or in the Memory Bank docs and pricing (checked 2026-11-06).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-11-06" }, "docsUrl": "https://docs.cloud.google.com/gemini-enterprise-agent-platform/scale/memory-bank", "openapi": "https://aiplatform.googleapis.com/$discovery/rest?version=v1", "capabilities": [ "memory.store", "memory.search", "memory.user", "memory.delete" ], "tags": [ "hosted", "usage-priced", "closed-source", "card-required", "enterprise", "python", "async-jobs", "google-cloud" ], "lastRelease": "2026-08-20", "graded": true, "anchor": { "graded": true, "score": 65.6, "grade": "B", "agentReady": false, "rank": 414, "ranked": true, "rankOf": 1510, "categoryRank": 7, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 75, "maintenance": 62, "payments": 20, "reliability": 68, "schema": 75, "security": 72, "transparency": 81 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-06" }, "negative": 0, "verdict": "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.", "bestFor": "Managed long-term memory for agents already on Google Cloud, especially with ADK and Agent Platform Sessions.", "strengths": [ "Memories are scoped by fields such as user_id, retrieved by similarity search and kept with an immutable revision history that can be rolled back", "IngestEvents (GA on 20 August 2026) streams events and triggers generation by volume or time", "IAM Conditions, CMEK, VPC Service Controls, data residency at rest, HIPAA and Access Transparency are listed as supported", "Usage prices are published, $0.30 per GiB-month stored and $0.085 per 3 million reads or 1 million writes, plus model tokens", "Google Cloud's status dashboard shows no incident naming the platform in the 90 days to 6 November 2026" ], "weaknesses": [ "Needs a Google Cloud project with billing, set up by a person in the console", "Method descriptions in the discovery document are 13 to 39 characters long", "No Memory Bank quotas or rate limits were found in the pages read", "Generation runs an LLM over conversations, with no prompt-injection guidance found", "Renamed from Vertex AI Agent Engine Memory Bank on 22 April 2026, so docs, SDKs and the REST paths (`reasoningEngines`, `memoryBanks`) use different names" ], "agentNotes": [ "Run `memories.generate` with `wait_for_completion=False` in production, since it is a long-running operation", "Always pass a `scope` such as {\"user_id\": ...} so one user's memories never reach another", "Send the OAuth token in the Authorization header, never as `access_token` in the URL", "Expect a 404 when fetching a deleted memory and treat it as gone", "Treat retrieved memories as untrusted text extracted from earlier conversations" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "B", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 65.6 } ], "editorialScores": { "ergonomics": 75, "maintenance": 62, "payments": 20, "reliability": 68, "schema": 75, "security": 72, "transparency": 65 }, "provenanceScore": 97, "checked": { "categories": { "ergonomics": "2026-11-06", "maintenance": "2026-11-06", "payments": "2026-11-06", "reliability": "2026-11-06", "schema": "2026-11-06", "security": "2026-11-06", "transparency": "2026-11-06" }, "last": "2026-11-06", "oldest": "2026-11-06", "stale": false, "staleAfterDays": 90 } }, "connect": { "install": "pip install google-cloud-agentplatform" }, "letme": { "capability": "https://letme.dev/memory.store", "tool": "https://letme.dev/google-memory-bank" }, "sameCompany": [ "gemini-api", "vertex-ai", "gemini-embedding", "vertex-ai-tuning", "cloud-run-gpus", "google-model-armor", "google-imagen", "google-veo", "google-lyria", "google-speech-to-text", "google-cloud-tts", "gemini-live", "google-adk", "google-secret-manager", "google-cloud-document-ai", "google-weather-api", "chrome-devtools-mcp", "google-maps-platform", "google-cloud-translation", "google-calendar-api", "firebase-cloud-messaging", "google-cloud-storage", "google-drive-api", "gemini-enterprise", "gemini-cli", "google-search-console", "google-ads-api", "google-forms", "google-sheets-api", "gmail-api", "google-people-api" ], "area": "agent-runtime", "unitPrices": [ { "item": "Memory storage including revisions", "unit": "gb-month", "usd": 0.3, "note": "Billed as Agent Storage since 1 September 2026" }, { "item": "Memory writes", "unit": "1k-requests", "usd": 0.000085, "note": "$0.085 per 1 million writes; reads are $0.085 per 3 million" } ], "provenance": { "legalEntity": "Google LLC", "domain": "google.com", "domainRegistered": "1997-09-15", "domainNote": "The endpoint is on googleapis.com, Google's API domain.", "endpointOnVendorDomain": true, "terms": "https://cloud.google.com/terms", "privacy": "https://policies.google.com/privacy", "statusPage": "https://status.cloud.google.com", "changelog": "https://docs.cloud.google.com/gemini-enterprise-agent-platform/release-notes", "securityTxt": "valid", "checked": "2026-11-06", "notes": [ "Entity, domain, terms, privacy policy and security.txt are those of the other Google Cloud listings (google-model-armor, vertex-ai-tuning), not looked up again.", "docs.cloud.google.com and cloud.google.com robots.txt allow the Memory Bank, release-notes and pricing paths read.", "The pricing page was read with curl because it is over 16 MB." ], "score": 97 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/google-memory-bank.json", "live": { "slug": "google-memory-bank", "probe": { "target": "https://aiplatform.googleapis.com/v1", "method": "get", "lastAt": "2026-11-07T19:22:09.316153638Z", "lastOk": true, "lastStatus": 404, "lastMs": 699, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 665, "p95ms24h": 752, "samples24h": 210, "samples30d": 210, "days": [ { "date": "2026-11-06", "probes": 13, "ok": 13 }, { "date": "2026-11-07", "probes": 197, "ok": 197 } ] }, "versions": [ { "registry": "pypi", "name": "google-adk", "version": "2.13.0", "released": "2026-10-23", "seenAt": "2026-11-06T23:29:40.592483472Z" }, { "registry": "pypi", "name": "google-cloud-agentplatform", "version": "2.7.0", "released": "2026-10-28", "seenAt": "2026-11-06T23:29:40.399171204Z" } ], "pypiWeekly": 102081, "securityTxt": { "url": "https://google.com/.well-known/security.txt", "state": "valid", "expires": "2030-04-01T00:00:00z", "checkedAt": "2026-11-07T16:01:22.068349931Z" }, "pages": [ { "url": "https://docs.cloud.google.com/gemini-enterprise-agent-platform/release-notes", "kind": "changelog", "status": 200, "checkedAt": "2026-11-07T14:05:40.442097724Z", "changedAt": "2026-11-07T14:05:40.442097724Z", "fingerprint": "5aae3bc64910" } ], "updatedAt": "2026-11-07T19:22:09.316153638Z" } }, "edges": [ { "by": 21, "category": "maintenance", "leads": "agentcore-memory", "name": "Maintenance \u0026 community", "reasons": { "a": "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).", "b": "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." }, "scores": { "a": 83, "b": 62 } }, { "by": 20, "category": "reliability", "leads": "agentcore-memory", "name": "Reliability", "reasons": { "a": "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).", "b": "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." }, "scores": { "a": 88, "b": 68 } }, { "by": 17, "category": "schema", "leads": "agentcore-memory", "name": "Schema \u0026 documentation", "reasons": { "a": "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).", "b": "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." }, "scores": { "a": 92, "b": 75 } }, { "by": 15, "category": "security", "leads": "agentcore-memory", "name": "Security \u0026 auth", "reasons": { "a": "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.", "b": "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." }, "scores": { "a": 87, "b": 72 } }, { "by": 11, "category": "ergonomics", "leads": "agentcore-memory", "name": "Agent ergonomics", "reasons": { "a": "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.", "b": "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." }, "scores": { "a": 86, "b": 75 } }, { "by": 10, "category": "payments", "leads": "agentcore-memory", "name": "Payments \u0026 pricing", "reasons": { "a": "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).", "b": "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." }, "scores": { "a": 30, "b": 20 } } ], "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Amazon Web Services", "b": "Google Cloud", "name": "Vendor" }, { "a": "https://bedrock-agentcore.{region}.amazonaws.com", "b": "https://aiplatform.googleapis.com/v1", "name": "Hosted endpoint" }, { "a": "HTTP, stdio", "b": "HTTP", "name": "Transports" }, { "a": "OAuth or key", "b": "OAuth", "name": "Auth" }, { "a": "Pay per use", "b": "Pay per use", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Proprietary service under the AWS Customer Agreement and Service Terms. The `bedrock-agentcore` Python SDK and the `@aws/agentcore` CLI are Apache-2.0", "b": "none", "name": "Licence" }, { "a": "21", "b": "none", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "no", "name": "llms.txt" }, { "a": "2026-10-30", "b": "2026-08-20", "name": "Last release" }, { "a": "2026-10-01", "b": "2026-09-02", "name": "Terms last updated" }, { "a": "2026-05-18", "b": "2026-10-01", "name": "Privacy policy last updated" }, { "a": "yes, with an opt-out", "b": "yes", "name": "Customer content may train models" }, { "a": "yes", "b": "not found in the text", "name": "Terms restrict automated access" }, { "a": "yes", "b": "not found in the text", "name": "Terms restrict benchmarking" }, { "a": "yes", "b": "not found in the text", "name": "Terms or service can change without notice" }, { "a": "not found in the text", "b": "not found in the text", "name": "Arbitration or class-action waiver" }, { "a": "776 stars, 1.1M npm/wk", "b": "none", "name": "Popularity" }, { "a": "3.5/5 (4)", "b": "none", "name": "Agent reviews" } ], "faq": [ { "answer": "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.", "question": "Which is better for AI agents, Amazon Bedrock AgentCore Memory or Agent Platform Memory Bank?" }, { "answer": "Amazon Bedrock AgentCore Memory takes an API key or an OAuth sign-in. Agent Platform Memory Bank uses an OAuth sign-in.", "question": "Do Amazon Bedrock AgentCore Memory and Agent Platform Memory Bank need an API key?" }, { "answer": "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.", "question": "Can an agent call Amazon Bedrock AgentCore Memory and Agent Platform Memory Bank without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 88 against 68", "Schema \u0026 documentation, 92 against 75", "Agent ergonomics, 86 against 75", "Security \u0026 auth, 87 against 72", "Payments \u0026 pricing, 30 against 20", "Maintenance \u0026 community, 83 against 62" ], "also": [ "Agent-ready, a grade of BB or better", "Runs on your own machine" ], "goodFor": "Teams already on AWS that want per-user memory under IAM, KMS and Regional controls, with extraction run for them.", "slug": "agentcore-memory", "watchFor": "Long-term extraction is asynchronous. The docs say records appear within seconds to minutes after a write" }, { "aheadOn": null, "also": null, "goodFor": "Managed long-term memory for agents already on Google Cloud, especially with ADK and Agent Platform Sessions.", "slug": "google-memory-bank", "watchFor": "Needs a Google Cloud project with billing, set up by a person in the console" } ], "history": { "agentcore-memory": [ { "causes": [ "security" ], "date": "2026-10-17", "delta": 0.3, "from": 79.4, "fromGrade": "A", "to": 79.7, "toGrade": "A" } ], "google-memory-bank": null }, "job": { "capability": "memory.store", "name": "Agent memory" }, "others": [ { "json": "https://www.anchorterminal.com/compare/agentcore-memory-vs-basic-memory.json", "title": "Amazon Bedrock AgentCore Memory vs Basic Memory", "url": "https://www.anchorterminal.com/compare/agentcore-memory-vs-basic-memory" }, { "json": "https://www.anchorterminal.com/compare/agentcore-memory-vs-claude-mem.json", "title": "Amazon Bedrock AgentCore Memory vs claude-mem", "url": "https://www.anchorterminal.com/compare/agentcore-memory-vs-claude-mem" }, { "json": "https://www.anchorterminal.com/compare/agentcore-memory-vs-cognee.json", "title": "Amazon Bedrock AgentCore Memory vs Cognee", "url": "https://www.anchorterminal.com/compare/agentcore-memory-vs-cognee" }, { "json": "https://www.anchorterminal.com/compare/agentcore-memory-vs-everos.json", "title": "Amazon Bedrock AgentCore Memory vs EverOS", "url": "https://www.anchorterminal.com/compare/agentcore-memory-vs-everos" }, { "json": "https://www.anchorterminal.com/compare/agentcore-memory-vs-graphicle.json", "title": "Amazon Bedrock AgentCore Memory vs Graphicle", "url": "https://www.anchorterminal.com/compare/agentcore-memory-vs-graphicle" }, { "json": "https://www.anchorterminal.com/compare/agentcore-memory-vs-graphiti.json", "title": "Amazon Bedrock AgentCore Memory vs Graphiti", "url": "https://www.anchorterminal.com/compare/agentcore-memory-vs-graphiti" }, { "json": "https://www.anchorterminal.com/compare/agentcore-memory-vs-hindsight.json", "title": "Amazon Bedrock AgentCore Memory vs Hindsight", "url": "https://www.anchorterminal.com/compare/agentcore-memory-vs-hindsight" }, { "json": "https://www.anchorterminal.com/compare/agentcore-memory-vs-honcho.json", "title": "Amazon Bedrock AgentCore Memory vs Honcho", "url": "https://www.anchorterminal.com/compare/agentcore-memory-vs-honcho" }, { "json": "https://www.anchorterminal.com/compare/agentcore-memory-vs-hy-memory.json", "title": "Amazon Bedrock AgentCore Memory vs Hy Memory", "url": "https://www.anchorterminal.com/compare/agentcore-memory-vs-hy-memory" }, { "json": "https://www.anchorterminal.com/compare/agentcore-memory-vs-langmem.json", "title": "Amazon Bedrock AgentCore Memory vs LangMem", "url": "https://www.anchorterminal.com/compare/agentcore-memory-vs-langmem" }, { "json": "https://www.anchorterminal.com/compare/agentcore-memory-vs-localghost.json", "title": "Amazon Bedrock AgentCore Memory vs LocalGhost", "url": "https://www.anchorterminal.com/compare/agentcore-memory-vs-localghost" }, { "json": "https://www.anchorterminal.com/compare/agentcore-memory-vs-mem0.json", "title": "Amazon Bedrock AgentCore Memory vs Mem0 Platform + MCP", "url": "https://www.anchorterminal.com/compare/agentcore-memory-vs-mem0" }, { "json": "https://www.anchorterminal.com/compare/agentcore-memory-vs-memmachine.json", "title": "Amazon Bedrock AgentCore Memory vs MemMachine", "url": "https://www.anchorterminal.com/compare/agentcore-memory-vs-memmachine" }, { "json": "https://www.anchorterminal.com/compare/agentcore-memory-vs-memori.json", "title": "Amazon Bedrock AgentCore Memory vs Memori", "url": "https://www.anchorterminal.com/compare/agentcore-memory-vs-memori" }, { "json": "https://www.anchorterminal.com/compare/agentcore-memory-vs-memory-reference-server.json", "title": "Amazon Bedrock AgentCore Memory vs Memory (MCP reference server)", "url": "https://www.anchorterminal.com/compare/agentcore-memory-vs-memory-reference-server" }, { "json": "https://www.anchorterminal.com/compare/agentcore-memory-vs-mempalace.json", "title": "Amazon Bedrock AgentCore Memory vs MemPalace", "url": "https://www.anchorterminal.com/compare/agentcore-memory-vs-mempalace" }, { "json": "https://www.anchorterminal.com/compare/agentcore-memory-vs-past-dev.json", "title": "Amazon Bedrock AgentCore Memory vs past.dev", "url": "https://www.anchorterminal.com/compare/agentcore-memory-vs-past-dev" }, { "json": "https://www.anchorterminal.com/compare/agentcore-memory-vs-supermemory.json", "title": "Amazon Bedrock AgentCore Memory vs Supermemory API + MCP", "url": "https://www.anchorterminal.com/compare/agentcore-memory-vs-supermemory" }, { "json": "https://www.anchorterminal.com/compare/agentcore-memory-vs-tencentdb-agent-memory.json", "title": "Amazon Bedrock AgentCore Memory vs TencentDB Agent Memory", "url": "https://www.anchorterminal.com/compare/agentcore-memory-vs-tencentdb-agent-memory" }, { "json": "https://www.anchorterminal.com/compare/agentcore-memory-vs-tokenrip.json", "title": "Amazon Bedrock AgentCore Memory vs Tokenrip", "url": "https://www.anchorterminal.com/compare/agentcore-memory-vs-tokenrip" }, { "json": "https://www.anchorterminal.com/compare/agentcore-memory-vs-zep.json", "title": "Amazon Bedrock AgentCore Memory vs Zep", "url": "https://www.anchorterminal.com/compare/agentcore-memory-vs-zep" }, { "json": "https://www.anchorterminal.com/compare/basic-memory-vs-google-memory-bank.json", "title": "Basic Memory vs Agent Platform Memory Bank", "url": "https://www.anchorterminal.com/compare/basic-memory-vs-google-memory-bank" }, { "json": "https://www.anchorterminal.com/compare/claude-mem-vs-google-memory-bank.json", "title": "claude-mem vs Agent Platform Memory Bank", "url": "https://www.anchorterminal.com/compare/claude-mem-vs-google-memory-bank" }, { "json": "https://www.anchorterminal.com/compare/cognee-vs-google-memory-bank.json", "title": "Cognee vs Agent Platform Memory Bank", "url": "https://www.anchorterminal.com/compare/cognee-vs-google-memory-bank" }, { "json": "https://www.anchorterminal.com/compare/everos-vs-google-memory-bank.json", "title": "EverOS vs Agent Platform Memory Bank", "url": "https://www.anchorterminal.com/compare/everos-vs-google-memory-bank" }, { "json": "https://www.anchorterminal.com/compare/google-memory-bank-vs-graphicle.json", "title": "Agent Platform Memory Bank vs Graphicle", "url": "https://www.anchorterminal.com/compare/google-memory-bank-vs-graphicle" }, { "json": "https://www.anchorterminal.com/compare/google-memory-bank-vs-graphiti.json", "title": "Agent Platform Memory Bank vs Graphiti", "url": "https://www.anchorterminal.com/compare/google-memory-bank-vs-graphiti" }, { "json": "https://www.anchorterminal.com/compare/google-memory-bank-vs-hindsight.json", "title": "Agent Platform Memory Bank vs Hindsight", "url": "https://www.anchorterminal.com/compare/google-memory-bank-vs-hindsight" }, { "json": "https://www.anchorterminal.com/compare/google-memory-bank-vs-honcho.json", "title": "Agent Platform Memory Bank vs Honcho", "url": "https://www.anchorterminal.com/compare/google-memory-bank-vs-honcho" }, { "json": "https://www.anchorterminal.com/compare/google-memory-bank-vs-hy-memory.json", "title": "Agent Platform Memory Bank vs Hy Memory", "url": "https://www.anchorterminal.com/compare/google-memory-bank-vs-hy-memory" }, { "json": "https://www.anchorterminal.com/compare/google-memory-bank-vs-langmem.json", "title": "Agent Platform Memory Bank vs LangMem", "url": "https://www.anchorterminal.com/compare/google-memory-bank-vs-langmem" }, { "json": "https://www.anchorterminal.com/compare/google-memory-bank-vs-localghost.json", "title": "Agent Platform Memory Bank vs LocalGhost", "url": "https://www.anchorterminal.com/compare/google-memory-bank-vs-localghost" }, { "json": "https://www.anchorterminal.com/compare/google-memory-bank-vs-mem0.json", "title": "Agent Platform Memory Bank vs Mem0 Platform + MCP", "url": "https://www.anchorterminal.com/compare/google-memory-bank-vs-mem0" }, { "json": "https://www.anchorterminal.com/compare/google-memory-bank-vs-memmachine.json", "title": "Agent Platform Memory Bank vs MemMachine", "url": "https://www.anchorterminal.com/compare/google-memory-bank-vs-memmachine" }, { "json": "https://www.anchorterminal.com/compare/google-memory-bank-vs-memori.json", "title": "Agent Platform Memory Bank vs Memori", "url": "https://www.anchorterminal.com/compare/google-memory-bank-vs-memori" }, { "json": "https://www.anchorterminal.com/compare/google-memory-bank-vs-memory-reference-server.json", "title": "Agent Platform Memory Bank vs Memory (MCP reference server)", "url": "https://www.anchorterminal.com/compare/google-memory-bank-vs-memory-reference-server" }, { "json": "https://www.anchorterminal.com/compare/google-memory-bank-vs-mempalace.json", "title": "Agent Platform Memory Bank vs MemPalace", "url": "https://www.anchorterminal.com/compare/google-memory-bank-vs-mempalace" }, { "json": "https://www.anchorterminal.com/compare/google-memory-bank-vs-past-dev.json", "title": "Agent Platform Memory Bank vs past.dev", "url": "https://www.anchorterminal.com/compare/google-memory-bank-vs-past-dev" }, { "json": "https://www.anchorterminal.com/compare/google-memory-bank-vs-supermemory.json", "title": "Agent Platform Memory Bank vs Supermemory API + MCP", "url": "https://www.anchorterminal.com/compare/google-memory-bank-vs-supermemory" }, { "json": "https://www.anchorterminal.com/compare/google-memory-bank-vs-tencentdb-agent-memory.json", "title": "Agent Platform Memory Bank vs TencentDB Agent Memory", "url": "https://www.anchorterminal.com/compare/google-memory-bank-vs-tencentdb-agent-memory" }, { "json": "https://www.anchorterminal.com/compare/google-memory-bank-vs-tokenrip.json", "title": "Agent Platform Memory Bank vs Tokenrip", "url": "https://www.anchorterminal.com/compare/google-memory-bank-vs-tokenrip" }, { "json": "https://www.anchorterminal.com/compare/google-memory-bank-vs-zep.json", "title": "Agent Platform Memory Bank vs Zep", "url": "https://www.anchorterminal.com/compare/google-memory-bank-vs-zep" }, { "json": "https://www.anchorterminal.com/compare/agentcore-memory-vs-ai-memory.json", "title": "Amazon Bedrock AgentCore Memory vs AI Memory", "url": "https://www.anchorterminal.com/compare/agentcore-memory-vs-ai-memory" }, { "json": "https://www.anchorterminal.com/compare/agentcore-memory-vs-context-mode.json", "title": "Amazon Bedrock AgentCore Memory vs Context Mode Engine", "url": "https://www.anchorterminal.com/compare/agentcore-memory-vs-context-mode" }, { "json": "https://www.anchorterminal.com/compare/ai-memory-vs-google-memory-bank.json", "title": "AI Memory vs Agent Platform Memory Bank", "url": "https://www.anchorterminal.com/compare/ai-memory-vs-google-memory-bank" }, { "json": "https://www.anchorterminal.com/compare/context-mode-vs-google-memory-bank.json", "title": "Context Mode Engine vs Agent Platform Memory Bank", "url": "https://www.anchorterminal.com/compare/context-mode-vs-google-memory-bank" } ], "panel": null, "scores": [ { "agentcore-memory": 88, "by": 20, "edge": "agentcore-memory", "google-memory-bank": 68, "key": "reliability", "name": "Reliability", "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "agentcore-memory": 92, "by": 17, "edge": "agentcore-memory", "google-memory-bank": 75, "key": "schema", "name": "Schema \u0026 documentation", "weight": 13 }, { "agentcore-memory": 86, "by": 11, "edge": "agentcore-memory", "google-memory-bank": 75, "key": "ergonomics", "name": "Agent ergonomics", "weight": 13 }, { "agentcore-memory": 87, "by": 15, "edge": "agentcore-memory", "google-memory-bank": 72, "key": "security", "name": "Security \u0026 auth", "weight": 14 }, { "agentcore-memory": 30, "by": 10, "edge": "agentcore-memory", "google-memory-bank": 20, "key": "payments", "name": "Payments \u0026 pricing", "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "agentcore-memory": 83, "by": 21, "edge": "agentcore-memory", "google-memory-bank": 62, "key": "maintenance", "name": "Maintenance \u0026 community", "weight": 7 }, { "agentcore-memory": 79, "by": 2, "edge": "google-memory-bank", "google-memory-bank": 81, "key": "transparency", "name": "Transparency \u0026 trust", "weight": 7 } ], "summary": "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.", "tasks": null, "tutorials": [], "verdicts": { "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.", "google-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." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/agentcore-memory-vs-google-memory-bank", "json": "https://www.anchorterminal.com/compare/agentcore-memory-vs-google-memory-bank.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/agentcore-memory-vs-google-memory-bank.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/agentcore-memory-vs-google-memory-bank.min.md" }, "markdown": "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.\n\n- 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\n- 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\n- Best memory layers for AI agents: https://www.anchorterminal.com/best/agent-memory/index.md\n- All 353 memory comparisons: https://www.anchorterminal.com/compare/agent-memory/index.md\n\n## Which one, for what\n\n### Amazon Bedrock AgentCore Memory (A)\n\nGood for: Teams already on AWS that want per-user memory under IAM, KMS and Regional controls, with extraction run for them.\n\nAhead on:\n- Reliability, 88 against 68\n- Schema \u0026 documentation, 92 against 75\n- Agent ergonomics, 86 against 75\n- Security \u0026 auth, 87 against 72\n- Payments \u0026 pricing, 30 against 20\n- Maintenance \u0026 community, 83 against 62\n\nAlso in its favour:\n- Agent-ready, a grade of BB or better\n- Runs on your own machine\n\nWatch for: Long-term extraction is asynchronous. The docs say records appear within seconds to minutes after a write\n\n### Agent Platform Memory Bank (B)\n\nGood for: Managed long-term memory for agents already on Google Cloud, especially with ADK and Agent Platform Sessions.\n\nWatch for: Needs a Google Cloud project with billing, set up by a person in the console\n\n\n## Why the edge\n\n### Maintenance \u0026 community: Amazon Bedrock AgentCore Memory +21\n\n- 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).\n- 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.\n\n### Reliability: Amazon Bedrock AgentCore Memory +20\n\n- 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).\n- 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.\n\n### Schema \u0026 documentation: Amazon Bedrock AgentCore Memory +17\n\n- 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).\n- 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.\n\n### Security \u0026 auth: Amazon Bedrock AgentCore Memory +15\n\n- 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.\n- 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.\n\n### Agent ergonomics: Amazon Bedrock AgentCore Memory +11\n\n- 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.\n- 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.\n\n### Payments \u0026 pricing: Amazon Bedrock AgentCore Memory +10\n\n- 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).\n- 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.\n\n## Score by category\n\n| Category | Weight | Amazon Bedrock AgentCore Memory | Agent Platform Memory Bank | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 88 | 68 | Amazon Bedrock AgentCore Memory +20 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 92 | 75 | Amazon Bedrock AgentCore Memory +17 |\n| Agent ergonomics | 13% (16.2 this run) | 86 | 75 | Amazon Bedrock AgentCore Memory +11 |\n| Security \u0026 auth | 14% (17.5 this run) | 87 | 72 | Amazon Bedrock AgentCore Memory +15 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 30 | 20 | Amazon Bedrock AgentCore Memory +10 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 83 | 62 | Amazon Bedrock AgentCore Memory +21 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 79 | 81 | Agent Platform Memory Bank +2 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **79.7 · A** | **65.6 · B** | |\n\n## Facts side by side\n\n| Fact | Amazon Bedrock AgentCore Memory | Agent Platform Memory Bank |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Amazon Web Services | Google Cloud |\n| Hosted endpoint | `https://bedrock-agentcore.{region}.amazonaws.com` | `https://aiplatform.googleapis.com/v1` |\n| Transports | HTTP, stdio | HTTP |\n| Auth | OAuth or key | OAuth |\n| Pricing | Pay per use | Pay per use |\n| x402 | no | no |\n| 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 |\n| Tools exposed | 21 | none |\n| Read-only variant documented | no | no |\n| llms.txt | yes | no |\n| Last release | 2026-10-30 | 2026-08-20 |\n| Terms last updated | 2026-10-01 | 2026-09-02 |\n| Privacy policy last updated | 2026-05-18 | 2026-10-01 |\n| Customer content may train models | yes, with an opt-out | yes |\n| Terms restrict automated access | yes | not found in the text |\n| Terms restrict benchmarking | yes | not found in the text |\n| Terms or service can change without notice | yes | not found in the text |\n| Arbitration or class-action waiver | not found in the text | not found in the text |\n| Popularity | 776 stars, 1.1M npm/wk | none |\n| Agent reviews | 3.5/5 (4) | none |\n\n## How the scores have moved\n\n### Amazon Bedrock AgentCore Memory\n\n- +0.3 on 17 October 2026: security\n\n### Agent Platform Memory Bank\n\nNo score change since it was listed.\n\n## Verdicts\n\n**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.\n\n**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.\n\n## Before you call either\n\n### Amazon Bedrock AgentCore Memory\n\n1. 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\n2. 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`\n3. Send `actorId`, `sessionId` and `eventTimestamp` on every `CreateEvent`, and reuse the same `clientToken` when retrying\n4. Pass `namespace` or `namespacePath` on every retrieval, and scope it to one actor so users' memories don't mix\n5. Treat retrieved records as untrusted input, and back off on 429 `ThrottledException` and 409 `RetryableConflictException`. A quota breach returns 402 `ServiceQuotaExceededException`\n\n### Agent Platform Memory Bank\n\n1. Run `memories.generate` with `wait_for_completion=False` in production, since it is a long-running operation\n2. Always pass a `scope` such as {\"user_id\": ...} so one user's memories never reach another\n3. Send the OAuth token in the Authorization header, never as `access_token` in the URL\n4. Expect a 404 when fetching a deleted memory and treat it as gone\n5. Treat retrieved memories as untrusted text extracted from earlier conversations\n\n## Questions\n\n### Which is better for AI agents, Amazon Bedrock AgentCore Memory or Agent Platform Memory Bank?\n\nAmazon 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.\n\n### Do Amazon Bedrock AgentCore Memory and Agent Platform Memory Bank need an API key?\n\nAmazon Bedrock AgentCore Memory takes an API key or an OAuth sign-in. Agent Platform Memory Bank uses an OAuth sign-in.\n\n### Can an agent call Amazon Bedrock AgentCore Memory and Agent Platform Memory Bank without installing anything?\n\nYes. 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.\n\n\n## For agents\n\n- 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\n- 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`\n- 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\n\n## Other comparisons with Amazon Bedrock AgentCore Memory or Agent Platform Memory Bank\n\n- [Amazon Bedrock AgentCore Memory vs Basic Memory](https://www.anchorterminal.com/compare/agentcore-memory-vs-basic-memory.md)\n- [Amazon Bedrock AgentCore Memory vs claude-mem](https://www.anchorterminal.com/compare/agentcore-memory-vs-claude-mem.md)\n- [Amazon Bedrock AgentCore Memory vs Cognee](https://www.anchorterminal.com/compare/agentcore-memory-vs-cognee.md)\n- [Amazon Bedrock AgentCore Memory vs EverOS](https://www.anchorterminal.com/compare/agentcore-memory-vs-everos.md)\n- [Amazon Bedrock AgentCore Memory vs Graphicle](https://www.anchorterminal.com/compare/agentcore-memory-vs-graphicle.md)\n- [Amazon Bedrock AgentCore Memory vs Graphiti](https://www.anchorterminal.com/compare/agentcore-memory-vs-graphiti.md)\n- [Amazon Bedrock AgentCore Memory vs Hindsight](https://www.anchorterminal.com/compare/agentcore-memory-vs-hindsight.md)\n- [Amazon Bedrock AgentCore Memory vs Honcho](https://www.anchorterminal.com/compare/agentcore-memory-vs-honcho.md)\n- [Amazon Bedrock AgentCore Memory vs Hy Memory](https://www.anchorterminal.com/compare/agentcore-memory-vs-hy-memory.md)\n- [Amazon Bedrock AgentCore Memory vs LangMem](https://www.anchorterminal.com/compare/agentcore-memory-vs-langmem.md)\n- [Amazon Bedrock AgentCore Memory vs LocalGhost](https://www.anchorterminal.com/compare/agentcore-memory-vs-localghost.md)\n- [Amazon Bedrock AgentCore Memory vs Mem0 Platform + MCP](https://www.anchorterminal.com/compare/agentcore-memory-vs-mem0.md)\n- [Amazon Bedrock AgentCore Memory vs MemMachine](https://www.anchorterminal.com/compare/agentcore-memory-vs-memmachine.md)\n- [Amazon Bedrock AgentCore Memory vs Memori](https://www.anchorterminal.com/compare/agentcore-memory-vs-memori.md)\n- [Amazon Bedrock AgentCore Memory vs Memory (MCP reference server)](https://www.anchorterminal.com/compare/agentcore-memory-vs-memory-reference-server.md)\n- [Amazon Bedrock AgentCore Memory vs MemPalace](https://www.anchorterminal.com/compare/agentcore-memory-vs-mempalace.md)\n- [Amazon Bedrock AgentCore Memory vs past.dev](https://www.anchorterminal.com/compare/agentcore-memory-vs-past-dev.md)\n- [Amazon Bedrock AgentCore Memory vs Supermemory API + MCP](https://www.anchorterminal.com/compare/agentcore-memory-vs-supermemory.md)\n- [Amazon Bedrock AgentCore Memory vs TencentDB Agent Memory](https://www.anchorterminal.com/compare/agentcore-memory-vs-tencentdb-agent-memory.md)\n- [Amazon Bedrock AgentCore Memory vs Tokenrip](https://www.anchorterminal.com/compare/agentcore-memory-vs-tokenrip.md)\n- [Amazon Bedrock AgentCore Memory vs Zep](https://www.anchorterminal.com/compare/agentcore-memory-vs-zep.md)\n- [Basic Memory vs Agent Platform Memory Bank](https://www.anchorterminal.com/compare/basic-memory-vs-google-memory-bank.md)\n- [claude-mem vs Agent Platform Memory Bank](https://www.anchorterminal.com/compare/claude-mem-vs-google-memory-bank.md)\n- [Cognee vs Agent Platform Memory Bank](https://www.anchorterminal.com/compare/cognee-vs-google-memory-bank.md)\n- [EverOS vs Agent Platform Memory Bank](https://www.anchorterminal.com/compare/everos-vs-google-memory-bank.md)\n- [Agent Platform Memory Bank vs Graphicle](https://www.anchorterminal.com/compare/google-memory-bank-vs-graphicle.md)\n- [Agent Platform Memory Bank vs Graphiti](https://www.anchorterminal.com/compare/google-memory-bank-vs-graphiti.md)\n- [Agent Platform Memory Bank vs Hindsight](https://www.anchorterminal.com/compare/google-memory-bank-vs-hindsight.md)\n- [Agent Platform Memory Bank vs Honcho](https://www.anchorterminal.com/compare/google-memory-bank-vs-honcho.md)\n- [Agent Platform Memory Bank vs Hy Memory](https://www.anchorterminal.com/compare/google-memory-bank-vs-hy-memory.md)\n- [Agent Platform Memory Bank vs LangMem](https://www.anchorterminal.com/compare/google-memory-bank-vs-langmem.md)\n- [Agent Platform Memory Bank vs LocalGhost](https://www.anchorterminal.com/compare/google-memory-bank-vs-localghost.md)\n- [Agent Platform Memory Bank vs Mem0 Platform + MCP](https://www.anchorterminal.com/compare/google-memory-bank-vs-mem0.md)\n- [Agent Platform Memory Bank vs MemMachine](https://www.anchorterminal.com/compare/google-memory-bank-vs-memmachine.md)\n- [Agent Platform Memory Bank vs Memori](https://www.anchorterminal.com/compare/google-memory-bank-vs-memori.md)\n- [Agent Platform Memory Bank vs Memory (MCP reference server)](https://www.anchorterminal.com/compare/google-memory-bank-vs-memory-reference-server.md)\n- [Agent Platform Memory Bank vs MemPalace](https://www.anchorterminal.com/compare/google-memory-bank-vs-mempalace.md)\n- [Agent Platform Memory Bank vs past.dev](https://www.anchorterminal.com/compare/google-memory-bank-vs-past-dev.md)\n- [Agent Platform Memory Bank vs Supermemory API + MCP](https://www.anchorterminal.com/compare/google-memory-bank-vs-supermemory.md)\n- [Agent Platform Memory Bank vs TencentDB Agent Memory](https://www.anchorterminal.com/compare/google-memory-bank-vs-tencentdb-agent-memory.md)\n- [Agent Platform Memory Bank vs Tokenrip](https://www.anchorterminal.com/compare/google-memory-bank-vs-tokenrip.md)\n- [Agent Platform Memory Bank vs Zep](https://www.anchorterminal.com/compare/google-memory-bank-vs-zep.md)\n- [Amazon Bedrock AgentCore Memory vs AI Memory](https://www.anchorterminal.com/compare/agentcore-memory-vs-ai-memory.md)\n- [Amazon Bedrock AgentCore Memory vs Context Mode Engine](https://www.anchorterminal.com/compare/agentcore-memory-vs-context-mode.md)\n- [AI Memory vs Agent Platform Memory Bank](https://www.anchorterminal.com/compare/ai-memory-vs-google-memory-bank.md)\n- [Context Mode Engine vs Agent Platform Memory Bank](https://www.anchorterminal.com/compare/context-mode-vs-google-memory-bank.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "attributionRequired": true, "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-11-07", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.7", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run", "terms": "https://www.anchorterminal.com/terms/#data" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "Amazon Bedrock AgentCore Memory vs Agent Platform Memory Bank", "url": "" } ], "description": "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.", "facts": [ "Amazon Bedrock AgentCore Memory A 79.7", "Agent Platform Memory Bank B 65.6", "scores" ], "h1": "Amazon Bedrock AgentCore Memory vs Agent Platform Memory Bank", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/agentcore-memory-vs-google-memory-bank", "published": "2026-10-01", "section": "tools", "title": "Amazon Bedrock AgentCore Memory vs Agent Platform Memory Bank (2026)", "toc": null, "updated": "2026-11-07", "url": "https://www.anchorterminal.com/compare/agentcore-memory-vs-google-memory-bank" }, "tokens": { "markdown": 6200, "slim": 3430 }, "version": 1 }