The service exposes the controls an operator needs: usage, audit trails, key rotation, ingestion history, exports, manifests, and runtime status.
service features tracked in the manifest
hosted bridge tools with argument hints
public and workspace route groups
Usage events and audits show route, actor, key label, status, and workspace scope.
Create keys per agent, worker, or pipeline, then revoke them without touching memory data.
Paste, file, and batch imports leave run records with source metadata and item counts.
Recent exports make it easy to review the live memory surface or move data elsewhere.
A small weekly loop catches most workspace problems before they turn into stale memory.
Check route volume, failed calls, inactive keys, and high-noise clients.
Replace long-lived or shared keys with named, scoped keys per client.
Confirm large imports split cleanly and did not flood memory with duplicates.
Require checkpoints at the end of agent sessions and long automations.
Concrete responses for common hosted-memory incidents.
The manifest is intentionally public so client builders can track the service surface.
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.