Rensei docs
API ReferenceDaemon

Persist an exact host-level session restart fence.

Runtime-worker-JWT-only planned-restart coordination mutation. The JWT must remain unrevoked and bound to the named organization and live host; its worker registration may already be deregistered, because a restart fence conserves an existing host rather than granting new work authority. One fence id accepts one exact ordered session set: exact replay returns the same durable revision, while changed bytes are refused. Fence expiry is never release authority.

POST
/api/daemon/restart-fences

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
fenceId*string
Length1 <= length
hostId*string
Length1 <= length
sessions*array<>
Items1 <= items <= 256
issuedAt*number
holdUntil*number
state*string

Response Body

The exact fence is durable and acknowledged.

application/json
  1. response
requestBytes*string
Length1 <= length
revision*string
Match^(0|[1-9][0-9]*)$
expectedAdoptionRevision*string
Match^(0|[1-9][0-9]*)$
requestDigest*string
Match^[0-9a-f]{64}$
idempotentReplay*boolean
state*string
correlations*array<>
Example Request
curl -X POST 'https://app.rensei.ai/api/daemon/restart-fences' \  -H 'Content-Type: application/json' \  -d '{  "fenceId": "string",  "hostId": "string",  "sessions": [    {      "orgId": "string",      "sessionId": "string",      "processEpoch": 0,      "controllerGeneration": 0,      "lastForwardedSeq": 0    }  ],  "issuedAt": 0,  "holdUntil": 0,  "state": "held"}'
Example Response
{  "requestBytes": "string",  "revision": "string",  "expectedAdoptionRevision": "string",  "requestDigest": "string",  "idempotentReplay": true,  "state": "held",  "correlations": [    {      "revision": "string",      "ordinal": 0,      "sessionId": "string",      "shimId": "string",      "processEpoch": "string",      "controllerGeneration": "string",      "lastForwardedSeq": "string"    }  ]}

AF-compatible worker registration

AF-compatible registration endpoint. Accepts three auth modes: 1. `Authorization: Bearer rsk_live_*` or `rsp_live_*` (registration token in header). 2. Legacy `WORKER_API_KEY` (transitional; being removed). 3. User session cookie / `rsk_` API key with `projectId` in body (new-user onboarding). `projectAdmissionVersion: 2` makes `projectIds` authoritative, including explicit empty = serve none. When the version is absent, the platform uses the bounded legacy projection. Returns a `runtimeToken` (and `runtimeTokenExpiresAt`) for runtime-JWT-capable callers; legacy callers receive `null` for these fields.

Atomically publish one complete per-org adoption batch before Ready.

Atomically publish one complete per-org adoption batch before Ready. - Rensei REST API operation reference.