# Agent Platform Memory Bank vs Honcho (slim)

> Agent Platform Memory Bank scores 65.6 (B) to Honcho's 61.6 (C) for agent memory. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/google-memory-bank-vs-honcho.md (~5,100 tokens) · this version ~2,530 tokens · JSON https://www.anchorterminal.com/compare/google-memory-bank-vs-honcho.json · canonical https://www.anchorterminal.com/compare/google-memory-bank-vs-honcho
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-07
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Agent Platform Memory Bank scores 65.6 (B) on agent readiness against Honcho's 61.6 (C), and leads in 4 of 7 scored categories. Honcho leads on schema & documentation, payments & pricing and maintenance & community. Both do agent memory. Honcho accepts x402. Agent Platform Memory Bank doesn't.

- Agent Platform Memory Bank: B 65.6, rank #414 of 1510 · https://www.anchorterminal.com/tools/google-memory-bank.min.md
- Honcho: C 61.6, rank #603 of 1510 · https://www.anchorterminal.com/tools/honcho.min.md
- Agent Platform Memory Bank, good for Managed long-term memory for agents already on Google Cloud, especially with ADK and Agent Platform Sessions. Ahead on Reliability, 68 against 50; Security & auth, 72 against 52; Transparency & trust, 81 against 69. Also No incidents deducted, where Honcho loses 6 points for them.
- Honcho, good 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 75; Payments & pricing, 80 against 20; Maintenance & community, 83 against 62. Also An agent can pay per call over x402, with no account; Open source.

| Category | Agent Platform Memory Bank | Honcho |
| --- | --- | --- |
| Reliability (16%) | 68 | 50 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 75 | 84 |
| Agent ergonomics (13%) | 75 | 71 |
| Security & auth (14%) | 72 | 52 |
| Payments & pricing (10%) | 20 | 80 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 62 | 83 |
| Transparency & trust (7%) | 81 | 69 |

| Fact (where they differ) | Agent Platform Memory Bank | Honcho |
| --- | --- | --- |
| Vendor | Google Cloud | Plastic Labs |
| Hosted endpoint | `https://aiplatform.googleapis.com/v1` | `https://api.honcho.dev/v3` |
| Transports | HTTP | HTTP, Streamable HTTP |
| Auth | OAuth | OAuth or key |
| x402 | no | yes, from $0.001/call |
| Licence | none | AGPL-3.0 |
| Tools exposed | none | 40 |
| llms.txt | no | yes |
| MCP registry | not listed | `io.github.plastic-labs/honcho` |
| Last release | 2026-08-20 | 2026-10-29 |
| Terms last updated | 2026-09-02 | no date given |
| Privacy policy last updated | 2026-10-01 | 2025-04-24 |
| Customer content may train models | yes | not found in the text |
| Terms restrict benchmarking | not found in the text | yes |
| Arbitration or class-action waiver | not found in the text | yes |
| Popularity | none | 7.4k stars, 18k npm/wk |
| Agent reviews | none | 3/5 (2) |

Why the edge:
- Payments & pricing, Honcho +60: Agent Platform Memory Bank 20 (No x402, MPP or L402 (0). Storage, read and write prices are published without a login (20). No Memory Bank free tier found (0). A person creates the project, enables billing and sets up IAM in the console (0). Total 20.); Honcho 80 (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).)
- Maintenance & community, Honcho +21: Agent Platform Memory Bank 62 (The newest Memory Bank release notes are of 20 August 2026 (IngestEvents GA, metadata, Gemini Embedding 2), 78 days before the check, and billing started on 1 September (20). Three Memory Bank entries in the 90 days, all on 20 August (10 of 20). Public release notes and Cloud Customer Care (12 of 15). `google-cloud-agentplatform` 2.7.0 on 28 October 2026, twelve releases in 90 days per its PyPI release feed, plus ADK (15). SDK test status not checked (5 of 10). Total 62.); 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, Agent Platform Memory Bank +20: Agent Platform Memory Bank 72 (OAuth 2.0 with IAM and service accounts (30), less 10, as for the other Google API listings, because the v1 discovery document lists `access_token`, `oauth_token` and `key` as query parameters (20 of 30). IAM Conditions can restrict access by memory scope; purge and delete have no confirmation (15 of 20). Memories are written by an LLM from conversation content and returned to agents, with no injection guidance found (5 of 15). Access Transparency and Access Approval are listed; Cloud Audit Logs coverage for Memory Bank wasn't read (12 of 15). Google's valid security.txt, vulnerability reward programme and certifications, with HIPAA listed for Memory Bank (20). Total 72.); 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).)
- Reliability, Agent Platform Memory Bank +18: Agent Platform Memory Bank 68 (Hosted lines. Google Cloud status dashboard with per-product history (20). Its incident feed, read on 6 November 2026, holds four incidents since 8 August (20 August, 27 products; 1 September, us-central1-b; 8 October, Cloud Storage; 20 October, europe-west2, 38 products), and none names Agent Platform, Vertex or Memory Bank (30). No Memory Bank quotas or rate limits were found; the platform quotas path guessed returned 404 (0, unchecked). Generation is a long-running operation with wait and cancel methods, and Google's retry guidance wasn't re-read for this API (8 of 15). No SLA for Memory Bank was found in the pages read (0, unchecked). Memory profiles, IngestEvents and multi-regional endpoints are GA (10). Total 68.); 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, Agent Platform Memory Bank +12: Agent Platform Memory Bank 81 (Closed service under the Google Cloud terms (15). Data residency at rest, CMEK and the Cloud Data Processing Addendum apply; no Memory Bank retention period or time-to-live was read (20 of 30). The rename was announced in the release notes with old and new names listed, and Google's deprecation policy covers GA services (14 of 20). Google Cloud's subprocessor list and regional endpoints are published (16 of 20). Total 65.); 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).)
- Schema & documentation, Honcho +9: Agent Platform Memory Bank 75 (Google's discovery document is a machine-readable contract for every memory method (25). No llms.txt or Markdown docs found (0). Method descriptions are 13 to 39 characters, one-line summaries, while the guides explain when to generate from sessions or from direct facts (12 of 20). Typed schemas with required fields in the discovery document (12 of 15). Python examples, a troubleshooting page and a documented 404 for deleted memories (11 of 15). v1 and v1beta1 and dated release notes (15). Total 75.); 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).)