Skip to content

Conversational AI
built for people

Speech to text, any LLM and realtime text to speech behind a single API.

Every conversation card is a real session. Speech to speech replies start as fast as 204 ms after a turn ends.

InworldTime to first token –– tok/s
Typical providerTime to first token –– tok/s
Same model, same prompt, two providers.

Pick a use case and press Speak, then read the line aloud.

Try saying "My account was disabled at 8:30 this morning."

ListeningTranscribing

Ask your agent to add Inworld.

Paste it into your agent

What a voice conversation needs

Speech to speech docs ↗

People leave 0 to 300 ms between turns. Answer that fast, and your agent feels human.

204 msfrom the end of a turn to the reply
202 msto go quiet when someone talks over it
up to 90%cache hits on repeated prompts
up to 10×faster first token for the slowest 1%
speech to speech · turn closed to first audio · the 22 turns on this page
human turn gap, 0 to 300 ms0 ms100200300400500600700800fastest 219 ms · median 488 ms · slowest 708 msmedian 488 msthe median turn, hop by hopListening 0 msReasoning +159 msTalking +292 ms
These are the 22 turns recorded for the examples on this page. Replies started between 219 and 708 ms after the turn closed. In the median turn, the transcript arrived as the turn closed, the first token of the reply came 159 ms later and the first audio 292 ms after that.
0:16

“What are three easy dinners I could make tonight?” and then, while the agent was still answering, “Actually, just the quickest one.”

  0.34 s  speech_started  5.10 s  speech_stopped  5.10 s  transcription.completed  What are three easy dinners I could make tonight?  5.10 s  response.created  5.77 s  output_audio (first chunk)  8.03 s  speech_started  8.03 s  response.done  cancelled because the person cut in 11.51 s  speech_stopped 11.51 s  transcription.completed  Actually, just the quickest one. 11.51 s  response.created 11.83 s  output_audio (first chunk) 12.54 s  response.done  completed
The API cancelled the reply when the person cut in.
Turn 1

“Finally home. I think the interview went well.”

That is wonderful news, I am so proud of you.

Turn 2

“What should I do tonight to switch off?”

How about a long bath and your favorite movie?

Prompt vs. output tokens per requestconsumer turn vs. enterprise task
Consumer turnmedian prompt 13 to 36× the replyprompt: the whole conversation so farreplyEnterprise tasklong outputs (illustrative)promptgenerated code or document
Consumer turnmedian prompt 13 to 36× the reply
prompt: the whole conversation so farreply
Enterprise tasklong outputs (illustrative)
promptgenerated code or document
The bars show an example consumer turn of 3,500 tokens in and 200 out, and the enterprise row is illustrative.
These two turns come from one session, and the second reply was written with the first turn in its prompt.
One turn, several model callsconceptual
one user turn, left to right in timethe person is waiting: everything before the first tokenMemory readIntent checkModerationReply streamsfirst tokenMemory write
one user turn, left to right in time
Memory read
Intent check
Moderation
Reply streams
first token
Memory write
the person is waiting: everything before the first token
This diagram is conceptual and not to scale. Only the calls that run before the first token add to the wait, because the others run while the reply streams.
Consumer vs. enterprise inferencesix differences and the engineering for each
THE WORKLOADENTERPRISE AICONSUMER AIWHAT WE BUILTWho waits
a workflow; seconds are fine
a person, inside a 0 to 300 ms turn gap
Realtime decoding: first token 154 → 117 ms
Prompt shape
long outputs: code, documents
huge prompt, short reply: 13 to 36× more in than out
KV-aware routing: up to 90% cache hits on repeated prompts
Load
business hours, steady
evening peaks and launch-day spikes
Four tiers per request on the same weights
Failure
retry inside the workflow
an outage sends users to the next app
Five nines on half a billion requests
Models
closed frontier models, one vendor's policy
open models, the app's own fine-tunes and policy
Your weights on a dedicated deployment, with draft models trained on your requests
Who pays
per seat, by contract
per free user: 98% of US households pay nothing for AI
$0.07 per million input tokens (Gemma 4 26B)
THE WORKLOAD
Who waits
ENTERPRISE AI
a workflow; seconds are fine
CONSUMER AI
a person, inside a 0 to 300 ms turn gap
WHAT WE BUILT
Realtime decoding: first token 154 → 117 ms
Prompt shape
ENTERPRISE AI
long outputs: code, documents
CONSUMER AI
huge prompt, short reply: 13 to 36× more in than out
WHAT WE BUILT
KV-aware routing: up to 90% cache hits on repeated prompts
Load
ENTERPRISE AI
business hours, steady
CONSUMER AI
evening peaks and launch-day spikes
WHAT WE BUILT
Four tiers per request on the same weights
Failure
ENTERPRISE AI
retry inside the workflow
CONSUMER AI
an outage sends users to the next app
WHAT WE BUILT
Five nines on half a billion requests
Models
ENTERPRISE AI
closed frontier models, one vendor's policy
CONSUMER AI
open models, the app's own fine-tunes and policy
WHAT WE BUILT
Your weights on a dedicated deployment, with draft models trained on your requests
Who pays
ENTERPRISE AI
per seat, by contract
CONSUMER AI
per free user: 98% of US households pay nothing for AI
WHAT WE BUILT
$0.07 per million input tokens (Gemma 4 26B)
The enterprise column is our characterization.

Four parts, one session

Pricing ↗

Use each part on its own, or all together.
Speech to speech listens, reasons and talks on one connection.

Real recorded sessions.
Press play to hear the person, the agent, and how fast each reply started.

Ordering lunch in Spanish
0:16
Person

“Hola, ¿practicamos cómo pedir la comida?”

Heard as happy, 89% confidence
Agent

Sí, ¿qué desea comer hoy?

Person

“Quiero una ensalada y agua con gas, por favor.”

Heard as happy, 45% confidence
Agent

Muy bien, ¿desea algo de postre también?

The person's lines are generated with text to speech.

For teams building for people

Case studies →
LatitudeLatitude

Every story beat, read aloud.

97%of the voice in Latitude's Voyage, on Inworld
up to 5×faster than the closest alternative
StatusStatus

Cost per user, from dollars to cents a day.

95%lower cost
19 daysto a million users
LiveKitLiveKit

Inworld voices in LiveKit Agents, with no second API key.

TTS + STTin LiveKit Agents
One flagturns on Expressive mode

Start building

Conversational AI built for people runs on Inworld. Who are you building for?

Questions

Can one API handle speech to text, the LLM and text to speech for a voice agent?

Yes, one Inworld AI speech to speech connection listens, reasons and talks, so you don't need separate speech to text, LLM and text to speech vendors. You choose the LLM, and the connection runs over WebSocket or WebRTC. You don't manage the glue code between the parts, and you can swap any layer with a one-field change in the session configuration.

Which LLMs can I use with Inworld speech to speech?

Any model in Inworld Inference works with Inworld AI's speech to speech, including Gemma 4, DeepSeek V4 Flash and GLM 5.3 Flash. You switch models by changing one field in the session configuration, so you can trade reasoning depth for speed from one session to the next. Open models start from $0.07 per million input tokens, for Gemma 4 26B.

What does the voice profile do?

Inworld AI's Realtime STT-1 speech to text model returns a voice profile with every final transcript, giving the emotion, age, accent and vocal style it hears and a confidence score for each. In speech to speech, your app reads the voice profile from each transcription event and can pass it to the LLM as context, so the reply can change when someone sounds tired or upset.

How fast is Inworld speech to speech end to end?

Inworld AI's speech to speech API returned first audio as fast as 204 ms after the turn closed and 462 ms at the median. Part of that time is the LLM writing its first words and part is the voice starting to speak, so choosing a faster LLM shortens the wait when latency matters more than reasoning depth. How long the API waits before it closes a turn depends on the turn-detection eagerness you set.

Does Inworld speech to speech handle interruptions?

Yes, Inworld AI's speech to speech API stops talking when the user cuts in, because semantic VAD detects when the user starts speaking and cancels the in-flight response. The audio connection stays open, so the model can resume or pivot without closing the session. In one session, the response was cancelled 202 ms after the person started talking.

Is Inworld speech to speech compatible with the OpenAI Realtime API?

Yes, Inworld AI's speech to speech API follows the OpenAI Realtime protocol, with the same event names and message flow, so you can move an OpenAI Realtime client over with few changes. You change the endpoint and the key and keep your event handling. Inworld extensions such as voice profiles, backchannels and memory sit in an optional providerData field, so a client that ignores them still works.

How much does a conversation cost?

There is no separate session fee for Inworld AI's speech to speech, so a conversation costs the sum of its parts at your plan's rates. Realtime TTS-2 costs $12.50 per 1M characters on the Growth plan and $25 on demand. Realtime TTS-2 Flash costs $7 on Growth, $15 on demand and $5 on Enterprise, up to 16× lower than the $80 list price of Eleven v4. Realtime STT-1 costs $0.10 an hour on every paid plan ($0.15 on demand), and LLM tokens bill at the model's Inference rate.

Which consumer apps use conversational voice AI?

We built Inworld AI speech to speech for consumer apps where people talk to AI out loud, such as companions, language learning, fitness coaching, wellness and social apps. One connection listens, reasons and talks, and each part bills at its own rate with no separate session fee. Talkpal, a language learning app, cut its text to speech costs by 40% with Inworld.