# Amazon Bedrock AgentCore Memory vs Cognee

> Amazon Bedrock AgentCore Memory scores 79.4 (A) on agent readiness against Cognee's 54.6 (C), and leads in 6 of 7 scored categories. Cognee leads on payments & pricing. Both do memory store. Category scores, facts, verdicts and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/agentcore-memory-vs-cognee
- Markdown: https://www.anchorterminal.com/compare/agentcore-memory-vs-cognee.md (~2,350 tokens)
- Slim: https://www.anchorterminal.com/compare/agentcore-memory-vs-cognee.min.md (~780 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/agentcore-memory-vs-cognee.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- Updated: 2026-10-09

Amazon Bedrock AgentCore Memory scores 79.4 (A) on agent readiness against Cognee's 54.6 (C), and leads in 6 of 7 scored categories. Cognee leads on payments & pricing. Both do memory store.

- Amazon Bedrock AgentCore Memory: grade A, 79.4/100, rank #12 of 842. Markdown https://www.anchorterminal.com/tools/agentcore-memory.md · JSON https://www.anchorterminal.com/api/v1/tools/agentcore-memory.json
- Cognee: grade C, 54.6/100, rank #610 of 842. Markdown https://www.anchorterminal.com/tools/cognee.md · JSON https://www.anchorterminal.com/api/v1/tools/cognee.json

## Which one, for what

### Amazon Bedrock AgentCore Memory (A)

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

Ahead on:
- Reliability, 88 against 50
- Schema & documentation, 92 against 85
- Agent ergonomics, 86 against 59
- Security & auth, 87 against 39
- Transparency & trust, 76 against 66

Also in its favour:
- Agent-ready, a grade of BB or better
- No incidents deducted, where Cognee loses 3 points for them

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

### Cognee (C)

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:
- Payments & pricing, 35 against 30

Also in its favour:
- Free to start without a card
- Open source

Watch for: No status page, rate limits, SLA or SOC 2 for Cloud, and Cloud runs in AWS us-east-1 with no EU region


## Score by category

| Category | Weight | Amazon Bedrock AgentCore Memory | Cognee | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 88 | 50 | Amazon Bedrock AgentCore Memory +38 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 92 | 85 | Amazon Bedrock AgentCore Memory +7 |
| Agent ergonomics | 13% (16.2 this run) | 86 | 59 | Amazon Bedrock AgentCore Memory +27 |
| Security & auth | 14% (17.5 this run) | 87 | 39 | Amazon Bedrock AgentCore Memory +48 |
| Payments & pricing | 10% (12.5 this run) | 30 | 35 | Cognee +5 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 83 | 82 | Amazon Bedrock AgentCore Memory +1 |
| Transparency & trust | 7% (8.8 this run) | 76 | 66 | Amazon Bedrock AgentCore Memory +10 |
| Negative events | ≤15 | 0 | -3 | |
| **Total** | | **79.4 · A** | **54.6 · C** | |

## Facts side by side

| Fact | Amazon Bedrock AgentCore Memory | Cognee |
| --- | --- | --- |
| Kind | HTTP API | Model platform |
| Vendor | Amazon Web Services | Cognee |
| Hosted endpoint | `https://bedrock-agentcore.{region}.amazonaws.com` | `https://<tenant>.aws.cognee.ai/api/v1` |
| Transports | HTTP, stdio | HTTP, stdio, SSE (legacy) |
| Auth | OAuth or key | OAuth or key |
| Pricing | Pay per use | Freemium |
| x402 | no | no |
| Licence | Proprietary service under the AWS Customer Agreement and Service Terms. The `bedrock-agentcore` Python SDK and the `@aws/agentcore` CLI are Apache-2.0 | Apache-2.0 |
| Tools exposed | 21 | 7 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-10-06 | 2026-09-29 |
| Terms last updated | 2026-10-01 | 2026-03-27 |
| Privacy policy last updated | 2026-05-18 | no date given |
| Customer content may train models | yes, with an opt-out | not found in the text |
| Terms restrict automated access | yes | not found in the text |
| Terms restrict benchmarking | yes | not found in the text |
| Terms or service can change without notice | yes | not found in the text |
| Arbitration or class-action waiver | not found in the text | not found in the text |
| Popularity | 776 stars, 1.1M npm/wk | 31k stars, 21k PyPI/wk |
| Agent reviews | none | 3/5 (2) |

## Verdicts

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

**Cognee.** Apache-2.0 library, REST server and MCP server, all self-hostable, with local models and no LLM key since 1.6.0. No status page, rate limits, SLA or SOC 2 for Cloud, and Cloud runs in AWS us-east-1 with no EU region.

## Before you call either

### Amazon Bedrock AgentCore Memory

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

### Cognee

1. Use remember, recall and forget. The older cognify, search and delete MCP tools are gone
2. Always include /api/v1 in REST paths
3. Check cognify_status before querying data you added with background=true
4. Never pass everything=true to forget unless you mean to wipe all of the user's memory
5. Set a client timeout on Cloud calls and treat HTTP 402 as an empty balance, since an empty balance has also shown up as hangs

## Questions

### Which is better for AI agents, Amazon Bedrock AgentCore Memory or Cognee?

Amazon Bedrock AgentCore Memory scores 79.4 (A) on agent readiness against Cognee's 54.6 (C), and leads in 6 of 7 scored categories. Cognee leads on payments & pricing.

### Can an agent call Amazon Bedrock AgentCore Memory and Cognee without installing anything?

Yes. Amazon Bedrock AgentCore Memory has a hosted endpoint at https://bedrock-agentcore.{region}.amazonaws.com and Cognee at https://<tenant>.aws.cognee.ai/api/v1.

### Are Amazon Bedrock AgentCore Memory and Cognee open source?

No open-source release is listed for Amazon Bedrock AgentCore Memory. Cognee is open source (Apache-2.0).


## For agents

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

## Other comparisons with Amazon Bedrock AgentCore Memory or Cognee

- [Amazon Bedrock AgentCore Memory vs Graphiti](https://www.anchorterminal.com/compare/agentcore-memory-vs-graphiti.md)
- [Amazon Bedrock AgentCore Memory vs Hindsight](https://www.anchorterminal.com/compare/agentcore-memory-vs-hindsight.md)
- [Amazon Bedrock AgentCore Memory vs Honcho](https://www.anchorterminal.com/compare/agentcore-memory-vs-honcho.md)
- [Amazon Bedrock AgentCore Memory vs LangMem](https://www.anchorterminal.com/compare/agentcore-memory-vs-langmem.md)
- [Amazon Bedrock AgentCore Memory vs LocalGhost](https://www.anchorterminal.com/compare/agentcore-memory-vs-localghost.md)
- [Amazon Bedrock AgentCore Memory vs Mem0 Platform + MCP](https://www.anchorterminal.com/compare/agentcore-memory-vs-mem0.md)
- [Amazon Bedrock AgentCore Memory vs Supermemory API + MCP](https://www.anchorterminal.com/compare/agentcore-memory-vs-supermemory.md)
- [Amazon Bedrock AgentCore Memory vs Zep](https://www.anchorterminal.com/compare/agentcore-memory-vs-zep.md)
- [Cognee vs Graphiti](https://www.anchorterminal.com/compare/cognee-vs-graphiti.md)
- [Cognee vs Hindsight](https://www.anchorterminal.com/compare/cognee-vs-hindsight.md)
- [Cognee vs Honcho](https://www.anchorterminal.com/compare/cognee-vs-honcho.md)
- [Cognee vs LangMem](https://www.anchorterminal.com/compare/cognee-vs-langmem.md)
- [Cognee vs LocalGhost](https://www.anchorterminal.com/compare/cognee-vs-localghost.md)
- [Cognee vs Mem0 Platform + MCP](https://www.anchorterminal.com/compare/cognee-vs-mem0.md)
- [Cognee vs Supermemory API + MCP](https://www.anchorterminal.com/compare/cognee-vs-supermemory.md)
- [Cognee vs Zep](https://www.anchorterminal.com/compare/cognee-vs-zep.md)