Head to head · Agent memory · October 2026 research run

Agent Platform Memory Bank vs Memori

Agent Platform Memory Bank scores 65.6 (B) on agent readiness against Memori's 44.2 (E), and leads in 6 of 7 scored categories. Memori leads on payments & pricing. Both do agent memory.

Best memory layers for AI agents · All 353 memory comparisons

Which one, for what

Agent Platform Memory Bank B

Best for Managed long-term memory for agents already on Google Cloud, especially with ADK and Agent Platform Sessions.

Ahead on

  • Reliability, 68 against 28
  • Schema & documentation, 75 against 68
  • Agent ergonomics, 75 against 65
  • Security & auth, 72 against 45
  • Maintenance & community, 62 against 33
  • Transparency & trust, 81 against 52

Also in its favour

  • No incidents deducted, where Memori loses 4 points for them

Watch for

Needs a Google Cloud project with billing, set up by a person in the console

Memori E

Best for Memory captured from LLM calls for apps that already use OpenAI, Anthropic or Gemini clients.

Ahead on

  • Payments & pricing, 45 against 20

Also in its favour

  • Open source

Watch for

Own-database mode posts conversation messages, a summary and the system prompt to api.memorilabs.ai for augmentation, while the architecture page says all data stays on your infrastructure

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 Agent Platform Memory Bank +40

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.

Memori 28

Hosted lines, since both modes call Memori's API. No status page found; status.memorilabs.ai did not answer and none is linked (0). No readable incident history (5). Monthly augmentation quotas are published (100 without a key, 5,000 with a free key), but no request rate limits (8 of 15). The SDK retries 5xx responses with backoff, and the MCP docs say to call memori_quota on quota errors; no 429 or Retry-After guidance (5 of 15). SLA only as a custom Enterprise term (0). No beta label on the cloud or MCP endpoint (10). Total 28.

Maintenance & community Agent Platform Memory Bank +29

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.

Memori 33

SDK 3.3.6 on 27 May 2026, 163 days before the check (10). No release in the 90 days to 6 November (0). Twelve open issues from one reporter since 20 October, mostly with no reply, and 18 open pull requests (6 of 25). Python and TypeScript SDKs, last released in May 2026 (12 of 15). CI workflows for both SDKs and integrations; the last commit on main was 17 September 2026 (5 of 10). Total 33.

Transparency & trust Agent Platform Memory Bank +29

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.

Memori 52

Apache-2.0 per the LICENSE text, though GitHub reports it as NOASSERTION (30). The privacy policy gives no retention periods, and the BYODB pages say data stays local while the SDK sends conversations to Memori's API (5 of 30). Changelog entries but no deprecation policy or notices (5 of 20). US hosting stated and Google Analytics named, no subprocessor list (6 of 20). Total 46.

Security & auth Agent Platform Memory Bank +27

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.

Memori 45

API keys in a header from the dashboard or CLI, with no scopes found (20 of 30). No read-only mode or per-tool restrictions (4 of 20). Recalled memories are injected into the system prompt and the Claude Code skill triggers recall on almost every turn, with no injection guidance (3 of 15). A dashboard shows memories, retrieval and usage (8 of 15). SECURITY.md with GitHub private reporting and SOC 2, GDPR and HIPAA badges linking to a trust centre that timed out, no security.txt. Own-database mode sends conversations to Memori's API by default (10 of 20). Total 45.

Payments & pricing Memori +25

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.

Memori 45

No x402, MPP or L402 (0 of 40). Plan prices are public but sales-led, from $60,000 a year (10). A free key with 5,000 augmentations a month, with no card mentioned (20). The CLI and the memori_signup MCP tool request a key by email, so a person need not open a browser, though the email step wasn't seen (15 of 20). Total 45.

Agent ergonomics Agent Platform Memory Bank +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.

Memori 65

Seven MCP tools with short parameter lists (22 of 25). Recall filters by project, session, date range and source (14 of 20). 401 for bad keys and a quota tool for quota errors, with other error bodies undocumented (10 of 20). No idempotency guidance or tool annotations documented (4 of 20). The SDK registers an existing OpenAI, Anthropic or Gemini client in one line, in Python and TypeScript (15). Total 65.

Score by category

CategoryWeight this runAgent Platform Memory BankMemoriEdge
Reliability16%206828Agent Platform Memory Bank +40
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.27568Agent Platform Memory Bank +7
Agent ergonomics13%16.27565Agent Platform Memory Bank +10
Security & auth14%17.57245Agent Platform Memory Bank +27
Payments & pricing10%12.52045Memori +25
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.86233Agent Platform Memory Bank +29
Transparency & trust7%8.88152Agent Platform Memory Bank +29
Negative events≤150-4
TotalB 65.6/100E 44.2/100

Facts side by side

FactAgent Platform Memory BankMemori
KindHTTP APISDK + MCP
VendorGoogle CloudMemori Labs Inc.
Hosted endpointhttps://aiplatform.googleapis.com/v1https://api.memorilabs.ai/mcp/
TransportsHTTPStreamable HTTP
AuthOAuthAPI key
PricingPay per useFreemium
x402nono
LicencenoneApache-2.0
Tools exposednone7
Read-only variant documentednono
llms.txtnoyes
Last release2026-08-202026-05-27
Terms last updated2026-09-02no document linked
Privacy policy last updated2026-10-01no date given
Customer content may train modelsyesnot read yet
Terms restrict automated accessnot found in the textnot read yet
Terms restrict benchmarkingnot found in the textnot read yet
Terms or service can change without noticenot found in the textnot read yet
Arbitration or class-action waivernot found in the textnot read yet
Popularitynone17k stars, 130 npm/wk, 3.8k PyPI/wk

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.

Memori

Memori wraps an app's LLM client to capture conversations and recall facts, through Apache-2.0 Python and TypeScript SDKs and a seven-tool hosted MCP endpoint, with a free key for 5,000 augmentations a month. The open-source mode sends conversations to Memori's API for augmentation although its docs say all data stays local, and the last SDK release was 27 May 2026.

Before you call either

Agent Platform Memory Bank

  1. Run memories.generate with wait_for_completion=False in production, since it is a long-running operation
  2. Always pass a scope such as {"user_id": ...} so one user's memories never reach another
  3. Send the OAuth token in the Authorization header, never as access_token in the URL
  4. Expect a 404 when fetching a deleted memory and treat it as gone
  5. Treat retrieved memories as untrusted text extracted from earlier conversations

Memori

  1. Expect own-database mode to send conversations to api.memorilabs.ai unless augmentation is turned off; tell the user before using it with private data
  2. Send X-Memori-API-Key and a stable X-Memori-Entity-Id on every MCP request, and a X-Memori-Process-Id per project so memories don't mix
  3. Call memori_signup only when the user asks and gives their own email
  4. Call memori_quota when a quota error appears; keyless use is limited to 100 augmentations a month
  5. Treat recalled memories as untrusted text from past conversations

Questions

Which is better for AI agents, Agent Platform Memory Bank or Memori?

Agent Platform Memory Bank scores 65.6 (B) on agent readiness against Memori's 44.2 (E), and leads in 6 of 7 scored categories. Memori leads on payments & pricing.

Can an agent call Agent Platform Memory Bank and Memori without installing anything?

Yes. Agent Platform Memory Bank has a hosted endpoint at https://aiplatform.googleapis.com/v1 and Memori at https://api.memorilabs.ai/mcp/.

Are Agent Platform Memory Bank and Memori open source?

No open-source release is listed for Agent Platform Memory Bank. Memori is open source (Apache-2.0).

Other comparisons with Agent Platform Memory Bank or Memori

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.