Agent Platform Memory Bank vs past.dev

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.

past.dev 40

No x402, MPP or L402. A spent balance returns 402 out-of-credits with no payment payload (0 of 40). Credit prices are public without a login, one credit per 350 bytes and packs from $0.30 to $0.13 per 1,000 credits, re-read on 2 November (20). Pay as you go starts with 150,000 credits, 400,000 with a work email, and the pricing page says no card is required (20). A person signs up in a browser. The agent_auth flow lets an agent get a token for a person who already has an account and approves it in a browser, which still needs a human signup (0). 0 + 20 + 20 + 0 = 40.

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.

past.dev 77

Read for a closed service. The changelog's newest entry is the week of 19 October 2026, with framework connectors, MCP deletion tools and a breaking refusal of / in data point ids (30). Seven dated weekly entries in the 90 days from 4 August (weeks of 24 August, 14, 21 and 28 September, and 5, 12 and 19 October), and the integrations post of 28 October (20). A public changelog, a community Slack and email support on Flex, none of which we tested (10 of 15). The MCP server is in the official MCP registry as dev.past/past under the past.dev domain namespace, published 30 September 2026, and official framework packages now exist on npm and PyPI, but there is no general-purpose SDK (12 of 15; was 5). The Claude Code and Codex plugin repositories are MIT with a check.yml workflow, with CI results unchecked, per the 19 October check (5 of 10). 30 + 20 + 10 + 12 + 5 = 77.

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.

past.dev 66

Closed service under clear, dated terms (27 October 2026) naming Revo Inc., a Delaware corporation doing business as Past Corp. (15). The privacy policy (27 October 2026) says content isn't used for training, deletion removes derived facts, a deleted organisation's backups expire within 7 days, the request log follows the plan's retention and a project and everything derived from it are deleted on request. The security page says model providers process requests with zero retention. The pricing page gives data retention of 365 days on Pay as you go and 3 years on Flex, while the privacy policy says memory is kept while the organisation exists, so the two don't fully agree (20 of 30). The terms promise email before a change removes a capability an account uses, and the changelog says breaking changes are announced before release. Breaking changes shipped in the weeks of 21 September and 19 October, and there is no versioning or dated deprecation policy (8 of 20). AWS is named as host. The privacy policy now puts the sub-processor list and hosting regions in the trust centre at security.revo.ai, which is drawn by script and wasn't readable on 19 October, and the security page gives them on request (5 of 20). 15 + 20 + 8 + 5 = 48.

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.

past.dev 86

OpenAPI 3.1.0 at past.dev/openapi.json with 34 operations on 27 paths, re-read on 2 November (25). llms.txt with a "When to use" section, llms-full.txt, a Markdown copy of every page and a docs MCP server (10). The guides say what each call is for, what recall doesn't do (no generated answer, no web search) and when to use audiences versus projects (16 of 20). 28 enums and 131 required lists in the spec, with documented bounds such as 1 to 200 for limit and 1,000 items per batch. metadata is a free-form object that never filters recall (13 of 15). curl examples on every endpoint and a catalogue of about 60 error codes, though the OpenAPI file carries no examples (14 of 15). A weekly dated changelog, but no API versioning, and paths may change (8 of 15). 25 + 10 + 16 + 13 + 14 + 8 = 86.

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.

past.dev 83

Graded on the Memory API, with the MCP servers noted. Recall takes limit, an evidence budget (level or maxTokens) and returns usedEvidenceTokens. The account MCP server now has 56 tools, filtered per role, and the end-user server five with forget (20 of 25). Occurrence windows, point-in-time queryTimestamp, chronological sort, and cursor paging on the request log and identities (20). Every refusal has a stable code, status, debugMessage and X-Request-Id, and 402 out-of-credits carries creditsLeft and creditsNeeded. The 429 has no body (18 of 20). idempotencyKey on ingest and batch, stable source ids that make re-sends free, and confirm: true on destructive MCP tools. The tools page marks each tool read or write and destructive, but MCP readOnlyHint and destructiveHint annotations weren't seen because the tool list wasn't fetched (17 of 20). Two required fields on ingest and recall. Since the 19 October check past.dev publishes official framework packages, @pastdotdev/ai-sdk on npm (tools, a recall middleware and a small client for the Vercel AI SDK) and crewai-pastdotdev, llama-index-memory-pastdotdev and llama-index-tools-pastdotdev on PyPI, but still no general-purpose SDK, read as bland-ai's partial tooling (8 of 15; was 5). 20 + 20 + 18 + 17 + 8 = 83.

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.

past.dev 64

Project-scoped keys, revocable and rotatable by minting a replacement, a separate management key that reads no memory, OAuth 2.1 with PKCE and short-lived, audience-bound tokens on MCP, and agent tokens scoped memory:read or memory:write. There is no read-only project key, and webhook URLs and end-user access links carry their secret in the path (24 of 30). Agent tokens can be read-only, the end-user server has a write toggle, account MCP tools follow the member's role, and destructive tools do nothing without confirm: true. A project key can still delete any data in its project (15 of 20). Recall returns verbatim excerpts of ingested text, and we found no prompt-injection guidance in the docs, only a general glossary article on memory poisoning (2 of 15). Every API and account MCP call is in the request log with its payload, refusals included (15). security.txt is valid until 1 May 2027 and the security page names support@past.dev for vulnerability reports. No bug bounty or public advisories. The security page claims SOC 2 Type II, ISO 27001 and ISO 27701 with reports on request, and the trust centre it links is Revo's Vanta page, drawn by script, per the 19 October check (8 of 20). 24 + 15 + 2 + 15 + 8 = 64.