OpenAI launched GPT-Live-1 in the API on September 10, 2026. It is a voice model designed for full-duplex conversation: the user and assistant can listen and speak at the same time instead of waiting through rigid, turn-by-turn exchanges.
The practical change is larger than a more natural voice. GPT-Live-1 can keep the spoken interaction responsive while delegating deeper reasoning, retrieval, or tool use to a backend model. That separation gives developers a new way to build phone agents, voice-enabled apps, tutors, support systems, and hands-free business workflows.
Source note: This guide reflects OpenAI’s launch announcement and GPT-Live documentation available on September 10, 2026. Pricing, model access, supported voices, and API behavior can change; confirm the current documentation before estimating or deploying a production system.
GPT-Live-1 at a glance
GPT-Live-1 is the real-time conversational layer, not necessarily the only model in the system. OpenAI highlights these capabilities:
- full-duplex listening and speaking;
- improved interruption and pause handling;
- delegation to a backend reasoning model or agent harness;
- system-prompt control over tone, pace, and conversational style;
- stronger handling of background noise and silent thinking time;
- improved continuity during longer sessions;
- native transcripts and response text;
- keyword biasing and alphanumeric understanding;
- browser, server, and phone integration paths;
- broader voice choices across accents, dialects, and languages.
OpenAI says GPT-Live-1 is available in the API at $0.05 per minute for the front-end voice layer. Backend model and tool usage are separate charges. The price of a complete voice agent therefore depends on session duration, delegated work, retrieval, external APIs, telephony, storage, and monitoring—not only the headline per-minute rate.
What full-duplex voice changes
Many voice agents use a chained architecture:
- speech-to-text converts the caller’s audio;
- a language model produces an answer;
- text-to-speech turns the answer into audio;
- custom application logic decides when each stage should start or stop.
That design is understandable and still useful, but every handoff can add latency and lose conversational signals. Pauses, acknowledgements, interruptions, laughter, self-corrections, and background speech are difficult to coordinate when each stage sees only part of the interaction.
GPT-Live-1 is designed to reason over incoming and outgoing audio together. A user can interrupt, revise a request, or hesitate without forcing the application to treat every silence as the end of a turn. OpenAI reports a 30-percentage-point improvement over GPT-Realtime-2.1 on its Full Duplex Bench. That is OpenAI’s benchmark result, not an independent guarantee, so teams should test the exact accents, devices, noise conditions, and workflows their users will encounter.
The new voice-agent architecture
The most important implementation decision is the boundary between conversation and work.
GPT-Live-1 handles the interaction
The live layer manages speech, timing, interruptions, tone, and the immediate conversational context. It should acknowledge the user, ask concise clarifying questions, and continue naturally while longer work happens elsewhere.
A backend model handles deeper work
OpenAI’s documentation calls this delegation. GPT-Live-1 can send conversation context to a managed Responses API backend or to a client-controlled backend. The backend can search, reason, call tools, retrieve account information, or coordinate a workflow, then return the result to the voice layer.
This split lets a developer match the backend to the task. A lower-cost model may be enough for scheduling or order status, while a stronger reasoning model such as GPT-6 Astra may be appropriate for a complex support case. The voice layer remains consistent even when the backend route changes.
The application keeps control
The surrounding application still owns authentication, permissions, tool definitions, business rules, data access, logging, and escalation. A natural voice does not make an unsafe action safe. Any operation that changes an account, sends information, books something, or affects money should have explicit authorization and a recoverable audit trail.
WebRTC, WebSockets, or SIP?
OpenAI documents four main connection patterns.
| Connection | Best starting point | What to plan for |
|---|---|---|
| WebRTC | Browser and client-side voice experiences | HTTPS, microphone permission, media tracks, event channel, server-minted session credentials |
| WebSockets | Server-side audio applications | Streaming audio, connection recovery, buffering, and server capacity |
| Server-side controls | Backend access to an active session | Sideband events, policy enforcement, tool execution, and state synchronization |
| Telephony and SIP | Phone agents and contact-centre workflows | Call routing, carrier behavior, consent, recording rules, transfers, and human escalation |
For a first browser prototype, OpenAI recommends its WebRTC quickstart. The API key should remain on a trusted server; it should never be embedded in browser or mobile-app code. A successful session-start event is only the first check. Test that the user can hear the response, interruptions work, delegated results return, and the session closes cleanly with final usage recorded.
Pricing and total operating cost
The announced $0.05-per-minute price covers the GPT-Live-1 front-end voice layer. A ten-minute session would therefore start at $0.50 for that layer, before backend and infrastructure costs.
Budget separately for:
- the backend reasoning model;
- search, file retrieval, or other tool calls;
- telephony or media providers;
- data storage and transcripts;
- observability, evaluation, and alerting;
- human handoff and support operations;
- retries, abandoned calls, and long periods of silence.
Cost per successful outcome is a better metric than cost per minute. A cheaper session that fails and requires a second call may cost more than a slightly more capable route that resolves the request safely the first time.
Where GPT-Live-1 could be useful
Strong initial use cases have a clear conversational benefit and a bounded action space:
- appointment scheduling and reservation intake;
- order, delivery, and account-status questions;
- guided onboarding inside a mobile or web application;
- language practice and tutoring;
- field-service assistants used while the worker’s hands are occupied;
- museum, tourism, and accessibility experiences;
- support triage with a reliable handoff to a person.
The Canadian Tank Museum mobile audio guide is an example of how audio can make a physical visitor experience more accessible and engaging. A live conversational layer could extend that pattern, but only when content accuracy, connectivity, accessibility, and visitor privacy have been designed from the beginning.
Production risks that demos can hide
Interruptions are not always intent
Background conversation, a television, or another person near the microphone can look like an interruption. Test whether the system distinguishes a user’s correction from unrelated speech and whether it resumes gracefully after uncertainty.
Transcripts can be wrong
Names, confirmation numbers, addresses, and financial figures need read-back or structured confirmation. OpenAI notes strong alphanumeric understanding and keyword biasing, but high-consequence data still requires verification.
Delegated work can outlive the conversation
A backend tool may still be running when the user changes direction or ends the call. Define cancellation behavior, idempotency, timeouts, and what the voice layer says while work is pending.
A human escalation path is essential
The agent should recognize requests it cannot safely complete and transfer the user with context. A failed transfer, dropped call, or unavailable team needs a clear fallback rather than an endless conversational loop.
Privacy rules vary by context
Voice can contain biometric, health, financial, and personal information. Review consent, retention, recording, regional privacy, and vendor requirements before collecting production audio or transcripts.
A practical evaluation plan
Start with one narrow workflow and 25 to 50 representative conversations. Include quiet rooms, mobile networks, strong accents, interruptions, long pauses, background speech, corrections, and incomplete information.
Track:
- time to first useful response;
- interruption and pause errors;
- task completion rate;
- tool-call and backend accuracy;
- number of clarifying questions;
- human transfer rate and transfer quality;
- cost per completed outcome;
- privacy or policy failures;
- user-rated naturalness and trust.
Do not release based on a polished demo alone. Run scripted evaluations, adversarial cases, monitored pilots, and rollback tests before opening a voice agent to real customers.
How I can help build a voice product
I provide AI consulting and custom AI development for teams evaluating GPT-Live-1, designing delegation and tool boundaries, connecting business systems, and building measurable safety and quality checks.
I can also deliver the product layer through mobile app development, website development, SaaS product engineering, and workflow automation.
Book a free strategy call to scope a small voice-agent pilot around a real customer or operational workflow.
Official sources
Frequently asked questions
What is GPT-Live-1?
GPT-Live-1 is OpenAI's API model for natural full-duplex voice conversations. It can listen while speaking, handle interruptions, and delegate deeper reasoning or tool work to a separate backend model.
How much does GPT-Live-1 cost?
OpenAI announced a price of $0.05 per minute for the front-end voice layer. Backend model usage, tool calls, and supporting infrastructure are billed separately, so teams should calculate total session cost rather than voice cost alone.
Does GPT-Live-1 replace the backend AI model?
Not necessarily. OpenAI positions GPT-Live-1 as the conversational voice layer. It can delegate complex reasoning and actions to a backend model such as GPT-6 Astra, another OpenAI model, or a third-party model chosen by the developer.
Can GPT-Live-1 answer phone calls?
Yes. OpenAI documents telephony and SIP as supported integration paths and describes uses such as reservations and customer support. Production deployments still need call routing, consent, escalation, privacy, monitoring, and failure handling.
Which connection should developers use?
OpenAI recommends WebRTC for browser voice applications, WebSockets for server-side audio integrations, server-side controls for backend access to an existing session, and telephony or SIP for phone integrations.