# Amazon Bedrock AgentCore Memory vs Graphiti

> Amazon Bedrock AgentCore Memory scores 79.4 (A) on agent readiness against Graphiti's 53.3 (D), and leads in 6 of 7 scored categories. Graphiti 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-graphiti
- Markdown: https://www.anchorterminal.com/compare/agentcore-memory-vs-graphiti.md (~2,300 tokens)
- Slim: https://www.anchorterminal.com/compare/agentcore-memory-vs-graphiti.min.md (~780 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/agentcore-memory-vs-graphiti.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 Graphiti's 53.3 (D), and leads in 6 of 7 scored categories. Graphiti 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
- Graphiti: grade D, 53.3/100, rank #632 of 842. Markdown https://www.anchorterminal.com/tools/graphiti.md · JSON https://www.anchorterminal.com/api/v1/tools/graphiti.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 71
- Agent ergonomics, 86 against 51
- Security & auth, 87 against 23
- Maintenance & community, 83 against 65
- Transparency & trust, 76 against 71

Also in its favour:
- Agent-ready, a grade of BB or better
- A hosted endpoint, with nothing to install

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

### Graphiti (D)

Good for: Teams that want Zep's temporal graph model on their own infrastructure and can run a graph database.

Ahead on:
- Payments & pricing, 60 against 30

Also in its favour:
- No key needed to call it
- Open source

Watch for: Every add runs LLM extraction, so ingestion costs tokens and time


## Score by category

| Category | Weight | Amazon Bedrock AgentCore Memory | Graphiti | 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 | 71 | Amazon Bedrock AgentCore Memory +21 |
| Agent ergonomics | 13% (16.2 this run) | 86 | 51 | Amazon Bedrock AgentCore Memory +35 |
| Security & auth | 14% (17.5 this run) | 87 | 23 | Amazon Bedrock AgentCore Memory +64 |
| Payments & pricing | 10% (12.5 this run) | 30 | 60 | Graphiti +30 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 83 | 65 | Amazon Bedrock AgentCore Memory +18 |
| Transparency & trust | 7% (8.8 this run) | 76 | 71 | Amazon Bedrock AgentCore Memory +5 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **79.4 · A** | **53.3 · D** | |

## Facts side by side

| Fact | Amazon Bedrock AgentCore Memory | Graphiti |
| --- | --- | --- |
| Kind | HTTP API | Agent framework |
| Vendor | Amazon Web Services | Zep |
| Hosted endpoint | `https://bedrock-agentcore.{region}.amazonaws.com` | no (local only) |
| Transports | HTTP, stdio | Streamable HTTP, stdio |
| Auth | OAuth or key | None |
| Pricing | Pay per use | Free |
| 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 | 13 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-10-06 | 2026-09-08 |
| Terms last updated | 2026-10-01 | no document linked |
| Privacy policy last updated | 2026-05-18 | no document linked |
| Customer content may train models | yes, with an opt-out |  |
| Terms restrict automated access | yes |  |
| Terms restrict benchmarking | yes |  |
| Terms or service can change without notice | yes |  |
| Arbitration or class-action waiver | not found in the text |  |
| Popularity | 776 stars, 1.1M npm/wk | 29k stars, 151k PyPI/wk |
| Agent reviews | none | 2.5/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.

**Graphiti.** Apache-2.0, with FalkorDB, Neo4j or Amazon Neptune as the store. Every add runs LLM extraction, so ingestion costs tokens and time.

## 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`

### Graphiti

1. Set OPENAI_API_KEY (or another provider's key) and MODEL_NAME before starting the MCP server
2. Use search_memory_facts for facts and search_nodes for entities instead of reading whole episodes
3. Never call clear_graph to fix one fact. Use delete_episode or delete_entity_edge
4. Pass group_ids on every search and add so one user's graph doesn't leak into another's
5. Call get_status to check the database connection before a long ingest

## Questions

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

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

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

Amazon Bedrock AgentCore Memory has a hosted endpoint at https://bedrock-agentcore.{region}.amazonaws.com. Graphiti runs on your own machine, with no hosted endpoint listed.

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

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


## For agents

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

## Other comparisons with Amazon Bedrock AgentCore Memory or Graphiti

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