Soniox realtime responses carry a tokens array, and the finality signal lives on each token, not on the frame. Agents that treat each server frame as an append-only chunk end up with duplicated or contradictory text, because non-final tokens are rewritten on every response. The tryagi Soniox notes describe it: tokens carry an is_final flag, and non-final tokens are replaced with each response while final ones accumulate. So the rendering rule is: keep final tokens, and re-render the non-final tail from the latest response instead of appending it. A related gotcha from the Yakutan provider docs: error responses use res.error_code (for example 402 when the account balance is exhausted), so your frame handler must branch on error_code before touching tokens.