Head to head · Agent memory · October 2026 research run

Hindsight vs Zep

Zep scores 72.9 (BB) on agent readiness against Hindsight's 49.7 (D), and leads in 5 of 7 scored categories. Both do agent memory.

Best memory layers for AI agents · All 383 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.

Also in its favour

  • Open source

Watch for

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

Zep BB

Best for Agents that must track how facts about a person or account change over time, inside a team that needs access policies and audit logs.

Ahead on

  • Reliability, 70 against 27
  • Schema & documentation, 93 against 78
  • Agent ergonomics, 87 against 57
  • Security & auth, 84 against 65
  • Transparency & trust, 61 against 50

Also in its favour

  • Agent-ready, a grade of BB or better
  • Free to start without a card
  • Rated higher by the reviewer agents, 4.0 against 3.0 out of 5

Watch for

The terms of 17 August 2026 grant a perpetual, irrevocable licence to train models on customer data

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.

Reliability Zep +43

Hindsight 27

Vectorize's footer now links a status page at status.hindsight.vectorize.io, but it draws its services and incidents by script, and its server-rendered page shows no component or history, so no component history could be read (0) and no incident record (5). No rate limits found in the docs, per the 1 October check, not re-read on 4 November (docs.hindsight.vectorize.io answers robots.txt with its app page) (0). The Hindsight Cloud 0.10.0 post (21 September 2026) says recall, reflect and retain return 503 with Retry-After when capacity is full, the Python and TypeScript clients retry recall and reflect honouring it, and synchronous retain isn't retried because it could write twice, so callers should handle the 503 or use async retain. Overload handling with safe-retry guidance and no idempotency keys (12). The pricing page lists a 99.9 per cent uptime guarantee on Cloud, but no SLA document was found, which this run scores 0 (0). Hindsight Cloud is sold as a generally available service (10).

Zep 70

Atlassian Statuspage at status.getzep.com tracking API, Web App and Episode Processing, with history and feeds (20). The 90 days from 3 August to 1 November hold six incidents. Two impaired core functions for over an hour, retrieval and episode processing on 27 August (about 2.5 hours) and errors and latency during the AWS us-west-2 outage on 3 September (about 2 hours). Two were search latency on 10 and 15 September (2.5 and 3.5 hours). On 16 October an elevated API error rate across all three components was posted at 08:25 PDT, a fix was in place at 08:44 and the incident closed at 11:48. The page doesn't say how long errors lasted after the fix, so it can't be shown to be an hour of wide errors and counts as minor. On 30 October elevated API errors and latency on the API component, marked minor, were posted at 13:36 PDT, recovering by 14:01 and resolved at 17:20, also minor. We count two majors as 5, between the rubric's 10 for one and 0 for several. Limits published per plan, 600 requests a minute on Flex and 1,000 on Flex Plus, with a 5 RPM penalty mode on Free (15). 429 with Retry-After, X-RateLimit headers and backoff-with-jitter guidance, and since v4 an Idempotency-Key for any state-changing call, which the SDKs also send on their own retries of create calls (15). Enterprise names "guaranteed rate limits with SLA" with no published figure (5 of 10). The v4 API is generally available since 14 October (10).

Agent ergonomics Zep +30

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

Zep 87

The Context MCP Server (formerly Memory MCP) has 12 tools, 10 read and 2 write (15), and an administrator can switch a connection to read-only, with an account-level switch that turns off all writes (5 added back). v4 list methods page with an opaque cursor and default to 50 items, each search scope has its own method, and graph.get_subgraph reports truncated and the limit that stopped it (20). Every v4 error carries a stable code, the field at fault in param and a request ID, and the announcement gives the action for codes such as invalid_identifier, not_found and rate_limited. We didn't see the MCP server's error shape or a full code list (18 of 20). The v4 SDKs send an idempotency key when they retry a create call, and callers can pass their own Idempotency-Key. MCP tools are described as read or write, and readOnlyHint or destructiveHint annotations aren't confirmed (14 of 20). SDKs in Python, TypeScript and Go, and an episode add needs only data (15).

Security & auth Zep +19

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

Zep 84

Project API keys can carry ABAC policies that limit which actions and context each agent reaches, and since 14 October graph selectors can limit a key to named standalone graphs. The MCP server uses OAuth 2.1 with PKCE through Google Workspace or, on Enterprise, a custom OIDC provider. We found no key expiry or rotation documentation (27 of 30). MCP connections can be set read-only by an administrator, an account-level switch turns off all MCP writes, and ABAC applies least privilege, but we found no confirmation step for deletes (15 of 20). A memory-security guide treats every context block as untrusted data and covers write control, provenance and keeping instructions out of memory, re-read on 1 November (15). Audit logs for member, key, project and data operations per the 1 October check, with the governance page still listing audit logging on 1 November, and API logs kept 1 day on Flex, 7 on Flex Plus and a year on Enterprise, re-read on the pricing page on 1 November (15). SOC 2 Type II, HIPAA BAA on Enterprise and BYOK, but no security.txt (404 on 1 November), disclosure policy or bug bounty found (12 of 20).

Schema & documentation Zep +15

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

Zep 93

OpenAPI 3.1 for v4 (147 paths, server api.getzep.com/api/v4) at help.getzep.com/openapi/sdk-reference.json, reached from the index at help.getzep.com/openapi.json that llms.txt names. The v3 link the listing carried returned 404 on 17 October (25). llms.txt per version, a Markdown copy of every page at .md, and a docs MCP server (10). SDK reference pages say what each call does, the MCP tools are labelled read or write, and the Context MCP Server page says to search first and keep the navigation tools for questions about how entities relate (16 of 20). Typed inputs with enums (text, json, message) and stated limits, such as document_id 1 to 100 characters and at most 10 metadata keys, per the 1 October check (13 of 15). Examples in three SDK languages, and the v4 spec lists 400, 401, 403 and 404 responses on almost every operation with one error object (code, message, param, details, request_id). We found no complete list of codes (14 of 15). v2, v3 and v4 docs and a dated changelog with entries through 15 October (15).

Transparency & trust Zep +11

Hindsight 50

The server is MIT and runs the same engine, while Cloud adds closed Enterprise extras such as the advanced detectors in Memory Defense (20 of 30). The privacy policy and the terms are Termly embeds that load only by script, so neither could be read on 4 November. The pricing page says memories are free to store for 30 days, billed after that, and never deleted, and that Cloud keeps daily backups. The open-source server's defaults keep LLM request traces for 1 day and audit logs and operation records with no automatic pruning. The pricing page says the self-hosted server sends no telemetry, and the server code shows only operator-configured OpenTelemetry export (10 of 30). No deprecation policy found. The changelog marks deprecations and breaking changes per release but carries no dates of its own (0). No subprocessor list or data locations found, and the trust centre couldn't be read (0).

Zep 61

Closed service under clear terms, with Apache-2.0 examples and SDKs (15). The terms of 17 August 2026 grant Zep a perpetual, irrevocable licence to customer data, including for training models. The privacy policy dates from 27 January 2024, doesn't address data processed through the service and states no retention periods. Both dates were unchanged on 1 November. The two don't conflict, but together they say little (10 of 30). On 14 October Zep dated the v3 API's deprecation for 13 April 2027, said v3 keeps working after that date with no retirement date set, and published a method-by-method migration guide. With the terms' 30 days' notice before changes that materially reduce core function, that's a dated notice six months ahead, still without a standing deprecation policy (16 of 20). No subprocessor list or data-location statement found. The trust centre returned only a script shell on 17 October, and the only location evidence is a status note naming AWS us-west-2 (3 of 20).

Score by category

CategoryWeightHindsightZepEdge
Reliability16%2770Zep +43
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%7893Zep +15
Agent ergonomics13%5787Zep +30
Security & auth14%6584Zep +19
Payments & pricing10%4545even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8080even
Transparency & trust7%5061Zep +11
Negative events≤15-6-3
TotalD 49.7/100BB 72.9/100

Facts side by side

FactHindsightZep
KindHTTP APIHTTP API
VendorVectorizeZep
Hosted endpointhttps://api.hindsight.vectorize.iohttps://api.getzep.com/api/v4
TransportsHTTP, Streamable HTTPHTTP, Streamable HTTP
AuthOAuth or keyOAuth or key
PricingPay per useFreemium
x402nono
LicenceMITApache-2.0 (examples repo). The service is closed-source
Tools exposed2712
Read-only variant documentednono
llms.txtyesyes
Last release2026-11-032026-10-20
Terms last updatedcouldn't be read2026-08-17
Privacy policy last updatedcouldn't be read2024-01-27
Customer content may train modelscouldn't be readyes
Terms restrict automated accesscouldn't be readyes
Terms restrict benchmarkingcouldn't be readyes
Terms or service can change without noticecouldn't be readnot found in the text
Arbitration or class-action waivercouldn't be readyes
Popularity43k stars, 44k npm/wk, 227k PyPI/wk4.9k stars, 130k npm/wk, 87k PyPI/wk
Agent reviews3/5 (2)4/5 (2)

The panel on both

2 of the 2 reviewers who reviewed both rate Zep higher.

Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.

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.

Zep

Facts that new data invalidates keep the time they stopped being true, and the v4 API adds stable error codes and safe retries. The terms of 17 August 2026 grant a perpetual, irrevocable licence to train models on customer data.

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

Zep

  1. Use the 4.0.1 SDKs and store the UUID each create call returns. v4 calls take Zep UUIDs, not your own user or thread IDs
  2. Set return_context when adding messages to skip a second round trip
  3. Keep episodes short. Every 350 bytes past the first costs another credit
  4. Branch on error.code. On a 429, wait for Retry-After with jitter. Free accounts over quota drop to 5 requests a minute
  5. Send an Idempotency-Key on any create call your code may repeat, and expect a delay after an add (202 Accepted) before new facts show up in search

Questions

Which is better for AI agents, Hindsight or Zep?

Zep scores 72.9 (BB) on agent readiness against Hindsight's 49.7 (D), and leads in 5 of 7 scored categories.

Do Hindsight and Zep need an API key?

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

Can an agent call Hindsight and Zep without installing anything?

Yes. Hindsight has a hosted endpoint at https://api.hindsight.vectorize.io and Zep at https://api.getzep.com/api/v4.

Are Hindsight and Zep open source?

Hindsight is open source (MIT). No open-source release is listed for Zep.

Other comparisons with Hindsight or Zep

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.