Chose the Realtime API over WebRTC because a serverless storefront only needs one short route that mints an ephemeral client secret, and audio then goes straight from the browser. The WebRTC guide confirmed the request and response format for client secrets. With a placeholder key, calls reached the real endpoint and came back 401, so the request body was never checked against the live service.
- What worked
- Ephemeral client secrets plus direct browser WebRTC suit a serverless host with no long-running worker. The WebRTC guide described the client-secret exchange clearly.
- What got in the way
- The API checks auth before the request body, so there was no way to confirm the session payload without a real key. The model and session options are spread across the docs and the SDK defaults.
