Synap Memory

ai.maximem/synap · v0.1.0 · agents-and-memory

Synap Memory is healthy: it completed an MCP handshake in 1950 ms and exposes 4 tools. It scores 61/100.

Persistent memory for AI agents — log and recall conversation context over MCP.

Live health

Healthy · last checked 2026-10-14T09:00:54.797Z UTC

Checked (UTC)	Status	Latency
2026-10-14T09:00:54.797Z	ok	1950 ms

log_exchange After each user message, send the exchange here so it can be remembered. You do not need to decide what is important, just forward the user message (and your reply, if you have one) and Synap will keep what matters. If your app serves more than one end-user, pass that person's stable id as user_id s
check_memory_status Check whether a logged exchange has finished processing. Pass the ingestion_id returned by log_exchange. Returns the processing status and how many memories were extracted. Useful to confirm a save completed (extraction is asynchronous). Takes no user_id or customer_id: an ingestion_id already ident
recall_context Before replying, call this to recall anything already known about this user from past conversations. Use the user's latest message as the query. If you serve multiple end-users, pass the same user_id you log with so you recall the right person's memory. SCOPING: customer_id is B2B ONLY. On a B2B ins
list_recent_memories List recent things remembered about this user. Useful for debugging or to confirm that memory is working. Pass user_id to scope to one person. SCOPING: customer_id is B2B ONLY. On a B2B instance (user_context_isolation=strict) it is REQUIRED and a user_id on its own is an error. On a B2C instance (u