# Cognee vs Memori (slim)

> Cognee scores 47.7 (D) to Memori's 44.2 (E) for agent memory. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/cognee-vs-memori.md (~5,200 tokens) · this version ~2,930 tokens · JSON https://www.anchorterminal.com/compare/cognee-vs-memori.json · canonical https://www.anchorterminal.com/compare/cognee-vs-memori
- 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)

Cognee scores 47.7 (D) on agent readiness against Memori's 44.2 (E), and leads in 4 of 7 scored categories. Memori leads on agent ergonomics, security & auth and payments & pricing. Both do agent memory.

- Cognee: D 47.7, rank #1146 of 1510 · https://www.anchorterminal.com/tools/cognee.min.md
- Memori: E 44.2, rank #1231 of 1510 · https://www.anchorterminal.com/tools/memori.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 Reliability, 43 against 28; Schema & documentation, 85 against 68; Maintenance & community, 82 against 33; Transparency & trust, 72 against 52. Also Runs on your own machine; Free to start without a card.
- Memori, good for Memory captured from LLM calls for apps that already use OpenAI, Anthropic or Gemini clients. Ahead on Agent ergonomics, 65 against 59; Security & auth, 45 against 39; Payments & pricing, 45 against 35.

| Category | Cognee | Memori |
| --- | --- | --- |
| Reliability (16%) | 43 | 28 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 85 | 68 |
| Agent ergonomics (13%) | 59 | 65 |
| Security & auth (14%) | 39 | 45 |
| Payments & pricing (10%) | 35 | 45 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 82 | 33 |
| Transparency & trust (7%) | 72 | 52 |

| Fact (where they differ) | Cognee | Memori |
| --- | --- | --- |
| Kind | Platform | SDK + MCP |
| Vendor | Cognee | Memori Labs Inc. |
| Hosted endpoint | `https://<tenant>.aws.cognee.ai/api/v1` | `https://api.memorilabs.ai/mcp/` |
| Transports | HTTP, stdio, SSE (legacy) | Streamable HTTP |
| Auth | OAuth or key | API key |
| Last release | 2026-10-29 | 2026-05-27 |
| Terms last updated | 2026-03-27 | no document linked |
| Customer content may train models | not found in the text | not read yet |
| Terms restrict automated access | not found in the text | not read yet |
| Terms restrict benchmarking | not found in the text | not read yet |
| Terms or service can change without notice | not found in the text | not read yet |
| Arbitration or class-action waiver | not found in the text | not read yet |
| Popularity | 31k stars | 17k stars, 130 npm/wk, 3.8k PyPI/wk |
| Agent reviews | 3/5 (2) | none |

Why the edge:
- Maintenance & community, Cognee +49: 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.); Memori 33 (SDK 3.3.6 on 27 May 2026, 163 days before the check (10). No release in the 90 days to 6 November (0). Twelve open issues from one reporter since 20 October, mostly with no reply, and 18 open pull requests (6 of 25). Python and TypeScript SDKs, last released in May 2026 (12 of 15). CI workflows for both SDKs and integrations; the last commit on main was 17 September 2026 (5 of 10). Total 33.)
- Transparency & trust, Cognee +20: Cognee 72 (The library, REST server and MCP server are Apache-2.0, and Cloud is closed (25 of 30). The privacy notice of 20 September 2026 gives retention by data type (account data deleted 30 days after termination, product usage 24 months, technical logs 30 days to 12 months, billing 10 years for the EU entity and 7 for the US one), and the security page names a data protection officer and deletes a tenant's whole database when it goes (22 of 30, per 2 October and re-read on 4 November). Deprecations now come as dated changelog notices. v1.6.5 (16 October) deprecates `cognee.memify()` and `POST /api/v1/memify` with a FutureWarning "for one release", and the REST reference marks memify deprecated. No written policy with a notice period, so 15 of 20 (6 on 1 October). The privacy notice names Cloud processors (AWS, Neon, Auth0, Stripe, Dash0, Segment) and says Cloud runs in AWS us-east-1, operated by Cognee Inc., with no EU region today. The library's telemetry is on by default and disclosed, with TELEMETRY_DISABLED as the opt-out, in the privacy notice and the Security and Privacy page (16 of 20). The "anonymous" wording is charged once as a negative event, not here. 25 + 22 + 15 + 16 = 78.); Memori 52 (Apache-2.0 per the LICENSE text, though GitHub reports it as NOASSERTION (30). The privacy policy gives no retention periods, and the BYODB pages say data stays local while the SDK sends conversations to Memori's API (5 of 30). Changelog entries but no deprecation policy or notices (5 of 20). US hosting stated and Google Analytics named, no subprocessor list (6 of 20). Total 46.)
- Schema & documentation, Cognee +17: 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.); Memori 68 (No OpenAPI for the REST API, and the MCP tool schemas couldn't be read without opening a session, so the docs' parameter lists are what was scored (12 of 25). llms.txt with Markdown docs for both modes (10). Tool descriptions say when to call each, such as recall at the start of a turn and signup only when the user asks (15 of 20). Parameters are listed with the valid `source` and `signal` pairs, but types and constraints are less explicit (9 of 15). Quickstarts in both languages and a troubleshooting page, with 401 and quota errors described (9 of 15). Keep a Changelog with semantic versioning (13 of 15). Total 68.)
- Reliability, Cognee +15: 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.); Memori 28 (Hosted lines, since both modes call Memori's API. No status page found; status.memorilabs.ai did not answer and none is linked (0). No readable incident history (5). Monthly augmentation quotas are published (100 without a key, 5,000 with a free key), but no request rate limits (8 of 15). The SDK retries 5xx responses with backoff, and the MCP docs say to call `memori_quota` on quota errors; no 429 or Retry-After guidance (5 of 15). SLA only as a custom Enterprise term (0). No beta label on the cloud or MCP endpoint (10). Total 28.)
- Payments & pricing, Memori +10: 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.); Memori 45 (No x402, MPP or L402 (0 of 40). Plan prices are public but sales-led, from $60,000 a year (10). A free key with 5,000 augmentations a month, with no card mentioned (20). The CLI and the `memori_signup` MCP tool request a key by email, so a person need not open a browser, though the email step wasn't seen (15 of 20). Total 45.)
- Agent ergonomics, Memori +6: 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.); Memori 65 (Seven MCP tools with short parameter lists (22 of 25). Recall filters by project, session, date range and source (14 of 20). 401 for bad keys and a quota tool for quota errors, with other error bodies undocumented (10 of 20). No idempotency guidance or tool annotations documented (4 of 20). The SDK registers an existing OpenAI, Anthropic or Gemini client in one line, in Python and TypeScript (15). Total 65.)