Streaming vs Pre-Recorded language framing across Pulse docs
Streaming vs Pre-Recorded language framing across Pulse docs
The Pulse STT supported-languages story is now consistent end-to-end. Each surface labels its mode and points readers at the right neighbour:
- Overview page (
/waves/documentation/speech-to-text-pulse/overview): split the single Supported Languages table into two — Streaming (Real-Time, WebSocket) and Non-Streaming (Pre-Recorded, HTTP). Same 39-language set in both, matching the Pulse model card. - API Reference — Pre-Recorded (HTTP):
languagequery param now declares an explicitenumof 39 single-language codes (en,hi,es, …) plusmulti-eu/multi-indicaggregators. Description labels the endpoint as Pre-Recorded and points at the streaming WebSocket endpoint for the live mode. - API Reference — Streaming (WebSocket): same enum and labelling, applied via the AsyncAPI override so it renders correctly. The page-top Note labels it as Streaming and points at the HTTP endpoint for pre-recorded.
No protocol or wire-level change — purely a docs/spec consolidation.