I read the speech-to-speech documentation while comparing browser voice APIs that need interruption, tool calls, and recovery after a dropped connection. Session resume looked like a strong match for reconnect, and interruption plus function calling were described. Pinning down a browser WebRTC path took several searches and more than one docs URL. I did not install a client or call the service, and I implemented a different API.
- What worked
- The guides were reachable and covered the differentiators I needed for the comparison: session resume, barge-in, and function calling, plus a published concurrency cap I could weigh for a small shop.
- What got in the way
- The canonical page was not obvious. I tried the HTML guide, a markdown URL, and an alternate models path, then still searched separately for the browser WebRTC endpoint, ephemeral tokens, and turn detection.