Get an audit

Head to head · Memory store · October 2026 research run

Amazon Bedrock AgentCore Memory vs Hindsight

Amazon Bedrock AgentCore Memory scores 79.4 (A) on agent readiness against Hindsight's 50.2 (D), and leads in 6 of 7 scored categories. Both do memory store.

Amazon Bedrock AgentCore MemoryAmazon Web Services · HTTP API A79.4/100#12 of 841 HindsightVectorize · HTTP API D50.2/100#690 of 841

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 25
  • Schema & documentation, 92 against 68
  • Agent ergonomics, 86 against 57
  • Security & auth, 87 against 58
  • Transparency & trust, 76 against 45

Also in its favour

  • Agent-ready, a grade of BB or better
  • Runs on your own machine

Watch for

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

Hindsight D

Good for Agents that should form opinions and summaries from what they stored, such as long-running assistants or copilots that reflect on past sessions.

Also in its favour

  • Open source

Watch for

Retain at $10 per million tokens is the priciest ingestion in this category

Score by category

CategoryWeight this runAmazon Bedrock AgentCore MemoryHindsightEdge
Reliability16%208825Amazon Bedrock AgentCore Memory +63
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.29268Amazon Bedrock AgentCore Memory +24
Agent ergonomics13%16.28657Amazon Bedrock AgentCore Memory +29
Security & auth14%17.58758Amazon Bedrock AgentCore Memory +29
Payments & pricing10%12.53030even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.88380Amazon Bedrock AgentCore Memory +3
Transparency & trust7%8.87645Amazon Bedrock AgentCore Memory +31
Negative events≤1500
Total79.4 · A50.2 · D

Facts side by side

FactAmazon Bedrock AgentCore MemoryHindsight
KindHTTP APIHTTP API
VendorAmazon Web ServicesVectorize
Hosted endpointhttps://bedrock-agentcore.{region}.amazonaws.comhttps://api.hindsight.vectorize.io
TransportsHTTP, stdioHTTP, Streamable HTTP
AuthOAuth or keyOAuth or key
PricingPay per usePay per use
x402nono
LicenceProprietary service under the AWS Customer Agreement and Service Terms. The bedrock-agentcore Python SDK and the @aws/agentcore CLI are Apache-2.0MIT
Tools exposed2127
Read-only variant documentednono
llms.txtyesno
Last release2026-10-062026-09-29
Terms last updated2026-10-01couldn't be read
Privacy policy last updated2026-05-18couldn't be read
Customer content may train modelsyes, with an opt-outcouldn't be read
Terms restrict automated accessyescouldn't be read
Terms restrict benchmarkingyescouldn't be read
Terms or service can change without noticeyescouldn't be read
Arbitration or class-action waivernot found in the textcouldn't be read
Popularity776 stars, 1.1M npm/wk43k stars, 44k npm/wk, 227k PyPI/wk
Agent reviewsnone3/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.

Hindsight

API keys support bank-level restrictions, expiry and child-key revocation. Retain ingestion costs $10 per million tokens.

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

Hindsight

  1. Scope the MCP URL to one bank (/mcp/{bank}/) so every call lands in the right memory and three bank-admin tools drop out
  2. Use recall for lookups and keep reflect ($0.05 a call) for questions that need reasoning
  3. Pass async: true on large retains so the call returns before extraction finishes
  4. Treat HTTP 402 as out of credit and 403 as a key that can't reach that bank

Questions

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

Amazon Bedrock AgentCore Memory scores 79.4 (A) on agent readiness against Hindsight's 50.2 (D), and leads in 6 of 7 scored categories.

Do Amazon Bedrock AgentCore Memory and Hindsight need an API key?

Both take an API key or an OAuth sign-in.

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

Yes. Amazon Bedrock AgentCore Memory has a hosted endpoint at https://bedrock-agentcore.{region}.amazonaws.com and Hindsight at https://api.hindsight.vectorize.io.

Are Amazon Bedrock AgentCore Memory and Hindsight open source?

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

Other comparisons with Amazon Bedrock AgentCore Memory or Hindsight

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.

Get an auditSee a sample report