Memorylayer does not need a heavy client library to be useful. These snippets show the exact calls agents, scripts, and custom dashboards need.
ready-to-copy snippets for common clients
operator and agent workflows
required vendor SDKs; HTTP is enough
Use browser or Node fetch with bearer auth and a simple JSON body.
Requests examples cover checkpointing, recall, and integration jobs without a vendor SDK.
Shell snippets make it easy to test keys, routes, ingest, and bridge calls manually.
Public manifests describe routes, tools, arguments, snippets, playbooks, and examples.
These are deliberately plain. They match the service contract exactly.
Call the hosted bridge from a Node or browser-side tool runner.
Use Memorylayer from scripts, workers, or custom agent harnesses.
Small curl call for debugging keys and tool output.
Fetch workspace-specific URLs, skills, headers, and tool discovery.
Push a small handoff or imported dataset into workspace memory.
Build a tool picker from the public MCP manifest.
Use these as implementation checklists for agent clients and workspace operators.
The agent starts with useful state and leaves a handoff behind.
A repo can be picked up by another session without reading stale chat logs.
Operators can keep the workspace useful instead of letting memories rot.
A single entity becomes a navigable map of prior work.
A custom client can wire itself without hardcoded docs.