Fullplex

Fullplex is Resia's native full-duplex voice API service. Full-duplex means that speech travels in both directions at the same time: your application sends a person's speech and receives Fullplex's speech on one connection. The model name is resia-fullplex-1.

You can use Fullplex in two ways:

Use What it is How it starts Read more
Live session A direct voice conversation between your application and Fullplex, such as a voice feature in a web app or a mobile app. Your server opens a WebSocket to the Live API. Live API
Phone call A call of a Call Agent that runs on Fullplex. You place a call with POST /v1/calls, or a person calls a number that the agent answers. Call Agents

Fullplex speaks English only.

A live session needs no Call Agent and no phone number. Your application carries the audio. To place or answer phone calls, use a Call Agent.

Live sessions

A live session is one voice conversation on one WebSocket, a connection that carries events in both directions. Your application sends the person's audio, and Fullplex sends back speech and transcripts while the person talks.

Keep the API key on your server. Never send it to a browser or a mobile app. The app sends audio through your server. Signed-in organization members can use their portal ID token in a browser; see Authentication.

A session has four stages:

  1. Connect. Your server opens wss://api.resia.ai/v1/live/sessions with a Resia API key. The key needs editor or owner scope.
  2. Start. Your application sends session.start as the first event. Resia answers with session.started, which holds the session ID. It arrives when the session is ready to talk. Open the session before the person speaks, and put text that changes for each call at the end of instructions; see Start a session fast.
  3. Talk. Your application sends audio in session.input_audio.append events. Fullplex sends speech in session.output_audio.delta events, and a transcript of each side as text.
  4. Close. Your application sends session.close. A session also ends when the connection drops or when the session reaches its time limit.

session.start sets the session. Only model is required:

{
  "type": "session.start",
  "session": {
    "model": "resia-fullplex-1",
    "instructions": "You are the voice assistant of a dental office. Help the caller book a cleaning.",
    "audio": {"output": {"voice": "cartesia:VOICE_ID_FROM_THE_LIST"}},
    "store": true
  }
}
Setting What it does Can it change during the session?
instructions What Fullplex says and does in this conversation. Your application can add instructions and context with events.
input Earlier messages of the conversation, as text. No
audio.format The audio encoding of both directions. No
audio.output.voice The voice. See Voices. No
store true saves a recording. See Recordings. No
delegation Who does a task that the conversation needs. See Delegation. The type and the mode stay fixed.

Connect a live session gives every field, its limits, and the audio formats. Session events lists every event and error.

Session limits

Limit Value
Session length At most 3,600 seconds.
No audio input The session ends 30 seconds after session.started.
Sessions at the same time Five for each organization by default. GET /v1/rate-limits reports fullplex.concurrent_sessions and fullplex.in_progress. See Rate limits.

After a session

Each session leaves a record. GET /v1/live/session-history lists your organization's sessions, newest first. GET /v1/live/sessions/{session_id} returns one session with its start time, duration, close reason, and whether it has a recording. See Session records and voices.

Fullplex on phone calls

A Call Agent can run its phone calls on Fullplex. Set these fields on the Call Agent:

{
  "model_architecture": "speech_to_speech",
  "speech_to_speech_model": "resia-fullplex-1",
  "in_call_llm": null
}

These settings take effect at once, without review. The agent keeps its instructions, inputs, and call analysis, and its calls go through POST /v1/calls and your phone numbers as other calls do.

When Butler creates a Call Agent, the agent runs on Fullplex by default. The Butler page gives the exceptions.

Voices

Fullplex speaks with a Cartesia or a Fish voice. You choose the voice from a catalog:

curl --fail-with-body --silent --show-error \
  "$RESIA_API_BASE/v1/live/available-voices?provider=cartesia" \
  --header "Authorization: Bearer $RESIA_API_KEY"

provider is cartesia, the default, or fish. Each voice has an id, a name, a gender, and a language. Choose an English voice.

Use Where you set the voice Without a choice
Live session session.audio.output.voice in session.start, as cartesia:<voice ID> or fish:<voice ID>. The default voice, Cartesia Skylar.
Phone call The Call Agent's voices list, with tts_provider and voice_id. List the voices with GET /v1/call-agents/available-voices. See Voices. The default voice.
  • A voice stays the same for a whole session or call.
  • Fish voices are not available to an organization that has a business associate agreement (BAA) or zero data retention (ZDR) with Resia. The Fish catalog is then empty. Cartesia voices stay available.
  • A private voice does not appear in the catalog. Use the ID that Resia supplied for your use.

Recordings

Use How a recording is made How you get it
Live session Only when session.start has store: true. Without it, Resia saves no recording of the session. GET /v1/live/sessions/{session_id}/content, after the session closes.
Phone call As for any call. GET /v1/calls/{call_id}/recording. See Read calls.

A live session recording is a stereo WAV file. The left channel has the input audio, and the right channel has the output audio. recorded on the session record says whether a complete recording exists. See Download a recording.

Delegation

Some requests need work that takes time, such as a lookup in your system or a web search. Delegation gives that task to something outside the conversation, and Fullplex speaks the result when it arrives.

A live session delegates to one of two targets:

Target Who does the task Use it when
Your application Resia sends session.delegation.created. Your application does the work and sends the result back as an event. Your own code or your own model does the work.
A backend assistant A model that you name in session.start does the task with the tools that you allow: your function tools, MCP (Model Context Protocol) tools, web search, or image generation. You want Resia to run the model. Function tools still execute in your application.

delegation.mode sets how often the session delegates:

Mode Behavior
auto, the default The session selects when to delegate.
always The session delegates its replies to completed turns of the person.
off The session does not delegate.

The target and the mode stay fixed for the session. See Delegation for the settings, and Session events for the events that carry tasks and results.

Prices

Use Price
Live API session 2.5 cents per minute, billed by the second, plus backend token and hosted-tool charges when used. A session that receives no input audio is not charged.
Fullplex telephone call 10 cents per started minute, unless your organization's contract sets another price.
  • A live session of 90 seconds costs 3.75 cents for its time. A backend assistant adds the cost of its model tokens and of its hosted tools, such as web search.
  • A phone call that is connected for 61 seconds counts as two started minutes, so it costs 20 cents.
  • GET /v1/live/sessions/{session_id}/charge returns the charge of one live session. GET /v1/call-charges lists what each call cost.
  • Resia refuses a new live session with 402 when your balance is $0.00 or less.

See Billing for balances and charges.

Start with the Live API

  1. Complete Get access to get an API key.
  2. Read Live API for access, cost, and limits.
  3. Open a session with Connect a live session.
  4. Handle audio, transcripts, and errors with Session events.
  5. Read sessions, charges, recordings, and voices with Session records and voices.

To move a GPT-Live-1 client to Fullplex, see Move from GPT-Live-1 to Fullplex.

To use Fullplex on phone calls instead, start with the Quickstart, then set the fields in Fullplex on phone calls.

API reference

WebSocket /v1/live/sessions · Live (Fullplex) · Call Agents