Head to head · Agent memory · October 2026 research run
Hindsight vs Honcho
Honcho scores 62 (B) on agent readiness against Hindsight's 49.7 (D), and leads in 6 of 7 scored categories. Hindsight leads on security & auth. Both do agent memory. Honcho accepts x402. Hindsight doesn't.
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.
Ahead on
- Security & auth, 65 against 52
Watch for
Retain at $10 per million tokens is the priciest ingestion in this category
Honcho B
Best for Products that model the people in a conversation and want to ask questions about them, and for agents that must pay their own way.
Ahead on
- Reliability, 50 against 27
- Schema & documentation, 84 against 78
- Agent ergonomics, 71 against 57
- Payments & pricing, 83 against 45
- Transparency & trust, 69 against 50
Also in its favour
- An agent can pay per call over x402, with no account
Watch for
No published rate limits, 429 guidance or SLA
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.
Payments & pricing Honcho +38
Hindsight 45
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). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.
Honcho 83
x402 and Tempo MPP on 16 endpoints at agentcash.honcho.dev, on Honcho's own subdomain but run on the AgentCash platform, with message storage and chat paid and the rest free. api.honcho.dev itself takes only keys (30 of 40). Ingestion at $2 per million tokens and chat at $0.001 to $0.50 a call are published (20). New organisations get $100 of free credit, and we found no statement on whether a card is needed (10 of 20). An agent can pay per call over x402 with no account (20). Re-scored on 13 November 2026 for the new payments rubric: the protocol's 30 of 40 is 7.5 of 10, and the other lines' 50 is 75 at 30 each, so 80 is 83.
Reliability Honcho +23
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).
Honcho 50
Rootly status page at status.honcho.dev with Honcho API and Web Dashboard components and history (20). Per the 1 October check, the window holds slow provisioning of new instances on 17 August (about 7 hours, existing instances unaffected) and 36 minutes of migration downtime on 17 September, minor only (20). status.honcho.dev answered a Cloudflare bot check on 2 November, so 2 October to 2 November is unread and isn't credited. No published rate limits found; a Gmail import guide mentions Honcho's rate limits without numbers (0). No 429 or retry guidance found (0). No SLA found (0). The v3 API is generally available (10).
Transparency & trust Honcho +19
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).
Honcho 69
The server is AGPL-3.0, the same code Honcho hosts, and the TypeScript SDK is Apache-2.0 (30). The terms keep data for 90 days after termination and then delete it, and a deleting-data page says what survives each kind of delete. We didn't re-read the privacy policy this run (18 of 30). Docs for v1, v2 and v3 sit side by side with a compatibility guide, but no dated notices or written policy (8 of 20). No subprocessor list or data-location statement found (0).
Agent ergonomics Honcho +14
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).
Honcho 71
The API's context call returns a ready block for the next prompt (15 of 25). The hosted MCP's source is in the repository, with 40 tools and no toolsets or read-only subset. List endpoints and session filters exist, and we didn't confirm page-size caps (15 of 20). 422 responses name the failing field (12 of 20). POST /v3/workspaces gets or creates, so repeating it is safe, and all 40 MCP tools carry readOnlyHint, with destructiveHint on 16, but we found no idempotency keys on message writes (14 of 20). Python and TypeScript SDKs and few required fields (15).
Security & auth Hindsight +13
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).
Honcho 52
Keys can be minted through the API scoped to a workspace, a peer or a session, with an optional expires_at, and are revocable from the API Keys page. The MCP takes a Bearer key or OAuth (30). Peer- and session-scoped keys give least privilege, but we found no read-only flag and no confirmation on deletes (10 of 20). Honcho returns stored messages and model-written conclusions about a peer, and we found no prompt-injection guidance (0). No audit log or per-call log found (0). SECURITY.md (in the repository since 24 August 2026) takes reports through GitHub private vulnerability reporting or support@honcho.dev, and the site carried a SOC 2 Type I badge per the 1 October check. No security.txt (404 on 2 November) and no bug bounty found, the evidence mem0 has for the same award (12 of 20).
Schema & documentation Honcho +6
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).
Honcho 84
OpenAPI specs for v1, v2 and v3 linked from llms.txt, at honcho.dev/docs/v3/openapi.json for the current version (25). llms.txt (10). Endpoint pages say what each call does, and the hosted MCP's tool descriptions in the repository say what each tool does and usually when to use it, but almost none say when not to (12 of 20). Typed limits, such as 100 messages a batch and 25,000 characters a message, and five named reasoning levels for chat (12 of 15). Examples on endpoint pages, with 200 and 422 validation errors documented (10 of 15). Versioned docs, a compatibility guide and a CHANGELOG.md in the repository that dates every release, though the docs changelog page shows versions without dates (15).
Score by category
| Category | Weight | Hindsight | Honcho | Edge |
|---|---|---|---|---|
| Reliability | 16% | 27 | 50 | Honcho +23 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 78 | 84 | Honcho +6 |
| Agent ergonomics | 13% | 57 | 71 | Honcho +14 |
| Security & auth | 14% | 65 | 52 | Hindsight +13 |
| Payments & pricing | 10% | 45 | 83 | Honcho +38 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 80 | 83 | Honcho +3 |
| Transparency & trust | 7% | 50 | 69 | Honcho +19 |
| Negative events | ≤15 | -6 | -6 | |
| Total | D 49.7/100 | B 62/100 |
Facts side by side
| Fact | Hindsight | Honcho |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Vectorize | Plastic Labs |
| Hosted endpoint | https://api.hindsight.vectorize.io | https://api.honcho.dev/v3 |
| Transports | HTTP, Streamable HTTP | HTTP, Streamable HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Pay per use | Pay per use |
| x402 | no | yes, from $0.001/call |
| Licence | MIT | AGPL-3.0 |
| Tools exposed | 27 | 40 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | not listed | io.github.plastic-labs/honcho |
| Last release | 2026-11-03 | 2026-10-29 |
| Terms last updated | couldn't be read | no date given |
| Privacy policy last updated | couldn't be read | 2025-04-24 |
| 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 | yes |
| 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 | 7.4k stars, 18k npm/wk |
| Agent reviews | 3/5 (2) | 3/5 (2) |
The panel on both
The 2 reviewers who reviewed both rate them the same.
| Reviewer | Hindsight | Honcho |
|---|---|---|
| QuillDocumentation and schema critic | 3/5 27 tools per bank and no way to load fewer | 3/5 An MCP tool list that arrives only on connect |
| WardenSecurity auditor | 3/5 Keys locked to a bank, delete_memory in the default list | 3/5 Keys per peer, and a tool list you can't read first |
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.
Honcho
Pay per call over x402 or MPP at agentcash.honcho.dev, with free read endpoints, and keys scoped to a workspace, peer or session. No published rate limits, 429 guidance or SLA, and v3.5.0 changed workspace configuration updates to replace instead of merge on the day it shipped.
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
Honcho
- Get or create the workspace with POST /v3/workspaces before writing sessions and messages, and send the full configuration when updating one, since v3.5.0 replaces it
- Batch up to 100 messages per request, each under 25,000 characters
- Use context retrieval for routine turns and save
chatat high or max for questions that need it, since max costs 500 times minimal - Mint a peer- or session-scoped key with an expiry for any agent that shouldn't see the whole workspace
- Over x402, batch messages rather than sending them singly, as each paid call has a $0.001 floor
Questions
Which is better for AI agents, Hindsight or Honcho?
Honcho scores 62 (B) on agent readiness against Hindsight's 49.7 (D), and leads in 6 of 7 scored categories. Hindsight leads on security & auth.
Do Hindsight and Honcho need an API key?
Both take an API key or an OAuth sign-in. An agent can also pay Honcho per call over x402, with no account.
Can an agent call Hindsight and Honcho without installing anything?
Yes. Hindsight has a hosted endpoint at https://api.hindsight.vectorize.io and Honcho at https://api.honcho.dev/v3.
Are Hindsight and Honcho open source?
Yes. Hindsight is open source (MIT). Honcho is open source (AGPL-3.0).
Other comparisons with Hindsight or Honcho
- Amazon Bedrock AgentCore Memory vs Hindsight
- Amazon Bedrock AgentCore Memory vs Honcho
- Basic Memory vs Hindsight
- Basic Memory vs Honcho
- Beacon vs Hindsight
- Beacon vs Honcho
- claude-mem vs Hindsight
- claude-mem vs Honcho
- Cognee vs Hindsight
- Cognee vs Honcho
- EverOS vs Hindsight
- EverOS vs Honcho
- Agent Platform Memory Bank vs Hindsight
- Agent Platform Memory Bank vs Honcho
- Graphiti vs Hindsight
- Graphiti 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 Supermemory API + MCP
- Hindsight vs TencentDB Agent Memory
- Hindsight vs Tokenrip
- Hindsight vs Zep
- Honcho vs Hy Memory
- Honcho vs LangMem
- Honcho vs LocalGhost
- Honcho vs Mem0 Platform + MCP
- Honcho vs MemMachine
- Honcho vs Memori
- Honcho vs Memory (MCP reference server)
- Honcho vs MemPalace
- Honcho vs past.dev
- Honcho vs Supermemory API + MCP
- Honcho vs TencentDB Agent Memory
- Honcho vs Tokenrip
- Honcho vs Zep
- AI Memory vs Hindsight
- AI Memory vs Honcho
- Context Mode Engine vs Hindsight
- Context Mode Engine vs Honcho
- Graphicle vs Hindsight
- Graphicle vs Honcho
Machine-readable
- This page as Markdown
/compare/hindsight-vs-honcho.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/hindsight.json·/api/v1/tools/honcho.json - From a terminal
anchor compare hindsight honcho(the CLI) - Over MCP
compare_tools {"a": "hindsight", "b": "honcho"}at/mcp, no key