client.memories
Browse chronologically, read one, or hand over new material.
client.search
Rank by relevance, or assemble context inside a token budget.
client.spaces
File, unfile, merge, and choose which Space a context works in. One memory can sit in several; filing is refused when the Space is read by more people than the memory allows, and a capture that names no Space is refused outright.
client.sources
Where material came from, with its access scope.
client.documents
What was ingested, before anything was extracted from it.
client.jobs
What became of a piece of material handed to the pipeline.
client.entities
The people, projects and systems memories are about.
client.graph
Traverse from one entity to what it is connected to.
client.conflicts
Contradictions the system could not settle, and your verdict.
client.conversations
Append turns, and let extraction read the exchange as a whole.
client.integrations
Connected sources, and asking one to sync now.
client.health
Liveness and readiness.
client.googleTypeScript only
Drive and Gmail through the deployment rather than through Google: search, read, download, save, send. Google's own tokens never leave the server.
client.agentTypeScript only
One request made of somebody's own machine, and a signed link to whatever came back.
Filing something into a Space can be refused — a memory may only go into a Space no wider than itself, so organising your notes cannot quietly become a disclosure. The whole request is refused rather than partly applied. The audience rule, in full.