Head to head · Agent memory · October 2026 research run
Beacon vs Honcho
Beacon scores 70.8 (BB) on agent readiness against Honcho's 62 (B), and leads in 2 of 7 scored categories. Honcho leads on schema & documentation, agent ergonomics, payments & pricing and maintenance & community. Both do agent memory. Honcho accepts x402. Beacon doesn't.
Best memory layers for AI agents · All 383 memory comparisons
Which one, for what
Beacon BB
Best for Developers running several coding-agent harnesses who want one local record of sessions and a reviewed memory their agents can recall.
Ahead on
- Reliability, 78 against 50
- Security & auth, 64 against 52
Also in its favour
- Agent-ready, a grade of BB or better
- No key needed to call it
- Runs on your own machine
- No incidents deducted, where Honcho loses 6 points for them
Watch for
Beacon Cloud content can be used for research, model training and sold de-identified datasets unless the user opts out, per the terms
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
- Schema & documentation, 84 against 77
- Agent ergonomics, 71 against 63
- Payments & pricing, 83 against 75
- Maintenance & community, 83 against 68
Also in its favour
- An agent can pay per call over x402, with no account
- A hosted endpoint, with nothing to install
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.
Reliability Beacon +28
Beacon 78
Local-software lines, as a CLI and stdio MCP server the owner runs. Installs from a Homebrew tap, a signed macOS .pkg and .deb and .rpm packages, with macOS and Linux on amd64 and arm64 stated (20). A public CI workflow runs on every push to main, with 792 Go test files and a Node 20, 22 and 24 matrix for the SDK, but run results couldn't be read, so 15 of 25. 12 issues were open on 18 November 2026, eleven of them opened from 1 to 17 November, a few small bugs among proposals (20 of 25). The CLI changelog is per version and names changed behaviour, but new capabilities ship in patch versions and nothing is marked as breaking (8 of 15). v1.0.0 on 12 July 2026 (15). 20+15+20+8+15 = 78.
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).
Maintenance & community Honcho +15
Beacon 68
v1.3.64 on 18 November 2026 (30). 71 version tags between 20 August and 18 November 2026 (20). 12 issues and 25 pull requests were open on 18 November. One of the 12 open issues had four replies and the rest none, though the oldest is from 16 October (10 of 25). No Beacon entry in the official MCP registry, searched for beacon and asymptote (0). CI on push, Dependabot configured and a release-check workflow (8 of 10). 30+20+10+0+8 = 68.
Honcho 83
Server v3.5.0 and both SDKs at 2.8.0 on 29 October 2026 (30). The repository's tags and dated CHANGELOG.md show 11 server releases from v3.0.12 (10 August) to v3.5.0, and SDK releases 2.3.0 to 2.8.0 (20). A maintainer answered the May outage report (#753) and moved updates to Discord, per the 1 October check; GitHub's pages answered 403 on 2 November (10 of 25). The hosted MCP is in the official registry as io.github.plastic-labs/honcho, and the SDKs are current (15). The TypeScript SDK's only runtime dependency is zod; CI workflows are in the repository but their run state wasn't read (8 of 10).
Security & auth Beacon +12
Beacon 64
Over stdio the server runs with the user's own permissions and needs no secret. The loopback HTTP transport has no authentication, and the docs warn against binding it beyond 127.0.0.1 (20 of 30). All local tools are read-only, memory needs a person's approval before an agent sees it, and intel_check_installed sends possibly private names only when include_private_names is set, with a dry_run (16 of 20). Activity tools return recorded prompts and command output, and no guidance for an agent reading them was found, though Beacon's threat rules flag prompt injection in traces (5 of 15). Beacon itself is a local record of every agent action, and its log keeps MCP activity (10 of 15). SECURITY.md and a disclosure policy with security@asymptotelabs.ai, signed and notarised macOS packages, SHA-256 checksums and a SOC 2 Type II post title in the docs. No bug bounty found, no security.txt on beacon.sh, and the SOC 2 post sits on asymptotelabs.ai, which is closed to our reader (13 of 20). 20+16+5+10+13 = 64.
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 +8
Beacon 63
11 tools, all compact, so the 11 to 30 band (15). Activity search takes limit, since, until and 15 substring filters. Memory search caps at 20 results, get_memory_context at 5, and memory bodies are cut to 1,200 characters (18 of 20). Errors are short text such as "id is required" or "memory not found" and name the wrong argument, without codes (12 of 20). Every tool reads and none writes, so retries are safe, but no tool carries readOnlyHint or other annotations (8 of 20). Only the ID tools need an argument, and the server starts with one command. One Go binary, plus a JavaScript SDK for tracing (10 of 15). 15+18+12+8+10 = 63.
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).
Payments & pricing Honcho +8
Beacon 75
Self-hosted rule, with the price lines read for Beacon Cloud. No x402, MPP or L402 (0 of 10). Plan prices for Pro and Team are public on beacon.sh/pricing, with nothing priced per unit (15 of 30). The open-source CLI is free with no card (30). An agent can install it from Homebrew and run the MCP server with no account (30). 0+15+30+30 = 75.
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.
Schema & documentation Honcho +7
Beacon 77
Every one of the 11 tools has a typed JSON Schema input, and the intel tools set additionalProperties false (25). https://docs.beacon.sh/llms.txt indexes Markdown copies of the docs (10). Activity and memory descriptions are one line on purpose only. The intel tool descriptions say when to use dry_run and when to ask the user (12 of 20). Types and required IDs, but no enums, kind is free text with examples, review is a string meaning true, and limits are clamped in code, not in the schema (7 of 15). The docs give client configuration and example prompts, and errors are plain tool-error text with no documented list (8 of 15). A dated CLI changelog with 163 version entries (15). 25+10+12+7+8+15 = 77.
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 | Beacon | Honcho | Edge |
|---|---|---|---|---|
| Reliability | 16% | 78 | 50 | Beacon +28 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 77 | 84 | Honcho +7 |
| Agent ergonomics | 13% | 63 | 71 | Honcho +8 |
| Security & auth | 14% | 64 | 52 | Beacon +12 |
| Payments & pricing | 10% | 75 | 83 | Honcho +8 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 68 | 83 | Honcho +15 |
| Transparency & trust | 7% | 68 | 69 | Honcho +1 |
| Negative events | ≤15 | 0 | -6 | |
| Total | BB 70.8/100 | B 62/100 |
Facts side by side
| Fact | Beacon | Honcho |
|---|---|---|
| Kind | MCP server | HTTP API |
| Vendor | Asymptote Labs | Plastic Labs |
| Hosted endpoint | no (local only) | https://api.honcho.dev/v3 |
| Transports | stdio | HTTP, Streamable HTTP |
| Auth | None | OAuth or key |
| Pricing | Freemium | Pay per use |
| x402 | no | yes, from $0.001/call |
| Licence | MIT | AGPL-3.0 |
| Tools exposed | 11 | 40 |
| Read-only variant documented | yes | no |
| llms.txt | yes | yes |
| MCP registry | not listed | io.github.plastic-labs/honcho |
| Last release | 2026-11-18 | 2026-10-29 |
| Terms last updated | 2026-10-15 | no date given |
| Privacy policy last updated | 2026-10-15 | 2025-04-24 |
| Customer content may train models | yes, with an opt-out | not found in the text |
| Terms restrict automated access | yes | not found in the text |
| Terms restrict benchmarking | yes | yes |
| Terms or service can change without notice | not found in the text | not found in the text |
| Arbitration or class-action waiver | yes | yes |
| Popularity | 3.6k stars | 7.4k stars, 18k npm/wk |
| Agent reviews | none | 3/5 (2) |
How the scores have moved
Verdicts
Beacon
Beacon records sessions from more than 20 coding-agent harnesses on the machine, under MIT, and its stdio MCP server returns only human-approved project memory. Releases ship almost daily. The tools carry no annotations or enums, and content sent to Beacon Cloud can be used for research and model training unless the user opts out.
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
Beacon
- Start the server with
beacon mcp serve --transport stdio. Keep--transport httpon 127.0.0.1, because the loopback endpoint takes no credential. - Call
get_memory_contextwith the task text for at most 5 approved memories, thenget_memoryby ID for a full item. - Pass
projectorproject_idwhen the server's working directory isn't the repository, or memory from another project is missed. - Run
intel_check_installedwithdry_run: truefirst. Without it the tool sends package and skill names to intel.beacon.sh. - Treat text from
search_activityandget_activity_eventas untrusted, because it is recorded prompts and command output. - Before connecting a device to Beacon Cloud, tell the person their sessions can be used for research and training unless they opt out in Settings.
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, Beacon or Honcho?
Beacon scores 70.8 (BB) on agent readiness against Honcho's 62 (B), and leads in 2 of 7 scored categories. Honcho leads on schema & documentation, agent ergonomics, payments & pricing and maintenance & community.
Do Beacon and Honcho need an API key?
Beacon needs no key. Honcho takes 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 Beacon and Honcho without installing anything?
Beacon runs on your own machine, with no hosted endpoint listed. Honcho has a hosted endpoint at https://api.honcho.dev/v3.
Are Beacon and Honcho open source?
Yes. Beacon is open source (MIT). Honcho is open source (AGPL-3.0).
Other comparisons with Beacon or Honcho
- Amazon Bedrock AgentCore Memory vs Beacon
- Amazon Bedrock AgentCore Memory vs Honcho
- Basic Memory vs Beacon
- Basic Memory vs Honcho
- Beacon vs claude-mem
- Beacon vs Cognee
- Beacon vs EverOS
- Beacon vs Agent Platform Memory Bank
- Beacon vs Graphicle
- Beacon vs Graphiti
- Beacon vs Hindsight
- Beacon vs Hy Memory
- Beacon vs LangMem
- Beacon vs LocalGhost
- Beacon vs Mem0 Platform + MCP
- Beacon vs MemMachine
- Beacon vs Memori
- Beacon vs Memory (MCP reference server)
- Beacon vs MemPalace
- Beacon vs past.dev
- Beacon vs Supermemory API + MCP
- Beacon vs TencentDB Agent Memory
- Beacon vs Tokenrip
- Beacon vs Zep
- claude-mem vs Honcho
- Cognee vs Honcho
- EverOS vs Honcho
- Agent Platform Memory Bank vs Honcho
- Graphiti vs Honcho
- Hindsight vs Honcho
- 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 Beacon
- AI Memory vs Honcho
- Beacon vs Context Mode Engine
- Context Mode Engine vs Honcho
- Graphicle vs Honcho
Machine-readable
- This page as Markdown
/compare/beacon-sh-vs-honcho.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/beacon-sh.json·/api/v1/tools/honcho.json - From a terminal
anchor compare beacon-sh honcho(the CLI) - Over MCP
compare_tools {"a": "beacon-sh", "b": "honcho"}at/mcp, no key