Sessions
Bind the runtime sessionId to the session (attribution)
The embed posts the runtime sessionId (known only after connect) so the platform can attribute the live session to your app for usage + reactive kill. app_id is taken from the verified session token, never the client.
POST
Bind the runtime sessionId to the session (attribution)
Authorizations
The scoped runtime session JWT from POST /v1/sessions/token. The embed's browser presents it (Authorization: Bearer, or a token body field) to the runtime exchange routes. Not an API key.
Response
Bound.
Previous
Settle a live session on closeThe embed posts this when the player unmounts. Frees a concurrency slot, refunds the unused session-minutes reservation, and records the actual GPU-seconds to usage + billing.
Next
Bind the runtime sessionId to the session (attribution)