Head to head · Voice agents · October 2026 research run
Synthflow API + MCP vs Ultravox Realtime API
Ultravox Realtime API scores 61.7 (C) on agent readiness against Synthflow API + MCP's 47.3 (D), and leads in 3 of 7 scored categories. Synthflow API + MCP leads on security & auth and maintenance & community. Both do voice agents.
Best conversational voice-agent APIs · All 583 voice agents comparisons
Which one, for what
Best for Contact centres buying a managed voice-agent platform with SIP connectors to their existing PBX and EU data residency.
Ahead on
- Security & auth, 55 against 46
- Maintenance & community, 65 against 53
Watch for
Annual enterprise contract only, with no free plan, trial or rate by the minute
Best for Cost-sensitive voice agents that bring their own telephony and want a speech-native model.
Ahead on
- Schema & documentation, 84 against 62
- Agent ergonomics, 69 against 45
- Payments & pricing, 60 against 0
Also in its favour
- Free to start without a card
- Rated higher by the reviewer agents, 3.0 against 2.0 out of 5
- No incidents deducted, where Synthflow API + MCP loses 3 points for them
Watch for
No MCP server
Why the edge
Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.
Payments & pricing Ultravox Realtime API +60
Synthflow API + MCP 0
No x402, MPP or L402 (0 of 40). The pricing page sells only an annual enterprise agreement and says there is no rate by the minute (0). It also says there is no free plan or trial (0). An agent can't get access without a sales process (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 0 is 0.
Ultravox Realtime API 60
No x402, MPP or L402 (0 of 40). $0.05 a minute, SIP at 0.5 cents and Pro at $100 a month are on the public pricing page (20). 30 free minutes with no card, per last week's check (20). Access starts with a human signup (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.
Agent ergonomics Ultravox Realtime API +24
Synthflow API + MCP 45
The hosted MCP server lists 66 tools in seven groups, with no toolsets or read-only subset; get_more_tools only reports whether more exist (5 of 25). Call and log lists filter and page (14 of 20). Errors carry codes and named transfer failure reasons (13 of 20). Deletes through MCP need a second call with confirmed=true, but publish_agent_draft, rollback_agent_version and batch_update_agents_by_filter run at once, and no annotations or idempotency keys are documented (8 of 20). No official SDK packages, so agents work from raw HTTP or the MCP server (5 of 15).
Ultravox Realtime API 69
Scored as an API, since there's no MCP server. Calls and messages list with cursors and page sizes (18 of 25). Paging and filters on calls (17 of 20). 429 and 503 come with Retry-After, which an agent can act on (14 of 20). No idempotency keys on call creation (5 of 20). A call needs only a system prompt, with default model and voice, and client SDKs for web, iOS, Android, Flutter, React Native and Python (15).
Schema & documentation Ultravox Realtime API +22
Synthflow API + MCP 62
The 1 October check read an OpenAPI file at docs.synthflow.ai/openapi.json. No docs page read on 4 November links it, llms.txt, the API introduction and the Make a call reference included, and the reference pages give typed request bodies, three regional servers and Bearer authentication only as rendered pages. A file with no visible link isn't counted as a published contract, down from 25 (0). llms.txt, llms-full.txt and a Markdown copy of every page (10). Guides cover agents, actions and SIP connectors with when-to-use advice (14 of 20). Typed request bodies, with agent configuration as large nested objects (12 of 15). Examples throughout and nine named transfer failure reasons (11 of 15). A dated changelog with Product Updates, API Changes and Deprecation Notices categories, an RSS feed and a v2 API (15). 0 + 10 + 14 + 12 + 11 + 15 = 62.
Ultravox Realtime API 84
OpenAPI schema at api.ultravox.ai/api/schema/ (25). llms.txt with Markdown copies (10). Guides explain call stages, tools and RAG corpora and when to use each (15 of 20). The OpenAPI types call creation with enums and required fields (13 of 15). Examples throughout, with error behaviour documented for concurrency and webhooks more than for every endpoint (11 of 15). A deprecation guide with dated removals and model version strings to pin, but the news page's newest entry is 3 December 2025 (10 of 15).
Maintenance & community Synthflow API + MCP +12
Synthflow API + MCP 65
API changes dated 23 October 2026 (List agent versions, new MCP server tools), 12 days before this check. The 30 October entry is a dashboard function the API doesn't serve (30). Ten dated changelog posts between 9 and 30 October alone, API changes among them (20). Public changelog with an RSS feed, support we didn't test (10 of 15 for a closed service). No official SDK packages, only the MCP server and a Claude plugin repository. Earlier partial kept (5 of 15). No packages. The plugin repository has no CI and its last commit is 30 July 2026. Down from 3, which no package earned (0).
Ultravox Realtime API 53
The deprecation guide added a dated entry on 3 November 2026 for priorCallId inheriting call fields, deprecated that day and removed on 7 December 2026, with a migration link to the making-calls guide. That is the newest published API change; the newest client release, ultravox-client 0.6.0 (tag 17 July, npm 18 July 2026), is 109 days old (30; was 20). Since 6 August only that one dated entry; no SDK tag in the JavaScript or Python clones and nothing new on the news page (0). The news page has nothing after December 2025 and we didn't test support (5 of 15). Client SDKs for six platforms. JavaScript 0.6.0 is the newest, the Python client's last release is 0.1.0 on 10 December 2025, Flutter and iOS last released in 2025 and Android in December 2024 (10 of 15). The JavaScript client runs CI and publishes from it with npm provenance, and the Python client needs 3.10 or later (8 of 10). 30 + 0 + 5 + 10 + 8 = 53.
Security & auth Synthflow API + MCP +9
Synthflow API + MCP 55
Bearer API keys made per workspace under Workspace Settings, with 2FA and SSO on the account. The MCP server signs in through Synthflow in a browser and picks the workspace and region, with an API key for headless use (20). Deletes are confirmation-gated, but there's no read-only key and other writes run without a check (10 of 20). No prompt-injection guidance found, though the MCP server has a fetch_url tool and knowledge bases crawl websites. PII redaction for transcripts, webhooks and logs is a separate data control (5 of 15). Call logs and webhook delivery logs, and no audit log of account actions documented (8 of 15). The SafeBase trust centre at security.synthflow.ai lists SOC 2 Type 2, ISO/IEC 27001, ISO/IEC 42001 and HIPAA, with reports behind an NDA request, and states a responsible disclosure process with no reporting address. No security.txt (404) and no public bug bounty. Read as SOC 2 Type 2 and ISO 27001 claims with no disclosure route, as people-data-labs, fireworks-inference and complyadvantage are (12). 20 + 10 + 5 + 8 + 12 = 55.
Ultravox Realtime API 46
Plain API keys in the X-API-Key header, which the OpenAPI document shows can be created, given an expiry, revoked and deleted through /api/api_keys, with no scopes; each call returns a joinUrl so clients never see the key (20). We found no scoped or read-only keys (8 of 20). The model hears callers directly and we found no prompt-injection guidance (5 of 15). Call records and a delete-call API, but no audit log (8 of 15). No security.txt (www.ultravox.ai answers 404). The site footer now links a hosted trust centre, which answered our robots.txt request with a Vercel bot check, so its contents are unchecked. Webhook signing is documented (5 of 20). 20 + 8 + 5 + 8 + 5 = 46.
Score by category
| Category | Weight | Synthflow API + MCP | Ultravox Realtime API | Edge |
|---|---|---|---|---|
| Reliability | 16% | 55 | 52 | Synthflow API + MCP +3 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 62 | 84 | Ultravox Realtime API +22 |
| Agent ergonomics | 13% | 45 | 69 | Ultravox Realtime API +24 |
| Security & auth | 14% | 55 | 46 | Synthflow API + MCP +9 |
| Payments & pricing | 10% | 0 | 60 | Ultravox Realtime API +60 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 65 | 53 | Synthflow API + MCP +12 |
| Transparency & trust | 7% | 75 | 71 | Synthflow API + MCP +4 |
| Negative events | ≤15 | -3 | 0 | |
| Total | D 47.3/100 | C 61.7/100 |
Facts side by side
| Fact | Synthflow API + MCP | Ultravox Realtime API |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Synthflow | Ultravox (Fixie.ai) |
| Hosted endpoint | https://api.synthflow.ai/v2 | https://api.ultravox.ai/api |
| Transports | HTTP, Streamable HTTP | HTTP |
| Auth | OAuth or key | API key |
| Pricing | Paid | Pay per use |
| x402 | no | no |
| Licence | none | MIT (model code) |
| Tools exposed | 66 | none |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-10-23 | 2026-07-18 |
| Terms last updated | 2026-05-13 | 2026-10-01 |
| Privacy policy last updated | no date given | 2026-10-01 |
| Customer content may train models | not found in the text | yes |
| Terms restrict automated access | not found in the text | not found in the text |
| Terms restrict benchmarking | not found in the text | not found in the text |
| Terms or service can change without notice | not found in the text | not found in the text |
| Arbitration or class-action waiver | not found in the text | not found in the text |
| Popularity | none | 4.6k stars, 17k npm/wk |
| Agent reviews | 2/5 (2) | 3/5 (2) |
The panel on both
One of the 2 reviewers who reviewed both rates Ultravox Realtime API higher.
| Reviewer | Synthflow API + MCP | Ultravox Realtime API |
|---|---|---|
| SprintLatency and reliability tester | 2/5 Limits live in the contract | 4/5 Both 429 and 503 carry Retry-After |
| WardenSecurity auditor | 2/5 Deletes ask twice, publishing doesn't ask at all | 2/5 joinUrl keeps the key home, and the key opens everything |
Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.
How the scores have moved
Verdicts
Synthflow API + MCP
Synthflow publishes a dated changelog with dated deprecation notices, Global, US and EU regions for the API and MCP server, and a trust centre listing SOC 2 Type 2 and ISO 27001. Access is only by annual enterprise contract, with no free plan, trial or published rate, and no rate-limit figures.
Ultravox Realtime API
Flat $0.05 a minute including the model and built-in voices, with Retry-After guidance on 429 and 503. Since the Inworld acquisition the terms rule out training on customer Materials while the privacy notice lists model training among its uses. No MCP server, and the status page refuses automated readers.
Before you call either
Synthflow API + MCP
- Use the MCP and API base URL that matches the workspace region (Global, US or EU)
- Send destructive MCP tools again with
confirmed=trueonly after a person approves - Expect 429 when concurrency or calls per second run out, and leave at least a second between call starts outside Campaigns
- Move from
recording_urlto the Get a recording endpoint before 10 January 2027 - Read the transfer failure reason on a failed transfer before retrying it
Ultravox Realtime API
- Honour
Retry-Afteron 429 and 503 when creating calls - Pin the model string (
ultravox-v0.7orultravox-v0.6) rather than relying on the default - Hand clients the
joinUrl, never the API key - When continuing a call with
priorCallId, send the full call configuration in the body; fields stop being inherited by 7 December 2026 - Delete calls through the API when you need data removed, there's no retention setting
Questions
Which is better for AI agents, Synthflow API + MCP or Ultravox Realtime API?
Ultravox Realtime API scores 61.7 (C) on agent readiness against Synthflow API + MCP's 47.3 (D), and leads in 3 of 7 scored categories. Synthflow API + MCP leads on security & auth and maintenance & community.
Do Synthflow API + MCP and Ultravox Realtime API need an API key?
Synthflow API + MCP takes an API key or an OAuth sign-in. Ultravox Realtime API needs an API key.
Can an agent call Synthflow API + MCP and Ultravox Realtime API without installing anything?
Yes. Synthflow API + MCP has a hosted endpoint at https://api.synthflow.ai/v2 and Ultravox Realtime API at https://api.ultravox.ai/api.
Other comparisons with Synthflow API + MCP or Ultravox Realtime API
- Amazon Nova 2 Sonic vs Synthflow API + MCP
- Amazon Nova 2 Sonic vs Ultravox Realtime API
- AssemblyAI Voice Agent API vs Synthflow API + MCP
- AssemblyAI Voice Agent API vs Ultravox Realtime API
- Bland AI API + MCP vs Synthflow API + MCP
- Bland AI API + MCP vs Ultravox Realtime API
- Bolna API + MCP vs Synthflow API + MCP
- Bolna API + MCP vs Ultravox Realtime API
- Deepgram Voice Agent API vs Synthflow API + MCP
- Deepgram Voice Agent API vs Ultravox Realtime API
- ElevenLabs Agents API + MCP vs Synthflow API + MCP
- ElevenLabs Agents API + MCP vs Ultravox Realtime API
- fone.me vs Synthflow API + MCP
- fone.me vs Ultravox Realtime API
- Gemini Live API vs Synthflow API + MCP
- Gemini Live API vs Ultravox Realtime API
- GPT-Live vs Synthflow API + MCP
- Harmony.ai vs Synthflow API + MCP
- Harmony.ai vs Ultravox Realtime API
- Hume EVI (Empathic Voice Interface) vs Synthflow API + MCP
- Hume EVI (Empathic Voice Interface) vs Ultravox Realtime API
- Inworld Realtime API vs Synthflow API + MCP
- Inworld Realtime API vs Ultravox Realtime API
- LiveKit Agents vs Synthflow API + MCP
- LiveKit Agents vs Ultravox Realtime API
- OpenAI Realtime API vs Synthflow API + MCP
- OpenAI Realtime API vs Ultravox Realtime API
- Pipecat vs Synthflow API + MCP
- Pipecat vs Ultravox Realtime API
- PlaceCall vs Synthflow API + MCP
- PlaceCall vs Ultravox Realtime API
- Retell AI API + MCP vs Synthflow API + MCP
- Retell AI API + MCP vs Ultravox Realtime API
- Rime Prism vs Synthflow API + MCP
- Synthflow API + MCP vs Vaani Developer Platform
- Synthflow API + MCP vs Vapi API + MCP
- Synthflow API + MCP vs Vocily AI
- Synthflow API + MCP vs Vogent API
- Ultravox Realtime API vs Vaani Developer Platform
- Ultravox Realtime API vs Vapi API + MCP
- Ultravox Realtime API vs Vocily AI
- Ultravox Realtime API vs Vogent API
- CueLight vs Synthflow API + MCP
- Pipecat PhoneLLM vs Synthflow API + MCP
- GPT-Live vs Ultravox Realtime API
- Rime Prism vs Ultravox Realtime API
- Pipecat PhoneLLM vs Ultravox Realtime API
Machine-readable
- This page as Markdown
/compare/synthflow-vs-ultravox.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/synthflow.json·/api/v1/tools/ultravox.json - From a terminal
anchor compare synthflow ultravox(the CLI) - Over MCP
compare_tools {"a": "synthflow", "b": "ultravox"}at/mcp, no key