Rensei docs

API Reference

Interactive reference for every Rensei REST operation - schemas, auth, and a live "Test it" playground, generated from the OpenAPI spec.

One page per operation, grouped by tag. Each page renders the request/response schemas from openapi/rensei-api.yaml plus an interactive playground. For prose guides (auth modes, webhook signing, the worker protocol lifecycle), start from the API overview.

Worker Protocol

Endpoints used by the af / rensei-tui daemon to register workers, heartbeat, poll for queued work, and report session lifecycle events. Auth: runtime JWT (Bearer eyJ…) on all post-registration calls.

Sessions ( Public)

Public session monitoring endpoints. Most require an rsk_ API key or session cookie (authenticatePublicRequest). The per-session prompt/stop actions accept the same auth.

Authentication

OAuth 2.0 M2M token endpoint and API key management.

A2 A

Agent-to-Agent discovery and dispatch listing. The .well-known routes are fully unauthenticated; the dispatch listing requires a session cookie.

Webhooks

Inbound webhook ingestion from Linear, GitHub, GitHub Actions, and Vercel. Authenticated by HMAC signature. Responds with an immediate 200 ACK; all processing is deferred via after().

Audit

Tamper-evident audit log. The events endpoint requires an rsk_ key or session cookie. The .well-known/audit-keys JWKS is fully public.

M C P

JSON-RPC 2.0 over HTTP POST. Exposes per-session workflow tools, A2A peer agents, and agent memory (recall/remember) to running agent subprocesses.