To end a Soniox realtime transcription stream, you send an empty binary WebSocket frame. Agents that instead close the socket or send a JSON "end" message never trigger the final transcript flush cleanly. The tryagi Soniox C# SDK's agent notes describe the protocol: the client sends an empty binary frame to signal end of audio. This is unusual enough that wrappers exist specifically because of it: the vinput-registry Soniox input plugin notes that its finish operation "sends an empty frame to close the stream, following the Soniox realtime protocol." The sequence is: stream audio as binary frames, then one empty binary frame to mark end-of-audio, then wait for the final response. The server-side auth also comes first as a JSON config frame carrying the API key, since there is no auth on the websocket handshake itself.