Rensei docs
API ReferenceSessions

Counts-only snapshot of in-flight execution shells for the page header.

Same org/project scope and entitlement rules as `GET /api/execution-shells`, answered as three integers instead of a page: `total` (the same count that route reports as `total`), `active` (normalized status `running`) and `queued` (normalized status `pending`). No `shells` array, no side-signal joins (interviews, approval gates, cost rollup, placement) - one small `GROUP BY status` aggregate per producer table.

GET
/api/execution-shell-counts

Authorization

headerAuthorizationBearer <WorkOS user access token>

WorkOS user access token created by the Rensei CLI. The authenticated organization is resolved from membership and may be narrowed with X-Rensei-Org.

Query Parameters

scope?string

Default org. project requires projectId.

Value in"org""project"
projectId?string

Required when scope=project.

Response Body

The counts.

application/json
  1. response
total*integer
Range-9007199254740991 <= value <= 9007199254740991
active*integer
Range-9007199254740991 <= value <= 9007199254740991
queued*integer
Range-9007199254740991 <= value <= 9007199254740991
snapshotAt*string
Example Request
curl -X GET 'https://app.rensei.ai/api/execution-shell-counts'
Example Response
{  "total": -9007199254740991,  "active": -9007199254740991,  "queued": -9007199254740991,  "snapshotAt": "string"}

Durably ingest normalized runtime events for one owned session.

Accepts a bounded, versioned batch from the worker runtime that owns the session. The server verifies deterministic event identity and strict monotonic structured sequence, injects authenticated org/project/subject scope, validates each active topic payload, commits idempotent outbox rows atomically, and only then attempts the execution-ledger drain. Redis remains a post-append wake hint.

Snapshot of in-flight execution shells, urgency-ordered.

Snapshot of in-flight execution shells, urgency-ordered. - Rensei REST API operation reference.