mocop
Browse · Docs · Guide · Analyze

Speko Router streaming API

API by Speko · asyncapi

WebSocket contract of the Speko Router: streaming speech-to-text and text-to-speech sessions, plus the five native speech-to-speech routes. On the STT and TTS routes JSON text frames carry the control messages and events documented here and binary frames carry raw audio in the format the session.configure frame declared, with no JSON envelope. On /v1/realtime, /v1/live, /v1/bidi, /v1/realtime/translations and /v1/realtime/translations/qwen the Router speaks the OpenAI/xAI Realtime, GPT-Live, Gemini Live, OpenAI realtime translation and Alibaba LiveTranslate protocols natively: audio travels base64-encoded inside the vendor's own JSON events, the Router forwards a bounded set of vendor commands and every vendor server event verbatim, and only its own error frame is Router-shaped. The Go types in package relayapi are the source of truth for every Router-defined shape in this document, and speccheck_test.go machine-checks the two against each other. The HTTP endpoints are specified…

Verification: observed. Source: crawl.

Capabilities (14)

  • sendBidiEvents
  • receiveBidiEvents
  • sendLiveEvents
  • receiveLiveEvents
  • sendRealtimeEvents
  • receiveRealtimeEvents
  • sendTranslationEvents
  • receiveTranslationEvents
  • sendQwenTranslationEvents
  • receiveQwenTranslationEvents
  • sendSTTFrames
  • receiveSTTFrames
  • sendTTSFrames
  • receiveTTSFrames
About · Contact · Privacy