The argument in one line.
OpenAI's GPT Live-1 speech-to-speech model removes the stitched speech-to-text-to-speech pipeline that made older voice agents sound robotic, and an AI coding agent can now wire it to a live phone number without writing code.
Read if. Skip if.
- Someone building or reselling AI phone receptionists who wants to know whether speech-to-speech finally beats a stitched speech-to-text pipeline.
- A non-technical builder who wants to see an AI coding agent wire a voice stack together without writing code.
- Anyone evaluating LiveKit, Telnyx, or GPT Live-1 as pieces of a voice-agent stack and wants to see them connected live.
- You need a production-ready receptionist script today. This is a fast proof-of-concept, not a hardened call-flow build.
- You want a deep technical explanation of the GPT Live-1 API itself rather than a click-through setup guide.
The full version, fast.
OpenAI's GPT Live-1 is a true speech-to-speech model, meaning it listens to raw audio instead of a transcript, so it catches pauses, laughs, and tone the way a stitched-together speech-to-text-to-speech stack never could, and it now runs reliably enough on a real phone number to replace it. The walkthrough uses Codex, OpenAI's coding agent, to connect GPT Live-1 to LiveKit (which bridges the model to a phone line) and Telnyx (which provides the number), all through plain-language prompts instead of manual code. The result is a working AI receptionist that takes a live call, and a second prompt adds a tool call so the agent can look up a real-time gold price mid-conversation, proving the stack can do more than talk.
Chat with this breakdown — free.
Sign in and you get 23 free chat messages on us — ask for the hook, quote a framework, find the exact transcript moment, generate a markdown action plan. Bring your own key when you want unlimited.
Create a free account →Where the time goes.

01 · What's New? (Demo)
Plays a call built on GPT Live-1 back to back with an older three-model voice-agent setup to show the difference in latency and tone.

02 · What I'm Covering
States the plan: build a receptionist voice agent on a real phone number using Codex, LiveKit, and the new GPT Live-1 model, no coding required.

03 · Codex Setup
Points to OpenAI's Codex desktop app as the tool that will build the entire system from prompts, and covers its free and paid tiers.

04 · LiveKit Setup
Introduces LiveKit as the platform that connects the voice model to a phone number, explains the free vs. cloud tiers, and recommends cloud so the agent stays reachable when the computer is off.

05 · Telnyx Phone Number Setup
Picks Telnyx as the phone number provider for non-US numbers, noting LiveKit itself can sell US numbers directly.

06 · Prompting Codex
Opens the Codex desktop app, creates a project folder, and dictates a single voice prompt describing a plumbing-company receptionist built on LiveKit and GPT Live-1.

07 · Building the Voice Agent
Watches Codex research LiveKit's docs and API, generate LiveKit API keys, and wire the OpenAI key into the project while narrating each authentication step.

08 · Connecting Telnyx to Codex
Creates a Telnyx account, buys a number, generates a Telnyx API key, and hands it to Codex so it can finish linking the phone number to the LiveKit agent.

09 · Live Call Test
Calls the finished agent live: it introduces itself as a plumbing company's AI receptionist and works through a leaking-shower-head scenario that escalates into a flooding emergency.

10 · Results & Refinement Notes
Reacts to the call, noting the agent correctly told the flooded caller to move to safety and call emergency services, and flags that its 'demo agent' framing would need removing for real use.

11 · Adding Tool Calls
Dictates a second prompt telling Codex to add a function call that hits a public API for the live gold price and reads the result back mid-conversation.

12 · Live Test: Function Call
Calls the agent again and asks for the live gold price; it triggers the new tool call and reads back a real, timestamped quote.

13 · Final Thoughts
Wraps with a call to subscribe and points to a companion video building websites with GPT-6 Astra.
Lines worth screenshotting.
- OpenAI's GPT Live-1 is a true speech-to-speech model: it listens directly to audio instead of reading a transcript, so it reacts to laughs, pauses, and tone like a real person would.
- Older voice agents stitch together three separate models (speech-to-text, a text model, text-to-speech), which adds latency and gives every reply a robotic quality.
- Speech-to-speech models have existed for a while, but they rarely held up over a real phone line until now, where latency and dropped calls finally stopped being a problem.
- An AI coding agent can build and deploy a full voice-agent stack, connect a phone number, and add live tool calls from plain-language prompts, with no manual coding required.
- LiveKit is the same infrastructure OpenAI uses to run ChatGPT's own Advanced Voice Mode, so building on it puts a hobbyist project on the identical stack as OpenAI's own production voice product.
- LiveKit's free tier covers one agent and one connected phone number, enough to build and test an entire voice-agent stack before paying anything.
- A phone number from a telephony provider like Telnyx costs about a dollar a month, and test calls run a couple of cents each, so a full working demo costs under five dollars to build.
- Tool calls turn a voice agent from a conversation into a system: adding a live gold-price lookup took one follow-up prompt and worked on the very next call.
- The agent handled an escalating flood scenario mid-demo by telling the caller to move away from the danger and contact emergency services, showing basic safety reasoning built into the base response.
- Self-hosting a voice-agent platform is free but only runs while the host computer stays on, which is why a cloud tier is the practical choice for an agent meant to answer calls at 2 a.m.
- Naming a specific tool's CLI in a prompt, rather than just the product name, is what gets an AI coding agent to install the right tooling instead of guessing.
- A demo AI receptionist still needs a human fallback: the system in the video introduced itself as a demo agent and had limits it couldn't work around yet.
Voice Agents Now Sound Human And Ship Fast
A true speech-to-speech model removes the stitched pipeline that made older voice agents sound robotic, and a coding agent can now assemble the whole phone-answering stack from plain prompts.
- A true speech-to-speech model reacts to tone, pauses, and laughter because it processes raw audio, not a transcript, which is why it sounds distinctly less robotic than older voice agents.
- Stitching together speech-to-text, a language model, and text-to-speech adds latency at every hop, and that compounding delay is what makes older voice agents feel stilted on a live call.
- A phone-based AI receptionist is built from three separate pieces, the voice model, a real-time routing platform, and a phone number provider, and each can be swapped independently.
- A coding agent can build and deploy a full technical system from spoken or typed instructions, which means fluency with prompting matters more than fluency with any one dashboard.
- Free tiers of coding-agent tools come with usage caps, so budget for an eventual upgrade if a build session runs long.
- Free tiers of infrastructure platforms are often enough to build and fully test a working prototype before any money changes hands.
- Self-hosted infrastructure is free but only available while the host machine stays powered on, so anything meant to be reachable around the clock belongs on a cloud tier instead.
- Choosing infrastructure that a major AI lab already runs its own production product on is a reasonable way to bet on reliability without doing the vetting yourself.
- International phone numbers and US numbers can come from different providers, and picking the wrong one adds an unnecessary extra signup step.
- A working phone number for a voice-agent prototype costs about a dollar a month, so hardware cost is negligible next to the model and infrastructure choices.
- Naming the exact tool by its formal name, such as a CLI rather than just the product name, in a prompt to a coding agent gets more reliable setup behavior than a vague reference.
- A single, specific prompt describing the use case, the stack, and the integrations needed is enough to kick off an entire multi-service build.
- A coding agent can read a platform's own documentation live and translate it into working setup steps, which removes the need to manually read API docs.
- Sensitive credentials like API keys should be pasted into a secrets file the agent points you to, not directly into a chat window, so they never pass through the model.
- Connecting a third-party service to an AI-built system is usually just generating an API key and handing it to the coding agent, no manual integration code required.
- Adding a small balance to a telephony account before testing avoids a failed call breaking the flow of a build session.
- Testing a new voice agent with an escalating, high-stakes scenario, not just a scripted happy path, is what reveals whether it can actually reason, not just recite.
- A convincing voice agent still needs a verified safety response for emergencies, since callers will occasionally test edge cases like this by accident.
- A first working build will carry leftover scaffolding, like a 'this is a demo agent' disclaimer, that needs a follow-up prompt to remove before it's presentable.
- Conversational refinement is an ongoing pass, not a one-shot outcome; plan for a second and third prompt round after the first working version.
- A voice agent that can only talk back is not useful for real business tasks; tool calls are what turn conversation into action.
- Adding a new capability to an already-working voice agent is a single follow-up prompt, not a rebuild, when the underlying agent was built by a coding agent in the first place.
- Verifying a new tool call with a real, checkable answer, like a live price with a timestamp, is a fast way to confirm the integration is pulling live data and not a cached or hallucinated value.
Terms worth knowing.
- Speech-to-speech (S2S)
- A model architecture that processes and generates raw audio directly, without converting speech to text and back, so it preserves tone, pauses, and emotion that a text-based pipeline loses.
- LiveKit
- An open-source real-time voice and video infrastructure platform that connects an AI model to a phone line or app, either self-hosted for free or run on a paid cloud tier.
- Telnyx
- A telecom provider used to buy and manage phone numbers and route calls into a voice-agent platform.
- Codex
- OpenAI's coding agent, used here to write and deploy an entire voice-agent stack from plain-language instructions instead of manual code.
- Tool call
- A function a voice agent can trigger mid-conversation to pull outside data, such as a live price or a calendar slot, instead of only generating spoken replies.
Things they pointed at.
Lines you could clip.
“this right here is an AGI moment for voice AI”
“the model itself is actually listening to your voice instead of reading a transcript”
“please move everyone away from the water and stairs and contact local emergency services on 000 if there's any immediate danger”
“the latest spot quote from GoldAPI is $4,314.50 per troy ounce, updated about 30 seconds ago”
Word for word.
Don't just watch it. Burn it in.
See every word as it's spoken — crank it to 2× and still catch all of it. The same dual-channel trick behind Amazon's Kindle + Audible.
The bait, then the rug-pull.
The video opens mid-call: a synthetic voice is already negotiating an accounting quote before anyone explains what's happening. That's the pitch. OpenAI's new GPT Live-1 sounds close enough to human that the demo needs no introduction before it makes its own case.
Named ideas worth stealing.
The old voice-agent stack (3 stitched models)
- Speech to text
- AI text model
- Text to speech
The legacy pattern for voice agents before speech-to-speech: transcribe the caller's audio, generate a text reply, then synthesize speech from that text. Each hop adds latency and strips out tone, which is why these agents sound robotic.
How they asked for the click.
“90% of you watching right now are not subscribed to the channel at all”
Delivered as a mid-video pattern interrupt inside the build montage rather than a scripted outro ask, paired with an on-screen SUBSCRIBE lower-third.



































































