Rensei docs
API ReferenceWorker Protocol

Observe privileged-verification finalization status

Read-only status observation bound to the exact ordered invocation, claim, confirmation digest, consumed attempt number, and current receiver-bound runtime JWT. It never creates finalization/evidence authority, acquires a lease, or resumes a workflow. Pending is HTTP 202; confirmation-final HTTP 200 streams exact retained first/duplicate response bytes selected by permanent child disposition; deadline-final HTTP 200 returns the exact nine-member status.

GET
/api/daemon/plugin-verbs/result/acknowledgement-confirmation/status

Authorization

workerJwt
AuthorizationBearer <token>

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

In: header

Query Parameters

invocationId*string
Formatuuid
claimId*string
Formatuuid
confirmationRequestSha256*string
Match^[0-9a-f]{64}$
attemptNumber*string
Value in"1" | "2"

Response Body

application/json

application/json

application/json

application/json

application/json

curl -X GET "https://example.com/api/daemon/plugin-verbs/result/acknowledgement-confirmation/status?invocationId=497f6eca-6276-4993-bfeb-53cbbbba6f08&claimId=497f6eca-6276-4993-bfeb-53cbbbba6f08&confirmationRequestSha256=string&attemptNumber=1"
Empty
Empty
{
  "error": "Session not found"
}
{
  "error": "Session not found"
}
{
  "error": "Session not found"
}
{
  "error": "Session not found"
}
{
  "error": "Session not found"
}

Confirm Donmai terminal lease acknowledgement and authorize continuation

Runtime-JWT-only confirmation for a settled `rensei.verify.run` result. Requires `X-Rensei-Confirmation-Attempt: 1|2`, exact retained settlement/result-response digests, and a canonical Donmai acknowledgement outcome. Applied outcomes may retain `release-pending` with provider release incomplete or observe `released`; permitted rejection outcomes authorize only the action-failure edge. This is the sole positive continuation authority; the result endpoint itself always reports `resumed: 0` for first settlement.

Get queued session detail for cloud runners

Lets a cloud runner-in-box (e2b/modal/daytona) fetch its session detail from the platform rather than the local daemon control API (`127.0.0.1:7734/api/daemon/sessions/:id`), which does not exist inside a cloud sandbox. The provisioner stamps `DONMAI_DAEMON_URL=<platform-url>` into the box's env so `donmai agent run` fetches its detail here. Source of truth is the Redis `work:items` hash. The full payload is available **only while the session is still QUEUED** - it is deleted on claim. Auth: bearer worker token (runtime JWT or legacy `WORKER_API_KEY`). The response includes `authToken`, system prompts, repo URL, and org ID - not readable without authentication.