# Amazon Bedrock AgentCore Memory vs LangMem

> Amazon Bedrock AgentCore Memory scores 79.4 (A) on agent readiness against LangMem's 47.9 (D), and leads in 6 of 7 scored categories. LangMem 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-langmem
- Markdown: https://www.anchorterminal.com/compare/agentcore-memory-vs-langmem.md (~2,400 tokens)
- Slim: https://www.anchorterminal.com/compare/agentcore-memory-vs-langmem.min.md (~780 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/agentcore-memory-vs-langmem.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 LangMem's 47.9 (D), and leads in 6 of 7 scored categories. LangMem 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
- LangMem: grade D, 47.9/100, rank #734 of 842. Markdown https://www.anchorterminal.com/tools/langmem.md · JSON https://www.anchorterminal.com/api/v1/tools/langmem.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 32
- Schema & documentation, 92 against 55
- Agent ergonomics, 86 against 66
- Security & auth, 87 against 45
- Maintenance & community, 83 against 15
- Transparency & trust, 76 against 59

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

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

### LangMem (D)

Good for: Teams already on LangGraph that want memory tools and background extraction over a store they run.

Ahead on:
- Payments & pricing, 60 against 30

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

Watch for: The newest PyPI release, 0.0.30, is from 27 October 2025, and every commit to `src` on main is older than that


## Score by category

| Category | Weight | Amazon Bedrock AgentCore Memory | LangMem | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 88 | 32 | Amazon Bedrock AgentCore Memory +56 |
| 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 | 66 | Amazon Bedrock AgentCore Memory +20 |
| Security & auth | 14% (17.5 this run) | 87 | 45 | Amazon Bedrock AgentCore Memory +42 |
| Payments & pricing | 10% (12.5 this run) | 30 | 60 | LangMem +30 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 83 | 15 | Amazon Bedrock AgentCore Memory +68 |
| Transparency & trust | 7% (8.8 this run) | 76 | 59 | Amazon Bedrock AgentCore Memory +17 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **79.4 · A** | **47.9 · D** | |

## Facts side by side

| Fact | Amazon Bedrock AgentCore Memory | LangMem |
| --- | --- | --- |
| Kind | HTTP API | SDK + MCP |
| Vendor | Amazon Web Services | LangChain |
| 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 | MIT |
| Tools exposed | 21 | none |
| Read-only variant documented | no | no |
| llms.txt | yes | no |
| Last release | 2026-10-06 | 2025-10-27 |
| 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 | 1.7k stars, 214k PyPI/wk |

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

**LangMem.** Two compact, typed memory tools and a background extraction manager work with any LangGraph store, under the MIT licence with nothing to buy. The newest PyPI release, 0.0.30, dates from 27 October 2025. The repository has no changelog, tags or test workflow, and 23 of 54 open issues have no reply.

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

### LangMem

1. Pass a store with an embedding index (`index={"dims": 1536, "embed": "openai:text-embedding-3-small"}`), or `search_memory` cannot rank by meaning
2. Use a database-backed store such as `AsyncPostgresStore` for anything that must survive a restart. `InMemoryStore` loses everything
3. Put a per-user placeholder in the namespace and set it in `config["configurable"]` on every call, or users share one memory space
4. Send the memory `id` with `update` and `delete`, and never with `create`. A retried `create` writes a duplicate under a new UUID
5. Run on Python 3.11 or later. `src/langmem/knowledge/extraction.py` uses `typing.NotRequired`, which Python 3.10 lacks

## Questions

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

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

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

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

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

No open-source release is listed for Amazon Bedrock AgentCore Memory. LangMem is open source (MIT).


## For agents

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

## Other comparisons with Amazon Bedrock AgentCore Memory or LangMem

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