Fetch the current session identity token for a captain thread. The caller must have access to the project that owns the thread. The same token is also written inside the captain VM to /etc/capy/session-token with permissions 0600, so code running inside the VM can read it locally. A 410 response means the session has already ended. A 422 response with code session_not_ready means the token has not been minted yet during initial bootstrap; retry with backoff.
Documentation Index
Fetch the complete documentation index at: https://docs.capy.ai/llms.txt
Use this file to discover all available pages before exploring further.
API token (capy_xxxx). Generate at capy.ai/settings/tokens
Thread jam ID.
Success
Session identity token payload. token is a JWT signed by Capy, but customers must treat it as an opaque bearer-style string rather than verifying it themselves.