# Cognee vs Agent Platform Memory Bank (slim)

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

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

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

- Cognee: D 47.7, rank #1146 of 1510 · https://www.anchorterminal.com/tools/cognee.min.md
- Agent Platform Memory Bank: B 65.6, rank #414 of 1510 · https://www.anchorterminal.com/tools/google-memory-bank.min.md
- Cognee, good for Agents whose memory has to include documents, wikis and chat tools as well as conversation, and for teams happy to self-host. Ahead on Schema & documentation, 85 against 75; Payments & pricing, 35 against 20; Maintenance & community, 82 against 62. Also Runs on your own machine; Free to start without a card; Open source.
- Agent Platform Memory Bank, good for Managed long-term memory for agents already on Google Cloud, especially with ADK and Agent Platform Sessions. Ahead on Reliability, 68 against 43; Agent ergonomics, 75 against 59; Security & auth, 72 against 39; Transparency & trust, 81 against 72. Also No incidents deducted, where Cognee loses 9 points for them.

| Category | Cognee | Agent Platform Memory Bank |
| --- | --- | --- |
| Reliability (16%) | 43 | 68 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 85 | 75 |
| Agent ergonomics (13%) | 59 | 75 |
| Security & auth (14%) | 39 | 72 |
| Payments & pricing (10%) | 35 | 20 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 82 | 62 |
| Transparency & trust (7%) | 72 | 81 |

| Fact (where they differ) | Cognee | Agent Platform Memory Bank |
| --- | --- | --- |
| Kind | Platform | HTTP API |
| Vendor | Cognee | Google Cloud |
| Hosted endpoint | `https://<tenant>.aws.cognee.ai/api/v1` | `https://aiplatform.googleapis.com/v1` |
| Transports | HTTP, stdio, SSE (legacy) | HTTP |
| Auth | OAuth or key | OAuth |
| Pricing | Freemium | Pay per use |
| Licence | Apache-2.0 | none |
| Tools exposed | 7 | none |
| llms.txt | yes | no |
| Last release | 2026-10-29 | 2026-08-20 |
| Terms last updated | 2026-03-27 | 2026-09-02 |
| Privacy policy last updated | no date given | 2026-10-01 |
| Customer content may train models | not found in the text | yes |
| Popularity | 31k stars | none |
| Agent reviews | 3/5 (2) | none |

Why the edge:
- Security & auth, Agent Platform Memory Bank +33: Cognee 39 (Cloud takes an `X-Api-Key` per tenant, which the security page says can be rotated, and the API reference lists endpoints to create and delete keys. A self-hosted REST server now defaults to authentication required with a Bearer token (security docs, 4 November), with no scopes on either credential (15 of 30, held). Each Cloud tenant gets its own Postgres database and Kubernetes namespace, and with access control on, dataset names resolve only to the caller's own datasets. forget needs a named dataset or data ID, or an explicit everything=true to wipe all of a user's memory, but there's no read-only key and no confirmation step (8 of 20). Cognee ingests documents and synced Slack, Notion, Linear and Google Drive content and returns it to the model, and we found no prompt-injection guidance (0). Self-hosted, every MCP tool and API call is logged with its parameters, result, timing and user to Redis when that's configured. We found no audit log for Cloud (6 of 15). SECURITY.md asks for reports to security@cognee.ai, and an OpenSSF Scorecard workflow runs in CI. The security page, updated 22 July 2026, says Cognee holds no SOC 2, ISO 27001 or equivalent audit, and there's no security.txt (10 of 20). On 4 November SECURITY.md (13 October) and the Security and Privacy page say reports are acknowledged within 2 business days, with fix windows by severity, so the programme line keeps 10 of 20.); 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.)
- Reliability, Agent Platform Memory Bank +25: Cognee 43 (We departed from the checklist here. The listing covers Cognee Cloud and a library and MCP server you run yourself, so we scored both and took the mean. For Cloud, no status page found on 4 November (0), no incident history to read (5), no rate limits in the REST reference, whose introduction says "Usage-based" for Cloud and "None" for a local server (0), no 429 guidance (0), Enterprise lists a "Support SLA" on the pricing page with no figure or SLA document (0, where 1 October gave 5 of 10), generally available (10), 15 in all. For the local package, cognee on PyPI with Python 3.10 to 3.14 stated in SECURITY.md and pyproject.toml (20). 64 GitHub Actions workflows, and test_suites.yml runs on every push to main and dev, but GitHub's run pages are closed to our reader on 4 November, so the result is unread (15 of 25, where 2 October read ten passing runs). Open regressions not counted, per the 2 October check (10 of 25). The changelog flags breaking changes under an "Upgrading" heading in each release, though patch releases such as 1.6.3, 1.6.5 and 1.6.6 carry them and 11 MCP tools went in May without a version bump (10 of 15). Version 1.6.6 (15). 70 in all. Mean 42.5, rounded half up to 43.); Agent Platform Memory Bank 68 (Hosted lines. Google Cloud status dashboard with per-product history (20). Its incident feed, read on 6 November 2026, holds four incidents since 8 August (20 August, 27 products; 1 September, us-central1-b; 8 October, Cloud Storage; 20 October, europe-west2, 38 products), and none names Agent Platform, Vertex or Memory Bank (30). No Memory Bank quotas or rate limits were found; the platform quotas path guessed returned 404 (0, unchecked). Generation is a long-running operation with wait and cancel methods, and Google's retry guidance wasn't re-read for this API (8 of 15). No SLA for Memory Bank was found in the pages read (0, unchecked). Memory profiles, IngestEvents and multi-regional endpoints are GA (10). Total 68.)
- Maintenance & community, Cognee +20: Cognee 82 (cognee v1.6.6 tagged on 29 October 2026 (30). Stable tags from 6 August are v1.4.2 (8 August), v1.5.0 to v1.5.4, v1.6.0 to v1.6.6 and cognee-mcp-v0.5.7 (8 October), well over three (20); dev and rc tags not counted. Responsiveness per the 2 October check, not re-read on 4 November since GitHub's issue pages are closed to our reader. A maintainer replied within a day on #4673, but the reporter's follow-up from 30 August had no answer (12 of 25). The official Python package is current. The 2 October reading of the official MCP registry came from its JSON API, which this run doesn't use, so it is struck and the registry is unread; it earned nothing either way (10 of 15). Dependabot, uv.lock and dependency floors raised in 1.6.5 and 1.6.6, with CI configured but its results unread (10). 30 + 20 + 12 + 10 + 10 = 82.); 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.)
- Agent ergonomics, Agent Platform Memory Bank +16: Cognee 59 (The tools reference lists 7 MCP tools, remember, recall, forget, code_search, search_tools, call_tool and cognify_status, with search_tools and call_tool reaching further tools on demand and COGNEE_MCP_TOOL_MODE=minimal cutting the list to the memory tools (25). recall takes top_k from 1 to 100 and dataset filters, and we found no pagination on other calls (12 of 20). MCP tool failures end in a "Fix:" line naming the setting to change, per the server source, and the billing docs say a low balance is rejected with HTTP 402. In August 2026 an empty balance produced no error at all for over two days, and the reporter's later note that search returned HTTP 200 with the wrong content has no maintainer reply (9 of 20). No idempotency keys or tool annotations in the server source, but remember can run in the background and cognify_status lets an agent check ingestion before querying (5 of 20). Python only, and the MCP server starts with one docker run (8 of 15). On 4 November the tools reference and cognee-mcp 0.5.7 source still register the same seven tools, with no tool annotations.); 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, Cognee +15: Cognee 35 (No x402, MPP or L402 (0). Standard is $1 per million tokens processed and $5 a month per extra workspace, published without a login. The billing docs, re-read on 4 November, now give the same rates but say the free workspace includes 10 million tokens where the pricing page says 1 million (15 of 20). Free includes a workspace, "no card required" (20). A person signs up for a Cloud tenant in the browser (0). Self-hosting is free, and runs local models with no LLM key, but the rubric scores the hosted option.); 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.)
- Schema & documentation, Cognee +10: Cognee 85 (Each REST reference page publishes its OpenAPI 3.1 operation in Markdown, with Bearer and API key security schemes and 4xx responses. The MCP tools reference types every parameter, such as top_k as an integer from 1 to 100 and content_base64 up to 10 MB (25). llms.txt plus separate llms-mcp.md and llms-api.md indexes (10). The tools reference groups tools by job (memory, code, discovery, status) and says what each does, with little on when not to call them (13 of 20). Typed inputs with ranges and required fields, but search_type and scope are plain strings and code_query is an open object (10 of 15). Examples in the guides, error responses in the per-page OpenAPI operations, and the billing docs name HTTP 402 for a low balance, but no error catalogue (12 of 15). Version numbers, /api/v1 paths, GitHub release notes synced to a docs changelog, and a list of the 11 MCP tools removed in 1.x (15). Re-read on 4 November, the reference lists 144 pages. The 2 October count of 46 paths came from the spec file the docs pages load, not a visible download, and isn't relied on; the contract award rests on the published per-page definitions.); 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.)