Skip to main content
If your app already uses the OpenAI Realtime API, you change three values and keep the rest of your code. 60db accepts the OpenAI GA protocol, so the same events, session fields and client libraries work.

What changes

Only the three values above change. Event names, session shape, tool definitions and response.done usage follow the OpenAI GA spec.

Migrate

1

Replace the key and base URL

Use SIXTYDB_API_KEY in place of OPENAI_API_KEY, and set the base URL below in your client.
2

Change the model and voice

Set the model to 60db-realtime-v1-mini. Set audio.output.voice to a 60db voice ID. Use List voices to find one.
3

Test a session

Run one text turn and one audio turn. Check that response.done returns usage and that audio plays.

Client examples

Not supported yet

Code that depends on these features needs a change or must wait:
  • WebRTC transport
  • SIP calling (call_id)
  • Out-of-band responses (conversation: "none")
  • Image input
  • MCP tools inside a session
See the full list on the Realtime overview.

60db extensions

The memory, knowledge and intent session fields are 60db extensions. OpenAI ignores them, so they are safe to send to either service. Add them when you want Smart Memory, Collections or filler speech. See 60db extensions.