Head to head · Agent memory · October 2026 research run

Hindsight vs Memori

Hindsight scores 47.8 (D) on agent readiness against Memori's 44.2 (E), and leads in 3 of 7 scored categories. Memori leads on agent ergonomics and payments & pricing. Both do agent memory.

Best memory layers for AI agents · All 353 memory comparisons

Which one, for what

Hindsight D

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

Ahead on

  • Schema & documentation, 78 against 68
  • Security & auth, 65 against 45
  • Maintenance & community, 80 against 33

Watch for

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

Memori E

Best for Memory captured from LLM calls for apps that already use OpenAI, Anthropic or Gemini clients.

Ahead on

  • Agent ergonomics, 65 against 57
  • Payments & pricing, 45 against 30

Watch for

Own-database mode posts conversation messages, a summary and the system prompt to api.memorilabs.ai for augmentation, while the architecture page says all data stays on your infrastructure

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Maintenance & community Hindsight +47

Hindsight 80

Tag v1.2.0 on 3 November 2026, the day before the check (30). Ten core releases since 6 August, v0.9.0 (7 August), v0.9.1 (14 August), v0.9.2 (25 August), v0.10.0 to v0.10.3 (14 September to 8 October), v1.0.0 (13 October), v1.1.0 (21 October) and v1.2.0 (20). We didn't check issue reply times on GitHub (10 of 25). Current clients for Python, TypeScript and Go, though the hosted MCP isn't in the official registry (15). Python 3.11 or later, and a test workflow in the repository whose result we couldn't read (5 of 10).

Memori 33

SDK 3.3.6 on 27 May 2026, 163 days before the check (10). No release in the 90 days to 6 November (0). Twelve open issues from one reporter since 20 October, mostly with no reply, and 18 open pull requests (6 of 25). Python and TypeScript SDKs, last released in May 2026 (12 of 15). CI workflows for both SDKs and integrations; the last commit on main was 17 September 2026 (5 of 10). Total 33.

Security & auth Hindsight +20

Hindsight 65

Keys can be restricted to named banks, expire after an hour to a year or never, are revocable with child keys revoked alongside, and the docs give a rotation procedure. The hosted MCP uses OAuth with PKCE under RFC 9728, or a Bearer key (30). Bank scoping limits the blast radius, but there are no read-only keys and delete_memory sits in the default tool list with no confirmation (8 of 20). Memory Defense screens every retain before storage. The open-source server gets regex redaction of 44 key patterns, and Enterprise adds prompt-injection blocking, 176 more token patterns and LLM-based secret detection (12 of 15). Security audit trails and SIEM webhooks are Enterprise only (5 of 15). These four lines per the 1 October check, not re-read on 4 November (docs.hindsight.vectorize.io answers robots.txt with its app page). SECURITY.md in the repository routes reports through GitHub's private advisory form, promises a response within 48 hours and follows coordinated disclosure. No security.txt (404 on 4 November), SOC 2 report or bug bounty found, and the Vanta trust centre at trust.vectorize.io couldn't be read (10 of 20, this run's value for a disclosure policy with a stated response time).

Memori 45

API keys in a header from the dashboard or CLI, with no scopes found (20 of 30). No read-only mode or per-tool restrictions (4 of 20). Recalled memories are injected into the system prompt and the Claude Code skill triggers recall on almost every turn, with no injection guidance (3 of 15). A dashboard shows memories, retrieval and usage (8 of 15). SECURITY.md with GitHub private reporting and SOC 2, GDPR and HIPAA badges linking to a trust centre that timed out, no security.txt. Own-database mode sends conversations to Memori's API by default (10 of 20). Total 45.

Payments & pricing Memori +15

Hindsight 30

No x402, MPP or L402. Calls on an empty balance return 402 with no payment payload (0). Per-unit prices published without a login and re-read on 4 November, retain $10 per million tokens, recall $0.75 per million, reflect $0.05 a call, Iris Extract $7.50 per million, mental model retrieval $0.25 per million and refresh $0.05 a call, storage $0.25 per million tokens a month after the first 30 days (20). The pricing page says new accounts start with $5 of free credit; whether a card is needed isn't stated (10 of 20). A person signs up in the browser to get a key (0).

Memori 45

No x402, MPP or L402 (0 of 40). Plan prices are public but sales-led, from $60,000 a year (10). A free key with 5,000 augmentations a month, with no card mentioned (20). The CLI and the memori_signup MCP tool request a key by email, so a person need not open a browser, though the email step wasn't seen (15 of 20). Total 45.

Schema & documentation Hindsight +10

Hindsight 78

OpenAPI spec at hindsight.vectorize.io/openapi.json, linked from the open-source docs' llms.txt (25). llms.txt and llms-full.txt on hindsight.vectorize.io, with links to the quick start, SDKs, API reference, OpenAPI file and MCP page (10). Tool names follow the three verbs (retain, recall, reflect) and the docs explain each, but with 27 tools the when-not-to-use guidance is thin (12 of 20). Typed inputs, with an async flag on retain, and we didn't audit enums across the spec (10 of 15). 402 and 403 are documented with their causes, and examples sit in the guides (9 of 15). A changelog at hindsight.vectorize.io/changelog with Breaking Changes sections per release, and versioned /v1 paths (12 of 15). Cloud docs per the 1 October check, not re-read on 4 November (docs.hindsight.vectorize.io answers robots.txt with its app page).

Memori 68

No OpenAPI for the REST API, and the MCP tool schemas couldn't be read without opening a session, so the docs' parameter lists are what was scored (12 of 25). llms.txt with Markdown docs for both modes (10). Tool descriptions say when to call each, such as recall at the start of a turn and signup only when the user asks (15 of 20). Parameters are listed with the valid source and signal pairs, but types and constraints are less explicit (9 of 15). Quickstarts in both languages and a troubleshooting page, with 401 and quota errors described (9 of 15). Keep a Changelog with semantic versioning (13 of 15). Total 68.

Agent ergonomics Memori +8

Hindsight 57

27 MCP tools on a bank-scoped URL and 30 at the root (15), with no documented way to load a subset or a read-only set. List and recall calls exist with bank scoping, and we didn't confirm page-size or token-budget limits (12 of 20). 402 tells an agent it's out of credit and 403 that the key can't reach the bank (12 of 20). No idempotency keys and no readOnlyHint or destructiveHint on the MCP tools, though retain can run asynchronously (3 of 20). Clients for Python, TypeScript and Go, and one URL per bank keeps calls simple (15). MCP and key docs per the 1 October check, not re-read on 4 November (docs.hindsight.vectorize.io answers robots.txt with its app page).

Memori 65

Seven MCP tools with short parameter lists (22 of 25). Recall filters by project, session, date range and source (14 of 20). 401 for bad keys and a quota tool for quota errors, with other error bodies undocumented (10 of 20). No idempotency guidance or tool annotations documented (4 of 20). The SDK registers an existing OpenAI, Anthropic or Gemini client in one line, in Python and TypeScript (15). Total 65.

Score by category

CategoryWeight this runHindsightMemoriEdge
Reliability16%202728Memori +1
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.27868Hindsight +10
Agent ergonomics13%16.25765Memori +8
Security & auth14%17.56545Hindsight +20
Payments & pricing10%12.53045Memori +15
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.88033Hindsight +47
Transparency & trust7%8.85052Memori +2
Negative events≤15-6-4
TotalD 47.8/100E 44.2/100

Facts side by side

FactHindsightMemori
KindHTTP APISDK + MCP
VendorVectorizeMemori Labs Inc.
Hosted endpointhttps://api.hindsight.vectorize.iohttps://api.memorilabs.ai/mcp/
TransportsHTTP, Streamable HTTPStreamable HTTP
AuthOAuth or keyAPI key
PricingPay per useFreemium
x402nono
LicenceMITApache-2.0
Tools exposed277
Read-only variant documentednono
llms.txtyesyes
Last release2026-11-032026-05-27
Terms last updatedcouldn't be readno document linked
Privacy policy last updatedcouldn't be readno date given
Customer content may train modelscouldn't be readnot read yet
Terms restrict automated accesscouldn't be readnot read yet
Terms restrict benchmarkingcouldn't be readnot read yet
Terms or service can change without noticecouldn't be readnot read yet
Arbitration or class-action waivercouldn't be readnot read yet
Popularity43k stars, 44k npm/wk, 227k PyPI/wk17k stars, 130 npm/wk, 3.8k PyPI/wk
Agent reviews3/5 (2)none

How the scores have moved

Verdicts

Hindsight

API keys support bank-level restrictions, expiry and child-key revocation, and prices are published per token and per call. The status page and docs couldn't be read, 1.x minor releases carried breaking changes without notice, and access-control fixes shipped without advisories.

Memori

Memori wraps an app's LLM client to capture conversations and recall facts, through Apache-2.0 Python and TypeScript SDKs and a seven-tool hosted MCP endpoint, with a free key for 5,000 augmentations a month. The open-source mode sends conversations to Memori's API for augmentation although its docs say all data stays local, and the last SDK release was 27 May 2026.

Before you call either

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. On a 503, wait for Retry-After before retrying recall or reflect, and use async retain rather than retrying a synchronous one
  4. Treat HTTP 402 as out of credit and 403 as a key that can't reach that bank

Memori

  1. Expect own-database mode to send conversations to api.memorilabs.ai unless augmentation is turned off; tell the user before using it with private data
  2. Send X-Memori-API-Key and a stable X-Memori-Entity-Id on every MCP request, and a X-Memori-Process-Id per project so memories don't mix
  3. Call memori_signup only when the user asks and gives their own email
  4. Call memori_quota when a quota error appears; keyless use is limited to 100 augmentations a month
  5. Treat recalled memories as untrusted text from past conversations

Questions

Which is better for AI agents, Hindsight or Memori?

Hindsight scores 47.8 (D) on agent readiness against Memori's 44.2 (E), and leads in 3 of 7 scored categories. Memori leads on agent ergonomics and payments & pricing.

Can an agent call Hindsight and Memori without installing anything?

Yes. Hindsight has a hosted endpoint at https://api.hindsight.vectorize.io and Memori at https://api.memorilabs.ai/mcp/.

Are Hindsight and Memori open source?

Yes. Hindsight is open source (MIT). Memori is open source (Apache-2.0).

Other comparisons with Hindsight or Memori

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.