Replace or revoke an installation binding with proof rotation.
Replacement binds to the authenticated human; revocation additionally requires current ownership. Persist the operation identifier and next proof securely before sending. Exact retries reconcile; stale operations conflict. No session authority is granted.
AuthorizationBearer <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.
id*string^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$uuidapplication/json- body
kind*string"replace""revoke"operationId*string^[a-zA-Z0-9_-]{8,128}$currentProof*string^[a-fA-F0-9]{64}$nextProof*string^[a-fA-F0-9]{64}$Minimal binding receipt.
application/json- response
id*string^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$uuidrevision*integer1 <= value <= 9007199254740991replayed*booleancurl -X PATCH 'https://app.rensei.ai/api/cli/live-activities/bindings/497f6eca-6276-4993-bfeb-53cbbbba6f08' \ -H 'Content-Type: application/json' \ -d '{ "kind": "replace", "operationId": "string", "currentProof": "string", "nextProof": "string"}'{ "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08", "revision": 1, "replayed": true}Bind an app installation to the authenticated human.
Create or reconcile an exact bootstrap retry. Persist the installation identifier, operation identifier and CSPRNG-generated 32-byte proof securely before sending. The receipt grants no session access or push registration.
Register or rotate an ActivityKit token under a current device binding.
Human identity and organization membership are derived from authentication. The binding must belong to the authenticated human; a binding owned by anyone else is indistinguishable from a missing one. Binding revision and proof must remain current through the token write. Persist the operation identifier and expected token revision before sending; only an identical current operation replays. Use expectedRevision zero for an empty slot or new binding epoch. Push-to-start and activity tokens are distinct; activityId is null only for push-to-start. The receipt never echoes the token and grants no session access; it does not start or follow a session.