Get session activity time-series
Three access modes: 1. Worker JWT with `?sessionId=<rawLinearSessionId>`. 2. Unauthenticated with `?sessionId=<rawId>&sessionHash=<32-hex>`. 3. Authenticated CLI/dashboard with `?sessionId=<rawOrHashedId>` + `rsk_` bearer or session cookie.
AuthorizationBearer <rsk_live_*>Rensei API key presented as Authorization: Bearer rsk_live_. Required API-key scopes are recorded per operation in x-rensei-required-scopes.
sessionId*stringRaw linearSessionId, trackerSessionId, or 16-char public hash.
sessionHash?string32-char hex hash for unauthenticated access (SHA-256("session:{rawId}").slice(0,32)).
cursor?stringOpaque cursor for incremental polling (alias after also accepted).
Activity list with cursor.
application/json- response
activities*array<>cursor?stringOpaque cursor for polling next batch.
sessionStatus*PublicSessionStatusCoarse public lifecycle. starting means a worker owns the claim but runner execution is not yet acknowledged; working begins only after the source lifecycle advances to running/finalizing (or a post-running stuck projection). Health diagnostics such as claimStuck remain independent of this lifecycle value.
"queued""parked""starting""working""completed""failed""stopped""timed_out"curl -X GET 'https://app.rensei.ai/api/public/session-activities?sessionId=string'{ "activities": [ { "id": "string", "type": "thought", "content": "string", "toolName": "string", "timestamp": "2019-08-24T14:15:22Z" } ], "cursor": "string", "sessionStatus": "queued"}MAB router performance posteriors and recent decisions
Returns the current Beta-distribution posteriors for all known `(provider, workType)` arms, recent observation history, and a summary of routing health. Includes survival-derived reward annotations where available. Supports cursor-based pagination for the observations list. Auth: `rsk_` API key or session cookie (`authenticatePublicRequest`).
List enriched sessions for the authenticated org
Returns enriched session list with health summaries. Accepts an optional project scope via `?projectId=` or `?project=<slug>`. Falls back to parsing the `Referer` header for dashboard calls.