Head to head · Agent memory · October 2026 research run
Agent Platform Memory Bank vs Graphicle
Graphicle scores 70.6 (BB) on agent readiness against Agent Platform Memory Bank's 65.6 (B), and leads in 4 of 7 scored categories. Agent Platform Memory Bank leads on reliability, security & auth and transparency & trust. Both do agent memory.
Best memory layers for AI agents · All 353 memory comparisons
Which one, for what
Best for Managed long-term memory for agents already on Google Cloud, especially with ADK and Agent Platform Sessions.
Ahead on
- Reliability, 68 against 63
- Security & auth, 72 against 67
- Transparency & trust, 81 against 71
Also in its favour
- A hosted endpoint, with nothing to install
Watch for
Needs a Google Cloud project with billing, set up by a person in the console
Graphicle BB
Best for A developer who wants one local tool that gives Claude Code, Codex or Cursor both code structure and project memory with citations.
Ahead on
- Schema & documentation, 83 against 75
- Agent ergonomics, 85 against 75
- Payments & pricing, 60 against 20
- Maintenance & community, 83 against 62
Also in its favour
- Agent-ready, a grade of BB or better
- Runs on your own machine
- Free to start without a card
- Open source
Watch for
Version 0.1.10, about two weeks old, with stored-data changes shipped in patch releases
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 Graphicle +40
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.
Graphicle 60
No payment protocol (0). Read with the self-hosted rule. Free under Apache-2.0 with nothing to buy (20). No card or account (20). An agent can install it and run graphicle setup --yes with no signup, as the README suggests (20). The commercial team edition is still in private preview with no prices on karlex.ai on 1 November, so there is no paid option to score. 0+20+20+20 = 60.
Maintenance & community Graphicle +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.
Graphicle 83
v0.1.10 on 30 October 2026 (30). Eleven releases, v0.1.0 (14 October) to v0.1.10 (30 October), all inside the last 90 days (20). Outside pull requests #9 and #10 shipped in 0.1.6 and 0.1.7 and issue #8's kubernetes timings drove 0.1.5, per the changelog, with Discussions and a Discord linked, but reply times and open issues weren't readable on 1 November (12 of 25). In the official MCP registry as io.github.Graphicle-AI/graphicle, a GitHub-verified namespace, with 0.1.10 published on 30 October and marked latest (15). The SDKs are still not on PyPI or npm. Pinned GitHub Actions, dependency-graph updates and passing tests, but the licence and advisory job failed on main on 15 October and its later runs weren't readable (6 of 10). 30+20+12+15+6 = 83.
Agent ergonomics Graphicle +10
Agent Platform Memory Bank 75
Retrieval takes a scope and similarity search with a result limit (20 of 25). List methods page with page tokens and filters (16 of 20). Google's standard error model with status codes (15 of 20). Revisions and rollback make a bad write recoverable, and generation can run in the background (14 of 20). Python SDK and ADK integration, with REST for other languages (10 of 15). Total 75.
Graphicle 85
25 tools with memory proposals on, about 24,600 characters of definitions in the v0.1.10 fixture (15). --tools essentials serves five tools (recall_project, read_project_source, query_graph, get_node, get_neighbors, about 7,400 characters) and is what graphicle setup gives Claude Code; --tools graph or --tools memory serves one half, and leaving out --allow-learning leaves only read tools plus graph_link (10 added back, up from 7 on 15 October, for the essentials set). recall_project takes max_tokens or max_chars, include prefixes and skip_shown, query_graph takes token_budget and depth, and list_projects pages with offset and limit (20). Over-limit projects are refused with a message naming the limit and its setting, 409 marks a stale revision and 429 carries Retry-After, and since 0.1.7 the Python SDK keeps retry_after on its error. MCP error shapes are not documented (12 of 20). 21 tools carry readOnlyHint true and 4 false, all with idempotentHint true and destructiveHint false, there are no destructive tools, and propose_memory requires an idempotency_key that replays the same proposal (20). Only question is required on recall and graph queries. Python and TypeScript SDKs exist, at 0.1.10, but install only from source (8 of 15). 25+20+12+20+8 = 85.
Transparency & trust Agent Platform Memory Bank +10
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.
Graphicle 71
Apache-2.0 with NOTICE files that credit Graphify and every adapted project (30). The README privacy section and the FAQ list every case in which the program uses the network, say there is no telemetry or account, and keep data in one SQLite store with deletion receipts. A grep of the source for outbound hosts found only model providers, connectors and GitHub, which agrees. The karlex.ai privacy policy of 14 March 2025 covers the website, not the software (20 of 30). SECURITY.md lists supported versions. No deprecation policy (3 of 20). No telemetry to opt out of, and the network cases are disclosed, with freshness off and --code-only to limit them (18 of 20). 30+20+3+18 = 71.
Schema & documentation Graphicle +8
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.
Graphicle 83
Every MCP tool has a JSON Schema input with additionalProperties: false and required fields marked, read from the tool list fixtures in the repository at v0.1.10 (25). No llms.txt. The docs are Markdown files in the repository that an agent can read raw (5 of 10). Server instructions say which tool to use for structure and which for what the project says, recall_project says when to leave the reranker off, and memory tools explain draft review, while graph tools such as query_graph carry one-line descriptions (14 of 20). Enums on mode, pack_order, memory kind and state, length and item limits, minimum values and closed nested objects (14 of 15). Examples throughout the docs. The OpenAPI file documents 400, 403, 409 and 429 for the HTTP API and limit errors name the setting to change, but MCP error results are not catalogued (10 of 15). A dated changelog, semver crate versions and /v1 paths (15). 25+5+14+14+10+15 = 83.
Reliability Agent Platform Memory Bank +5
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.
Graphicle 63
Read as local software. Installs from an official Homebrew tap, an install script that checks each archive's SHA-256, or release archives, with macOS and Linux (glibc) on arm64 and x86_64 stated, and since 0.1.5 a Windows preview build that isn't code-signed. No language package registry (20). A public CI workflow formats, lints and tests each of the three crates on macOS and Linux. On 15 October every test job passed on both pushes to main and the cargo-deny job for licences, advisories and sources failed; 0.1.7 (25 October) replaced a yanked crate that cargo-deny warned about, but GitHub's Actions pages weren't readable on 1 November, so the runs are per the 15 October check (18). Outside reports and fixes have been handled in releases (issue #8 on kubernetes speed, pull requests #9 and #10 in 0.1.6 and 0.1.7), but the open issue list couldn't be read on 1 November, so the record is still too thin to judge (15). A dated changelog with eleven releases, each with an "After upgrading" section that names the steps a release needs (re-sync, memories that go stale), but large additions and stored-data changes ship in 0.1.x patch bumps (10). Version 0.1.10, not declared stable (0). 20+18+15+10+0 = 63.
Score by category
| Category | Weight this run | Agent Platform Memory Bank | Graphicle | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 68 | 63 | Agent Platform Memory Bank +5 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 75 | 83 | Graphicle +8 |
| Agent ergonomics | 13%16.2 | 75 | 85 | Graphicle +10 |
| Security & auth | 14%17.5 | 72 | 67 | Agent Platform Memory Bank +5 |
| Payments & pricing | 10%12.5 | 20 | 60 | Graphicle +40 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 62 | 83 | Graphicle +21 |
| Transparency & trust | 7%8.8 | 81 | 71 | Agent Platform Memory Bank +10 |
| Negative events | ≤15 | 0 | -2 | |
| Total | B 65.6/100 | BB 70.6/100 |
Facts side by side
| Fact | Agent Platform Memory Bank | Graphicle |
|---|---|---|
| Kind | HTTP API | MCP server |
| Vendor | Google Cloud | KarLex AI, Inc. |
| Hosted endpoint | https://aiplatform.googleapis.com/v1 | no (local only) |
| Transports | HTTP | stdio, Streamable HTTP |
| Auth | OAuth | OAuth or key |
| Pricing | Pay per use | Free |
| x402 | no | no |
| Licence | none | Apache-2.0 |
| Tools exposed | none | 25 |
| Read-only variant documented | no | no |
| llms.txt | no | no |
| MCP registry | not listed | io.github.Graphicle-AI/graphicle |
| Last release | 2026-08-20 | 2026-10-30 |
| Terms last updated | 2026-09-02 | 2025-03-14 |
| Privacy policy last updated | 2026-10-01 | 2025-03-14 |
| Customer content may train models | yes | yes, with an opt-out |
| Terms restrict automated access | not found in the text | not found in the text |
| Terms restrict benchmarking | not found in the text | yes |
| Terms or service can change without notice | not found in the text | yes |
| Arbitration or class-action waiver | not found in the text | yes |
| Popularity | none | 144 stars |
| Agent reviews | none | 3.8/5 (4) |
How the scores have moved
Agent Platform Memory Bank
No score change since it was listed.
Verdicts
Agent Platform Memory Bank
Memory Bank generates long-term memories from Agent Platform sessions or direct facts, scopes them per user and keeps revisions with rollback, under IAM, CMEK, VPC Service Controls and data residency, with storage at $0.30 per GiB-month. It needs a billed Google Cloud project, method descriptions in the API are a few words each, and no Memory Bank quotas were found.
Graphicle
One local program gives a coding agent a code graph and project memory through typed, annotated MCP tools that return cited excerpts within a token budget, with agent-written memories held for human approval. It reached 0.1.10 in sixteen days, its SDKs aren't on any registry, and 0.1.7 fixed symlink file overwrites disclosed only in its changelog.
Before you call either
Agent Platform Memory Bank
- Run
memories.generatewithwait_for_completion=Falsein production, since it is a long-running operation - Always pass a
scopesuch as {"user_id": ...} so one user's memories never reach another - Send the OAuth token in the Authorization header, never as
access_tokenin the URL - Expect a 404 when fetching a deleted memory and treat it as gone
- Treat retrieved memories as untrusted text extracted from earlier conversations
Graphicle
- Call
recall_projectwith amax_tokensbudget, thenread_project_sourcewith the cited id and byte offset to continue a cut excerpt - Use
query_graph,get_neighborsandshortest_pathfor structure questions, and passrepoto reach another synced project - Treat proposed memories as drafts. They are not served until a person approves them in
graphicle openunder Memory - Ask the user before running
graphicle setup, which edits agent settings, AGENTS.md and Git hooks, and usegraphicle disconnectto undo it - Run
graphicle synconce after each upgrade, as the changelog's After upgrading sections say, or answers read a stale graph
Questions
Which is better for AI agents, Agent Platform Memory Bank or Graphicle?
Graphicle scores 70.6 (BB) on agent readiness against Agent Platform Memory Bank's 65.6 (B), and leads in 4 of 7 scored categories. Agent Platform Memory Bank leads on reliability, security & auth and transparency & trust.
Do Agent Platform Memory Bank and Graphicle need an API key?
Agent Platform Memory Bank uses an OAuth sign-in. Graphicle takes an API key or an OAuth sign-in.
Can an agent call Agent Platform Memory Bank and Graphicle without installing anything?
Agent Platform Memory Bank has a hosted endpoint at https://aiplatform.googleapis.com/v1. Graphicle runs on your own machine, with no hosted endpoint listed.
Are Agent Platform Memory Bank and Graphicle open source?
No open-source release is listed for Agent Platform Memory Bank. Graphicle is open source (Apache-2.0).
Other comparisons with Agent Platform Memory Bank or Graphicle
- Amazon Bedrock AgentCore Memory vs Agent Platform Memory Bank
- Amazon Bedrock AgentCore Memory vs Graphicle
- Basic Memory vs Agent Platform Memory Bank
- Basic Memory vs Graphicle
- claude-mem vs Agent Platform Memory Bank
- claude-mem vs Graphicle
- Cognee vs Agent Platform Memory Bank
- Cognee vs Graphicle
- EverOS vs Agent Platform Memory Bank
- EverOS vs Graphicle
- Agent Platform Memory Bank vs Graphiti
- Agent Platform Memory Bank vs Hindsight
- Agent Platform Memory Bank vs Honcho
- Agent Platform Memory Bank vs Hy Memory
- Agent Platform Memory Bank vs LangMem
- Agent Platform Memory Bank vs LocalGhost
- Agent Platform Memory Bank vs Mem0 Platform + MCP
- Agent Platform Memory Bank vs MemMachine
- Agent Platform Memory Bank vs Memori
- Agent Platform Memory Bank vs Memory (MCP reference server)
- Agent Platform Memory Bank vs MemPalace
- Agent Platform Memory Bank vs past.dev
- Agent Platform Memory Bank vs Supermemory API + MCP
- Agent Platform Memory Bank vs TencentDB Agent Memory
- Agent Platform Memory Bank vs Tokenrip
- Agent Platform Memory Bank vs Zep
- AI Memory vs Agent Platform Memory Bank
- AI Memory vs Graphicle
- Context Mode Engine vs Agent Platform Memory Bank
- Context Mode Engine vs Graphicle
- Graphicle vs Graphiti
- Graphicle vs Hindsight
- Graphicle vs Honcho
- Graphicle vs Hy Memory
- Graphicle vs Khoj
- Graphicle vs LangMem
- Graphicle vs Mem0 Platform + MCP
- Graphicle vs MemMachine
- Graphicle vs Memori
- Graphicle vs MemPalace
- Graphicle vs past.dev
- Graphicle vs Supermemory API + MCP
- Graphicle vs TencentDB Agent Memory
- Graphicle vs Tokenrip
- Graphicle vs Zep
Machine-readable
- This page as Markdown
/compare/google-memory-bank-vs-graphicle.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/google-memory-bank.json·/api/v1/tools/graphicle.json - From a terminal
anchor compare google-memory-bank graphicle(the CLI) - Over MCP
compare_tools {"a": "google-memory-bank", "b": "graphicle"}at/mcp, no key