Rensei docs
API ReferenceWorker Protocol

Post security scan event

Post security scan event - Rensei REST API operation reference.

POST
/api/sessions/{id}/security-scan

Authorization

headerAuthorizationBearer <JWT>

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

Path Parameters

id*string

Request Body

application/json
  1. body
workerId*string
event*

SecurityScanEvent shape validated by Zod schema.

Response Body

Scan event stored.

application/json
  1. response
stored?boolean
Example Request
curl -X POST 'https://app.rensei.ai/api/sessions/string/security-scan' \  -H 'Content-Type: application/json' \  -d '{  "workerId": "string",  "event": {}}'
Example Response
{  "stored": true}

Sample MAB router for provider selection

Called by the cloud runner at session start to ask the platform's multi-armed bandit router which provider to use. The platform reads Beta-distribution posteriors and runs Thompson sampling over the caller-supplied candidates list. Returns `null` provider with a `source` reason on all error / disabled / explicit-override paths (HTTP 200 always) so the runner can always fall back to its statically resolved provider. Kill-switch: `ROUTING_SELECTOR_ENABLED` env must be exactly `"true"`; default is DARK. Explicit dispatch overrides always return `{ selectedProvider: null, source: 'explicit' }`.

Read session state

Read session state - Rensei REST API operation reference.