Local by default
Your integration talks to the user’s node or vault, not to a central Legocia memory service.
Legocia SDK 1.0
Build on the edge.
Use local-first APIs for search, redaction, retrieval, and archive workflows without routing user memory through an external cloud service.
import
legocia from "@legocia/sdk"init
const vault = await legocia.connect("192.168.1.50")query
await vault.search({ intent: "find keys", timeframe: "24h" })result
3 relevant moments returned from local indexPrivate retrieval
Semantic search, event clustering, and redaction tools operate against the local archive index.
Sandboxed execution
App code runs in constrained environments with explicit access boundaries for archive operations.
Core surfaces
What developers can work with.
search()
Archive retrieval
Query indexed memories by intent, time window, tags, or derived scene summaries.
redact()
Sensitive data handling
Apply additional redaction passes for faces, screens, or custom detection policies.
sync()
Vault transfer
Control local transfer jobs between capture device, dock, and vault infrastructure.
Next Step
Go from docs into the live system references.
Use the terminal, topology maps, glossary, and research notes to understand how the local APIs sit inside the broader archive stack.
Open terminal