What does Supermemory actually do?
Supermemory's clearest positioning is that memory is not the same job as ordinary RAG. A vector database can retrieve document chunks, but it does not automatically maintain a user's preferences, update facts when they change, or decide which recent activity should follow the user into the next conversation. Supermemory packages those behaviors into a context layer for agents. Developers can send it chats, files, web content, and connector data, then call back for memory, search results, and user profiles when the agent needs context.
The product is also broader than a single developer API. One side is the Supermemory API for teams building agents; the other is Personal Supermemory for people who want Claude, Cursor, Codex, OpenCode, OpenClaw, or Hermes to remember across sessions. That matters for SEO and adoption because the product can be searched as an agent memory API, a RAG layer, a personal AI memory app, an MCP server, and a set of assistant plugins. This dual surface gives the product more practical hooks than a pure infrastructure repo.