Rensei docs
API ReferenceWorker Protocol

Poll for a pending plugin verb invocation

The daemon polls this endpoint to pick up plugin verb invocations queued by workflow engine steps. Returns the oldest pending invocation for the daemon's org/project scope, atomically marking it as in-flight. Returns `{ invocationId: null }` when the queue is empty or the daemon lost a race. Auth: `Bearer rsk_*` via `getCliOrSessionAuth` OR runtime JWT (`authenticateDaemon`).

GET
/api/daemon/plugin-verbs/poll

Authorization

headerAuthorizationBearer <rsk_live_*>

Rensei API key presented as Authorization: Bearer rsk_live_. Required API-key scopes are recorded per operation in x-rensei-required-scopes.

Header Parameters

X-Rensei-Bridge-Adapter?string

Adapter schema versions the daemon executes (e.g. v1). With X-Rensei-Bridge-Binaries, opts a host-bound runtime-JWT worker into the adapter lanes (ADR-2026-09-23 D9); ignored for rsk_*/user callers.

X-Rensei-Bridge-Binaries?string

Comma-separated name@version of binaries passing the host floor. A hint: the server serves only binaries this host holds an unrevoked consent for, whose consented subcommand set covers the contract.

Response Body

Poll result (empty or one invocation).

application/json
  1. response
invocationId*null
Example Request
curl -X GET 'https://app.rensei.ai/api/daemon/plugin-verbs/poll'
Example Response
{  "invocationId": null}

Acknowledge Donmai's durable privileged-verification claim

Runtime-JWT-only, receiver-bound CAS for `rensei.verify.run`. The strict JSON body is limited to 4096 bytes. This is the only transition from reservation (`delivered`) to durable local claim (`claimed`); replays return retained duplicate receipt bytes and changed authority conflicts.

Post plugin verb invocation result

Called by the daemon after executing a polled plugin verb invocation. Ordinary local-bridge results keep the existing resume behavior. `rensei.verify.run` is a strict runtime-JWT-only branch (maximum 2 MiB) requiring `X-Rensei-Claim-Acknowledgement-Receipt-Sha256` and `X-Rensei-Result-Attempt: 1|2|3|4`; it settles canonical result bytes and creates or reloads one immutable result-attempt authority before returning its exact bytes, echoed send number, and platform attempt id. It never resumes the workflow. Positive continuation occurs only at acknowledgement confirmation. Duplicate settlements are replay-safe and conflict on changed stable bytes.