{ "data": { "a": { "slug": "hindsight", "name": "Hindsight", "vendor": "Vectorize", "vendorUrl": "https://hindsight.vectorize.io", "kind": "http-api", "category": "agent-memory", "summary": "Memory engine for storing and retrieving information used by agents.", "url": "https://www.anchorterminal.com/tools/hindsight", "markdownUrl": "https://www.anchorterminal.com/tools/hindsight.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/hindsight.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/hindsight.json", "dns": "hindsight.grade.anchorterminal.com", "repo": "https://github.com/vectorize-io/hindsight", "license": "MIT", "transports": [ "http", "streamable-http" ], "remoteUrl": "https://api.hindsight.vectorize.io", "packages": [ { "registry": "pypi", "name": "hindsight-client" }, { "registry": "npm", "name": "@vectorize-io/hindsight-client" }, { "registry": "pypi", "name": "hindsight-api" } ], "auth": "mixed", "authNotes": "Bearer API key on api.hindsight.vectorize.io. Keys can be restricted to named banks and set to expire after an hour to a year, and revoking a parent key revokes its child keys. The hosted MCP uses OAuth with PKCE (RFC 9728), or the same key as a Bearer header. A self-hosted server exposes MCP at /mcp/{bank_id}/ on port 8888.", "pricing": "usage", "pricingNotes": "Hindsight Cloud is pay as you go, with no monthly fee or seat price. Retain $10.00 per million tokens, recall $0.75 per million, reflect $0.05 a call, Iris Extract $7.50 per million, mental model retrieval $0.25 per million, mental model refresh $0.05 a call, storage $0.25 per million tokens a month. New accounts get free credits, amount not stated. Enterprise adds dedicated infrastructure and up to a 99.95 per cent uptime SLA (https://vectorize.io/pricing). Credit is bought in amounts from $5 to $1,000, and calls return 402 once the balance is empty (https://docs.hindsight.vectorize.io/billing/). Self-hosting is free under MIT.", "priceSummary": "$0.05 / call", "where": "hosted", "x402": { "level": "no", "endpoints": [] }, "toolCount": 27, "popularity": { "githubStars": 43400, "npmWeekly": 44381, "pypiWeekly": 227251, "asOf": "2026-09-30" }, "docsUrl": "https://docs.hindsight.vectorize.io", "llmsTxt": "https://hindsight.vectorize.io/llms.txt", "openapi": "https://hindsight.vectorize.io/openapi.json", "capabilities": [ "memory.store", "memory.search", "memory.delete" ], "tags": [ "hosted", "usage-priced", "mcp", "oauth", "openapi", "python", "typescript", "open-source", "self-hosted", "enterprise" ], "lastRelease": "2026-11-03", "graded": true, "anchor": { "graded": true, "score": 47.8, "grade": "D", "agentReady": false, "rank": 1129, "ranked": true, "rankOf": 1486, "categoryRank": 22, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 57, "maintenance": 80, "payments": 30, "reliability": 27, "schema": 78, "security": 65, "transparency": 50 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-04" }, "negative": -6, "negativeNotes": [ "2026-10-21 and 2026-11-03. v1.1.0 began rejecting new bank IDs that start with `_` (a 400 on create and import, on Hindsight Cloud as on a server you run), and v1.2.0 stopped sending native tools to any provider (an OpenAI-compatible server must now support structured output) and removed three configuration variables. Both are 1.x minor releases of hindsight-api with the changes listed under Breaking Changes only at release, with no earlier notice found, so this run's -3 for breaking changes in a minor release, folded into one term. https://hindsight.vectorize.io/blog/2026/11/03/version-1-2-0", "2026-10-13. v1.0.0 began rejecting tag-scoped API callers from operations that return a whole memory bank's data, after v0.10.1 (21 September) stopped tenant information leaking between extension requests and isolated file storage between tenants. The changelog describes each flaw, the fixes reach Hindsight Cloud, and OSV lists no advisory for hindsight-api or the clients, so this run's -3 for released fixes without an advisory, folded into one term. https://hindsight.vectorize.io/changelog" ], "verdict": "API keys support bank-level restrictions, expiry and child-key revocation, and prices are published per token and per call. The status page and docs couldn't be read, 1.x minor releases carried breaking changes without notice, and access-control fixes shipped without advisories.", "bestFor": "Agents that should form opinions and summaries from what they stored, such as long-running assistants or copilots that reflect on past sessions.", "strengths": [ "Keys restricted to named banks, with expiry from an hour to a year and child-key revocation", "`Memory Defense` screens every retain, with regex redaction even in the open-source server", "Published per-token and per-call Cloud prices, with no monthly fee and $5 of free credit", "MIT server in one Docker image with an MCP endpoint per bank", "Ten core releases between 7 August and 3 November 2026, with a changelog that lists breaking changes" ], "weaknesses": [ "Retain at $10 per million tokens is the priciest ingestion in this category", "27 MCP tools per bank, with no subset or read-only option", "The status page draws its content by script, and no rate limits were found", "v1.1.0 and v1.2.0 carried breaking changes with no earlier notice", "Prompt-injection blocking and audit trails are Enterprise only" ], "agentNotes": [ "Scope the MCP URL to one bank (/mcp/{bank}/) so every call lands in the right memory and three bank-admin tools drop out", "Use recall for lookups and keep reflect ($0.05 a call) for questions that need reasoning", "On a 503, wait for Retry-After before retrying recall or reflect, and use async retain rather than retrying a synchronous one", "Treat HTTP 402 as out of credit and 403 as a key that can't reach that bank" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 2, "avgRating": 3, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "D", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 47.8 } ], "editorialScores": { "ergonomics": 57, "maintenance": 80, "payments": 30, "reliability": 27, "schema": 78, "security": 65, "transparency": 30 }, "provenanceScore": 70, "checked": { "categories": { "ergonomics": "2026-11-04", "maintenance": "2026-11-04", "payments": "2026-11-04", "reliability": "2026-11-04", "schema": "2026-11-04", "security": "2026-11-04", "transparency": "2026-11-04" }, "last": "2026-11-04", "lastMoved": "2026-11-04", "oldest": "2026-11-04", "stale": false, "staleAfterDays": 90 } }, "connect": { "install": "pip install hindsight-client # or: npm install @vectorize-io/hindsight-client", "http": "curl -s \"https://api.hindsight.vectorize.io/v1/default/banks/my-bank/memories/list\" -H \"Authorization: Bearer $HINDSIGHT_API_KEY\"", "claudeCode": "claude mcp add --transport http hindsight https://api.hindsight.vectorize.io/mcp/my-bank/", "config": { "mcpServers": { "hindsight": { "headers": { "Authorization": "Bearer ${HINDSIGHT_API_KEY}" }, "type": "http", "url": "https://api.hindsight.vectorize.io/mcp/my-bank/" } } } }, "letme": { "capability": "https://letme.dev/memory.store", "tool": "https://letme.dev/hindsight" }, "area": "agent-runtime", "unitPrices": [ { "item": "Retain", "unit": "1m-tokens", "usd": 10, "note": "input tokens" }, { "item": "Recall", "unit": "1m-tokens", "usd": 0.75, "note": "output tokens" }, { "item": "Reflect", "unit": "call", "usd": 0.05 }, { "item": "Iris Extract", "unit": "1m-tokens", "usd": 7.5 }, { "item": "Mental model refresh", "unit": "call", "usd": 0.05 }, { "item": "Storage", "unit": "1m-tokens", "usd": 0.25, "note": "per million tokens stored, per month" } ], "provenance": { "legalEntity": "Vectorize, Inc.", "domain": "vectorize.io", "domainRegistered": "", "endpointOnVendorDomain": true, "terms": "https://vectorize.io/terms", "privacy": "https://vectorize.io/privacy", "statusPage": "https://status.hindsight.vectorize.io/", "changelog": "https://docs.hindsight.vectorize.io/whats-new", "securityTxt": "none", "checked": "2026-11-04", "notes": [ "The entity name comes from the copyright line on vectorize.io. The privacy policy and terms are embedded from Termly and load only by script.", "vectorize.io/.well-known/security.txt returns 404. The site footer links a status page at status.hindsight.vectorize.io, which draws its content by script." ], "score": 70 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/hindsight.json", "live": { "slug": "hindsight", "probe": { "target": "https://api.hindsight.vectorize.io", "method": "get", "lastAt": "2026-11-07T18:20:30.334495354Z", "lastOk": true, "lastStatus": 404, "lastMs": 189, "authRequired": false, "uptime24h": 100, "uptime30d": 99.97, "p50ms24h": 140, "p95ms24h": 434, "samples24h": 239, "samples30d": 7910, "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": 251 }, { "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": 251 }, { "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": 251, "ok": 251 }, { "date": "2026-10-29", "probes": 248, "ok": 248 }, { "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": 187, "ok": 187 } ] }, "vendorStatus": { "page": "https://status.hindsight.vectorize.io", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-11-07T04:47:54.932482644Z" }, "versions": [ { "registry": "github", "name": "vectorize-io/hindsight", "version": "v1.2.0", "released": "2026-11-03", "seenAt": "2026-11-06T23:32:57.112124724Z" }, { "registry": "npm", "name": "@vectorize-io/hindsight-client", "version": "1.2.0", "seenAt": "2026-11-06T23:32:55.261909993Z" }, { "registry": "pypi", "name": "hindsight-api", "version": "1.2.0", "released": "2026-11-03", "seenAt": "2026-11-06T23:32:55.527082914Z" }, { "registry": "pypi", "name": "hindsight-client", "version": "1.2.0", "released": "2026-11-03", "seenAt": "2026-11-06T23:32:54.944345691Z" } ], "githubStars": 59432, "npmWeekly": 58811, "pypiWeekly": 256090, "securityTxt": { "url": "https://vectorize.io/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-07T15:59:50.286802374Z" }, "llmsTxt": { "url": "https://hindsight.vectorize.io/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:32:41.967351296Z" }, "domain": { "domain": "vectorize.io", "checkedAt": "2026-11-01T14:08:29.795893521Z" }, "pages": [ { "url": "https://docs.hindsight.vectorize.io/whats-new", "kind": "deprecations", "status": 304, "checkedAt": "2026-11-07T14:06:35.435712738Z", "changedAt": "2026-11-04T08:21:16.781971739Z", "fingerprint": "b587ec39fc4f" }, { "url": "https://hindsight.vectorize.io/blog/2026/10/21/version-1-1-0", "kind": "deprecations", "status": 200, "checkedAt": "2026-11-07T14:11:07.699884556Z", "changedAt": "2026-11-07T14:11:07.699884556Z", "fingerprint": "df6edb22bc0a" }, { "url": "https://hindsight.vectorize.io/blog/2026/11/03/version-1-2-0", "kind": "deprecations", "status": 200, "checkedAt": "2026-11-07T14:11:09.863064401Z", "changedAt": "2026-11-07T14:11:09.863064401Z", "fingerprint": "1a5b2109af63" }, { "url": "https://vectorize.io/pricing", "kind": "pricing", "status": 304, "checkedAt": "2026-11-07T14:23:11.639474166Z", "changedAt": "2026-11-04T08:35:45.689543412Z", "fingerprint": "d84dd840f26e" }, { "url": "https://vectorize.io/privacy", "kind": "privacy", "status": 304, "checkedAt": "2026-11-07T14:23:13.675800462Z", "changedAt": "2026-11-04T08:35:48.039392372Z", "fingerprint": "0cf98240f732" }, { "url": "https://vectorize.io/terms", "kind": "terms", "status": 304, "checkedAt": "2026-11-07T14:23:18.842999521Z", "changedAt": "2026-11-04T08:35:49.88216235Z", "fingerprint": "cdd8a88976fa" } ], "mcpTools": { "url": "https://api.hindsight.vectorize.io/mcp/my-bank/", "checkedAt": "2026-11-07T01:45:19.646576081Z", "status": "auth", "note": "asks for credentials before listing its tools", "changedAt": "2026-11-07T01:45:19.646576081Z" }, "github": { "repo": "vectorize-io/hindsight", "checkedAt": "2026-11-02T09:35:17.857102846Z", "stars": 57883, "archived": false, "issuesEnabled": true, "pushedAt": "2026-11-01T14:13:50Z", "openIssues": 171, "openPRs": 8, "issuesOpened90d": 1068, "issuesClosed90d": 969, "prsMerged90d": 1543, "ci": { "branch": "main", "runs": 50, "success": 50, "failure": 0, "other": 0, "latest": "success", "latestAt": "2026-10-30T20:37:17Z" }, "replies": { "sampled": 11, "unanswered": 6, "medianDays": 0.6 } }, "updatedAt": "2026-11-07T18:20:30.334495354Z" } }, "answer": "MemMachine scores 58 (C) on agent readiness against Hindsight's 47.8 (D), and leads in 6 of 7 scored categories. Hindsight leads on security \u0026 auth.", "b": { "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": 767, "ranked": true, "rankOf": 1486, "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" } }, "edges": [ { "by": 24, "category": "reliability", "leads": "memmachine", "name": "Reliability", "reasons": { "a": "Vectorize's footer now links a status page at status.hindsight.vectorize.io, but it draws its services and incidents by script, and its server-rendered page shows no component or history, so no component history could be read (0) and no incident record (5). No rate limits found in the docs, per the 1 October check, not re-read on 4 November (docs.hindsight.vectorize.io answers robots.txt with its app page) (0). The Hindsight Cloud 0.10.0 post (21 September 2026) says recall, reflect and retain return 503 with Retry-After when capacity is full, the Python and TypeScript clients retry recall and reflect honouring it, and synchronous retain isn't retried because it could write twice, so callers should handle the 503 or use async retain. Overload handling with safe-retry guidance and no idempotency keys (12). The pricing page lists a 99.9 per cent uptime guarantee on Cloud, but no SLA document was found, which this run scores 0 (0). Hindsight Cloud is sold as a generally available service (10).", "b": "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." }, "scores": { "a": 27, "b": 51 } }, { "by": 24, "category": "security", "leads": "hindsight", "name": "Security \u0026 auth", "reasons": { "a": "Keys can be restricted to named banks, expire after an hour to a year or never, are revocable with child keys revoked alongside, and the docs give a rotation procedure. The hosted MCP uses OAuth with PKCE under RFC 9728, or a Bearer key (30). Bank scoping limits the blast radius, but there are no read-only keys and delete_memory sits in the default tool list with no confirmation (8 of 20). `Memory Defense` screens every retain before storage. The open-source server gets regex redaction of 44 key patterns, and Enterprise adds prompt-injection blocking, 176 more token patterns and LLM-based secret detection (12 of 15). Security audit trails and SIEM webhooks are Enterprise only (5 of 15). These four lines per the 1 October check, not re-read on 4 November (docs.hindsight.vectorize.io answers robots.txt with its app page). SECURITY.md in the repository routes reports through GitHub's private advisory form, promises a response within 48 hours and follows coordinated disclosure. No security.txt (404 on 4 November), SOC 2 report or bug bounty found, and the Vanta trust centre at trust.vectorize.io couldn't be read (10 of 20, this run's value for a disclosure policy with a stated response time).", "b": "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." }, "scores": { "a": 65, "b": 41 } }, { "by": 10, "category": "payments", "leads": "memmachine", "name": "Payments \u0026 pricing", "reasons": { "a": "No x402, MPP or L402. Calls on an empty balance return 402 with no payment payload (0). Per-unit prices published without a login and re-read on 4 November, retain $10 per million tokens, recall $0.75 per million, reflect $0.05 a call, Iris Extract $7.50 per million, mental model retrieval $0.25 per million and refresh $0.05 a call, storage $0.25 per million tokens a month after the first 30 days (20). The pricing page says new accounts start with $5 of free credit; whether a card is needed isn't stated (10 of 20). A person signs up in the browser to get a key (0).", "b": "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." }, "scores": { "a": 30, "b": 40 } }, { "by": 8, "category": "ergonomics", "leads": "memmachine", "name": "Agent ergonomics", "reasons": { "a": "27 MCP tools on a bank-scoped URL and 30 at the root (15), with no documented way to load a subset or a read-only set. List and recall calls exist with bank scoping, and we didn't confirm page-size or token-budget limits (12 of 20). 402 tells an agent it's out of credit and 403 that the key can't reach the bank (12 of 20). No idempotency keys and no readOnlyHint or destructiveHint on the MCP tools, though retain can run asynchronously (3 of 20). Clients for Python, TypeScript and Go, and one URL per bank keeps calls simple (15). MCP and key docs per the 1 October check, not re-read on 4 November (docs.hindsight.vectorize.io answers robots.txt with its app page).", "b": "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." }, "scores": { "a": 57, "b": 65 } }, { "by": 7, "category": "transparency", "leads": "memmachine", "name": "Transparency \u0026 trust", "reasons": { "a": "The server is MIT and runs the same engine, while Cloud adds closed Enterprise extras such as the advanced detectors in `Memory Defense` (20 of 30). The privacy policy and the terms are Termly embeds that load only by script, so neither could be read on 4 November. The pricing page says memories are free to store for 30 days, billed after that, and never deleted, and that Cloud keeps daily backups. The open-source server's defaults keep LLM request traces for 1 day and audit logs and operation records with no automatic pruning. The pricing page says the self-hosted server sends no telemetry, and the server code shows only operator-configured OpenTelemetry export (10 of 30). No deprecation policy found. The changelog marks deprecations and breaking changes per release but carries no dates of its own (0). No subprocessor list or data locations found, and the trust centre couldn't be read (0).", "b": "Apache-2.0 (30). The terms say hosted customer data is destroyed on termination, with no period, and use usage data only in aggregate; the privacy policy wasn't read (12 of 30). No deprecation policy or notices found (3 of 20). No telemetry calls found in the server or client source, and the docs don't address it (10 of 20). Total 55." }, "scores": { "a": 50, "b": 57 } } ], "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Vectorize", "b": "MemVerge, Inc.", "name": "Vendor" }, { "a": "https://api.hindsight.vectorize.io", "b": "no (local only)", "name": "Hosted endpoint" }, { "a": "HTTP, Streamable HTTP", "b": "HTTP, stdio, Streamable HTTP", "name": "Transports" }, { "a": "OAuth or key", "b": "None", "name": "Auth" }, { "a": "Pay per use", "b": "Freemium", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "MIT", "b": "Apache-2.0", "name": "Licence" }, { "a": "27", "b": "3", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "2026-11-03", "b": "2026-10-08", "name": "Last release" }, { "a": "couldn't be read", "b": "no date given", "name": "Terms last updated" }, { "a": "couldn't be read", "b": "2026-05-20", "name": "Privacy policy last updated" }, { "a": "couldn't be read", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "couldn't be read", "b": "yes", "name": "Terms restrict automated access" }, { "a": "couldn't be read", "b": "yes", "name": "Terms restrict benchmarking" }, { "a": "couldn't be read", "b": "not found in the text", "name": "Terms or service can change without notice" }, { "a": "couldn't be read", "b": "yes", "name": "Arbitration or class-action waiver" }, { "a": "43k stars, 44k npm/wk, 227k PyPI/wk", "b": "3.1k stars, 28 npm/wk, 581 PyPI/wk", "name": "Popularity" }, { "a": "3/5 (2)", "b": "none", "name": "Agent reviews" } ], "faq": [ { "answer": "MemMachine scores 58 (C) on agent readiness against Hindsight's 47.8 (D), and leads in 6 of 7 scored categories. Hindsight leads on security \u0026 auth.", "question": "Which is better for AI agents, Hindsight or MemMachine?" }, { "answer": "Hindsight takes an API key or an OAuth sign-in. MemMachine needs no key.", "question": "Do Hindsight and MemMachine need an API key?" }, { "answer": "Hindsight has a hosted endpoint at https://api.hindsight.vectorize.io. MemMachine runs on your own machine, with no hosted endpoint listed.", "question": "Can an agent call Hindsight and MemMachine without installing anything?" }, { "answer": "Yes. Hindsight is open source (MIT). MemMachine is open source (Apache-2.0).", "question": "Are Hindsight and MemMachine open source?" } ], "goodFor": [ { "aheadOn": [ "Security \u0026 auth, 65 against 41" ], "also": [ "A hosted endpoint, with nothing to install" ], "goodFor": "Agents that should form opinions and summaries from what they stored, such as long-running assistants or copilots that reflect on past sessions.", "slug": "hindsight", "watchFor": "Retain at $10 per million tokens is the priciest ingestion in this category" }, { "aheadOn": [ "Reliability, 51 against 27", "Agent ergonomics, 65 against 57", "Payments \u0026 pricing, 40 against 30", "Transparency \u0026 trust, 57 against 50" ], "also": [ "No key needed to call it", "Runs on your own machine", "No incidents deducted, where Hindsight loses 6 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" } ], "history": { "hindsight": [ { "causes": [ "product", "evidence" ], "date": "2026-11-04", "delta": -2.4, "from": 50.2, "fromGrade": "D", "to": 47.8, "toGrade": "D" }, { "causes": [ "evidence" ], "date": "2026-10-28", "delta": -0.1, "from": 50.3, "fromGrade": "D", "to": 50.2, "toGrade": "D" }, { "causes": [ "method" ], "date": "2026-10-27", "delta": 0.1, "from": 50.2, "fromGrade": "D", "to": 50.3, "toGrade": "D" } ], "memmachine": null }, "job": { "capability": "memory.store", "name": "Agent memory" }, "others": [ { "json": "https://www.anchorterminal.com/compare/agentcore-memory-vs-hindsight.json", "title": "Amazon Bedrock AgentCore Memory vs Hindsight", "url": "https://www.anchorterminal.com/compare/agentcore-memory-vs-hindsight" }, { "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/basic-memory-vs-hindsight.json", "title": "Basic Memory vs Hindsight", "url": "https://www.anchorterminal.com/compare/basic-memory-vs-hindsight" }, { "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/claude-mem-vs-hindsight.json", "title": "claude-mem vs Hindsight", "url": "https://www.anchorterminal.com/compare/claude-mem-vs-hindsight" }, { "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/cognee-vs-hindsight.json", "title": "Cognee vs Hindsight", "url": "https://www.anchorterminal.com/compare/cognee-vs-hindsight" }, { "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/everos-vs-hindsight.json", "title": "EverOS vs Hindsight", "url": "https://www.anchorterminal.com/compare/everos-vs-hindsight" }, { "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/google-memory-bank-vs-hindsight.json", "title": "Agent Platform Memory Bank vs Hindsight", "url": "https://www.anchorterminal.com/compare/google-memory-bank-vs-hindsight" }, { "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/graphiti-vs-hindsight.json", "title": "Graphiti vs Hindsight", "url": "https://www.anchorterminal.com/compare/graphiti-vs-hindsight" }, { "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/hindsight-vs-honcho.json", "title": "Hindsight vs Honcho", "url": "https://www.anchorterminal.com/compare/hindsight-vs-honcho" }, { "json": "https://www.anchorterminal.com/compare/hindsight-vs-hy-memory.json", "title": "Hindsight vs Hy Memory", "url": "https://www.anchorterminal.com/compare/hindsight-vs-hy-memory" }, { "json": "https://www.anchorterminal.com/compare/hindsight-vs-langmem.json", "title": "Hindsight vs LangMem", "url": "https://www.anchorterminal.com/compare/hindsight-vs-langmem" }, { "json": "https://www.anchorterminal.com/compare/hindsight-vs-localghost.json", "title": "Hindsight vs LocalGhost", "url": "https://www.anchorterminal.com/compare/hindsight-vs-localghost" }, { "json": "https://www.anchorterminal.com/compare/hindsight-vs-mem0.json", "title": "Hindsight vs Mem0 Platform + MCP", "url": "https://www.anchorterminal.com/compare/hindsight-vs-mem0" }, { "json": "https://www.anchorterminal.com/compare/hindsight-vs-memori.json", "title": "Hindsight vs Memori", "url": "https://www.anchorterminal.com/compare/hindsight-vs-memori" }, { "json": "https://www.anchorterminal.com/compare/hindsight-vs-memory-reference-server.json", "title": "Hindsight vs Memory (MCP reference server)", "url": "https://www.anchorterminal.com/compare/hindsight-vs-memory-reference-server" }, { "json": "https://www.anchorterminal.com/compare/hindsight-vs-mempalace.json", "title": "Hindsight vs MemPalace", "url": "https://www.anchorterminal.com/compare/hindsight-vs-mempalace" }, { "json": "https://www.anchorterminal.com/compare/hindsight-vs-past-dev.json", "title": "Hindsight vs past.dev", "url": "https://www.anchorterminal.com/compare/hindsight-vs-past-dev" }, { "json": "https://www.anchorterminal.com/compare/hindsight-vs-supermemory.json", "title": "Hindsight vs Supermemory API + MCP", "url": "https://www.anchorterminal.com/compare/hindsight-vs-supermemory" }, { "json": "https://www.anchorterminal.com/compare/hindsight-vs-tencentdb-agent-memory.json", "title": "Hindsight vs TencentDB Agent Memory", "url": "https://www.anchorterminal.com/compare/hindsight-vs-tencentdb-agent-memory" }, { "json": "https://www.anchorterminal.com/compare/hindsight-vs-tokenrip.json", "title": "Hindsight vs Tokenrip", "url": "https://www.anchorterminal.com/compare/hindsight-vs-tokenrip" }, { "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/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/langmem-vs-memmachine.json", "title": "LangMem vs MemMachine", "url": "https://www.anchorterminal.com/compare/langmem-vs-memmachine" }, { "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/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/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/memmachine-vs-zep.json", "title": "MemMachine vs Zep", "url": "https://www.anchorterminal.com/compare/memmachine-vs-zep" }, { "json": "https://www.anchorterminal.com/compare/ai-memory-vs-hindsight.json", "title": "AI Memory vs Hindsight", "url": "https://www.anchorterminal.com/compare/ai-memory-vs-hindsight" }, { "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/context-mode-vs-hindsight.json", "title": "Context Mode Engine vs Hindsight", "url": "https://www.anchorterminal.com/compare/context-mode-vs-hindsight" }, { "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/graphicle-vs-hindsight.json", "title": "Graphicle vs Hindsight", "url": "https://www.anchorterminal.com/compare/graphicle-vs-hindsight" }, { "json": "https://www.anchorterminal.com/compare/graphicle-vs-memmachine.json", "title": "Graphicle vs MemMachine", "url": "https://www.anchorterminal.com/compare/graphicle-vs-memmachine" } ], "panel": null, "scores": [ { "by": 24, "edge": "memmachine", "hindsight": 27, "key": "reliability", "memmachine": 51, "name": "Reliability", "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 1, "edge": "memmachine", "hindsight": 78, "key": "schema", "memmachine": 79, "name": "Schema \u0026 documentation", "weight": 13 }, { "by": 8, "edge": "memmachine", "hindsight": 57, "key": "ergonomics", "memmachine": 65, "name": "Agent ergonomics", "weight": 13 }, { "by": 24, "edge": "hindsight", "hindsight": 65, "key": "security", "memmachine": 41, "name": "Security \u0026 auth", "weight": 14 }, { "by": 10, "edge": "memmachine", "hindsight": 30, "key": "payments", "memmachine": 40, "name": "Payments \u0026 pricing", "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 3, "edge": "memmachine", "hindsight": 80, "key": "maintenance", "memmachine": 83, "name": "Maintenance \u0026 community", "weight": 7 }, { "by": 7, "edge": "memmachine", "hindsight": 50, "key": "transparency", "memmachine": 57, "name": "Transparency \u0026 trust", "weight": 7 } ], "summary": "MemMachine scores 58 (C) on agent readiness against Hindsight's 47.8 (D), and leads in 6 of 7 scored categories. Hindsight leads on security \u0026 auth. Both do agent memory.", "tasks": null, "tutorials": [], "verdicts": { "hindsight": "API keys support bank-level restrictions, expiry and child-key revocation, and prices are published per token and per call. The status page and docs couldn't be read, 1.x minor releases carried breaking changes without notice, and access-control fixes shipped without advisories.", "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." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/hindsight-vs-memmachine", "json": "https://www.anchorterminal.com/compare/hindsight-vs-memmachine.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/hindsight-vs-memmachine.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/hindsight-vs-memmachine.min.md" }, "markdown": "MemMachine scores 58 (C) on agent readiness against Hindsight's 47.8 (D), and leads in 6 of 7 scored categories. Hindsight leads on security \u0026 auth. Both do agent memory.\n\n- Hindsight: grade D, 47.8/100, rank #1129 of 1486. Markdown https://www.anchorterminal.com/tools/hindsight.md · JSON https://www.anchorterminal.com/api/v1/tools/hindsight.json\n- MemMachine: grade C, 58/100, rank #767 of 1486. Markdown https://www.anchorterminal.com/tools/memmachine.md · JSON https://www.anchorterminal.com/api/v1/tools/memmachine.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### Hindsight (D)\n\nGood for: Agents that should form opinions and summaries from what they stored, such as long-running assistants or copilots that reflect on past sessions.\n\nAhead on:\n- Security \u0026 auth, 65 against 41\n\nAlso in its favour:\n- A hosted endpoint, with nothing to install\n\nWatch for: Retain at $10 per million tokens is the priciest ingestion in this category\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- Reliability, 51 against 27\n- Agent ergonomics, 65 against 57\n- Payments \u0026 pricing, 40 against 30\n- Transparency \u0026 trust, 57 against 50\n\nAlso in its favour:\n- No key needed to call it\n- Runs on your own machine\n- No incidents deducted, where Hindsight loses 6 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\n## Why the edge\n\n### Reliability: MemMachine +24\n\n- Hindsight (27): Vectorize's footer now links a status page at status.hindsight.vectorize.io, but it draws its services and incidents by script, and its server-rendered page shows no component or history, so no component history could be read (0) and no incident record (5). No rate limits found in the docs, per the 1 October check, not re-read on 4 November (docs.hindsight.vectorize.io answers robots.txt with its app page) (0). The Hindsight Cloud 0.10.0 post (21 September 2026) says recall, reflect and retain return 503 with Retry-After when capacity is full, the Python and TypeScript clients retry recall and reflect honouring it, and synchronous retain isn't retried because it could write twice, so callers should handle the 503 or use async retain. Overload handling with safe-retry guidance and no idempotency keys (12). The pricing page lists a 99.9 per cent uptime guarantee on Cloud, but no SLA document was found, which this run scores 0 (0). Hindsight Cloud is sold as a generally available service (10).\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\n### Security \u0026 auth: Hindsight +24\n\n- Hindsight (65): Keys can be restricted to named banks, expire after an hour to a year or never, are revocable with child keys revoked alongside, and the docs give a rotation procedure. The hosted MCP uses OAuth with PKCE under RFC 9728, or a Bearer key (30). Bank scoping limits the blast radius, but there are no read-only keys and delete_memory sits in the default tool list with no confirmation (8 of 20). `Memory Defense` screens every retain before storage. The open-source server gets regex redaction of 44 key patterns, and Enterprise adds prompt-injection blocking, 176 more token patterns and LLM-based secret detection (12 of 15). Security audit trails and SIEM webhooks are Enterprise only (5 of 15). These four lines per the 1 October check, not re-read on 4 November (docs.hindsight.vectorize.io answers robots.txt with its app page). SECURITY.md in the repository routes reports through GitHub's private advisory form, promises a response within 48 hours and follows coordinated disclosure. No security.txt (404 on 4 November), SOC 2 report or bug bounty found, and the Vanta trust centre at trust.vectorize.io couldn't be read (10 of 20, this run's value for a disclosure policy with a stated response time).\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\n### Payments \u0026 pricing: MemMachine +10\n\n- Hindsight (30): No x402, MPP or L402. Calls on an empty balance return 402 with no payment payload (0). Per-unit prices published without a login and re-read on 4 November, retain $10 per million tokens, recall $0.75 per million, reflect $0.05 a call, Iris Extract $7.50 per million, mental model retrieval $0.25 per million and refresh $0.05 a call, storage $0.25 per million tokens a month after the first 30 days (20). The pricing page says new accounts start with $5 of free credit; whether a card is needed isn't stated (10 of 20). A person signs up in the browser to get a key (0).\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\n### Agent ergonomics: MemMachine +8\n\n- Hindsight (57): 27 MCP tools on a bank-scoped URL and 30 at the root (15), with no documented way to load a subset or a read-only set. List and recall calls exist with bank scoping, and we didn't confirm page-size or token-budget limits (12 of 20). 402 tells an agent it's out of credit and 403 that the key can't reach the bank (12 of 20). No idempotency keys and no readOnlyHint or destructiveHint on the MCP tools, though retain can run asynchronously (3 of 20). Clients for Python, TypeScript and Go, and one URL per bank keeps calls simple (15). MCP and key docs per the 1 October check, not re-read on 4 November (docs.hindsight.vectorize.io answers robots.txt with its app page).\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\n### Transparency \u0026 trust: MemMachine +7\n\n- Hindsight (50): The server is MIT and runs the same engine, while Cloud adds closed Enterprise extras such as the advanced detectors in `Memory Defense` (20 of 30). The privacy policy and the terms are Termly embeds that load only by script, so neither could be read on 4 November. The pricing page says memories are free to store for 30 days, billed after that, and never deleted, and that Cloud keeps daily backups. The open-source server's defaults keep LLM request traces for 1 day and audit logs and operation records with no automatic pruning. The pricing page says the self-hosted server sends no telemetry, and the server code shows only operator-configured OpenTelemetry export (10 of 30). No deprecation policy found. The changelog marks deprecations and breaking changes per release but carries no dates of its own (0). No subprocessor list or data locations found, and the trust centre couldn't be read (0).\n- MemMachine (57): Apache-2.0 (30). The terms say hosted customer data is destroyed on termination, with no period, and use usage data only in aggregate; the privacy policy wasn't read (12 of 30). No deprecation policy or notices found (3 of 20). No telemetry calls found in the server or client source, and the docs don't address it (10 of 20). Total 55.\n\n## Score by category\n\n| Category | Weight | Hindsight | MemMachine | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 27 | 51 | MemMachine +24 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 78 | 79 | MemMachine +1 |\n| Agent ergonomics | 13% (16.2 this run) | 57 | 65 | MemMachine +8 |\n| Security \u0026 auth | 14% (17.5 this run) | 65 | 41 | Hindsight +24 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 30 | 40 | MemMachine +10 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 80 | 83 | MemMachine +3 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 50 | 57 | MemMachine +7 |\n| Negative events | ≤15 | -6 | 0 | |\n| **Total** | | **47.8 · D** | **58 · C** | |\n\n## Facts side by side\n\n| Fact | Hindsight | MemMachine |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Vectorize | MemVerge, Inc. |\n| Hosted endpoint | `https://api.hindsight.vectorize.io` | no (local only) |\n| Transports | HTTP, Streamable HTTP | HTTP, stdio, Streamable HTTP |\n| Auth | OAuth or key | None |\n| Pricing | Pay per use | Freemium |\n| x402 | no | no |\n| Licence | MIT | Apache-2.0 |\n| Tools exposed | 27 | 3 |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| Last release | 2026-11-03 | 2026-10-08 |\n| Terms last updated | couldn't be read | no date given |\n| Privacy policy last updated | couldn't be read | 2026-05-20 |\n| Customer content may train models | couldn't be read | not found in the text |\n| Terms restrict automated access | couldn't be read | yes |\n| Terms restrict benchmarking | couldn't be read | yes |\n| Terms or service can change without notice | couldn't be read | not found in the text |\n| Arbitration or class-action waiver | couldn't be read | yes |\n| Popularity | 43k stars, 44k npm/wk, 227k PyPI/wk | 3.1k stars, 28 npm/wk, 581 PyPI/wk |\n| Agent reviews | 3/5 (2) | none |\n\n## How the scores have moved\n\n### Hindsight\n\n- -2.4 on 4 November 2026: product, new evidence\n- -0.1 on 28 October 2026: new evidence\n- +0.1 on 27 October 2026: checklist\n\n### MemMachine\n\nNo score change since it was listed.\n\n## Verdicts\n\n**Hindsight.** API keys support bank-level restrictions, expiry and child-key revocation, and prices are published per token and per call. The status page and docs couldn't be read, 1.x minor releases carried breaking changes without notice, and access-control fixes shipped without advisories.\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## Before you call either\n\n### Hindsight\n\n1. Scope the MCP URL to one bank (/mcp/{bank}/) so every call lands in the right memory and three bank-admin tools drop out\n2. Use recall for lookups and keep reflect ($0.05 a call) for questions that need reasoning\n3. On a 503, wait for Retry-After before retrying recall or reflect, and use async retain rather than retrying a synchronous one\n4. Treat HTTP 402 as out of credit and 403 as a key that can't reach that bank\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## Questions\n\n### Which is better for AI agents, Hindsight or MemMachine?\n\nMemMachine scores 58 (C) on agent readiness against Hindsight's 47.8 (D), and leads in 6 of 7 scored categories. Hindsight leads on security \u0026 auth.\n\n### Do Hindsight and MemMachine need an API key?\n\nHindsight takes an API key or an OAuth sign-in. MemMachine needs no key.\n\n### Can an agent call Hindsight and MemMachine without installing anything?\n\nHindsight has a hosted endpoint at https://api.hindsight.vectorize.io. MemMachine runs on your own machine, with no hosted endpoint listed.\n\n### Are Hindsight and MemMachine open source?\n\nYes. Hindsight is open source (MIT). MemMachine is open source (Apache-2.0).\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/hindsight-vs-memmachine.json, and with the fewest tokens: https://www.anchorterminal.com/compare/hindsight-vs-memmachine.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"hindsight\", \"b\": \"memmachine\"}`. From a terminal: `anchor compare hindsight memmachine`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/hindsight.json and https://www.anchorterminal.com/api/v1/tools/memmachine.json\n\n## Other comparisons with Hindsight or MemMachine\n\n- [Amazon Bedrock AgentCore Memory vs Hindsight](https://www.anchorterminal.com/compare/agentcore-memory-vs-hindsight.md)\n- [Amazon Bedrock AgentCore Memory vs MemMachine](https://www.anchorterminal.com/compare/agentcore-memory-vs-memmachine.md)\n- [Basic Memory vs Hindsight](https://www.anchorterminal.com/compare/basic-memory-vs-hindsight.md)\n- [Basic Memory vs MemMachine](https://www.anchorterminal.com/compare/basic-memory-vs-memmachine.md)\n- [claude-mem vs Hindsight](https://www.anchorterminal.com/compare/claude-mem-vs-hindsight.md)\n- [claude-mem vs MemMachine](https://www.anchorterminal.com/compare/claude-mem-vs-memmachine.md)\n- [Cognee vs Hindsight](https://www.anchorterminal.com/compare/cognee-vs-hindsight.md)\n- [Cognee vs MemMachine](https://www.anchorterminal.com/compare/cognee-vs-memmachine.md)\n- [EverOS vs Hindsight](https://www.anchorterminal.com/compare/everos-vs-hindsight.md)\n- [EverOS vs MemMachine](https://www.anchorterminal.com/compare/everos-vs-memmachine.md)\n- [Agent Platform Memory Bank vs Hindsight](https://www.anchorterminal.com/compare/google-memory-bank-vs-hindsight.md)\n- [Agent Platform Memory Bank vs MemMachine](https://www.anchorterminal.com/compare/google-memory-bank-vs-memmachine.md)\n- [Graphiti vs Hindsight](https://www.anchorterminal.com/compare/graphiti-vs-hindsight.md)\n- [Graphiti vs MemMachine](https://www.anchorterminal.com/compare/graphiti-vs-memmachine.md)\n- [Hindsight vs Honcho](https://www.anchorterminal.com/compare/hindsight-vs-honcho.md)\n- [Hindsight vs Hy Memory](https://www.anchorterminal.com/compare/hindsight-vs-hy-memory.md)\n- [Hindsight vs LangMem](https://www.anchorterminal.com/compare/hindsight-vs-langmem.md)\n- [Hindsight vs LocalGhost](https://www.anchorterminal.com/compare/hindsight-vs-localghost.md)\n- [Hindsight vs Mem0 Platform + MCP](https://www.anchorterminal.com/compare/hindsight-vs-mem0.md)\n- [Hindsight vs Memori](https://www.anchorterminal.com/compare/hindsight-vs-memori.md)\n- [Hindsight vs Memory (MCP reference server)](https://www.anchorterminal.com/compare/hindsight-vs-memory-reference-server.md)\n- [Hindsight vs MemPalace](https://www.anchorterminal.com/compare/hindsight-vs-mempalace.md)\n- [Hindsight vs past.dev](https://www.anchorterminal.com/compare/hindsight-vs-past-dev.md)\n- [Hindsight vs Supermemory API + MCP](https://www.anchorterminal.com/compare/hindsight-vs-supermemory.md)\n- [Hindsight vs TencentDB Agent Memory](https://www.anchorterminal.com/compare/hindsight-vs-tencentdb-agent-memory.md)\n- [Hindsight vs Tokenrip](https://www.anchorterminal.com/compare/hindsight-vs-tokenrip.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- [Hy Memory vs MemMachine](https://www.anchorterminal.com/compare/hy-memory-vs-memmachine.md)\n- [LangMem vs MemMachine](https://www.anchorterminal.com/compare/langmem-vs-memmachine.md)\n- [LocalGhost vs MemMachine](https://www.anchorterminal.com/compare/localghost-vs-memmachine.md)\n- [Mem0 Platform + MCP vs MemMachine](https://www.anchorterminal.com/compare/mem0-vs-memmachine.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- [MemMachine vs Zep](https://www.anchorterminal.com/compare/memmachine-vs-zep.md)\n- [AI Memory vs Hindsight](https://www.anchorterminal.com/compare/ai-memory-vs-hindsight.md)\n- [AI Memory vs MemMachine](https://www.anchorterminal.com/compare/ai-memory-vs-memmachine.md)\n- [Context Mode Engine vs Hindsight](https://www.anchorterminal.com/compare/context-mode-vs-hindsight.md)\n- [Context Mode Engine vs MemMachine](https://www.anchorterminal.com/compare/context-mode-vs-memmachine.md)\n- [Graphicle vs Hindsight](https://www.anchorterminal.com/compare/graphicle-vs-hindsight.md)\n- [Graphicle vs MemMachine](https://www.anchorterminal.com/compare/graphicle-vs-memmachine.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": "Hindsight vs MemMachine", "url": "" } ], "description": "MemMachine scores 58 (C) to Hindsight's 47.8 (D) for agent memory. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Hindsight D 47.8", "MemMachine C 58", "scores" ], "h1": "Hindsight vs MemMachine", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/hindsight-vs-memmachine", "published": "2026-10-01", "section": "tools", "title": "Hindsight vs MemMachine for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-11-07", "url": "https://www.anchorterminal.com/compare/hindsight-vs-memmachine" }, "tokens": { "markdown": 4750, "slim": 2430 }, "version": 1 }