Rensei docs
API ReferenceDaemon

Persist exact replacement-controller adoption evidence.

Commits the exact negotiated evidence against one opaque server-prepared handoff and links every correlation resolved by that preparation. Exact replay is idempotent; client fence selectors are rejected.

POST
/api/daemon/session-shim/adoptions/commit

Authorization

workerJwt
headerAuthorizationBearer <JWT>

Short-lived worker runtime JWT minted by the platform. Claims bind the worker, project, organization, registration, and scopes.

Request Body

application/json
  1. body
orgId*string
Length1 <= length <= 256
sessionId*string
Length1 <= length <= 256
hostId*string
Length1 <= length <= 256
shimId*string
Length1 <= length <= 256
processEpoch*string
Match^(0|[1-9][0-9]*)$
evidenceId*string
Length1 <= length <= 256
preparedCorrelation?string
Length1 <= length <= 4096
recoveryCorrelation?string
Length1 <= length <= 4096
controllerId*string
Length1 <= length <= 256
controllerGeneration*string
Match^(0|[1-9][0-9]*)$
lastForwardedSeq*string
Match^(0|[1-9][0-9]*)$
carrierEpoch*string
Match^(0|[1-9][0-9]*)$
extensions*
observedAt*string
Match^(0|-?[1-9][0-9]*)$

Response Body

Adoption evidence is durable.

application/json
  1. response
evidence*
revision*string
Match^[1-9][0-9]*$
requestDigest*string
Match^[0-9a-f]{64}$
hostAdoptionRevision*string
Match^(0|[1-9][0-9]*)$
durableCorrelation*string
Length1 <= length
idempotentReplay*boolean
Example Request
curl -X POST 'https://app.rensei.ai/api/daemon/session-shim/adoptions/commit' \  -H 'Content-Type: application/json' \  -d '{  "orgId": "string",  "sessionId": "string",  "hostId": "string",  "shimId": "string",  "processEpoch": "string",  "evidenceId": "string",  "controllerId": "string",  "controllerGeneration": "string",  "lastForwardedSeq": "string",  "carrierEpoch": "string",  "extensions": {    "required": [      "carrier_epoch"    ],    "values": {      "carrier_epoch": "string"    }  },  "observedAt": "string"}'
Example Response
{  "evidence": {    "orgId": "string",    "sessionId": "string",    "hostId": "string",    "shimId": "string",    "processEpoch": "string",    "evidenceId": "string",    "preparedCorrelation": "string",    "recoveryCorrelation": "string",    "controllerId": "string",    "controllerGeneration": "string",    "lastForwardedSeq": "string",    "carrierEpoch": "string",    "extensions": {      "required": [        "carrier_epoch"      ],      "values": {        "carrier_epoch": "string"      }    },    "observedAt": "string"  },  "revision": "string",  "requestDigest": "string",  "hostAdoptionRevision": "string",  "durableCorrelation": "string",  "idempotentReplay": true}

Read the opaque expected host adoption revision before batch publication.

Read the opaque expected host adoption revision before batch publication. - Rensei REST API operation reference.

Prepare a strictly higher attach-v2 carrier epoch before Welcome.

Reserved for server-resolved selected-v3 session-shim takeover with full_host_frame_v3 and durable_carrier_proof_v2. Hosted activation remains closed before durable prepare or token mint until proof-v1 cutover, proof-v2 floor/predecessor, retained-candidate recovery, and the staged Relay receipt rail are verified.