Rensei docs
API ReferenceWorker Protocol

Post merge-queue landing verdict

Called by a daemon worker with `LANDING_CAPABILITY` after attempting to land a commit onto the merge queue (automerge / fast-forward). Records the outcome and triggers post-landing cleanup (lock release, next-work promotion, Linear notification). Auth: runtime JWT. Cross-tenant guard: `orgId` in body must match the JWT's org claim (mismatch returns 404, not 403).

POST
/api/daemon/landing/result

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
repoId*string

Canonical owner/repo form.

proposal*integer

Merge proposal sequence number.

issueId*string
linearSessionId*string
verdict*string
Value in"landed""conflict""failed"
message?string

Human-readable outcome message.

landedSha?string

The merged commit SHA (only on landed).

Response Body

Verdict recorded.

application/json
  1. response
ok*true
Value intrue
orgId*string
issueId*string
proposal*integer
verdict*string
Value in"landed""conflict""failed"
Example Request
curl -X POST 'https://app.rensei.ai/api/daemon/landing/result' \  -H 'Content-Type: application/json' \  -d '{  "orgId": "string",  "repoId": "string",  "proposal": 0,  "issueId": "string",  "linearSessionId": "string",  "verdict": "landed"}'
Example Response
{  "ok": true,  "orgId": "string",  "issueId": "string",  "proposal": 0,  "verdict": "landed"}

Mint a short-lived GitHub installation token for a repo

Called by the host daemon to obtain a short-lived GitHub App installation token for a specific repository. The token is minted from the org's GitHub App installation and expires in ~1 hour. The `orgId` in the body must match the authenticated org. Auth: `Bearer rsk_*` via `getCliOrSessionAuth` OR worker runtime JWT. API keys gate on their project fence; a runtime JWT gates on the fence of the credential that minted it (null = org-wide on both paths). A repository bound only as context inside that fence returns HTTP 403 with `{ token: null, reason: 'context-repository' }`; callers must not fall back to a PAT for that policy refusal. The refusal gates writes only: readOnly:true still mints a read-scoped token; read-only context delivery stays a separate path. Returns `{ token: null, reason }` (HTTP 200) on soft failures so the caller can decide whether to fall back to a stored PAT.

List daemon mutation history for a host

List daemon mutation history for a host - Rensei REST API operation reference.