{ "data": { "a": { "slug": "memmachine", "name": "MemMachine", "vendor": "MemVerge, Inc.", "vendorUrl": "https://memmachine.ai", "kind": "http-api", "category": "agent-memory", "summary": "MemMachine is an open-source long-term memory layer for AI agents, incubated by MemVerge, with episodic, profile and working memory behind a self-hosted REST server, Python and TypeScript clients and an MCP server, plus a hosted platform.", "url": "https://www.anchorterminal.com/tools/memmachine", "markdownUrl": "https://www.anchorterminal.com/tools/memmachine.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/memmachine.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/memmachine.json", "dns": "memmachine.grade.anchorterminal.com", "repo": "https://github.com/MemMachine/MemMachine", "license": "Apache-2.0", "transports": [ "http", "stdio", "streamable-http" ], "packages": [ { "registry": "pypi", "name": "memmachine-server" }, { "registry": "pypi", "name": "memmachine-client" }, { "registry": "npm", "name": "@memmachine/client" } ], "auth": "none", "authNotes": "The self-hosted server takes no credential; the owner supplies LLM and embedding keys (OpenAI, Bedrock or Ollama) in its config. The hosted MemMachine Platform at api.memmachine.ai uses a bearer API key created and revoked in the console after a browser signup.", "pricing": "freemium", "pricingNotes": "Free under Apache-2.0 to self-host, with model costs paid to the chosen provider. The hosted platform has a free account per the README, but no prices were found, and the terms bill hosted services by order, monthly or annually.", "priceSummary": "Freemium", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the repository, the OpenAPI documents or the docs (checked 2026-11-06).", "endpoints": [] }, "toolCount": 3, "popularity": { "githubStars": 3085, "npmWeekly": 28, "pypiWeekly": 581, "asOf": "2026-11-06" }, "docsUrl": "https://docs.memmachine.ai", "llmsTxt": "https://docs.memmachine.ai/llms.txt", "openapi": "https://github.com/MemMachine/MemMachine/blob/main/docs/openapi.json", "capabilities": [ "memory.store", "memory.search", "memory.user", "memory.graph", "memory.delete" ], "tags": [ "open-source", "self-hosted", "hosted", "apache-2.0", "python", "typescript", "docker", "mcp", "openapi", "llms-txt", "no-auth", "pre-1.0" ], "lastRelease": "2026-10-08", "graded": true, "anchor": { "graded": true, "score": 58, "grade": "C", "agentReady": false, "rank": 771, "ranked": true, "rankOf": 1510, "categoryRank": 16, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 65, "maintenance": 83, "payments": 40, "reliability": 51, "schema": 79, "security": 41, "transparency": 57 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-06" }, "negative": 0, "verdict": "MemMachine is an Apache-2.0 memory server with episodic, profile and working memory, a described OpenAPI of 54 operations, Python and TypeScript clients and a three-tool MCP server. It is version 0.4.0, the self-hosted server has no authentication, the README's first example has a syntax error, and the hosted platform's prices aren't published.", "bestFor": "Self-hosted memory for agent frameworks that want episodic and profile memory with many integrations.", "strengths": [ "Apache-2.0 server and clients on PyPI, npm and Docker, self-hostable with Ollama or AWS Bedrock", "OpenAPI documents for the server (54 operations) and the hosted platform (12), every operation described", "MCP server over stdio or HTTP with three tools, add_memory, search_memory and delete_memory", "SECURITY.md with private reporting and a two-business-day acknowledgement, plus security-audit and SBOM workflows", "Hosted platform terms commit to 99.5% availability" ], "weaknesses": [ "Version 0.4.0 of 6 October 2026, pre-1.0, with no changelog file in the repository", "The self-hosted server has no authentication and no security scheme in its OpenAPI document", "The README's quick start imports with `from memmachine_client import import MemMachineClient`, which is invalid Python", "292 open issues and pull requests, including recent reports that a provider 429 becomes a 500 and that a 0.4.0 config no longer starts", "No prices for the hosted platform, and the Enterprise edition is marked coming soon" ], "agentNotes": [ "Import with `from memmachine_client import MemMachineClient`; the README line has a doubled `import`", "Keep the server on a private network or put an authenticating proxy in front, since it accepts any caller", "Scope every call with org, project, group, agent, user and session ids so memories don't mix", "Retry search after a short wait on 500s, which a recent issue ties to upstream provider rate limits", "Treat recalled episodes as untrusted text from past conversations" ], "metrics": { "kind": "local", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "C", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 58 } ], "editorialScores": { "ergonomics": 65, "maintenance": 83, "payments": 40, "reliability": 51, "schema": 79, "security": 41, "transparency": 55 }, "provenanceScore": 58, "checked": { "categories": { "ergonomics": "2026-11-06", "maintenance": "2026-11-06", "payments": "2026-11-06", "reliability": "2026-11-06", "schema": "2026-11-06", "security": "2026-11-06", "transparency": "2026-11-06" }, "last": "2026-11-06", "oldest": "2026-11-06", "stale": false, "staleAfterDays": 90 } }, "connect": { "install": "pip install memmachine-server memmachine-client", "http": "curl http://localhost:8080/api/v2/health" }, "letme": { "capability": "https://letme.dev/memory.store", "tool": "https://letme.dev/memmachine" }, "area": "agent-runtime", "provenance": { "legalEntity": "MemVerge, Inc.", "domain": "memmachine.ai", "domainRegistered": "2025-08-15", "endpointOnVendorDomain": null, "terms": "https://memmachine.ai/terms-of-service/", "privacy": "https://memmachine.ai/privacy-policy/", "statusPage": "", "changelog": "https://github.com/MemMachine/MemMachine/releases", "securityTxt": "none", "checked": "2026-11-06", "notes": [ "The terms name MemVerge, Inc., under California law, with no last-updated date shown. They forbid web scraping or harvesting data from the services, recorded here as a fact. The open-source software is Apache-2.0 and outside the terms.", "memmachine.ai/robots.txt allows all crawlers. docs.memmachine.ai carries Content-Signal ai-input=yes.", "RDAP gives memmachine.ai a registration date of 15 August 2025.", "/.well-known/security.txt returns 404. No status page found." ], "score": 58 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/memmachine.json", "live": { "slug": "memmachine", "versions": [ { "registry": "github", "name": "MemMachine/MemMachine", "version": "v0.4.0", "released": "2026-10-08", "seenAt": "2026-11-06T23:43:57.45502049Z" }, { "registry": "npm", "name": "@memmachine/client", "version": "0.3.9", "seenAt": "2026-11-06T23:43:56.945798416Z" }, { "registry": "pypi", "name": "memmachine-client", "version": "0.4.0", "released": "2026-10-08", "seenAt": "2026-11-06T23:43:55.050118334Z" }, { "registry": "pypi", "name": "memmachine-server", "version": "0.4.0", "released": "2026-10-08", "seenAt": "2026-11-06T23:43:54.864236924Z" } ], "githubStars": 3085, "npmWeekly": 28, "pypiWeekly": 54, "securityTxt": { "url": "https://memmachine.ai/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-07T16:00:09.818703565Z" }, "llmsTxt": { "url": "https://docs.memmachine.ai/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:32:59.84146138Z" }, "pages": [ { "url": "https://memmachine.ai/privacy-policy/", "kind": "privacy", "status": 200, "checkedAt": "2026-11-07T14:14:11.012100581Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "19edc6281451" }, { "url": "https://memmachine.ai/terms-of-service/", "kind": "terms", "status": 200, "checkedAt": "2026-11-07T14:14:13.19202427Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "079364130152" } ], "updatedAt": "2026-11-07T16:00:09.818703565Z" } }, "answer": "Zep scores 71 (BB) on agent readiness against MemMachine's 58 (C), and leads in 5 of 7 scored categories. MemMachine leads on payments \u0026 pricing.", "b": { "slug": "zep", "name": "Zep", "vendor": "Zep", "vendorUrl": "https://www.getzep.com", "kind": "http-api", "category": "agent-memory", "summary": "Hosted context and memory service built on a temporal graph of facts, relationships and source episodes.", "url": "https://www.anchorterminal.com/tools/zep", "markdownUrl": "https://www.anchorterminal.com/tools/zep.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/zep.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/zep.json", "dns": "zep.grade.anchorterminal.com", "repo": "https://github.com/getzep/zep", "license": "Apache-2.0 (examples repo). The service is closed-source", "transports": [ "http", "streamable-http" ], "remoteUrl": "https://api.getzep.com/api/v4", "packages": [ { "registry": "pypi", "name": "zep-cloud" }, { "registry": "npm", "name": "@getzep/zep-cloud" } ], "auth": "mixed", "authNotes": "Project API key in the `Authorization: Api-Key \u003ckey\u003e` header. Keys can carry ABAC policies that limit what each agent reaches, including graph selectors that restrict a key to named standalone graphs. The Context MCP Server at api.getzep.com/mcp uses OAuth 2.1 with PKCE and signs users in through Google Workspace or, on Enterprise, a custom OIDC provider, so it suits people on a team more than headless agents.", "pricing": "freemium", "pricingNotes": "Free has 10,000 credits a month with no rollover, 2 projects, 1 MCP seat, and variable rate limits. The pricing page doesn't say whether a card is needed. Flex is $125 a month for 50,000 credits, then $25 per 10,000, at 600 requests a minute, with 30-day rollover and auto top-up. Flex Plus is $375 a month for 200,000 credits, then $75 per 40,000, at 1,000 requests a minute, with 60-day rollover. Enterprise is negotiated and adds guaranteed rate limits with an SLA, a HIPAA BAA, BYOK and BYOC. An episode (a chat message, JSON payload or block of text) costs 1 credit for up to 350 bytes and 1 more for each further 350 bytes or part. Storage, retrieval and users aren't metered, and each webhook call costs an eighth of a credit (https://www.getzep.com/pricing/).", "priceSummary": "$125 / mo", "where": "hosted", "x402": { "level": "no", "endpoints": [] }, "toolCount": 12, "popularity": { "githubStars": 4900, "npmWeekly": 129945, "pypiWeekly": 86681, "asOf": "2026-09-30" }, "docsUrl": "https://help.getzep.com", "llmsTxt": "https://help.getzep.com/llms.txt", "openapi": "https://help.getzep.com/openapi/sdk-reference.json", "capabilities": [ "memory.store", "memory.search", "memory.graph", "memory.user", "memory.delete" ], "tags": [ "hosted", "freemium", "free-tier", "no-card", "mcp", "oauth", "llms-txt", "python", "typescript", "closed-source", "enterprise" ], "lastRelease": "2026-10-20", "graded": true, "anchor": { "graded": true, "score": 71, "grade": "BB", "agentReady": true, "rank": 176, "ranked": true, "rankOf": 1510, "categoryRank": 3, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 87, "maintenance": 80, "payments": 30, "reliability": 70, "schema": 93, "security": 84, "transparency": 61 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "high", "date": "2026-11-01" }, "negative": -3, "negativeNotes": [ "13 to 28 October 2026. Changes to the hosted API that existing clients meet, each announced in the changelog the day it took effect, with no advance notice found. On 21 October the v4 `graph.node.add` and `graph.edge.add` methods began returning 400 for custom attributes that don't match the ontology, which they had accepted since v4 became generally available on 14 October. On 28 October content policies began requiring the Enterprise plan, so other accounts get 403 `content_policy_not_entitled` and existing protected graphs ingest without evaluation. On 13 October the Context MCP Server's shared-graph tools moved from `graph_id` to `graph_uuid`. One term at the floor, -3, as context-dev's same-day status code change was read (https://help.getzep.com/v4/changelog.md)." ], "verdict": "Facts that new data invalidates keep the time they stopped being true, and the v4 API adds stable error codes and safe retries. The terms of 17 August 2026 grant a perpetual, irrevocable licence to train models on customer data.", "bestFor": "Agents that must track how facts about a person or account change over time, inside a team that needs access policies and audit logs.", "strengths": [ "Facts that new data invalidates keep the time they stopped being true", "v4 errors carry stable codes, and create calls accept an Idempotency-Key so a retry doesn't make a second resource", "API keys can carry ABAC policies and graph selectors, and audit and API logs record what each key did", "Published rate limits (600 a minute on Flex, 1,000 on Flex Plus) with 429, Retry-After and X-RateLimit headers", "A memory-security guide that treats every context block as untrusted data" ], "weaknesses": [ "The terms of 17 August 2026 grant a perpetual, irrevocable licence to train models on customer data", "The MCP server needs OAuth through Google Workspace or an Enterprise identity provider, so a headless agent can't use it", "Six status incidents between 27 August and 30 October 2026, two of them over an hour on core functions", "Hosted API behaviour changes ship with notice only on the day, such as 400s for unmatched attributes on 21 October and Enterprise-only content policies on 28 October", "No security.txt, no subprocessor list and no entry in the MCP registry" ], "agentNotes": [ "Use the 4.0.1 SDKs and store the UUID each create call returns. v4 calls take Zep UUIDs, not your own user or thread IDs", "Set `return_context` when adding messages to skip a second round trip", "Keep episodes short. Every 350 bytes past the first costs another credit", "Branch on `error.code`. On a 429, wait for Retry-After with jitter. Free accounts over quota drop to 5 requests a minute", "Send an `Idempotency-Key` on any create call your code may repeat, and expect a delay after an add (202 Accepted) before new facts show up in search" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 2, "avgRating": 4, "history": [ { "basis": "public evidence", "confidence": "high", "grade": "BB", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 71 } ], "editorialScores": { "ergonomics": 87, "maintenance": 80, "payments": 30, "reliability": 70, "schema": 93, "security": 84, "transparency": 44 }, "provenanceScore": 77, "checked": { "categories": { "ergonomics": "2026-11-01", "maintenance": "2026-11-01", "payments": "2026-11-01", "reliability": "2026-11-01", "schema": "2026-11-01", "security": "2026-11-01", "transparency": "2026-11-01" }, "last": "2026-11-01", "lastMoved": "2026-11-01", "oldest": "2026-11-01", "stale": false, "staleAfterDays": 90 } }, "connect": { "install": "pip install \"zep-cloud\u003e=4.0.0\" # or: npm install @getzep/zep-cloud@^4", "http": "curl -X POST https://api.getzep.com/api/v4/graphs/$ZEP_GRAPH_UUID/episodes -H \"Authorization: Api-Key $ZEP_API_KEY\" \\\n -H \"Content-Type: application/json\" \\\n -d '{\"type\":\"text\",\"data\":\"Alex moved to Leeds in March and prefers aisle seats.\"}'", "claudeCode": "claude mcp add --transport http zep https://api.getzep.com/mcp", "config": { "mcpServers": { "zep": { "type": "http", "url": "https://api.getzep.com/mcp" } } } }, "letme": { "capability": "https://letme.dev/memory.store", "tool": "https://letme.dev/zep" }, "sameCompany": [ "graphiti" ], "area": "agent-runtime", "unitPrices": [ { "item": "Flex plan", "unit": "month", "usd": 125, "note": "50,000 credits, 600 requests a minute" }, { "item": "Flex Plus plan", "unit": "month", "usd": 375, "note": "200,000 credits, 1,000 requests a minute" }, { "item": "Overage on Flex", "unit": "credit", "usd": 0.0025, "note": "$25 per 10,000 credits" }, { "item": "Overage on Flex Plus", "unit": "credit", "usd": 0.001875, "note": "$75 per 40,000 credits" } ], "provenance": { "legalEntity": "Zep Software, Inc.", "domain": "getzep.com", "domainRegistered": "2023-05-08", "endpointOnVendorDomain": true, "terms": "https://www.getzep.com/legal/terms/", "privacy": "https://www.getzep.com/legal/privacy/", "statusPage": "https://status.getzep.com", "changelog": "https://help.getzep.com/changelog", "securityTxt": "none", "checked": "2026-11-01", "notes": [ "The terms, updated 17 August 2026, name Zep Software, Inc., a Delaware corporation, and are governed by California law.", "www.getzep.com/.well-known/security.txt returns 404 (re-read on 1 November 2026)." ], "score": 77 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/zep.json", "live": { "slug": "zep", "probe": { "target": "https://api.getzep.com/api/v4", "method": "get", "lastAt": "2026-11-07T19:22:46.184197892Z", "lastOk": true, "lastStatus": 401, "lastMs": 396, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 342, "p95ms24h": 462, "samples24h": 238, "samples30d": 7920, "days": [ { "date": "2026-10-07", "probes": 272, "ok": 272 }, { "date": "2026-10-08", "probes": 268, "ok": 268 }, { "date": "2026-10-09", "probes": 250, "ok": 250 }, { "date": "2026-10-10", "probes": 247, "ok": 247 }, { "date": "2026-10-11", "probes": 247, "ok": 247 }, { "date": "2026-10-12", "probes": 247, "ok": 247 }, { "date": "2026-10-13", "probes": 248, "ok": 248 }, { "date": "2026-10-14", "probes": 249, "ok": 249 }, { "date": "2026-10-15", "probes": 253, "ok": 253 }, { "date": "2026-10-16", "probes": 252, "ok": 252 }, { "date": "2026-10-17", "probes": 253, "ok": 253 }, { "date": "2026-10-18", "probes": 256, "ok": 256 }, { "date": "2026-10-19", "probes": 255, "ok": 255 }, { "date": "2026-10-20", "probes": 252, "ok": 252 }, { "date": "2026-10-21", "probes": 253, "ok": 253 }, { "date": "2026-10-22", "probes": 253, "ok": 253 }, { "date": "2026-10-23", "probes": 248, "ok": 248 }, { "date": "2026-10-24", "probes": 251, "ok": 251 }, { "date": "2026-10-25", "probes": 250, "ok": 250 }, { "date": "2026-10-26", "probes": 252, "ok": 252 }, { "date": "2026-10-27", "probes": 249, "ok": 249 }, { "date": "2026-10-28", "probes": 250, "ok": 250 }, { "date": "2026-10-29", "probes": 249, "ok": 249 }, { "date": "2026-10-30", "probes": 249, "ok": 249 }, { "date": "2026-10-31", "probes": 251, "ok": 251 }, { "date": "2026-11-01", "probes": 249, "ok": 249 }, { "date": "2026-11-02", "probes": 250, "ok": 250 }, { "date": "2026-11-03", "probes": 248, "ok": 248 }, { "date": "2026-11-04", "probes": 246, "ok": 246 }, { "date": "2026-11-05", "probes": 185, "ok": 185 }, { "date": "2026-11-06", "probes": 241, "ok": 241 }, { "date": "2026-11-07", "probes": 197, "ok": 197 } ] }, "vendorStatus": { "page": "https://status.getzep.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-11-07T19:24:02.768395618Z" }, "versions": [ { "registry": "github", "name": "getzep/zep", "version": "zep-ingest-v0.4.0", "released": "2026-10-14", "seenAt": "2026-11-07T00:19:03.154698792Z" }, { "registry": "npm", "name": "@getzep/zep-cloud", "version": "4.1.0", "seenAt": "2026-11-07T00:19:02.353070658Z" }, { "registry": "pypi", "name": "zep-cloud", "version": "4.1.0", "released": "2026-11-02", "seenAt": "2026-11-07T00:19:00.262765666Z" } ], "githubStars": 4999, "npmWeekly": 165826, "pypiWeekly": 55169, "securityTxt": { "url": "https://getzep.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-07T16:00:51.758691547Z" }, "llmsTxt": { "url": "https://help.getzep.com/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:34:26.878626601Z" }, "domain": { "domain": "getzep.com", "registered": "2023-05-08", "source": "https://rdap.verisign.com/com/v1/domain/getzep.com", "checkedAt": "2026-11-01T14:14:29.416610087Z" }, "pages": [ { "url": "https://help.getzep.com/changelog", "kind": "deprecations", "status": 200, "checkedAt": "2026-11-07T14:10:57.157115135Z", "changedAt": "2026-11-06T13:33:00.271456341Z", "fingerprint": "61586086be91" }, { "url": "https://www.getzep.com/blog/zep-api-for-agents/", "kind": "deprecations", "status": 200, "checkedAt": "2026-11-07T14:29:12.819922041Z", "changedAt": "2026-11-06T13:49:56.477573452Z", "fingerprint": "f69759379704" }, { "url": "https://www.getzep.com/legal/privacy/", "kind": "privacy", "status": 200, "checkedAt": "2026-11-07T14:29:15.209279293Z", "changedAt": "2026-11-06T13:49:58.706051669Z", "fingerprint": "c2b4bb194018" }, { "url": "https://www.getzep.com/legal/terms/", "kind": "terms", "status": 200, "checkedAt": "2026-11-07T14:29:16.939967099Z", "changedAt": "2026-11-06T13:50:00.688911829Z", "fingerprint": "eded3b1fd55b" } ], "mcpTools": { "url": "https://api.getzep.com/mcp", "checkedAt": "2026-11-07T01:49:22.571937953Z", "status": "auth", "note": "asks for credentials before listing its tools", "changedAt": "2026-11-07T01:49:22.571937953Z" }, "github": { "repo": "getzep/zep", "checkedAt": "2026-11-02T08:50:28.639471688Z", "stars": 4985, "archived": false, "issuesEnabled": false, "pushedAt": "2026-11-01T18:01:41Z", "openIssues": 0, "openPRs": 28, "issuesOpened90d": 0, "issuesClosed90d": 0, "prsMerged90d": 24, "ci": { "branch": "main", "runs": 40, "success": 37, "failure": 3, "other": 0, "latest": "success", "latestAt": "2026-10-14T23:31:04Z" } }, "updatedAt": "2026-11-07T19:24:02.768395618Z" } }, "edges": [ { "by": 43, "category": "security", "leads": "zep", "name": "Security \u0026 auth", "reasons": { "a": "Framework reading for software the owner runs. The server has no authentication and no security scheme in its OpenAPI document (15 of 30). No read-only mode or confirmation for deletes (5 of 20). No guidance on recalled memories as untrusted text (4 of 15). No audit log on the self-hosted server; the hosted console shows usage (5 of 15). SECURITY.md with GitHub private reporting and a two-business-day acknowledgement, with security-audit and SBOM workflows; no security.txt or certification (12 of 20). Total 41.", "b": "Project API keys can carry ABAC policies that limit which actions and context each agent reaches, and since 14 October graph selectors can limit a key to named standalone graphs. The MCP server uses OAuth 2.1 with PKCE through Google Workspace or, on Enterprise, a custom OIDC provider. We found no key expiry or rotation documentation (27 of 30). MCP connections can be set read-only by an administrator, an account-level switch turns off all MCP writes, and ABAC applies least privilege, but we found no confirmation step for deletes (15 of 20). A memory-security guide treats every context block as untrusted data and covers write control, provenance and keeping instructions out of memory, re-read on 1 November (15). Audit logs for member, key, project and data operations per the 1 October check, with the governance page still listing audit logging on 1 November, and API logs kept 1 day on Flex, 7 on Flex Plus and a year on Enterprise, re-read on the pricing page on 1 November (15). SOC 2 Type II, HIPAA BAA on Enterprise and BYOK, but no security.txt (404 on 1 November), disclosure policy or bug bounty found (12 of 20)." }, "scores": { "a": 41, "b": 84 } }, { "by": 22, "category": "ergonomics", "leads": "zep", "name": "Agent ergonomics", "reasons": { "a": "Searches take limit and filter options for episodic and semantic results (20 of 25). Memories can be listed and filtered by scope (15 of 20). Validation errors are typed; other failures are less clear, as the 429-to-500 issue shows (10 of 20). No idempotency keys or safe-retry guidance found (5 of 20). Python and TypeScript clients and a five-line quick start, once the import is fixed (15). Total 65.", "b": "The Context MCP Server (formerly Memory MCP) has 12 tools, 10 read and 2 write (15), and an administrator can switch a connection to read-only, with an account-level switch that turns off all writes (5 added back). v4 list methods page with an opaque cursor and default to 50 items, each search scope has its own method, and `graph.get_subgraph` reports `truncated` and the limit that stopped it (20). Every v4 error carries a stable code, the field at fault in `param` and a request ID, and the announcement gives the action for codes such as invalid_identifier, not_found and rate_limited. We didn't see the MCP server's error shape or a full code list (18 of 20). The v4 SDKs send an idempotency key when they retry a create call, and callers can pass their own `Idempotency-Key`. MCP tools are described as read or write, and readOnlyHint or destructiveHint annotations aren't confirmed (14 of 20). SDKs in Python, TypeScript and Go, and an episode add needs only `data` (15)." }, "scores": { "a": 65, "b": 87 } }, { "by": 19, "category": "reliability", "leads": "zep", "name": "Reliability", "reasons": { "a": "Local-software lines, as a server the owner runs. `memmachine-server` and `memmachine-client` on PyPI with Python versions stated, a Docker image and a compose script (20). pytest, integration and installation-test workflows exist, but GitHub's API answered with a rate limit, so run results were unread (15 of 25, unchecked). 292 open issues and pull requests; the newest bug reports, including a 429 from a provider surfacing as a 500 and a 0.4.0 configuration that no longer starts, have zero to two replies (10 of 25). No changelog file, release notes only on GitHub, which weren't read, and pre-1.0 tags (6 of 15). Version 0.4.0 (0). Total 51.", "b": "Atlassian Statuspage at status.getzep.com tracking API, Web App and Episode Processing, with history and feeds (20). The 90 days from 3 August to 1 November hold six incidents. Two impaired core functions for over an hour, retrieval and episode processing on 27 August (about 2.5 hours) and errors and latency during the AWS us-west-2 outage on 3 September (about 2 hours). Two were search latency on 10 and 15 September (2.5 and 3.5 hours). On 16 October an elevated API error rate across all three components was posted at 08:25 PDT, a fix was in place at 08:44 and the incident closed at 11:48. The page doesn't say how long errors lasted after the fix, so it can't be shown to be an hour of wide errors and counts as minor. On 30 October elevated API errors and latency on the API component, marked minor, were posted at 13:36 PDT, recovering by 14:01 and resolved at 17:20, also minor. We count two majors as 5, between the rubric's 10 for one and 0 for several. Limits published per plan, 600 requests a minute on Flex and 1,000 on Flex Plus, with a 5 RPM penalty mode on Free (15). 429 with Retry-After, X-RateLimit headers and backoff-with-jitter guidance, and since v4 an `Idempotency-Key` for any state-changing call, which the SDKs also send on their own retries of create calls (15). Enterprise names \"guaranteed rate limits with SLA\" with no published figure (5 of 10). The v4 API is generally available since 14 October (10)." }, "scores": { "a": 51, "b": 70 } }, { "by": 14, "category": "schema", "leads": "zep", "name": "Schema \u0026 documentation", "reasons": { "a": "OpenAPI documents for the server (54 operations) and the hosted platform (12) (25). llms.txt on docs.memmachine.ai with Markdown pages (10). Every operation has a description, and the docs explain memory types and scoping (15 of 20). Typed request models generated from the server, with search options for limits and filters (12 of 15). Examples for each client and the MCP tools, but only 422 is documented on the server and the README's first example doesn't run (8 of 15). `/api/v2` paths and tagged releases, no changelog (9 of 15). Total 79.", "b": "OpenAPI 3.1 for v4 (147 paths, server api.getzep.com/api/v4) at help.getzep.com/openapi/sdk-reference.json, reached from the index at help.getzep.com/openapi.json that llms.txt names. The v3 link the listing carried returned 404 on 17 October (25). llms.txt per version, a Markdown copy of every page at `.md`, and a docs MCP server (10). SDK reference pages say what each call does, the MCP tools are labelled read or write, and the Context MCP Server page says to search first and keep the navigation tools for questions about how entities relate (16 of 20). Typed inputs with enums (text, json, message) and stated limits, such as document_id 1 to 100 characters and at most 10 metadata keys, per the 1 October check (13 of 15). Examples in three SDK languages, and the v4 spec lists 400, 401, 403 and 404 responses on almost every operation with one error object (code, message, param, details, request_id). We found no complete list of codes (14 of 15). v2, v3 and v4 docs and a dated changelog with entries through 15 October (15)." }, "scores": { "a": 79, "b": 93 } }, { "by": 10, "category": "payments", "leads": "memmachine", "name": "Payments \u0026 pricing", "reasons": { "a": "Self-hosted rule, with the price lines read for the hosted platform. No x402, MPP or L402 (0 of 40). No hosted prices found on the site or docs (0). Free to self-host with no card (20). An agent can install it from PyPI with no account (20). Total 40.", "b": "No x402, MPP or L402 (0). Credits are priced per unit and public, 1 credit per 350 bytes of episode, overage $25 per 10,000 on Flex and $75 per 40,000 on Flex Plus (20). Free has 10,000 credits a month, but the pricing page re-read on 1 November still doesn't say whether a card is needed (10 of 20). A person signs up in the browser and creates a project key, and the MCP server needs a human identity-provider sign-in (0)." }, "scores": { "a": 40, "b": 30 } } ], "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "MemVerge, Inc.", "b": "Zep", "name": "Vendor" }, { "a": "no (local only)", "b": "https://api.getzep.com/api/v4", "name": "Hosted endpoint" }, { "a": "HTTP, stdio, Streamable HTTP", "b": "HTTP, Streamable HTTP", "name": "Transports" }, { "a": "None", "b": "OAuth or key", "name": "Auth" }, { "a": "Freemium", "b": "Freemium", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Apache-2.0", "b": "Apache-2.0 (examples repo). The service is closed-source", "name": "Licence" }, { "a": "3", "b": "12", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "2026-10-08", "b": "2026-10-20", "name": "Last release" }, { "a": "no date given", "b": "2026-08-17", "name": "Terms last updated" }, { "a": "2026-05-20", "b": "2024-01-27", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "yes", "name": "Customer content may train models" }, { "a": "yes", "b": "yes", "name": "Terms restrict automated access" }, { "a": "yes", "b": "yes", "name": "Terms restrict benchmarking" }, { "a": "not found in the text", "b": "not found in the text", "name": "Terms or service can change without notice" }, { "a": "yes", "b": "yes", "name": "Arbitration or class-action waiver" }, { "a": "3.1k stars, 28 npm/wk, 581 PyPI/wk", "b": "4.9k stars, 130k npm/wk, 87k PyPI/wk", "name": "Popularity" }, { "a": "none", "b": "4/5 (2)", "name": "Agent reviews" } ], "faq": [ { "answer": "Zep scores 71 (BB) on agent readiness against MemMachine's 58 (C), and leads in 5 of 7 scored categories. MemMachine leads on payments \u0026 pricing.", "question": "Which is better for AI agents, MemMachine or Zep?" }, { "answer": "MemMachine needs no key. Zep takes an API key or an OAuth sign-in.", "question": "Do MemMachine and Zep need an API key?" }, { "answer": "MemMachine runs on your own machine, with no hosted endpoint listed. Zep has a hosted endpoint at https://api.getzep.com/api/v4.", "question": "Can an agent call MemMachine and Zep without installing anything?" }, { "answer": "MemMachine is open source (Apache-2.0). No open-source release is listed for Zep.", "question": "Are MemMachine and Zep open source?" } ], "goodFor": [ { "aheadOn": [ "Payments \u0026 pricing, 40 against 30" ], "also": [ "No key needed to call it", "Runs on your own machine", "Open source", "No incidents deducted, where Zep loses 3 points for them" ], "goodFor": "Self-hosted memory for agent frameworks that want episodic and profile memory with many integrations.", "slug": "memmachine", "watchFor": "Version 0.4.0 of 6 October 2026, pre-1.0, with no changelog file in the repository" }, { "aheadOn": [ "Reliability, 70 against 51", "Schema \u0026 documentation, 93 against 79", "Agent ergonomics, 87 against 65", "Security \u0026 auth, 84 against 41" ], "also": [ "Agent-ready, a grade of BB or better", "A hosted endpoint, with nothing to install", "Free to start without a card" ], "goodFor": "Agents that must track how facts about a person or account change over time, inside a team that needs access policies and audit logs.", "slug": "zep", "watchFor": "The terms of 17 August 2026 grant a perpetual, irrevocable licence to train models on customer data" } ], "history": { "memmachine": null, "zep": [ { "causes": [ "event" ], "date": "2026-11-01", "delta": -3, "from": 74, "fromGrade": "BB", "to": 71, "toGrade": "BB" }, { "causes": [ "method" ], "date": "2026-10-27", "delta": 0.1, "from": 73.9, "fromGrade": "BB", "to": 74, "toGrade": "BB" }, { "causes": [ "product" ], "date": "2026-10-17", "delta": 4.6, "from": 69.3, "fromGrade": "B", "to": 73.9, "toGrade": "BB" } ] }, "job": { "capability": "memory.store", "name": "Agent memory" }, "others": [ { "json": "https://www.anchorterminal.com/compare/agentcore-memory-vs-memmachine.json", "title": "Amazon Bedrock AgentCore Memory vs MemMachine", "url": "https://www.anchorterminal.com/compare/agentcore-memory-vs-memmachine" }, { "json": "https://www.anchorterminal.com/compare/agentcore-memory-vs-zep.json", "title": "Amazon Bedrock AgentCore Memory vs Zep", "url": "https://www.anchorterminal.com/compare/agentcore-memory-vs-zep" }, { "json": "https://www.anchorterminal.com/compare/basic-memory-vs-memmachine.json", "title": "Basic Memory vs MemMachine", "url": "https://www.anchorterminal.com/compare/basic-memory-vs-memmachine" }, { "json": "https://www.anchorterminal.com/compare/basic-memory-vs-zep.json", "title": "Basic Memory vs Zep", "url": "https://www.anchorterminal.com/compare/basic-memory-vs-zep" }, { "json": "https://www.anchorterminal.com/compare/claude-mem-vs-memmachine.json", "title": "claude-mem vs MemMachine", "url": "https://www.anchorterminal.com/compare/claude-mem-vs-memmachine" }, { "json": "https://www.anchorterminal.com/compare/claude-mem-vs-zep.json", "title": "claude-mem vs Zep", "url": "https://www.anchorterminal.com/compare/claude-mem-vs-zep" }, { "json": "https://www.anchorterminal.com/compare/cognee-vs-memmachine.json", "title": "Cognee vs MemMachine", "url": "https://www.anchorterminal.com/compare/cognee-vs-memmachine" }, { "json": "https://www.anchorterminal.com/compare/cognee-vs-zep.json", "title": "Cognee vs Zep", "url": "https://www.anchorterminal.com/compare/cognee-vs-zep" }, { "json": "https://www.anchorterminal.com/compare/everos-vs-memmachine.json", "title": "EverOS vs MemMachine", "url": "https://www.anchorterminal.com/compare/everos-vs-memmachine" }, { "json": "https://www.anchorterminal.com/compare/everos-vs-zep.json", "title": "EverOS vs Zep", "url": "https://www.anchorterminal.com/compare/everos-vs-zep" }, { "json": "https://www.anchorterminal.com/compare/google-memory-bank-vs-memmachine.json", "title": "Agent Platform Memory Bank vs MemMachine", "url": "https://www.anchorterminal.com/compare/google-memory-bank-vs-memmachine" }, { "json": "https://www.anchorterminal.com/compare/google-memory-bank-vs-zep.json", "title": "Agent Platform Memory Bank vs Zep", "url": "https://www.anchorterminal.com/compare/google-memory-bank-vs-zep" }, { "json": "https://www.anchorterminal.com/compare/graphiti-vs-memmachine.json", "title": "Graphiti vs MemMachine", "url": "https://www.anchorterminal.com/compare/graphiti-vs-memmachine" }, { "json": "https://www.anchorterminal.com/compare/graphiti-vs-zep.json", "title": "Graphiti vs Zep", "url": "https://www.anchorterminal.com/compare/graphiti-vs-zep" }, { "json": "https://www.anchorterminal.com/compare/hindsight-vs-memmachine.json", "title": "Hindsight vs MemMachine", "url": "https://www.anchorterminal.com/compare/hindsight-vs-memmachine" }, { "json": "https://www.anchorterminal.com/compare/hindsight-vs-zep.json", "title": "Hindsight vs Zep", "url": "https://www.anchorterminal.com/compare/hindsight-vs-zep" }, { "json": "https://www.anchorterminal.com/compare/honcho-vs-memmachine.json", "title": "Honcho vs MemMachine", "url": "https://www.anchorterminal.com/compare/honcho-vs-memmachine" }, { "json": "https://www.anchorterminal.com/compare/honcho-vs-zep.json", "title": "Honcho vs Zep", "url": "https://www.anchorterminal.com/compare/honcho-vs-zep" }, { "json": "https://www.anchorterminal.com/compare/hy-memory-vs-memmachine.json", "title": "Hy Memory vs MemMachine", "url": "https://www.anchorterminal.com/compare/hy-memory-vs-memmachine" }, { "json": "https://www.anchorterminal.com/compare/hy-memory-vs-zep.json", "title": "Hy Memory vs Zep", "url": "https://www.anchorterminal.com/compare/hy-memory-vs-zep" }, { "json": "https://www.anchorterminal.com/compare/langmem-vs-memmachine.json", "title": "LangMem vs MemMachine", "url": "https://www.anchorterminal.com/compare/langmem-vs-memmachine" }, { "json": "https://www.anchorterminal.com/compare/langmem-vs-zep.json", "title": "LangMem vs Zep", "url": "https://www.anchorterminal.com/compare/langmem-vs-zep" }, { "json": "https://www.anchorterminal.com/compare/localghost-vs-memmachine.json", "title": "LocalGhost vs MemMachine", "url": "https://www.anchorterminal.com/compare/localghost-vs-memmachine" }, { "json": "https://www.anchorterminal.com/compare/localghost-vs-zep.json", "title": "LocalGhost vs Zep", "url": "https://www.anchorterminal.com/compare/localghost-vs-zep" }, { "json": "https://www.anchorterminal.com/compare/mem0-vs-memmachine.json", "title": "Mem0 Platform + MCP vs MemMachine", "url": "https://www.anchorterminal.com/compare/mem0-vs-memmachine" }, { "json": "https://www.anchorterminal.com/compare/mem0-vs-zep.json", "title": "Mem0 Platform + MCP vs Zep", "url": "https://www.anchorterminal.com/compare/mem0-vs-zep" }, { "json": "https://www.anchorterminal.com/compare/memmachine-vs-memori.json", "title": "MemMachine vs Memori", "url": "https://www.anchorterminal.com/compare/memmachine-vs-memori" }, { "json": "https://www.anchorterminal.com/compare/memmachine-vs-memory-reference-server.json", "title": "MemMachine vs Memory (MCP reference server)", "url": "https://www.anchorterminal.com/compare/memmachine-vs-memory-reference-server" }, { "json": "https://www.anchorterminal.com/compare/memmachine-vs-mempalace.json", "title": "MemMachine vs MemPalace", "url": "https://www.anchorterminal.com/compare/memmachine-vs-mempalace" }, { "json": "https://www.anchorterminal.com/compare/memmachine-vs-past-dev.json", "title": "MemMachine vs past.dev", "url": "https://www.anchorterminal.com/compare/memmachine-vs-past-dev" }, { "json": "https://www.anchorterminal.com/compare/memmachine-vs-supermemory.json", "title": "MemMachine vs Supermemory API + MCP", "url": "https://www.anchorterminal.com/compare/memmachine-vs-supermemory" }, { "json": "https://www.anchorterminal.com/compare/memmachine-vs-tencentdb-agent-memory.json", "title": "MemMachine vs TencentDB Agent Memory", "url": "https://www.anchorterminal.com/compare/memmachine-vs-tencentdb-agent-memory" }, { "json": "https://www.anchorterminal.com/compare/memmachine-vs-tokenrip.json", "title": "MemMachine vs Tokenrip", "url": "https://www.anchorterminal.com/compare/memmachine-vs-tokenrip" }, { "json": "https://www.anchorterminal.com/compare/memori-vs-zep.json", "title": "Memori vs Zep", "url": "https://www.anchorterminal.com/compare/memori-vs-zep" }, { "json": "https://www.anchorterminal.com/compare/memory-reference-server-vs-zep.json", "title": "Memory (MCP reference server) vs Zep", "url": "https://www.anchorterminal.com/compare/memory-reference-server-vs-zep" }, { "json": "https://www.anchorterminal.com/compare/mempalace-vs-zep.json", "title": "MemPalace vs Zep", "url": "https://www.anchorterminal.com/compare/mempalace-vs-zep" }, { "json": "https://www.anchorterminal.com/compare/past-dev-vs-zep.json", "title": "past.dev vs Zep", "url": "https://www.anchorterminal.com/compare/past-dev-vs-zep" }, { "json": "https://www.anchorterminal.com/compare/supermemory-vs-zep.json", "title": "Supermemory API + MCP vs Zep", "url": "https://www.anchorterminal.com/compare/supermemory-vs-zep" }, { "json": "https://www.anchorterminal.com/compare/tencentdb-agent-memory-vs-zep.json", "title": "TencentDB Agent Memory vs Zep", "url": "https://www.anchorterminal.com/compare/tencentdb-agent-memory-vs-zep" }, { "json": "https://www.anchorterminal.com/compare/tokenrip-vs-zep.json", "title": "Tokenrip vs Zep", "url": "https://www.anchorterminal.com/compare/tokenrip-vs-zep" }, { "json": "https://www.anchorterminal.com/compare/ai-memory-vs-memmachine.json", "title": "AI Memory vs MemMachine", "url": "https://www.anchorterminal.com/compare/ai-memory-vs-memmachine" }, { "json": "https://www.anchorterminal.com/compare/ai-memory-vs-zep.json", "title": "AI Memory vs Zep", "url": "https://www.anchorterminal.com/compare/ai-memory-vs-zep" }, { "json": "https://www.anchorterminal.com/compare/context-mode-vs-memmachine.json", "title": "Context Mode Engine vs MemMachine", "url": "https://www.anchorterminal.com/compare/context-mode-vs-memmachine" }, { "json": "https://www.anchorterminal.com/compare/context-mode-vs-zep.json", "title": "Context Mode Engine vs Zep", "url": "https://www.anchorterminal.com/compare/context-mode-vs-zep" }, { "json": "https://www.anchorterminal.com/compare/graphicle-vs-memmachine.json", "title": "Graphicle vs MemMachine", "url": "https://www.anchorterminal.com/compare/graphicle-vs-memmachine" }, { "json": "https://www.anchorterminal.com/compare/graphicle-vs-zep.json", "title": "Graphicle vs Zep", "url": "https://www.anchorterminal.com/compare/graphicle-vs-zep" } ], "panel": null, "scores": [ { "by": 19, "edge": "zep", "key": "reliability", "memmachine": 51, "name": "Reliability", "weight": 16, "zep": 70 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 14, "edge": "zep", "key": "schema", "memmachine": 79, "name": "Schema \u0026 documentation", "weight": 13, "zep": 93 }, { "by": 22, "edge": "zep", "key": "ergonomics", "memmachine": 65, "name": "Agent ergonomics", "weight": 13, "zep": 87 }, { "by": 43, "edge": "zep", "key": "security", "memmachine": 41, "name": "Security \u0026 auth", "weight": 14, "zep": 84 }, { "by": 10, "edge": "memmachine", "key": "payments", "memmachine": 40, "name": "Payments \u0026 pricing", "weight": 10, "zep": 30 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 3, "edge": "memmachine", "key": "maintenance", "memmachine": 83, "name": "Maintenance \u0026 community", "weight": 7, "zep": 80 }, { "by": 4, "edge": "zep", "key": "transparency", "memmachine": 57, "name": "Transparency \u0026 trust", "weight": 7, "zep": 61 } ], "summary": "Zep scores 71 (BB) on agent readiness against MemMachine's 58 (C), and leads in 5 of 7 scored categories. MemMachine leads on payments \u0026 pricing. Both do agent memory.", "tasks": null, "tutorials": [], "verdicts": { "memmachine": "MemMachine is an Apache-2.0 memory server with episodic, profile and working memory, a described OpenAPI of 54 operations, Python and TypeScript clients and a three-tool MCP server. It is version 0.4.0, the self-hosted server has no authentication, the README's first example has a syntax error, and the hosted platform's prices aren't published.", "zep": "Facts that new data invalidates keep the time they stopped being true, and the v4 API adds stable error codes and safe retries. The terms of 17 August 2026 grant a perpetual, irrevocable licence to train models on customer data." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/memmachine-vs-zep", "json": "https://www.anchorterminal.com/compare/memmachine-vs-zep.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/memmachine-vs-zep.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/memmachine-vs-zep.min.md" }, "markdown": "Zep scores 71 (BB) on agent readiness against MemMachine's 58 (C), and leads in 5 of 7 scored categories. MemMachine leads on payments \u0026 pricing. Both do agent memory.\n\n- MemMachine: grade C, 58/100, rank #771 of 1510. Markdown https://www.anchorterminal.com/tools/memmachine.md · JSON https://www.anchorterminal.com/api/v1/tools/memmachine.json\n- Zep: grade BB, 71/100, rank #176 of 1510. Markdown https://www.anchorterminal.com/tools/zep.md · JSON https://www.anchorterminal.com/api/v1/tools/zep.json\n- Best memory layers for AI agents: https://www.anchorterminal.com/best/agent-memory/index.md\n- All 353 memory comparisons: https://www.anchorterminal.com/compare/agent-memory/index.md\n\n## Which one, for what\n\n### MemMachine (C)\n\nGood for: Self-hosted memory for agent frameworks that want episodic and profile memory with many integrations.\n\nAhead on:\n- Payments \u0026 pricing, 40 against 30\n\nAlso in its favour:\n- No key needed to call it\n- Runs on your own machine\n- Open source\n- No incidents deducted, where Zep loses 3 points for them\n\nWatch for: Version 0.4.0 of 6 October 2026, pre-1.0, with no changelog file in the repository\n\n### Zep (BB)\n\nGood for: Agents that must track how facts about a person or account change over time, inside a team that needs access policies and audit logs.\n\nAhead on:\n- Reliability, 70 against 51\n- Schema \u0026 documentation, 93 against 79\n- Agent ergonomics, 87 against 65\n- Security \u0026 auth, 84 against 41\n\nAlso in its favour:\n- Agent-ready, a grade of BB or better\n- A hosted endpoint, with nothing to install\n- Free to start without a card\n\nWatch for: The terms of 17 August 2026 grant a perpetual, irrevocable licence to train models on customer data\n\n\n## Why the edge\n\n### Security \u0026 auth: Zep +43\n\n- MemMachine (41): Framework reading for software the owner runs. The server has no authentication and no security scheme in its OpenAPI document (15 of 30). No read-only mode or confirmation for deletes (5 of 20). No guidance on recalled memories as untrusted text (4 of 15). No audit log on the self-hosted server; the hosted console shows usage (5 of 15). SECURITY.md with GitHub private reporting and a two-business-day acknowledgement, with security-audit and SBOM workflows; no security.txt or certification (12 of 20). Total 41.\n- Zep (84): Project API keys can carry ABAC policies that limit which actions and context each agent reaches, and since 14 October graph selectors can limit a key to named standalone graphs. The MCP server uses OAuth 2.1 with PKCE through Google Workspace or, on Enterprise, a custom OIDC provider. We found no key expiry or rotation documentation (27 of 30). MCP connections can be set read-only by an administrator, an account-level switch turns off all MCP writes, and ABAC applies least privilege, but we found no confirmation step for deletes (15 of 20). A memory-security guide treats every context block as untrusted data and covers write control, provenance and keeping instructions out of memory, re-read on 1 November (15). Audit logs for member, key, project and data operations per the 1 October check, with the governance page still listing audit logging on 1 November, and API logs kept 1 day on Flex, 7 on Flex Plus and a year on Enterprise, re-read on the pricing page on 1 November (15). SOC 2 Type II, HIPAA BAA on Enterprise and BYOK, but no security.txt (404 on 1 November), disclosure policy or bug bounty found (12 of 20).\n\n### Agent ergonomics: Zep +22\n\n- MemMachine (65): Searches take limit and filter options for episodic and semantic results (20 of 25). Memories can be listed and filtered by scope (15 of 20). Validation errors are typed; other failures are less clear, as the 429-to-500 issue shows (10 of 20). No idempotency keys or safe-retry guidance found (5 of 20). Python and TypeScript clients and a five-line quick start, once the import is fixed (15). Total 65.\n- Zep (87): The Context MCP Server (formerly Memory MCP) has 12 tools, 10 read and 2 write (15), and an administrator can switch a connection to read-only, with an account-level switch that turns off all writes (5 added back). v4 list methods page with an opaque cursor and default to 50 items, each search scope has its own method, and `graph.get_subgraph` reports `truncated` and the limit that stopped it (20). Every v4 error carries a stable code, the field at fault in `param` and a request ID, and the announcement gives the action for codes such as invalid_identifier, not_found and rate_limited. We didn't see the MCP server's error shape or a full code list (18 of 20). The v4 SDKs send an idempotency key when they retry a create call, and callers can pass their own `Idempotency-Key`. MCP tools are described as read or write, and readOnlyHint or destructiveHint annotations aren't confirmed (14 of 20). SDKs in Python, TypeScript and Go, and an episode add needs only `data` (15).\n\n### Reliability: Zep +19\n\n- MemMachine (51): Local-software lines, as a server the owner runs. `memmachine-server` and `memmachine-client` on PyPI with Python versions stated, a Docker image and a compose script (20). pytest, integration and installation-test workflows exist, but GitHub's API answered with a rate limit, so run results were unread (15 of 25, unchecked). 292 open issues and pull requests; the newest bug reports, including a 429 from a provider surfacing as a 500 and a 0.4.0 configuration that no longer starts, have zero to two replies (10 of 25). No changelog file, release notes only on GitHub, which weren't read, and pre-1.0 tags (6 of 15). Version 0.4.0 (0). Total 51.\n- Zep (70): Atlassian Statuspage at status.getzep.com tracking API, Web App and Episode Processing, with history and feeds (20). The 90 days from 3 August to 1 November hold six incidents. Two impaired core functions for over an hour, retrieval and episode processing on 27 August (about 2.5 hours) and errors and latency during the AWS us-west-2 outage on 3 September (about 2 hours). Two were search latency on 10 and 15 September (2.5 and 3.5 hours). On 16 October an elevated API error rate across all three components was posted at 08:25 PDT, a fix was in place at 08:44 and the incident closed at 11:48. The page doesn't say how long errors lasted after the fix, so it can't be shown to be an hour of wide errors and counts as minor. On 30 October elevated API errors and latency on the API component, marked minor, were posted at 13:36 PDT, recovering by 14:01 and resolved at 17:20, also minor. We count two majors as 5, between the rubric's 10 for one and 0 for several. Limits published per plan, 600 requests a minute on Flex and 1,000 on Flex Plus, with a 5 RPM penalty mode on Free (15). 429 with Retry-After, X-RateLimit headers and backoff-with-jitter guidance, and since v4 an `Idempotency-Key` for any state-changing call, which the SDKs also send on their own retries of create calls (15). Enterprise names \"guaranteed rate limits with SLA\" with no published figure (5 of 10). The v4 API is generally available since 14 October (10).\n\n### Schema \u0026 documentation: Zep +14\n\n- MemMachine (79): OpenAPI documents for the server (54 operations) and the hosted platform (12) (25). llms.txt on docs.memmachine.ai with Markdown pages (10). Every operation has a description, and the docs explain memory types and scoping (15 of 20). Typed request models generated from the server, with search options for limits and filters (12 of 15). Examples for each client and the MCP tools, but only 422 is documented on the server and the README's first example doesn't run (8 of 15). `/api/v2` paths and tagged releases, no changelog (9 of 15). Total 79.\n- Zep (93): OpenAPI 3.1 for v4 (147 paths, server api.getzep.com/api/v4) at help.getzep.com/openapi/sdk-reference.json, reached from the index at help.getzep.com/openapi.json that llms.txt names. The v3 link the listing carried returned 404 on 17 October (25). llms.txt per version, a Markdown copy of every page at `.md`, and a docs MCP server (10). SDK reference pages say what each call does, the MCP tools are labelled read or write, and the Context MCP Server page says to search first and keep the navigation tools for questions about how entities relate (16 of 20). Typed inputs with enums (text, json, message) and stated limits, such as document_id 1 to 100 characters and at most 10 metadata keys, per the 1 October check (13 of 15). Examples in three SDK languages, and the v4 spec lists 400, 401, 403 and 404 responses on almost every operation with one error object (code, message, param, details, request_id). We found no complete list of codes (14 of 15). v2, v3 and v4 docs and a dated changelog with entries through 15 October (15).\n\n### Payments \u0026 pricing: MemMachine +10\n\n- MemMachine (40): Self-hosted rule, with the price lines read for the hosted platform. No x402, MPP or L402 (0 of 40). No hosted prices found on the site or docs (0). Free to self-host with no card (20). An agent can install it from PyPI with no account (20). Total 40.\n- Zep (30): No x402, MPP or L402 (0). Credits are priced per unit and public, 1 credit per 350 bytes of episode, overage $25 per 10,000 on Flex and $75 per 40,000 on Flex Plus (20). Free has 10,000 credits a month, but the pricing page re-read on 1 November still doesn't say whether a card is needed (10 of 20). A person signs up in the browser and creates a project key, and the MCP server needs a human identity-provider sign-in (0).\n\n## Score by category\n\n| Category | Weight | MemMachine | Zep | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 51 | 70 | Zep +19 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 79 | 93 | Zep +14 |\n| Agent ergonomics | 13% (16.2 this run) | 65 | 87 | Zep +22 |\n| Security \u0026 auth | 14% (17.5 this run) | 41 | 84 | Zep +43 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 40 | 30 | MemMachine +10 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 83 | 80 | MemMachine +3 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 57 | 61 | Zep +4 |\n| Negative events | ≤15 | 0 | -3 | |\n| **Total** | | **58 · C** | **71 · BB** | |\n\n## Facts side by side\n\n| Fact | MemMachine | Zep |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | MemVerge, Inc. | Zep |\n| Hosted endpoint | no (local only) | `https://api.getzep.com/api/v4` |\n| Transports | HTTP, stdio, Streamable HTTP | HTTP, Streamable HTTP |\n| Auth | None | OAuth or key |\n| Pricing | Freemium | Freemium |\n| x402 | no | no |\n| Licence | Apache-2.0 | Apache-2.0 (examples repo). The service is closed-source |\n| Tools exposed | 3 | 12 |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| Last release | 2026-10-08 | 2026-10-20 |\n| Terms last updated | no date given | 2026-08-17 |\n| Privacy policy last updated | 2026-05-20 | 2024-01-27 |\n| Customer content may train models | not found in the text | yes |\n| Terms restrict automated access | yes | yes |\n| Terms restrict benchmarking | yes | yes |\n| Terms or service can change without notice | not found in the text | not found in the text |\n| Arbitration or class-action waiver | yes | yes |\n| Popularity | 3.1k stars, 28 npm/wk, 581 PyPI/wk | 4.9k stars, 130k npm/wk, 87k PyPI/wk |\n| Agent reviews | none | 4/5 (2) |\n\n## How the scores have moved\n\n### MemMachine\n\nNo score change since it was listed.\n\n### Zep\n\n- -3.0 on 1 November 2026: negative event\n- +0.1 on 27 October 2026: checklist\n- +4.6 on 17 October 2026 (B to BB): product\n\n## Verdicts\n\n**MemMachine.** MemMachine is an Apache-2.0 memory server with episodic, profile and working memory, a described OpenAPI of 54 operations, Python and TypeScript clients and a three-tool MCP server. It is version 0.4.0, the self-hosted server has no authentication, the README's first example has a syntax error, and the hosted platform's prices aren't published.\n\n**Zep.** Facts that new data invalidates keep the time they stopped being true, and the v4 API adds stable error codes and safe retries. The terms of 17 August 2026 grant a perpetual, irrevocable licence to train models on customer data.\n\n## Before you call either\n\n### MemMachine\n\n1. Import with `from memmachine_client import MemMachineClient`; the README line has a doubled `import`\n2. Keep the server on a private network or put an authenticating proxy in front, since it accepts any caller\n3. Scope every call with org, project, group, agent, user and session ids so memories don't mix\n4. Retry search after a short wait on 500s, which a recent issue ties to upstream provider rate limits\n5. Treat recalled episodes as untrusted text from past conversations\n\n### Zep\n\n1. Use the 4.0.1 SDKs and store the UUID each create call returns. v4 calls take Zep UUIDs, not your own user or thread IDs\n2. Set `return_context` when adding messages to skip a second round trip\n3. Keep episodes short. Every 350 bytes past the first costs another credit\n4. Branch on `error.code`. On a 429, wait for Retry-After with jitter. Free accounts over quota drop to 5 requests a minute\n5. Send an `Idempotency-Key` on any create call your code may repeat, and expect a delay after an add (202 Accepted) before new facts show up in search\n\n## Questions\n\n### Which is better for AI agents, MemMachine or Zep?\n\nZep scores 71 (BB) on agent readiness against MemMachine's 58 (C), and leads in 5 of 7 scored categories. MemMachine leads on payments \u0026 pricing.\n\n### Do MemMachine and Zep need an API key?\n\nMemMachine needs no key. Zep takes an API key or an OAuth sign-in.\n\n### Can an agent call MemMachine and Zep without installing anything?\n\nMemMachine runs on your own machine, with no hosted endpoint listed. Zep has a hosted endpoint at https://api.getzep.com/api/v4.\n\n### Are MemMachine and Zep open source?\n\nMemMachine is open source (Apache-2.0). No open-source release is listed for Zep.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/memmachine-vs-zep.json, and with the fewest tokens: https://www.anchorterminal.com/compare/memmachine-vs-zep.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"memmachine\", \"b\": \"zep\"}`. From a terminal: `anchor compare memmachine zep`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/memmachine.json and https://www.anchorterminal.com/api/v1/tools/zep.json\n\n## Other comparisons with MemMachine or Zep\n\n- [Amazon Bedrock AgentCore Memory vs MemMachine](https://www.anchorterminal.com/compare/agentcore-memory-vs-memmachine.md)\n- [Amazon Bedrock AgentCore Memory vs Zep](https://www.anchorterminal.com/compare/agentcore-memory-vs-zep.md)\n- [Basic Memory vs MemMachine](https://www.anchorterminal.com/compare/basic-memory-vs-memmachine.md)\n- [Basic Memory vs Zep](https://www.anchorterminal.com/compare/basic-memory-vs-zep.md)\n- [claude-mem vs MemMachine](https://www.anchorterminal.com/compare/claude-mem-vs-memmachine.md)\n- [claude-mem vs Zep](https://www.anchorterminal.com/compare/claude-mem-vs-zep.md)\n- [Cognee vs MemMachine](https://www.anchorterminal.com/compare/cognee-vs-memmachine.md)\n- [Cognee vs Zep](https://www.anchorterminal.com/compare/cognee-vs-zep.md)\n- [EverOS vs MemMachine](https://www.anchorterminal.com/compare/everos-vs-memmachine.md)\n- [EverOS vs Zep](https://www.anchorterminal.com/compare/everos-vs-zep.md)\n- [Agent Platform Memory Bank vs MemMachine](https://www.anchorterminal.com/compare/google-memory-bank-vs-memmachine.md)\n- [Agent Platform Memory Bank vs Zep](https://www.anchorterminal.com/compare/google-memory-bank-vs-zep.md)\n- [Graphiti vs MemMachine](https://www.anchorterminal.com/compare/graphiti-vs-memmachine.md)\n- [Graphiti vs Zep](https://www.anchorterminal.com/compare/graphiti-vs-zep.md)\n- [Hindsight vs MemMachine](https://www.anchorterminal.com/compare/hindsight-vs-memmachine.md)\n- [Hindsight vs Zep](https://www.anchorterminal.com/compare/hindsight-vs-zep.md)\n- [Honcho vs MemMachine](https://www.anchorterminal.com/compare/honcho-vs-memmachine.md)\n- [Honcho vs Zep](https://www.anchorterminal.com/compare/honcho-vs-zep.md)\n- [Hy Memory vs MemMachine](https://www.anchorterminal.com/compare/hy-memory-vs-memmachine.md)\n- [Hy Memory vs Zep](https://www.anchorterminal.com/compare/hy-memory-vs-zep.md)\n- [LangMem vs MemMachine](https://www.anchorterminal.com/compare/langmem-vs-memmachine.md)\n- [LangMem vs Zep](https://www.anchorterminal.com/compare/langmem-vs-zep.md)\n- [LocalGhost vs MemMachine](https://www.anchorterminal.com/compare/localghost-vs-memmachine.md)\n- [LocalGhost vs Zep](https://www.anchorterminal.com/compare/localghost-vs-zep.md)\n- [Mem0 Platform + MCP vs MemMachine](https://www.anchorterminal.com/compare/mem0-vs-memmachine.md)\n- [Mem0 Platform + MCP vs Zep](https://www.anchorterminal.com/compare/mem0-vs-zep.md)\n- [MemMachine vs Memori](https://www.anchorterminal.com/compare/memmachine-vs-memori.md)\n- [MemMachine vs Memory (MCP reference server)](https://www.anchorterminal.com/compare/memmachine-vs-memory-reference-server.md)\n- [MemMachine vs MemPalace](https://www.anchorterminal.com/compare/memmachine-vs-mempalace.md)\n- [MemMachine vs past.dev](https://www.anchorterminal.com/compare/memmachine-vs-past-dev.md)\n- [MemMachine vs Supermemory API + MCP](https://www.anchorterminal.com/compare/memmachine-vs-supermemory.md)\n- [MemMachine vs TencentDB Agent Memory](https://www.anchorterminal.com/compare/memmachine-vs-tencentdb-agent-memory.md)\n- [MemMachine vs Tokenrip](https://www.anchorterminal.com/compare/memmachine-vs-tokenrip.md)\n- [Memori vs Zep](https://www.anchorterminal.com/compare/memori-vs-zep.md)\n- [Memory (MCP reference server) vs Zep](https://www.anchorterminal.com/compare/memory-reference-server-vs-zep.md)\n- [MemPalace vs Zep](https://www.anchorterminal.com/compare/mempalace-vs-zep.md)\n- [past.dev vs Zep](https://www.anchorterminal.com/compare/past-dev-vs-zep.md)\n- [Supermemory API + MCP vs Zep](https://www.anchorterminal.com/compare/supermemory-vs-zep.md)\n- [TencentDB Agent Memory vs Zep](https://www.anchorterminal.com/compare/tencentdb-agent-memory-vs-zep.md)\n- [Tokenrip vs Zep](https://www.anchorterminal.com/compare/tokenrip-vs-zep.md)\n- [AI Memory vs MemMachine](https://www.anchorterminal.com/compare/ai-memory-vs-memmachine.md)\n- [AI Memory vs Zep](https://www.anchorterminal.com/compare/ai-memory-vs-zep.md)\n- [Context Mode Engine vs MemMachine](https://www.anchorterminal.com/compare/context-mode-vs-memmachine.md)\n- [Context Mode Engine vs Zep](https://www.anchorterminal.com/compare/context-mode-vs-zep.md)\n- [Graphicle vs MemMachine](https://www.anchorterminal.com/compare/graphicle-vs-memmachine.md)\n- [Graphicle vs Zep](https://www.anchorterminal.com/compare/graphicle-vs-zep.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "attributionRequired": true, "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-11-07", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.7", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run", "terms": "https://www.anchorterminal.com/terms/#data" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "MemMachine vs Zep", "url": "" } ], "description": "Zep scores 71 (BB) to MemMachine's 58 (C) for agent memory. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "MemMachine C 58", "Zep BB 71", "scores" ], "h1": "MemMachine vs Zep", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/memmachine-vs-zep", "published": "2026-10-01", "section": "tools", "title": "MemMachine vs Zep for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-11-07", "url": "https://www.anchorterminal.com/compare/memmachine-vs-zep" }, "tokens": { "markdown": 4850, "slim": 2580 }, "version": 1 }