Workspaces, API keys, ingestion, usage trails, connection kits, and a small HTTP bridge around the real Engram engine.
Agents can recall the project, do the work, and leave a checkpoint behind.
Every workspace exposes connection JSON, env output, tool discovery, and starter skills.
The product is being hardened in public before pricing gets in the way.
Each project gets its own Engram-backed workspace, member list, keys, audit trail, and schema.
Issue keys per agent or job. Calls are tracked by route and key so operators can see what happened.
Paste notes, upload files, or batch import handoffs and reports into workspace memory.
Agents search, recall context, write outcomes, and leave checkpoints through the hosted bridge.
Memorylayer exposes the operational pieces agent clients need instead of hiding them behind a marketing page.
capabilities tracked across service, site, and agent surfaces.
hosted bridge tools exposed for agent workflows.
request and response fixtures for client builders.
pricing tiers; the service is free while it hardens.
New clients should not scrape docs or guess URLs. Ask the workspace for the config it wants you to use.
/api/workspaces/{slug}/connect
Endpoint map, MCP settings, starter skills, and recommended startup calls.
/api/workspaces/{slug}/env
Plain variables for local scripts, launchers, and worker processes.
/api/workspaces/{slug}/mcp/tools
A workspace-scoped tool catalog with argument hints.
SDK snippets, playbooks, and API fixtures are part of the service surface, available as pages and JSON.
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.
The useful path is compact: load memory, work, write the result, leave a clean stop point.
Engram stays focused on memory behavior. Memorylayer handles identity, workspaces, keys, dashboards, and hosted access.
Create workspaces, inspect memory health, issue keys, invite collaborators, and keep audit history in one place.
Use hosted endpoints for search, remember, recent memories, audit history, bootstrap, and a compact HTTP bridge for selected Engram tools.
This is still the real Engram engine underneath, so retrieval, graph, and memory improvements pass straight through to the hosted layer.
A practical feature matrix, agent examples, security posture, status page, changelog, copyable snippets, connection kits, and usage-aware docs.
Each workspace receives its own Engram schema and service boundary.
User identity is handled through GitHub OAuth with no local passwords.
Issue shareable invites with role-aware membership records.
Generate workspace keys for agents, apps, and ingestion pipelines.
Track service calls by route, key, and workspace.
Record workspace actions such as keys, invites, memory writes, and bridge calls.
Call selected Engram tools through a simple HTTP JSON bridge.
Discover URLs, headers, tools, and skills from one workspace endpoint.
Download markdown skills that teach agents how to use hosted memory.
Load the latest workspace memories without custom query code.
Run hosted retrieval against the real Engram memory graph.
Store narrative, fact, and procedure memories over HTTP.
Use these as starting points for agents, ingestion jobs, and usage monitors.
Load bootstrap -> Recall recent context -> Work normally -> Remember outcome
List bridge tools -> POST tool name and args -> Store audit trail