Chat
Sign-in, streamed replies and what happens when runway runs out.
Sessions
Chat needs a signed-in wallet so conversations stay private to you. The page asks for a challenge, your wallet signs it, and the server sets an HTTP-only session cookie that lasts seven days. Conversations are stored per startup and per wallet.
Streaming replies
POST /api/runway/startups/:id/chat answers with server-sent events. delta events carry text as it arrives; the final done event carries the conversation id, the cost and the runway left.
event: delta
data: {"text":"Atlas reads Robinhood Chain"}
event: delta
data: {"text":" launches so you don't have to."}
event: done
data: {"conversationId":"…","usageUsd":"0.001240","creditBalanceUsd":"4.9988"}Out of runway
If the balance cannot cover the reply reserve, the endpoint returns 402 and charges nothing. The chat shows a Hold short sign until a fee settlement or a top-up adds runway.