Rensei docs
API ReferenceWorker Protocol

Refresh expired runtime JWT

Refresh expired runtime JWT - Rensei REST API operation reference.

POST
/api/workers/{id}/refresh-token

Authorization

AuthorizationBearer <token>

Project-scoped worker registration token. Current handlers accept this only where explicitly listed.

In: header

Path Parameters

id*string

Response Body

application/json

application/json

application/json

curl -X POST "https://example.com/api/workers/string/refresh-token"
{
  "runtimeToken": "string",
  "expiresAt": "2019-08-24T14:15:22Z"
}
{
  "error": "Session not found"
}
{
  "error": "Session not found"
}

Poll for queued work

Atomically pops and pre-claims work items from the priority queue (ZPOPMIN). Also returns inbox messages for the worker's active sessions. Workers that receive `preClaimed: true` must NOT make a separate claim call. Runtime-JWT callers also receive `gitCredentials` (short-lived GitHub PAT) and optionally `batchWork` (code-survival scan items, gated on the `code-survival-scan` capability).

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.