memory layer.
Useful context.
Ready for the next session.
Engram memory and Mythic cognition, in one workspace. Recall previous work, check the next decision, and leave a clear handoff.
Engram holds the memory. Mythic keeps the session. Memory Layer connects them with shared workspaces, scoped keys, and a hosted MCP-compatible bridge.
How it fits togetherPick up where
the work left off.
A small loop for work that spans more than one session.
Make a place for the project.
Create a workspace and invite collaborators. Give each agent its own named, revocable API key.
Bring the useful context.
Save a decision, paste a handoff, or import notes and files. Preview a larger import through the API before writing it.
Recall before starting.
Search the workspace or fetch recent memories. Use the hosted bridge for compact context, graph lookups, and session tools.
Leave a clear stop point.
Write the outcome and save a checkpoint. Review API activity and audit history from the workspace.
Start with the connection kit.
Your workspace returns its endpoint map, authentication format, and starter calls.
Two layers.
One place to work.
Engram memory
Search and save context in an isolated workspace. Use direct HTTP routes or the MCP-compatible tool bridge for retrieval, handoffs, evidence, and curation.
Hosted capabilitiesMythic cognition
Keep persistent sessions, planner context, observed premises, and decision revisions beside your memory. Run registered Engram checks and resume the saved session.
Hosted cognitionGive the next session a head start.
Create a workspace, add context, and connect your first agent.