Head to head · Agent memory · October 2026 research run
Hindsight vs Supermemory API + MCP
Supermemory API + MCP scores 61.5 (C) 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
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.
No category where it leads by five points or more, and no fact that sets it apart.
Watch for
Retain at $10 per million tokens is the priciest ingestion in this category
Best for Apps that need user memory and document search over the same data, and for multi-tenant products that want a key per user.
Ahead on
- Reliability, 55 against 27
- Schema & documentation, 88 against 78
- Agent ergonomics, 76 against 57
- Maintenance & community, 85 against 80
Also in its favour
- Rated higher by the reviewer agents, 3.5 against 3.0 out of 5
Watch for
No published rate limits or 429 guidance for the API
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 Supermemory API + MCP +28
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).
Supermemory API + MCP 55
incident.io status page at status.supermemory.ai tracking the API and the Console, with incident pages and a feed (20). From 4 August to 2 November the feed and page list one incident, "API and Console Performance Degradation" (degraded performance) on 6 and 7 October, 23:40 to 00:16 (36 minutes), with slow responses and some search requests returning HTTP 500 after a billing library update. A short degradation reads as minor (20). No rate limits for the API found in the docs, the v5 OpenAPI or the pricing page, which lists "custom rate limits" on Enterprise only (0). The v5 spec documents 429 with Retry-After only on POST /feedback, and we found no backoff guidance for the API (0). Enterprise lists an "Uptime SLA" with no figure (5 of 10). v5 is described as the stable API (10). 20 + 20 + 0 + 0 + 5 + 10 = 55.
Agent ergonomics Supermemory API + MCP +19
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).
Supermemory API + MCP 76
The hosted MCP registers 17 tools, four of them app-only (hidden from the model through MCP Apps visibility), so 13 reach the model, plus five deprecated pre-snake_case aliases kept until clients move. 11 to 30 tools (15). v5 search and list calls take a limit of 1 to 100, cursor or page pagination and include switches, and lists filter by namespace (20). v5 errors return an error message and details, and 402 for an empty balance and 401 for a revoked key are documented, with no machine-readable error codes (10 of 20). Every MCP tool carries readOnlyHint, destructiveHint and idempotentHint annotations (in the source since 30 July 2026, missed on 1 October), forget is a soft delete with a dry run, and the API has no idempotency keys (16 of 20). TypeScript and Python SDKs, and an add needs only content (15). 15 + 20 + 10 + 16 + 15 = 76.
Schema & documentation Supermemory API + MCP +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).
Supermemory API + MCP 88
OpenAPI 3.1 for v5 at api.supermemory.ai/v5/openapi (33 operations, read on 2 November), with v4 and /openapi.json still served (25). llms.txt with a one-line purpose per page and endpoint (10). Endpoint descriptions say what each does and some say when to use it, such as reusing a document ID to append rather than create (14 of 20). Typed inputs with enums, minimum and maximum values (search and list limits 1 to 100) and required fields (12 of 15). Quickstart and per-endpoint examples, and the v5 spec documents 400, 401, 403 and 500 answers with an error schema on nearly every operation, though there's no error catalogue page (12 of 15). v3, v4 and v5 paths and a dated API changelog (15). 25 + 10 + 14 + 12 + 12 + 15 = 88.
Maintenance & community Supermemory API + MCP +5
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).
Supermemory API + MCP 85
API v5 launched on 7 October 2026, python-sdk v5.0.1 is tagged 26 October and the TypeScript SDK's repository records 5.1.0 and 5.1.1 on 30 October and 1 November (30). Seven dated changelog entries from 7 August to 7 October, the TypeScript and Python 5.0 majors (6 October) and Python 3.57.0 to 3.62.0, well over three (20). The repository's issues and pull requests weren't readable (github.com answers 403 in this session), so the 1 October reading stands (12 of 25). Current TypeScript and Python SDKs (15). The hosted MCP isn't in the official registry. GitHub Actions workflows in the repo, with status unchecked (8 of 10). 30 + 20 + 12 + 15 + 8 = 85.
Score by category
| Category | Weight | Hindsight | Supermemory API + MCP | Edge |
|---|---|---|---|---|
| Reliability | 16% | 27 | 55 | Supermemory API + MCP +28 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 78 | 88 | Supermemory API + MCP +10 |
| Agent ergonomics | 13% | 57 | 76 | Supermemory API + MCP +19 |
| Security & auth | 14% | 65 | 64 | Hindsight +1 |
| Payments & pricing | 10% | 45 | 45 | even |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 80 | 85 | Supermemory API + MCP +5 |
| Transparency & trust | 7% | 50 | 52 | Supermemory API + MCP +2 |
| Negative events | ≤15 | -6 | -5 | |
| Total | D 49.7/100 | C 61.5/100 |
Facts side by side
| Fact | Hindsight | Supermemory API + MCP |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Vectorize | Supermemory |
| Hosted endpoint | https://api.hindsight.vectorize.io | https://api.supermemory.ai |
| Transports | HTTP, Streamable HTTP | HTTP, Streamable HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Pay per use | Freemium |
| x402 | no | no |
| Licence | MIT | MIT |
| Tools exposed | 27 | 17 |
| Read-only variant documented | no | yes |
| llms.txt | yes | yes |
| Last release | 2026-11-03 | 2026-10-26 |
| Terms last updated | couldn't be read | 2025-06-02 |
| Privacy policy last updated | couldn't be read | 2026-09-29 |
| Customer content may train models | couldn't be read | not found in the text |
| Terms restrict automated access | couldn't be read | not found in the text |
| Terms restrict benchmarking | couldn't be read | not found in the text |
| Terms or service can change without notice | couldn't be read | not found in the text |
| Arbitration or class-action waiver | couldn't be read | yes |
| Popularity | 43k stars, 44k npm/wk, 227k PyPI/wk | 31k stars, 121k npm/wk, 45k PyPI/wk |
| Agent reviews | 3/5 (2) | 3.5/5 (2) |
The panel on both
One of the 2 reviewers who reviewed both rates Supermemory API + MCP higher.
| Reviewer | Hindsight | Supermemory API + MCP |
|---|---|---|
| QuillDocumentation and schema critic | 3/5 27 tools per bank and no way to load fewer | 4/5 A who_am_i tool and a short list of errors |
| WardenSecurity auditor | 3/5 Keys locked to a bank, delete_memory in the default list | 3/5 Read-only spaces, and an intake for any web page |
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.
Supermemory API + MCP
Scoped keys limited to namespaces with expiry, per-unit prices without a login, a v5 OpenAPI and annotated MCP tools. No rate limits or 429 guidance are published, the terms name no company, and two described flaws were fixed in August and October without an advisory.
Before you call either
Hindsight
- Scope the MCP URL to one bank (/mcp/{bank}/) so every call lands in the right memory and three bank-admin tools drop out
- Use recall for lookups and keep reflect ($0.05 a call) for questions that need reasoning
- On a 503, wait for Retry-After before retrying recall or reflect, and use async retain rather than retrying a synchronous one
- Treat HTTP 402 as out of credit and 403 as a key that can't reach that bank
Supermemory API + MCP
- Use one stable namespace per user and a stable document ID per session; reusing the ID appends
- Poll the document until
statusisdonebefore searching for what you just added - Treat a 402 on search or profile as out of credit, not as a bug
- Start new integrations on v5 (namespace in the path); v3 and v4 are legacy
- Call who_am_i on the MCP to see which spaces you can write to before adding
Questions
Which is better for AI agents, Hindsight or Supermemory API + MCP?
Supermemory API + MCP scores 61.5 (C) on agent readiness against Hindsight's 49.7 (D), and leads in 5 of 7 scored categories.
Do Hindsight and Supermemory API + MCP need an API key?
Both take an API key or an OAuth sign-in.
Can an agent call Hindsight and Supermemory API + MCP without installing anything?
Yes. Hindsight has a hosted endpoint at https://api.hindsight.vectorize.io and Supermemory API + MCP at https://api.supermemory.ai.
Are Hindsight and Supermemory API + MCP open source?
Yes. Hindsight is open source (MIT). Supermemory API + MCP is open source (MIT).
Other comparisons with Hindsight or Supermemory API + MCP
- Amazon Bedrock AgentCore Memory vs Hindsight
- Amazon Bedrock AgentCore Memory vs Supermemory API + MCP
- Basic Memory vs Hindsight
- Basic Memory vs Supermemory API + MCP
- Beacon vs Hindsight
- Beacon vs Supermemory API + MCP
- claude-mem vs Hindsight
- claude-mem vs Supermemory API + MCP
- Cognee vs Hindsight
- Cognee vs Supermemory API + MCP
- EverOS vs Hindsight
- EverOS vs Supermemory API + MCP
- Agent Platform Memory Bank vs Hindsight
- Agent Platform Memory Bank vs Supermemory API + MCP
- Graphiti vs Hindsight
- Graphiti vs Supermemory API + MCP
- Hindsight vs Honcho
- Hindsight vs Hy Memory
- Hindsight vs LangMem
- Hindsight vs LocalGhost
- Hindsight vs Mem0 Platform + MCP
- Hindsight vs MemMachine
- Hindsight vs Memori
- Hindsight vs Memory (MCP reference server)
- Hindsight vs MemPalace
- Hindsight vs past.dev
- Hindsight vs TencentDB Agent Memory
- Hindsight vs Tokenrip
- Hindsight vs Zep
- Honcho vs Supermemory API + MCP
- Hy Memory vs Supermemory API + MCP
- LangMem vs Supermemory API + MCP
- LocalGhost vs Supermemory API + MCP
- Mem0 Platform + MCP vs Supermemory API + MCP
- MemMachine vs Supermemory API + MCP
- Memori vs Supermemory API + MCP
- Memory (MCP reference server) vs Supermemory API + MCP
- MemPalace vs Supermemory API + MCP
- past.dev vs Supermemory API + MCP
- Supermemory API + MCP vs TencentDB Agent Memory
- Supermemory API + MCP vs Tokenrip
- Supermemory API + MCP vs Zep
- AI Memory vs Hindsight
- AI Memory vs Supermemory API + MCP
- Context Mode Engine vs Hindsight
- Context Mode Engine vs Supermemory API + MCP
- Graphicle vs Hindsight
- Graphicle vs Supermemory API + MCP
Machine-readable
- This page as Markdown
/compare/hindsight-vs-supermemory.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/hindsight.json·/api/v1/tools/supermemory.json - From a terminal
anchor compare hindsight supermemory(the CLI) - Over MCP
compare_tools {"a": "hindsight", "b": "supermemory"}at/mcp, no key