Create a new memory for an agent.
Persists a new memory the agent can recall in later executions. A `subject` makes it a memory about that person, filed under their participant id whichever form names them; an address no one in the workspace holds yet adds a contact for it, so the memory is recalled once they write in. Requires the Editor collaborator role. Returns 201 with a `Location` header pointing at the created memory, 400 when the payload is invalid or the subject names no one, and 409 when the agent already holds a memory with the same title about the same subject.
Authorization
Bearer JWT Authorization header using the Bearer scheme. Enter 'Bearer' [space] and then your token.
In: header
Path Parameters
The unique identifier of the agent.
The tenant identifier
The memory's title, content, optional tags, and optional subject.
1 <= length <= 2551 <= length <= 10000The end-user this memory is about: their participant id, or the
"provider:identifier" of one of their channel addresses (e.g.
"telegram:123456789"). Either way the memory is filed under the
participant id, which is what the agent recalls; an address no one holds
yet adds a contact for it. Omit or leave empty to create an agent-global
memory shared across every conversation.
length <= 512Response Body
curl -X POST "https://api.fruxon.com/v1/tenants/string/agents/string/memories" \ -H "Content-Type: application/json" \ -d '{ "title": "string", "content": "string" }'{
"id": "00000000-0000-0000-0000-000000000000",
"scope": "AGENT",
"subject": "string",
"writtenByIdentity": "string",
"title": "string",
"content": "string",
"tags": [
"string"
],
"createdAt": 0,
"modifiedAt": 0
}{
"type": "string",
"title": "string",
"status": 0,
"detail": "string",
"instance": "string",
"property1": null,
"property2": null
}{
"type": "string",
"title": "string",
"status": 0,
"detail": "string",
"instance": "string",
"property1": null,
"property2": null
}