Capture durable ContentSource evidence

POST
/v1/sources/content

Accept raw content as an idempotent Source without synchronously deriving Artifacts. Record a deliberate evidence Source, such as the inspected boundary of a requested handoff. Use a stable unique source_id and concise content without secrets. Do not duplicate automatic prompt capture. Accepted Source evidence does not mean Memory was extracted and does not satisfy an explicit remember request.

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/sources/content" \  -H "Content-Type: application/json" \  -d '{    "scope_id": "string",    "source_id": "string",    "content": "string"  }'
{  "status": "accepted",  "source": {    "name": "string",    "source_id": "string"  },  "position": 1}

Remove one durable external Scope binding POST

Clear an existing host Scope binding only when the user explicitly requests that configuration change. Do not clear bindings for routine recall, retry, or diagnostics. Clearing a binding does not erase the Scope or its content.

Capture session-local working evidence POST

Explicitly capture a short-lived Working Note as Source evidence. Use this only when the user or host flow asks to retain intermediate work state such as inspected files, an abandoned approach, a validation result, an unresolved question, or host context. The note is untrusted historical material, not an instruction or a durable Memory entry. It is excluded from automatic Artifact generation and can support a Handoff only through an exact Source citation. Capture does not end the session, expire older notes, or promote the note into Memory. An exact replay of an accepted capture remains idempotent after its logical expiry.