Create Live Call Session

Start a live voice call with a companion: returns a one-time WebSocket URL your client (a browser too) connects to, without ever seeing your API key.

spicy-live-1: the caller talks, the persona answers in a natural voice, and interruptions are handled, over one WebSocket (wss://api.spicyapi.com/v1/realtime, see Live Call WebSocket). Set the persona and voice here; the call itself follows the OpenAI Realtime event shape.

spicy-live-2 is the highest-quality live call: the role-play model spicy-companion-1 writes every reply (it stays in the scene and moves it forward), spoken by Spicy Voice 3 voices that act the emotion (Bella Bright, Roger, Sarah, Laura, Charlie, George, Callum, River, Harry, Liam, Alice, Matilda, Will, Jessica, Eric Smooth, Chris, Brian, Daniel, Lily, Adam, Bill, default Sarah), with turn-taking and interruptions handled for you. Same WebSocket events and audio formats as spicy-live-1. It takes language (en, zh, de, it, pt, es, ja, ko, fr, ru, default English) and no turn_detection. Billed at $0.08 per minute of call time (by the second) plus the reply tokens at $1.00 in, $2.80 out per 1M tokens; each charge arrives as a spicy.usage event. Opening a session needs a balance of at least $0.10.

The ticket in client_secret.value works once, within 60 seconds. Create the session on your server with your key and hand only the returned url to the browser. A call lasts up to 780 seconds per session; open a new session to continue.

Billed per turn from the tokens each reply used, per 1M tokens: text in $0.46, audio in $1.86, text out $1.40, audio out $3.74. Audio counts about 7 tokens per second in and 12.5 out, and the conversation so far is billed again as input on each turn, which comes to about 1 to 1.5 cents per minute of steady back-and-forth (measured on real calls, Oct 2026; less when the line is quiet). Opening a session needs a balance of at least $0.05; when the balance or your spend limit runs out mid-call, the call ends with a payment_required error event.

The persona in instructions is screened like a prompt before the session is created (422 when blocked). During the call both sides' transcripts are screened; a violation ends the call with a content_blocked error event. No custom or cloned voices, no camera or image input, no tools or web search. Sandbox keys get a session whose socket answers with canned events and bills nothing. Calls appear in the request log as type realtime with seconds, turns and total cost.

curl --request POST \
  --url https://api.spicyapi.com/v1/realtime/sessions \
  --header 'Authorization: Bearer $SPICYAPI_KEY' \
  --header 'Content-Type: application/json' \
  --data '{
    "model": "spicy-live-1",
    "voice": "Serena",
    "instructions": "You are Mara, 29, a playful bartender on a late-night call with the user. Flirt, tease, keep replies short.",
    "turn_detection": { "type": "server_vad", "silence_duration_ms": 600 }
  }'

{
  "id": "rt_5c2e8a1f9d3b7e4a",
  "object": "realtime.session",
  "model": "spicy-live-1",
  "voice": "Serena",
  "turn_detection": { "type": "server_vad", "silence_duration_ms": 600 },
  "max_seconds": 780,
  "input_audio": "pcm16 mono 16 kHz, base64 in input_audio_buffer.append",
  "output_audio": "pcm16 mono 24 kHz, base64 in response.audio.delta",
  "client_secret": { "value": "rts_9f1b3d5e7a2c4e6f8a0b", "expires_at": 1758553260 },
  "url": "wss://api.spicyapi.com/v1/realtime?session=rts_9f1b3d5e7a2c4e6f8a0b"
}