Rensei docs
API ReferenceDispatch

Discover cards and their project workflow backing.

Discovery for card-based dispatch: lists visible cards with published workflow backing and an install/activate hint when unbacked for the project (same resolver, same visibility and publication rules). With `card`, returns that one card's detail - the per-card help the CLI prints and the typed parameter schema (`paramSchema`: the workflow's caller-settable parameters with defaults and constraints, plus the card's declared inputs) the CLI validates and prompts against before dispatching.

GET
/api/cli/dispatch/cards

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.

Query Parameters

project*string
Length1 <= length
card?string
Length1 <= length

Response Body

Visible cards with published workflow backing, or one card's detail when card is given.

application/json
  1. response
requestedProject*string
resolvedProjectId*string
resolvedProjectSlug*string
cards*array<>
Example Request
curl -X GET 'https://app.rensei.ai/api/cli/dispatch/cards?project=string'
Example Response
{  "requestedProject": "string",  "resolvedProjectId": "string",  "resolvedProjectSlug": "string",  "cards": [    {      "id": "string",      "ref": "string",      "slug": "string",      "name": "string",      "description": "string",      "scope": "string",      "version": 0,      "workType": "string",      "role": "string",      "artifact": "string",      "inputs": null,      "paramSchema": {        "params": [          {            "name": "string",            "type": "string",            "required": true,            "callerSettable": true,            "tightenOnly": true,            "description": "string",            "default": null,            "constraints": {              "enum": [                "string"              ],              "maximum": 0            },            "schema": null          }        ],        "cardInputs": [          {            "name": "string",            "type": "string",            "required": true,            "default": null          }        ]      },      "workflow": {        "backed": true,        "via": "agent-dispatch",        "installTemplate": "agent-dispatch",        "hint": "string"      }    }  ]}

Inspect typed delegation capability availability.

Returns the exact capability probe consumed by the Rensei CLI. An empty mcpTools or lifecycle array remains a fail-closed declaration: typed dispatch and session lifecycle are not usable. Advertisement is all-or-nothing - the CLI requires every entry, so a partial list disables typed dispatch entirely. `lifecycle` is an inventory of served routes: all four exist under /api/cli/sessions/{sessionId} and admitted typed dispatch allocates a durable ledger session. `mcpTools` is NOT a tool inventory: it is the version handshake that unlocks those routes, and no platform MCP facade defines tools by those names - POST /api/cli/mcp serves `dispatch`, `get_receipt`, and `list_workflows` only. Do not issue tools/call against an mcpTools name.

Resolve workflow-admitted revision-pinned headless launch selections.

Read-only project/workflow preflight for non-browser dispatch clients. Returns exact harness and Agent Card refs emitted by the canonical launch-options producer; callers submit one launchSelection verbatim and never author revisions. Exactly one candidate carries isResolvedDefault when the assignment cascade (workflow node -> project workType -> project default -> org workType -> org default -> system), walked at the same site the runtime uses including the authorizing agent.invoke node of this admitted workflow, names a viable winner among the listed harness candidates; resolvedDefault repeats it with the tier that chose it. A client given no explicit model profile submits that candidate. Candidate order is NOT authority: when resolvedDefault is null, resolvedDefaultReason says why and the client must refuse rather than pick.