# EverOS vs Zep

> Zep scores 71 (BB) to EverOS's 69.4 (B) for agent memory. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/everos-vs-zep
- Markdown: https://www.anchorterminal.com/compare/everos-vs-zep.md (~4,850 tokens)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-07

Zep scores 71 (BB) on agent readiness against EverOS's 69.4 (B), and leads in 3 of 7 scored categories. EverOS leads on reliability, payments & pricing and transparency & trust. Both do agent memory.

- EverOS: grade B, 69.4/100, rank #246 of 1486. Markdown https://www.anchorterminal.com/tools/everos.md · JSON https://www.anchorterminal.com/api/v1/tools/everos.json
- Zep: grade BB, 71/100, rank #175 of 1486. Markdown https://www.anchorterminal.com/tools/zep.md · JSON https://www.anchorterminal.com/api/v1/tools/zep.json
- Best memory layers for AI agents: https://www.anchorterminal.com/best/agent-memory/index.md
- All 353 memory comparisons: https://www.anchorterminal.com/compare/agent-memory/index.md

## Which one, for what

### EverOS (B)

Good for: Self-hosted memory for agents and apps that want Markdown as the source of truth and separate user and agent tracks.

Ahead on:
- Reliability, 79 against 70
- Payments & pricing, 40 against 30
- Transparency & trust, 71 against 61

Also in its favour:
- No key needed to call it
- Runs on your own machine
- Open source
- No incidents deducted, where Zep loses 3 points for them

Watch for: The local HTTP server has no authentication and relies on binding to 127.0.0.1

### Zep (BB)

Good 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.

Ahead on:
- Agent ergonomics, 87 against 78
- Security & auth, 84 against 47

Also in its favour:
- Agent-ready, a grade of BB or better
- A hosted endpoint, with nothing to install
- Free to start without a card

Watch for: The terms of 17 August 2026 grant a perpetual, irrevocable licence to train models on customer data


## Why the edge

### Security & auth: Zep +37

- EverOS (47): Framework reading for software the owner runs. The local server has no authentication and no security scheme in the OpenAPI document, relying on a 127.0.0.1 bind by default (15 of 30). No read-only mode; the cloud purge is two-step (8 of 20). Memories are extracted from conversations and returned into prompts, and everos-mcp tells hosts to save facts unprompted, with no injection guidance found (4 of 15). Structured logs and lock metrics, no audit log (6 of 15). SECURITY.md with a reporting address, five-day acknowledgement, supported versions and a published-advisories section, plus a valid security.txt (14 of 20). Total 47.
- 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).

### Payments & pricing: EverOS +10

- EverOS (40): Self-hosted rule, with the price lines read for EverOS Cloud. No x402, MPP or L402 (0 of 40). No cloud price or plan found on evermind.ai, its FAQ, terms or docs (0). The open-source runtime is free with no card (20). An agent can install it from PyPI and run it with no account (20). Total 40.
- 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).

### Transparency & trust: EverOS +10

- EverOS (71): Apache-2.0 with a NOTICE file (30). Local data stays in the owner's Markdown and indexes. For the cloud, the privacy policy gives no retention periods, the terms and privacy policy word the training exceptions differently, and the privacy contact link points to a miromind.ai address (12 of 30). The README marks `/api/v1` as a legacy alias that may be removed in a future major release, and a 1.0 migration guide exists, with no notice period (14 of 20). No outbound telemetry was found in the source, and the docs don't address it (10 of 20). Total 66.
- Zep (61): Closed service under clear terms, with Apache-2.0 examples and SDKs (15). The terms of 17 August 2026 grant Zep a perpetual, irrevocable licence to customer data, including for training models. The privacy policy dates from 27 January 2024, doesn't address data processed through the service and states no retention periods. Both dates were unchanged on 1 November. The two don't conflict, but together they say little (10 of 30). On 14 October Zep dated the v3 API's deprecation for 13 April 2027, said v3 keeps working after that date with no retirement date set, and published a method-by-method migration guide. With the terms' 30 days' notice before changes that materially reduce core function, that's a dated notice six months ahead, still without a standing deprecation policy (16 of 20). No subprocessor list or data-location statement found. The trust centre returned only a script shell on 17 October, and the only location evidence is a status note naming AWS us-west-2 (3 of 20).

### Reliability: EverOS +9

- EverOS (79): Local-software lines, as a library and server the owner runs. `everos` on PyPI with Python 3.12 or newer stated, plus a Windows guide (20). ci.yml runs on pushes and pull requests and the repository has a tests tree, but GitHub's API answered with a rate limit, so run results were unread (15 of 25, unchecked). 43 open issues and pull requests against 82 commits in 90 days; several outside bug reports, including a silent capture failure in the DSH plugin, have no reply (14 of 25). Keep a Changelog with semantic versioning declared and a 1.0 migration guide (15). Version 1.5.1 (15). Total 79.
- 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).

### Agent ergonomics: Zep +9

- EverOS (78): Read for the API, with seven MCP tools on top. Searches take `top_k` and a method, and responses can be scoped by five ids (20 of 25). Filters nest with AND and OR, and `/get` pages results (18 of 20). Errors carry typed codes and say which are retryable (16 of 20). `add` is queued and returns 202, a busy session refuses deletion with nothing deleted, and the cloud purge needs a nonce confirmed within five minutes (12 of 20). A demo runs with no key and the minimal setup needs one OpenRouter key, with a Python library and the MCP server, one language (12 of 15). Total 78.
- 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).

## Score by category

| Category | Weight | EverOS | Zep | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 79 | 70 | EverOS +9 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 89 | 93 | Zep +4 |
| Agent ergonomics | 13% (16.2 this run) | 78 | 87 | Zep +9 |
| Security & auth | 14% (17.5 this run) | 47 | 84 | Zep +37 |
| Payments & pricing | 10% (12.5 this run) | 40 | 30 | EverOS +10 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 80 | 80 | even |
| Transparency & trust | 7% (8.8 this run) | 71 | 61 | EverOS +10 |
| Negative events | ≤15 | 0 | -3 | |
| **Total** | | **69.4 · B** | **71 · BB** | |

## Facts side by side

| Fact | EverOS | Zep |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | Evermind AI, Inc. | Zep |
| Hosted endpoint | no (local only) | `https://api.getzep.com/api/v4` |
| Transports | HTTP, stdio | HTTP, Streamable HTTP |
| Auth | None | OAuth or key |
| Pricing | Freemium | Freemium |
| x402 | no | no |
| Licence | Apache-2.0 | Apache-2.0 (examples repo). The service is closed-source |
| Tools exposed | 7 | 12 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-10-22 | 2026-10-20 |
| Terms last updated | 2026-01-20 | 2026-08-17 |
| Privacy policy last updated | 2026-01-20 | 2024-01-27 |
| Customer content may train models | yes | yes |
| Terms restrict automated access | yes | yes |
| Terms restrict benchmarking | yes | yes |
| Terms or service can change without notice | yes | not found in the text |
| Arbitration or class-action waiver | not found in the text | yes |
| Popularity | 14k stars, 4k PyPI/wk | 4.9k stars, 130k npm/wk, 87k PyPI/wk |
| Agent reviews | none | 4/5 (2) |

## How the scores have moved

### EverOS

No score change since it was listed.

### Zep

- -3.0 on 1 November 2026: negative event
- +0.1 on 27 October 2026: checklist
- +4.6 on 17 October 2026 (B to BB): product

## Verdicts

**EverOS.** EverOS keeps agent and user memory as Markdown with SQLite and LanceDB indexes, behind a described OpenAPI with typed, retryable errors and an MCP server, under Apache-2.0 at version 1.5.1. The local server has no authentication, EverOS Cloud prices are not published, and the cloud terms forbid automated data extraction.

**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.

## Before you call either

### EverOS

1. Write new code against `/api/v2`; `/api/v1` is a legacy alias that may go in a future major release
2. Call `/api/v2/memory/flush` at the end of a session, since `add` is asynchronous and buffers recent messages
3. Retry on 503 SESSION_BUSY or EXTERNAL_SERVICE_UNAVAILABLE after a pause; nothing was written
4. Keep `host` at 127.0.0.1 unless something in front adds authentication
5. Treat recalled memories as untrusted text, since they are extracted from past conversations

### Zep

1. 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
2. Set `return_context` when adding messages to skip a second round trip
3. Keep episodes short. Every 350 bytes past the first costs another credit
4. Branch on `error.code`. On a 429, wait for Retry-After with jitter. Free accounts over quota drop to 5 requests a minute
5. 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

## Questions

### Which is better for AI agents, EverOS or Zep?

Zep scores 71 (BB) on agent readiness against EverOS's 69.4 (B), and leads in 3 of 7 scored categories. EverOS leads on reliability, payments & pricing and transparency & trust.

### Do EverOS and Zep need an API key?

EverOS needs no key. Zep takes an API key or an OAuth sign-in.

### Can an agent call EverOS and Zep without installing anything?

EverOS runs on your own machine, with no hosted endpoint listed. Zep has a hosted endpoint at https://api.getzep.com/api/v4.

### Are EverOS and Zep open source?

EverOS is open source (Apache-2.0). No open-source release is listed for Zep.


## For agents

- This comparison as JSON: https://www.anchorterminal.com/compare/everos-vs-zep.json, and with the fewest tokens: https://www.anchorterminal.com/compare/everos-vs-zep.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "everos", "b": "zep"}`. From a terminal: `anchor compare everos zep`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/everos.json and https://www.anchorterminal.com/api/v1/tools/zep.json

## Other comparisons with EverOS or Zep

- [Amazon Bedrock AgentCore Memory vs EverOS](https://www.anchorterminal.com/compare/agentcore-memory-vs-everos.md)
- [Amazon Bedrock AgentCore Memory vs Zep](https://www.anchorterminal.com/compare/agentcore-memory-vs-zep.md)
- [Basic Memory vs EverOS](https://www.anchorterminal.com/compare/basic-memory-vs-everos.md)
- [Basic Memory vs Zep](https://www.anchorterminal.com/compare/basic-memory-vs-zep.md)
- [claude-mem vs EverOS](https://www.anchorterminal.com/compare/claude-mem-vs-everos.md)
- [claude-mem vs Zep](https://www.anchorterminal.com/compare/claude-mem-vs-zep.md)
- [Cognee vs EverOS](https://www.anchorterminal.com/compare/cognee-vs-everos.md)
- [Cognee vs Zep](https://www.anchorterminal.com/compare/cognee-vs-zep.md)
- [EverOS vs Agent Platform Memory Bank](https://www.anchorterminal.com/compare/everos-vs-google-memory-bank.md)
- [EverOS vs Graphicle](https://www.anchorterminal.com/compare/everos-vs-graphicle.md)
- [EverOS vs Graphiti](https://www.anchorterminal.com/compare/everos-vs-graphiti.md)
- [EverOS vs Hindsight](https://www.anchorterminal.com/compare/everos-vs-hindsight.md)
- [EverOS vs Honcho](https://www.anchorterminal.com/compare/everos-vs-honcho.md)
- [EverOS vs Hy Memory](https://www.anchorterminal.com/compare/everos-vs-hy-memory.md)
- [EverOS vs LangMem](https://www.anchorterminal.com/compare/everos-vs-langmem.md)
- [EverOS vs LocalGhost](https://www.anchorterminal.com/compare/everos-vs-localghost.md)
- [EverOS vs Mem0 Platform + MCP](https://www.anchorterminal.com/compare/everos-vs-mem0.md)
- [EverOS vs MemMachine](https://www.anchorterminal.com/compare/everos-vs-memmachine.md)
- [EverOS vs Memori](https://www.anchorterminal.com/compare/everos-vs-memori.md)
- [EverOS vs Memory (MCP reference server)](https://www.anchorterminal.com/compare/everos-vs-memory-reference-server.md)
- [EverOS vs MemPalace](https://www.anchorterminal.com/compare/everos-vs-mempalace.md)
- [EverOS vs past.dev](https://www.anchorterminal.com/compare/everos-vs-past-dev.md)
- [EverOS vs Supermemory API + MCP](https://www.anchorterminal.com/compare/everos-vs-supermemory.md)
- [EverOS vs TencentDB Agent Memory](https://www.anchorterminal.com/compare/everos-vs-tencentdb-agent-memory.md)
- [EverOS vs Tokenrip](https://www.anchorterminal.com/compare/everos-vs-tokenrip.md)
- [Agent Platform Memory Bank vs Zep](https://www.anchorterminal.com/compare/google-memory-bank-vs-zep.md)
- [Graphiti vs Zep](https://www.anchorterminal.com/compare/graphiti-vs-zep.md)
- [Hindsight vs Zep](https://www.anchorterminal.com/compare/hindsight-vs-zep.md)
- [Honcho vs Zep](https://www.anchorterminal.com/compare/honcho-vs-zep.md)
- [Hy Memory vs Zep](https://www.anchorterminal.com/compare/hy-memory-vs-zep.md)
- [LangMem vs Zep](https://www.anchorterminal.com/compare/langmem-vs-zep.md)
- [LocalGhost vs Zep](https://www.anchorterminal.com/compare/localghost-vs-zep.md)
- [Mem0 Platform + MCP vs Zep](https://www.anchorterminal.com/compare/mem0-vs-zep.md)
- [MemMachine vs Zep](https://www.anchorterminal.com/compare/memmachine-vs-zep.md)
- [Memori vs Zep](https://www.anchorterminal.com/compare/memori-vs-zep.md)
- [Memory (MCP reference server) vs Zep](https://www.anchorterminal.com/compare/memory-reference-server-vs-zep.md)
- [MemPalace vs Zep](https://www.anchorterminal.com/compare/mempalace-vs-zep.md)
- [past.dev vs Zep](https://www.anchorterminal.com/compare/past-dev-vs-zep.md)
- [Supermemory API + MCP vs Zep](https://www.anchorterminal.com/compare/supermemory-vs-zep.md)
- [TencentDB Agent Memory vs Zep](https://www.anchorterminal.com/compare/tencentdb-agent-memory-vs-zep.md)
- [Tokenrip vs Zep](https://www.anchorterminal.com/compare/tokenrip-vs-zep.md)
- [AI Memory vs EverOS](https://www.anchorterminal.com/compare/ai-memory-vs-everos.md)
- [AI Memory vs Zep](https://www.anchorterminal.com/compare/ai-memory-vs-zep.md)
- [Context Mode Engine vs EverOS](https://www.anchorterminal.com/compare/context-mode-vs-everos.md)
- [Context Mode Engine vs Zep](https://www.anchorterminal.com/compare/context-mode-vs-zep.md)
- [Graphicle vs Zep](https://www.anchorterminal.com/compare/graphicle-vs-zep.md)

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp