Agent Guide
Task guides for an agent: storing, updating, evolving, correcting, connecting and deleting records. Each says when to use it, the call, what comes back, and an example.
An agent reaches Everything Memory through ten tools over MCP. On connecting, it receives the engine's instructions and the description of each tool.
| Tool | What it does |
|---|---|
e_ingest | Store a new record; adjusts= to evolve an existing one |
e_update | Writes the next version of an existing record |
e_correct | Pin a correction to a wrong record |
e_property | Discover and attach label:value edge properties; connect two records; group several |
e_gather | Find evidence — semantic find, intersect/union, traverse |
e_timeline | Same retrieval, ordered by time |
e_read | Load full records with edge properties, corrections, adjustments |
e_audit | Reads the audit log |
e_system | Inspect agent profiles and lanes, and delete |
e_policy | Lists, downloads, uploads, enables and disables policies |
Start with a walkthrough. The skills that teach an agent these tasks are installed by the operator — see Agent Skills.
Agents use the tools over MCP. Programs, scripts and tests can make the same calls over REST: set EMEMORY_URL to the engine's address (for example, the API service the quickstart starts) and EMEMORY_API_KEY to a client key when authentication is on. Each page shows its REST equivalent.
A Walkthrough
This walkthrough runs on a new stack with authentication off, as the shipped template sets it. Every call names the agent profile restricted, which a new engine provides: it reads every lane and writes the lane default. Ids in the replies are examples; yours differ. Replies are trimmed to the fields that matter.
Storing a Record
When to Use
Finding Records
When to Use
Reading a Record
When to Use
Using the Timeline
When to Use
Updating a Record
When to Use
Evolving a Fact
When to Use
Correcting a Record
When to Use
Connecting Records
When to Use
Grouping Records
When to Use
Deleting a Record
When to Use