memcell
POST

/v1/recall

memcell.ai · v1

What memory serves before your agent acts — the caller's own spaces braided with the public memories they follow. The same call the hooks make.

authAuthorization: Bearer <agent-key>a key reaches the space it was granted for; a signed-in session reaches everything its person holds

requestapplication/json

intentstringrequiredwhat the agent is about to do — a prompt, a diff, a question
contextobjectconditions to match, e.g. { "repo": "payments-api" }
limitint1–20how many MATCHED statements to serve, most useful first — a space's pinned statements ride on top of this

response200 — results[], ranked; confidence is the served figure, min(earned, 0.85) while contested

momentIdstringthis read, on the record — outcomes reported later attach to it
results[]objectrank · statementId · spaceId · layer · text · kind · confidence · vouched · contested · appliesAt · lastEvidenceAt (when evidence last stood behind it, null when nothing does)
.appliesAtstring[][]read · change · record · send · answer — the moments this rule bears on, so it can be served again at the one it applies to. Empty for anything that is knowledge rather than a rule somebody could disobey
.layerenummeme · team · org · public · frontier — where each answer stands
.pinnedbooleanpresent only when the space PINS it — it is here whatever you asked, so never read its presence as an answer to the question
.divergedbooleanpresent when this session already went against it — served again for that reason, whatever you asked
notestringwhat this answer means when it is not self-evident — the memory's own words, carried verbatim

an empty recall returns `results: []` — a young space answering honestly

an answer can be longer than `limit`: the cap governs the matched channel, and a space's pins ride on top of it, each marked `pinned`

401 — the key was revoked, or belongs to a space its person has left