Head to head · Agent memory · October 2026 research run

Cognee vs Honcho

Honcho scores 62 (B) on agent readiness against Cognee's 49.9 (D), and leads in 5 of 7 scored categories. Both do agent memory. Honcho accepts x402. Cognee doesn't.

Best memory layers for AI agents · All 383 memory comparisons

Which one, for what

Cognee D

Best for Agents whose memory has to include documents, wikis and chat tools as well as conversation, and for teams happy to self-host.

Also in its favour

  • Runs on your own machine
  • Free to start without a card

Watch for

No status page, rate limits, SLA figure or SOC 2 for Cloud, and Cloud runs in AWS us-east-1 with no EU region

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 43
  • Agent ergonomics, 71 against 59
  • Security & auth, 52 against 39
  • Payments & pricing, 83 against 53

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 +30

Cognee 53

No x402, MPP or L402 (0). Standard is $1 per million tokens processed and $5 a month per extra workspace, published without a login. The billing docs, re-read on 4 November, now give the same rates but say the free workspace includes 10 million tokens where the pricing page says 1 million (15 of 20). Free includes a workspace, "no card required" (20). A person signs up for a Cloud tenant in the browser (0). Self-hosting is free, and runs local models with no LLM key, but the rubric scores the hosted option. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 35 is 53.

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.

Security & auth Honcho +13

Cognee 39

Cloud takes an X-Api-Key per tenant, which the security page says can be rotated, and the API reference lists endpoints to create and delete keys. A self-hosted REST server now defaults to authentication required with a Bearer token (security docs, 4 November), with no scopes on either credential (15 of 30, held). Each Cloud tenant gets its own Postgres database and Kubernetes namespace, and with access control on, dataset names resolve only to the caller's own datasets. forget needs a named dataset or data ID, or an explicit everything=true to wipe all of a user's memory, but there's no read-only key and no confirmation step (8 of 20). Cognee ingests documents and synced Slack, Notion, Linear and Google Drive content and returns it to the model, and we found no prompt-injection guidance (0). Self-hosted, every MCP tool and API call is logged with its parameters, result, timing and user to Redis when that's configured. We found no audit log for Cloud (6 of 15). SECURITY.md asks for reports to security@cognee.ai, and an OpenSSF Scorecard workflow runs in CI. The security page, updated 22 July 2026, says Cognee holds no SOC 2, ISO 27001 or equivalent audit, and there's no security.txt (10 of 20). On 4 November SECURITY.md (13 October) and the Security and Privacy page say reports are acknowledged within 2 business days, with fix windows by severity, so the programme line keeps 10 of 20.

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

Agent ergonomics Honcho +12

Cognee 59

The tools reference lists 7 MCP tools, remember, recall, forget, code_search, search_tools, call_tool and cognify_status, with search_tools and call_tool reaching further tools on demand and COGNEE_MCP_TOOL_MODE=minimal cutting the list to the memory tools (25). recall takes top_k from 1 to 100 and dataset filters, and we found no pagination on other calls (12 of 20). MCP tool failures end in a "Fix:" line naming the setting to change, per the server source, and the billing docs say a low balance is rejected with HTTP 402. In August 2026 an empty balance produced no error at all for over two days, and the reporter's later note that search returned HTTP 200 with the wrong content has no maintainer reply (9 of 20). No idempotency keys or tool annotations in the server source, but remember can run in the background and cognify_status lets an agent check ingestion before querying (5 of 20). Python only, and the MCP server starts with one docker run (8 of 15). On 4 November the tools reference and cognee-mcp 0.5.7 source still register the same seven tools, with no tool annotations.

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

Reliability Honcho +7

Cognee 43

We departed from the checklist here. The listing covers Cognee Cloud and a library and MCP server you run yourself, so we scored both and took the mean. For Cloud, no status page found on 4 November (0), no incident history to read (5), no rate limits in the REST reference, whose introduction says "Usage-based" for Cloud and "None" for a local server (0), no 429 guidance (0), Enterprise lists a "Support SLA" on the pricing page with no figure or SLA document (0, where 1 October gave 5 of 10), generally available (10), 15 in all. For the local package, cognee on PyPI with Python 3.10 to 3.14 stated in SECURITY.md and pyproject.toml (20). 64 GitHub Actions workflows, and test_suites.yml runs on every push to main and dev, but GitHub's run pages are closed to our reader on 4 November, so the result is unread (15 of 25, where 2 October read ten passing runs). Open regressions not counted, per the 2 October check (10 of 25). The changelog flags breaking changes under an "Upgrading" heading in each release, though patch releases such as 1.6.3, 1.6.5 and 1.6.6 carry them and 11 MCP tools went in May without a version bump (10 of 15). Version 1.6.6 (15). 70 in all. Mean 42.5, rounded half up to 43.

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

Score by category

CategoryWeightCogneeHonchoEdge
Reliability16%4350Honcho +7
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8584Cognee +1
Agent ergonomics13%5971Honcho +12
Security & auth14%3952Honcho +13
Payments & pricing10%5383Honcho +30
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8283Honcho +1
Transparency & trust7%7269Cognee +3
Negative events≤15-9-6
TotalD 49.9/100B 62/100

Facts side by side

FactCogneeHoncho
KindPlatformHTTP API
VendorCogneePlastic Labs
Hosted endpointhttps://<tenant>.aws.cognee.ai/api/v1https://api.honcho.dev/v3
TransportsHTTP, stdio, SSE (legacy)HTTP, Streamable HTTP
AuthOAuth or keyOAuth or key
PricingFreemiumPay per use
x402noyes, from $0.001/call
LicenceApache-2.0AGPL-3.0
Tools exposed740
Read-only variant documentednono
llms.txtyesyes
MCP registrynot listedio.github.plastic-labs/honcho
Last release2026-10-292026-10-29
Terms last updated2026-03-27no date given
Privacy policy last updatedno date given2025-04-24
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessnot found in the textnot found in the text
Terms restrict benchmarkingnot found in the textyes
Terms or service can change without noticenot found in the textnot found in the text
Arbitration or class-action waivernot found in the textyes
Popularity31k stars7.4k stars, 18k npm/wk
Agent reviews3/5 (2)3/5 (2)

The panel on both

The 2 reviewers who reviewed both split evenly.

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

Cognee

Apache-2.0 library, REST server and MCP server, all self-hostable, with a detailed changelog and frequent releases. Cloud has no status page, rate limits or SOC 2, and runs in AWS us-east-1. Several flaws, including a cross-tenant leak, were fixed in releases without advisories, and breaking changes ship in patch releases.

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

Cognee

  1. Use remember, recall and forget. The older cognify, search and delete MCP tools are gone
  2. Always include /api/v1 in REST paths
  3. Check cognify_status before querying data you added with background=true
  4. Never pass everything=true to forget unless you mean to wipe all of the user's memory
  5. Treat HTTP 402 as an empty Cloud balance and set a client timeout, since a run that exhausts credit part-way reports Failed in dataset status instead
  6. Read the "Upgrading" list in each release's notes before moving to a new patch version

Honcho

  1. 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
  2. Batch up to 100 messages per request, each under 25,000 characters
  3. Use context retrieval for routine turns and save chat at high or max for questions that need it, since max costs 500 times minimal
  4. Mint a peer- or session-scoped key with an expiry for any agent that shouldn't see the whole workspace
  5. 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, Cognee or Honcho?

Honcho scores 62 (B) on agent readiness against Cognee's 49.9 (D), and leads in 5 of 7 scored categories.

Can an agent call Cognee and Honcho without installing anything?

Yes. Cognee has a hosted endpoint at https://<tenant>.aws.cognee.ai/api/v1 and Honcho at https://api.honcho.dev/v3.

Are Cognee and Honcho open source?

Yes. Cognee is open source (Apache-2.0). Honcho is open source (AGPL-3.0).

Other comparisons with Cognee or Honcho

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.