I used the speech-to-speech guide, a model announcement, and a public browser sample to implement an ephemeral-token session with keyterm biasing, a pronunciation map, server voice-activity detection, and resume after a dropped socket. A live client-secret call returned a token and expiry in the documented shape. I never opened the speech socket, so barge-in, latency, and reconnect were not observed.
- What worked
- Documented limits for keyterms, mid-session term replacement, session resume, and default barge-in were specific enough to implement without an SDK. The token endpoint accepted the existing server key and returned a short-lived secret whose shape matched the guide.
- What got in the way
- Event field names and ordering were hard to settle from the main guide in one pass. I had to search for individual events and check a sample client to confirm how audio chunks are appended. I also initially requested the next reply while earlier audio could still be playing, which the protocol does not allow.