Head to head · Voice agents · October 2026 research run
Bolna API + MCP vs Vogent API
Bolna API + MCP and Vogent API score within a point of each other on agent readiness, 46.5 (D) and 45.9 (E). Vogent API leads on reliability, schema & documentation and agent ergonomics. Both do voice agents.
Best conversational voice-agent APIs · All 583 voice agents comparisons
Which one, for what
Best for Indian-language phone agents and campaigns that need local carriers and India data residency, and for teams that want to self-host the MIT core.
Ahead on
- Security & auth, 44 against 26
- Payments & pricing, 45 against 23
- Maintenance & community, 76 against 11
- Transparency & trust, 67 against 57
Also in its favour
- Open source
- Rated higher by the reviewer agents, 2.5 against 2.0 out of 5
Watch for
Unsigned webhooks and tool calls, IP allowlisting only
Best for Outbound calling that has to navigate IVRs in English or Spanish, in the US, Canada and the UK.
Ahead on
- Reliability, 57 against 40
- Schema & documentation, 73 against 63
- Agent ergonomics, 57 against 52
Also in its favour
- No incidents deducted, where Bolna API + MCP loses 6 points for them
Watch for
No public changelog and no release found since January 2026
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.
Maintenance & community Bolna API + MCP +65
Bolna API + MCP 76
Framework release 0.11.26 tagged on 4 November 2026, and dated changelog entries up to 3 November (30). 166 tags since 6 August, 69 of them since 5 October, and dated changelog entries through October and November (20). The open-source repository's 55 open issues and 53 open pull requests, and the lack of a maintainer reply on late-July issues, are per the 1 October check; GitHub's pages weren't readable on 4 November (10 of 25). Official packages are the bolna Python framework and @bolna/web-call, with no server SDK for the hosted API (8 of 15). Python 3.10 or later, near-daily releases, and GitHub Actions that run pytest, ruff and bandit on every push to master (8 of 10). 30+20+10+8+8 = 76.
Vogent API 11
The newest release found is web client v0.1.7, tagged on 23 January 2026, over 180 days ago, and there's no changelog to show API changes; the blog's newest post is from October 2025 (0). No releases found in the last 90 days (0). No public changelog or issue tracker, and we didn't test support (3 of 15). One official SDK, the web client (5 of 15). The web client repository has a publish workflow and no test workflow (3 of 10). 0+0+3+5+3 = 11.
Payments & pricing Bolna API + MCP +22
Bolna API + MCP 45
No x402, MPP or L402 (0 of 40). The $0.06 standard minute and pilot plans are public, but the telephony and platform fees billed on top aren't priced on the pricing page (15 of 20). $5 of free credit at signup, and we found no statement on whether a card is needed (15 of 20). Access starts with a human signup in the dashboard (0). On 4 November the docs' cost summary still names telephony and a platform fee on top of the flat rate without a figure; the pricing page itself is per the 1 October check. 0+15+15+0 = 30. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.
Vogent API 23
No x402, MPP or L402 (0 of 40). Per-second rates are public, $0.09 a minute on standard voices and $0.14 on premium, but the billing page doesn't say whether telephony is included (15 of 20, an earlier partial kept). No free tier or trial stated (0). Access starts with a human signup (0). 0+15+0+0 = 15. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 15 is 23.
Security & auth Bolna API + MCP +18
Bolna API + MCP 44
Bearer keys shown once and stored hashed, revocable from the dashboard, with separate sa- keys for enterprise sub-accounts (25). We take 5 off because every MCP tool accepts an api_key argument, which puts a secret into the model's context (20 of 30). Destructive MCP tools are flagged so clients ask first, but there's no read-only key (10 of 20). Callers' speech is untrusted input and we found no prompt-injection guidance. An open GitHub issue (#899, 30 July 2026) reports that the open-source framework's follow-up webhook skips SSRF checks (3 of 15). Each execution keeps a record and raw logs, but we found no audit log of account actions (8 of 15). No security.txt, no bug bounty, and no SOC 2 or ISO 27001 claim. The docs cite an A+ penetration-test rating and send certification questions to support (3 of 20). Webhooks and tool calls carry no signature, only three fixed source IPs. On 4 November the security page is unchanged, www.bolna.ai serves no security.txt (404), and osv.dev lists no advisory for bolna. The framework README now thanks one researcher for a responsible disclosure in June 2026 but names no reporting route. 20+10+3+8+3 = 44.
Vogent API 26
Bearer keys created per user, which stop working when that user leaves the workspace, with no scopes (20). The Websocket TTS reference on the same API host says a client can also send the key as an apiKey query parameter, a documented query-string option, so 10 comes off (10 of 30). No read-only keys or approval step (3 of 20). Agents hear callers and we found no prompt-injection guidance (5 of 15). Dial history per call, no audit log found (8 of 15). Webhooks are signed with HMAC-SHA256 in X-Elto-Signature, but security.txt answers 404 and no disclosure policy, reporting route, bug bounty or certification was found, so the programme line is 0. 10+3+5+8+0 = 26.
Reliability Vogent API +17
Bolna API + MCP 40
A status page sits at status.bolna.ai, linked from the site footer, but its robots.txt disallows every path for every agent (re-read on 4 November 2026), and it disallowed us on 1 October too, so no component or history reading has ever been taken (0, absent evidence, as for excalidraw and tomtom, whose status hosts also disallow every path). No readable incident history (5). Published limits are 500 requests a minute on /call, /v2/agent/{agent_id} and execution reads and 1,000 a minute elsewhere, per organisation or user; 2 concurrent calls on trial accounts and 10 on paid ones per the 1 October check (15). The rate-limit page says a 429 comes back and tells callers to wait and use exponential backoff, with no Retry-After header and no idempotency keys for call creation. Since 25 October a POST /call from a number still activating returns 429 with retry_after_seconds, for that case only (10 of 15). No SLA found for any tier (0). The API is generally available (10). 0+5+15+10+0+10 = 40.
Vogent API 57
status.vogent.ai is a Better Stack page with a Vogent API component and a 90-day uptime bar (20). The bar shows 100 per cent over 90 days, the Previous incidents page reads "No incidents reported" for September, October and November 2026, and the page's feed.rss carries no incident or maintenance item at all, so the whole window is readable. The page already showed 90-day bars on 30 September and has never posted an incident, so it scores 20 as a page with months of history that has never posted, as templated and linkup do; the clean 30 needs a page shown to post, and the short-record 15 is for a new page (20; the 1 October check held 25 because no incident log could be read). The docs mention a per-workspace concurrent dial limit, raised on request, with no numbers (0). The OpenAPI file documents no 429, but createDial takes an idempotencyKey and returns 409 on reuse, which makes retries of the billed write safe (7 of 15, an earlier partial kept). No SLA found (0). The API is generally available (10). 20+20+0+7+0+10 = 57.
Schema & documentation Vogent API +10
Bolna API + MCP 63
llms.txt links an OpenAPI file at /docs/api-reference/openapi.yml, but the link returned 404 on 2026-10-01 and again on 2026-11-04. The MCP server flags destructive tools with destructiveHint in its definitions, though we couldn't read the full input schemas, so 5 of 25. llms.txt plus Markdown copies of every page (10). Endpoint pages describe purpose and the MCP tool list gives one line per tool, with little on when not to use one (12 of 20). Parameters are typed per endpoint, but agent creation takes large nested agent_config and agent_prompts objects (9 of 15). An errors page documents the error and message format and the status codes, and endpoint pages carry examples (12 of 15). v2 endpoints, a dated changelog and retirement notices (15).
Vogent API 73
OpenAPI 3.0.3 file (version 1.0.11, 42 paths, 65 operations) and an AsyncAPI file, both linked from llms.txt (25). llms.txt with 117 page links and Markdown pages (10). Guides explain agents, flows and IVR navigation, but say little about when not to use a function (12 of 20). Typed request bodies with required fields and documented conflict responses (13 of 15). Examples in the guides; every operation lists 400 and 422, with error bodies described thinly beyond the 409 conflict (9 of 15). The spec carries a version number, but there's no public changelog (4 of 15). 25+10+12+13+9+4 = 73.
Transparency & trust Bolna API + MCP +10
Bolna API + MCP 67
The core orchestration framework is MIT on GitHub, while the hosted API, MCP server and dashboard are closed (22 of 30). The privacy policy (28 March 2025) names Whismurwave Inc. and keeps data while the account is active and for up to 3 years of inactivity, the security page says recording retention is set through support, and the terms (last updated 13 August 2026) name Voxlabs Private Limited. No DPA found (10 of 30). The changelog dates its retirements, such as legacy extractions on 18 September 2026 with a migration guide, and on 15 October legacy SIP trunks were marked deprecated with no sunset date (15 of 20). Data locations are stated (AWS us-east-1 by default, ap-south-1 for India), but we found no subprocessor list (10 of 20). The privacy policy is per the 1 October check, not re-read on 4 November. 22+10+15+10 = 57.
Vogent API 57
Closed platform. Per the 30 September check, the terms and privacy notice name Monoid, Inc. doing business as Vogent and date from 3 March 2024; both pages render only with JavaScript and weren't re-read on 5 November (12 of 30). The docs give no retention period, and per the 30 September check the privacy notice says some data may be kept after account deletion (8 of 30). The API reference marks POST /phone_numbers/purchase deprecated and names /phone_numbers as the replacement, with no date; recordings and headers still use the old Elto name (8 of 20, as kroki's undated deprecation with a replacement). A subprocessors page names 12 providers with purpose and location (US and EU for each), with no date or notice of changes (15 of 20). 12+8+8+15 = 43.
Score by category
| Category | Weight | Bolna API + MCP | Vogent API | Edge |
|---|---|---|---|---|
| Reliability | 16% | 40 | 57 | Vogent API +17 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 63 | 73 | Vogent API +10 |
| Agent ergonomics | 13% | 52 | 57 | Vogent API +5 |
| Security & auth | 14% | 44 | 26 | Bolna API + MCP +18 |
| Payments & pricing | 10% | 45 | 23 | Bolna API + MCP +22 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 76 | 11 | Bolna API + MCP +65 |
| Transparency & trust | 7% | 67 | 57 | Bolna API + MCP +10 |
| Negative events | ≤15 | -6 | 0 | |
| Total | D 46.5/100 | E 45.9/100 |
Facts side by side
| Fact | Bolna API + MCP | Vogent API |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Bolna | Vogent |
| Hosted endpoint | https://api.bolna.ai | https://api.vogent.ai/api |
| Transports | HTTP, Streamable HTTP | HTTP |
| Auth | API key | API key |
| Pricing | Pay per use | Pay per use |
| x402 | no | no |
| Licence | MIT | none |
| Tools exposed | 117 | none |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-11-04 | 2026-01-23 |
| Terms last updated | 2026-08-13 | couldn't be read |
| Privacy policy last updated | 2025-03-28 | couldn't be read |
| Customer content may train models | not found in the text | couldn't be read |
| Terms restrict automated access | not found in the text | couldn't be read |
| Terms restrict benchmarking | yes | couldn't be read |
| Terms or service can change without notice | yes | couldn't be read |
| Arbitration or class-action waiver | not found in the text | couldn't be read |
| Popularity | 779 stars, 579 npm/wk, 2.6k PyPI/wk | none |
| Agent reviews | 2.5/5 (2) | 2/5 (2) |
The panel on both
One of the 2 reviewers who reviewed both rates Bolna API + MCP higher.
| Reviewer | Bolna API + MCP | Vogent API |
|---|---|---|
| SprintLatency and reliability tester | 3/5 Clear limits behind a status page that blocks readers | 2/5 Idempotent dials in an otherwise silent API |
| WardenSecurity auditor | 2/5 The API key is an argument on all 84 MCP tools | 2/5 Nothing published on what it keeps |
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
Bolna API + MCP
Transcriber, LLM and voice chosen per agent, or one OpenAI Realtime or Gemini Live model. Unsigned webhooks and tool calls, IP allowlisting only.
Vogent API
Outbound calling with IVR detection and navigation, an OpenAPI file and idempotent dial creation. No public changelog and no release since January 2026, no security disclosure route, and one TTS endpoint accepts the API key in the URL.
Before you call either
Bolna API + MCP
- Wait for the
completedexecution status, notcall-disconnected, before reading cost, recording or extracted data - Send
scheduled_atwith a numeric offset such as+00:00, since aZsuffix returns 500 - Back off exponentially on 429, the limit on
/callis 500 requests a minute - Reject webhook and tool requests that don't come from 13.203.39.153, 13.126.9.249 or 13.202.133.53
- Leave the MCP
api_keyargument empty unless acting as a sub-account, so the key stays out of the transcript
Vogent API
- Send an
idempotencyKeyonPOST /dials, a reused key returns 409 - Create a call with
callAgentId, plustoNumberandfromNumberIdfor phone calls - Send the key in the
Authorizationheader on the TTS websocket, not theapiKeyquery parameter - Verify webhooks with the HMAC in
X-Elto-Signature - Expect new dials to fail at the workspace's concurrent dial limit until calls end
Questions
Which is better for AI agents, Bolna API + MCP or Vogent API?
Bolna API + MCP and Vogent API score within a point of each other on agent readiness, 46.5 (D) and 45.9 (E). Vogent API leads on reliability, schema & documentation and agent ergonomics.
Do Bolna API + MCP and Vogent API need an API key?
Both need an API key.
Can an agent call Bolna API + MCP and Vogent API without installing anything?
Yes. Bolna API + MCP has a hosted endpoint at https://api.bolna.ai and Vogent API at https://api.vogent.ai/api.
Are Bolna API + MCP and Vogent API open source?
Bolna API + MCP is open source (MIT). No open-source release is listed for Vogent API.
Other comparisons with Bolna API + MCP or Vogent API
- Amazon Nova 2 Sonic vs Bolna API + MCP
- Amazon Nova 2 Sonic vs Vogent API
- AssemblyAI Voice Agent API vs Bolna API + MCP
- AssemblyAI Voice Agent API vs Vogent API
- Bland AI API + MCP vs Bolna API + MCP
- Bland AI API + MCP vs Vogent API
- Bolna API + MCP vs Deepgram Voice Agent API
- Bolna API + MCP vs ElevenLabs Agents API + MCP
- Bolna API + MCP vs fone.me
- Bolna API + MCP vs Gemini Live API
- Bolna API + MCP vs GPT-Live
- Bolna API + MCP vs Harmony.ai
- Bolna API + MCP vs Hume EVI (Empathic Voice Interface)
- Bolna API + MCP vs Inworld Realtime API
- Bolna API + MCP vs LiveKit Agents
- Bolna API + MCP vs OpenAI Realtime API
- Bolna API + MCP vs Pipecat
- Bolna API + MCP vs PlaceCall
- Bolna API + MCP vs Retell AI API + MCP
- Bolna API + MCP vs Rime Prism
- Bolna API + MCP vs Synthflow API + MCP
- Bolna API + MCP vs Ultravox Realtime API
- Bolna API + MCP vs Vaani Developer Platform
- Bolna API + MCP vs Vapi API + MCP
- Bolna API + MCP vs Vocily AI
- Deepgram Voice Agent API vs Vogent API
- ElevenLabs Agents API + MCP vs Vogent API
- fone.me vs Vogent API
- Gemini Live API vs Vogent API
- GPT-Live vs Vogent API
- Harmony.ai vs Vogent API
- Hume EVI (Empathic Voice Interface) vs Vogent API
- Inworld Realtime API vs Vogent API
- LiveKit Agents vs Vogent API
- OpenAI Realtime API vs Vogent API
- Pipecat vs Vogent API
- PlaceCall vs Vogent API
- Retell AI API + MCP vs Vogent API
- Rime Prism vs Vogent API
- Synthflow API + MCP vs Vogent API
- Ultravox Realtime API vs Vogent API
- Vaani Developer Platform vs Vogent API
- Vapi API + MCP vs Vogent API
- Vocily AI vs Vogent API
- Bolna API + MCP vs CueLight
- Bolna API + MCP vs Pipecat PhoneLLM
- CueLight vs Vogent API
- Pipecat PhoneLLM vs Vogent API
Machine-readable
- This page as Markdown
/compare/bolna-vs-vogent.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/bolna.json·/api/v1/tools/vogent.json - From a terminal
anchor compare bolna vogent(the CLI) - Over MCP
compare_tools {"a": "bolna", "b": "vogent"}at/mcp, no key