Create Atomic Memory through the legacy remember input

POST
/v1/memory/remember

Create a standalone Atomic Memory and formal Owner. Omit expected_revision or pass null. Non-null legacy collection revision preconditions are unsupported before any write. Response records use true Atomic ArtifactRefs.

Authorization

BearerAuth
AuthorizationBearer <token>

Bearer credential resolved to an opaque authenticated Principal by the Server deployment.

In: header

Request Body

application/json

TypeScript Definitions

Use the request body type in TypeScript.

Response Body

application/json

application/json

application/json

application/json

application/json

application/json

application/json

curl -X POST "https://example.com/v1/memory/remember" \  -H "Content-Type: application/json" \  -d '{    "scope_id": "string",    "kind": "string",    "text": "string"  }'
{  "changed": true,  "records": [    {      "artifact": {        "family": "string",        "artifact_id": "string",        "revision": 1      },      "kind": "string",      "text": "string",      "state": "active",      "state_version": 0,      "merged_into_id": "string"    }  ]}

Process the pending Source window into Memory POST

Run one bounded Source-to-Memory activation for operational control and testing. Request processing of pending Source evidence when the user explicitly requests a flush or checkpoint. Processing depends on configured capabilities and may produce no Memory. Do not flush every turn or use it instead of an explicit Memory save. Report the actual processing result.

Search active Atomic Memory through the legacy query input POST

Require Scope read and search current active Atomic Memory with content filters before limits. Returns true Atomic ArtifactRefs and state versions, never synthetic old collection citations. Empty results are valid.