curl https://app.tryafk.com/api/v1/remember \
-H "Authorization: Bearer $KIP_KEY" \
-H "Content-Type: application/json" \
-d '{"memories": [{"title": "Q4 plan", "content": "Ada owns the Q4 launch plan; review is on 12 Nov.", "key": "acme:plan:q4"}]}'
{ "saved": 1, "duplicate": 0, "rejected": 0, "ignored": 0, "withheld": 0 }
API reference
Remember
Save what your app knows about a person into their Kip memory.
POST
/
api
/
v1
/
remember
curl https://app.tryafk.com/api/v1/remember \
-H "Authorization: Bearer $KIP_KEY" \
-H "Content-Type: application/json" \
-d '{"memories": [{"title": "Q4 plan", "content": "Ada owns the Q4 launch plan; review is on 12 Nov.", "key": "acme:plan:q4"}]}'
{ "saved": 1, "duplicate": 0, "rejected": 0, "ignored": 0, "withheld": 0 }
Memories go to the person’s own brain, private to them. They never go into the company brain from here. Kip reads them into the brain within a minute or two; then Recall and Ask find them.
Saving memories is free: it does not use credits.
Authorization
Authorization: Bearer kipm_..., the person’s key.
Body
object[]
required
Up to 50 memories:
title(required): a short name, up to 300 characterscontent(required): the memory in plain words, Markdown is fine, up to 20,000 characterskey: a stable name. Saving the same key again updates the memory instead of adding a copy.updated_at: when it last changed, ISO 8601. Now by default.
"conversation" | "import"
default:"conversation"
import when you are copying memories from somewhere else in bulk.Response
number
New or changed memories saved.
number
Already there, unchanged.
number
number
number
Not saved because they were empty or looked like they held a credential, password, card or bank number.
curl https://app.tryafk.com/api/v1/remember \
-H "Authorization: Bearer $KIP_KEY" \
-H "Content-Type: application/json" \
-d '{"memories": [{"title": "Q4 plan", "content": "Ada owns the Q4 launch plan; review is on 12 Nov.", "key": "acme:plan:q4"}]}'
{ "saved": 1, "duplicate": 0, "rejected": 0, "ignored": 0, "withheld": 0 }