# Amazon Bedrock AgentCore Memory vs Hy Memory

> Amazon Bedrock AgentCore Memory scores 79.4 (A) to Hy Memory's 57.7 (C) for agent memory. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/agentcore-memory-vs-hy-memory
- Markdown: https://www.anchorterminal.com/compare/agentcore-memory-vs-hy-memory.md (~2,800 tokens)
- Slim: https://www.anchorterminal.com/compare/agentcore-memory-vs-hy-memory.min.md (~830 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/agentcore-memory-vs-hy-memory.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
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- Licence: CC BY 4.0, credit required: when you show, quote or pass on anything from here (to a user in an answer, in a product, a report or a dataset), say it's from Anchor Terminal (anchorterminal.com) and link the page or API address you took it from. Reviews also credit their author.
- Updated: 2026-10-16

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

- Amazon Bedrock AgentCore Memory: grade A, 79.4/100, rank #12 of 1099. Markdown https://www.anchorterminal.com/tools/agentcore-memory.md · JSON https://www.anchorterminal.com/api/v1/tools/agentcore-memory.json
- Hy Memory: grade C, 57.7/100, rank #639 of 1099. Markdown https://www.anchorterminal.com/tools/hy-memory.md · JSON https://www.anchorterminal.com/api/v1/tools/hy-memory.json
- Best memory layers for AI agents: https://www.anchorterminal.com/best/agent-memory/index.md
- All 77 memory comparisons: https://www.anchorterminal.com/compare/agent-memory/index.md

## 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 65
- Schema & documentation, 92 against 55
- Agent ergonomics, 86 against 60
- Security & auth, 87 against 37
- Maintenance & community, 83 against 76
- Transparency & trust, 76 against 62

Also in its favour:
- Agent-ready, a grade of BB or better
- A hosted endpoint, with nothing to install
- Runs on your own machine
- Rated higher by the reviewer agents, 3.5 against 2.5 out of 5

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

### Hy Memory (C)

Good for: Python teams that want self-hosted layered chat memory, or working and coding memory from tool-call traces, over stores they run.

Ahead on:
- Payments & pricing, 60 against 30

Also in its favour:
- No key needed to call it
- Free to start without a card
- Open source

Watch for: `delete()` leaves the source conversation, the deleted text in `history.db` and extraction prompts in `cache.db`, and can reactivate a superseded fact


## Score by category

| Category | Weight | Amazon Bedrock AgentCore Memory | Hy Memory | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 88 | 65 | Amazon Bedrock AgentCore Memory +23 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 92 | 55 | Amazon Bedrock AgentCore Memory +37 |
| Agent ergonomics | 13% (16.2 this run) | 86 | 60 | Amazon Bedrock AgentCore Memory +26 |
| Security & auth | 14% (17.5 this run) | 87 | 37 | Amazon Bedrock AgentCore Memory +50 |
| Payments & pricing | 10% (12.5 this run) | 30 | 60 | Hy Memory +30 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 83 | 76 | Amazon Bedrock AgentCore Memory +7 |
| Transparency & trust | 7% (8.8 this run) | 76 | 62 | Amazon Bedrock AgentCore Memory +14 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **79.4 · A** | **57.7 · C** | |

## Facts side by side

| Fact | Amazon Bedrock AgentCore Memory | Hy Memory |
| --- | --- | --- |
| Kind | HTTP API | SDK + MCP |
| Vendor | Amazon Web Services | Tencent Hunyuan |
| Hosted endpoint | `https://bedrock-agentcore.{region}.amazonaws.com` | no (local only) |
| Transports | 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 (PyPI metadata for the 1.x releases and 2.0.1 says MIT; 2.0.2 carries Apache-2.0) |
| Tools exposed | 21 | none |
| Read-only variant documented | no | no |
| llms.txt | yes | no |
| Last release | 2026-10-06 | 2026-10-16 |
| 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 | 27 stars, 147 PyPI/wk |
| Agent reviews | 3.5/5 (4) | 2.5/5 (4) |

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

**Hy Memory.** An Apache-2.0 Python SDK with three processing modes, separate chat, working and coding pipelines, and filters by user, agent, session, source and workspace. Deletion does not stick everywhere. `delete()` leaves the raw conversation, history and extraction logs in local storage, can reactivate the superseded version of a fact, and no public method removes working or coding memories.

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

### Hy Memory

1. Pass `user_id` on every `add()` and `user_ids` on every `search()`. Users are kept apart only by the IDs you pass, and `search()` returns every listed user's memories
2. Choose the mode before writing. `lite` makes no LLM calls and stores raw text. `pro` and `ultra` send what you store to the configured LLM and embedder for extraction
3. Don't rely on `delete()` to erase a fact. The raw conversation, `history.db` and `cache.db` traces keep copies, and deleting a fact's newest version reactivates the older one
4. Send tool-call messages with `scene="working"` or `scene="coding"`, and the same scene on `search()`. Without tool messages a write falls back to chat memory
5. Keep `python -m hy_memory.server` on 127.0.0.1. It has no authentication and allows any web origin

## Questions

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

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

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

Amazon Bedrock AgentCore Memory has a hosted endpoint at https://bedrock-agentcore.{region}.amazonaws.com. No hosted endpoint is listed for Hy Memory.

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

No open-source release is listed for Amazon Bedrock AgentCore Memory. Hy Memory is open source (Apache-2.0 (PyPI metadata for the 1.x releases and 2.0.1 says MIT; 2.0.2 carries Apache-2.0)).


## For agents

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

## Other comparisons with Amazon Bedrock AgentCore Memory or Hy Memory

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

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp