Compare Lab
OpenAI Realtime API vs Synthflow
OpenAI Realtime API is positioned as speech-to-speech API for developers implementing their own voice application. Synthflow is positioned as a visual voice-agent workflow platform sold through scoped deployments and partner deliv
OpenAI Realtime API is positioned as speech-to-speech API for developers implementing their own voice application. Synthflow is positioned as a visual voice-agent workflow platform sold through scoped deployments and partner delivery. Start by deciding who owns the missing layers, then inspect the documented differences below.
Developer Frameworks and Full Platforms are different product categories. An underlying engine or framework is not a complete substitute for a deployed agent workflow.
10 jointly documented catalog fields. This measures evidence coverage, not equivalent quality or an overall winner.
Test opening hours, booking conflicts and an unanswered transfer.
Start where the records differ.
Values and evidence states are compared together. Shared facts follow the differences; Unknown never means No.
| Decision point | OpenAI Realtime API | Synthflow |
|---|---|---|
| Billing modelDifferent records | component-stack | custom-sales-led |
| Billing unitDifferent records | 1 million text/audio/image tokens; transcription separately metered | Contract minimum per year; call seconds aggregate to minutes; five AI chat messages count as one usage minute |
| Bring your modelDifferent records | Unknown | Yes |
| Warm transferDifferent records | Unknown | Yes |
| HIPAA pathDifferent records | Unknown | Yes |
| WebhooksDifferent records | YesUnknown | YesAPI / webhook |
Your requirements & next steps
Your requirements
Ready-made / AI receptionist · Strict evidence mode
No personal requirements yet. Add criteria in Advanced Filter to prioritize this comparison.
Realtime model tokens plus input transcription, tools and carrier/hosting; not GPT-Live session-minute billing.
Sales-ledcontract;call usage metered but exact unitrates and allowances negotiated.
Cached audio/text and image inputs have separate rates. Rate is not per-minute.
Starting commitment; complete contract cost remains unknown.
Model scope fixed to GPT-Realtime-2, not all voice models.
Rates,allowances andsimulationbilling come fromaccountagreement.
Published Realtime token rates do not establish these account/contract terms. GPT-Live duration billing and unrelated fine-tuning discounts must not be imported.
No complete current public contract rate and allowance schedule was established.
Published Realtime token rates do not establish these account/contract terms. GPT-Live duration billing and unrelated fine-tuning discounts must not be imported.
No complete current public contract rate and allowance schedule was established.
Published Realtime token rates do not establish these account/contract terms. GPT-Live duration billing and unrelated fine-tuning discounts must not be imported.
No complete current public contract rate and allowance schedule was established.
Repeated context, cache behavior and turn count affect token charges.
Reviewed current public offer; retain original billing scope and units.
Not yet researched against this buyer-critical field standard.
No complete current public contract rate and allowance schedule was established.
Full bill requires measured model/token/cache/tool/carrier usage; conversation minutes alone are insufficient.
No complete current public contract rate and allowance schedule was established.
Full bill requires measured model/token/cache/tool/carrier usage; conversation minutes alone are insufficient.
Research conclusion about cost completeness, not a vendor capability.
Anyone with this link can view the encoded decision criteria.
Vendor documentation establishes a claim. Public model benchmarks are separate context, not measurements of these platforms.
Open saved comparison ↗What to verify together.
OpenAI Realtime API
A token rate cannot be compared directly with a bundled call-minute price.
GPT-Realtime-2 audio input $32/M, audio output $64/M; text input $4/M, output $24/M · V3.3 evidence review · GPT-Realtime-2 input audio tokens only; output/audio/text/cache have different rates; not 2.1 rate evidence
Excluded / confirm: Complete cost cannot be established from this reference. Full bill requires measured model/token/cache/tool/carrier usage; conversation minutes alone are insufficient. · Input transcription, tool/backend calls, carrier and application infrastructure
Realtime model tokens plus input transcription, tools and carrier/hosting; not GPT-Live session-minute billing.
Synthflow
Do not apply old self-service rates to a new contract.
Enterprise contracts from $30,000 annually · V3.3 evidence review · Enterprise contract starting annual commitment; scoped quote required
Excluded / confirm: Complete cost cannot be established from this reference. No complete current public contract rate and allowance schedule was established. · Account agreement and carrier/add-on terms require quote
Sales-ledcontract;call usage metered but exact unitrates and allowances negotiated.
The evidence overlap.
Both records have documented values for Product type, Technical setup, Pricing model, OpenAI models, MCP tools, Function / tool calling, Interruption controls, Official product documentation, Checked within 30 days, Retained price snapshot. Matching availability does not measure behavior under your call conditions.
Run the same booking, tool failure and unsuccessful human-transfer cases. Record both outcomes and billable units before signing a deployment agreement.
Build a buyer-operated pilot →