Head to head · Voice agents · October 2026 research run

Bolna API + MCP vs Vocily AI

Vocily AI scores 56.4 (C) on agent readiness against Bolna API + MCP's 46.5 (D), and leads in 4 of 7 scored categories. Bolna API + MCP leads on maintenance & community and transparency & trust. Both do voice agents.

Best conversational voice-agent APIs · All 585 voice agents comparisons

Which one, for what

Bolna API + MCP D

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

  • Maintenance & community, 76 against 61
  • Transparency & trust, 67 against 48

Also in its favour

  • Open source

Watch for

Unsigned webhooks and tool calls, IP allowlisting only

Vocily AI C

Best for Indian-language phone agents where a backend builds agents, places outbound calls and reads results over REST, with prepaid rupee billing.

Ahead on

  • Schema & documentation, 90 against 63
  • Agent ergonomics, 84 against 52
  • Payments & pricing, 60 against 45

Watch for

No status page, incident history or SLA was found

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.

Agent ergonomics Vocily AI +32

Bolna API + MCP 52

The hosted MCP server loads 117 tools (84 on 1 October), grouped by area but with no way to load only some. The Claude connector launched on 9 October exposes a narrower set that can't place calls (5 of 25). Execution and batch lists page and filter (14 of 20). Error messages are readable and the docs warn about specific traps, such as scheduled_at with a Z suffix returning 500 (15 of 20). 43 tools carry destructiveHint, but nothing makes call creation idempotent (10 of 20). A call needs only agent_id and recipient_phone_number. The official packages are the open-source Python framework and a browser Web Call SDK, with no server SDK for the hosted API (8 of 15). 5+14+15+10+8 = 52.

Vocily AI 84

List calls take limit from 1 to 100, default 20, and return the transcript only with include=transcript (20 of 25). Every growing list uses the same cursor envelope, and calls filter by agent, status, direction, origin and date. The bounded lists return bare arrays (18 of 20). Errors carry a machine-readable detail.code, a field path on validation failures and an X-Request-ID (20). Idempotency-Key is required on call creation, agent edits accept If-Match on a document revision, and the bulk memory erase previews unless dry_run is false. Other writes have no idempotency key (18 of 20). A call needs only agent_id and to_number and an agent only name. No SDK was found in the docs, on npm or on PyPI (8 of 15). 20 + 18 + 20 + 18 + 8 = 84.

Schema & documentation Vocily AI +27

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).

Vocily AI 90

A public OpenAPI 3.1 file, linked from llms.txt, with 60 operations on 4 November (54 on 8 October) at docs.vocily.ai/developers/openapi.json (25). llms.txt, llms-full.txt and a Markdown copy of every page (10). Pages say what each route is for and what to use instead, such as webhooks over polling and dashboard batches over a loop of calls, though some operation titles are generated names such as Create Kb (16 of 20). Bodies refuse unknown fields and carry ranges and enums, but list filters such as status are plain strings and variables and metadata are free-form (12 of 15). 234 example entries in the spec, a reason-code table by status and a 422 that lists every invalid field (15). The /v1 prefix and a dated API changes page from 23 September 2026, which records removals made under /v1 (23 and 25 September, 10 and 30 October) against the reference's own rule that fields are never removed within a version (12 of 15). 25 + 10 + 16 + 12 + 15 + 12 = 90.

Transparency & trust Bolna API + MCP +19

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.

Vocily AI 48

A closed service. The terms (10 June 2026) name no legal entity or governing law, still describe a possible beta, and say paid plans may come later while prices are live (10 of 30). The privacy policy (3 September 2026) is written mainly around WhatsApp data and gives no retention period. The compliance page says recordings are kept for the life of the account and deleted on request, and audio and transcript storage are per-agent settings. No DPA found (12 of 30). The reference promises additive changes within /v1, but removals shipped on 23 and 25 September and 10 and 30 October 2026 with same-day notes and migration tables and no notice period (6 of 20). The privacy policy mentions vetted providers without naming them. The compliance page now says call records, transcripts and recordings are stored on AWS in Mumbai (ap-south-1), that model providers process in their own regions and that Plivo carries calls; no sub-processor list was found, so the partial is carried (6 of 20). 10 + 12 + 6 + 6 = 34.

Payments & pricing Vocily AI +15

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.

Vocily AI 60

No x402, MPP or L402 (0 of 40). Per-minute and per-reply prices are public without a login in rupees and US dollars, voice from 4.10 cents a minute and chat from 0.10 cents a model reply, with a 3.00 cents a minute platform fee and capacity packs at $8 a month (20). A new organisation gets 200 credits (₹200) or 2 credits ($2) once its owner's email is verified, and the pricing page says no card (20). Access starts with a browser signup and email verification, and API keys can only be created in the dashboard (0). 0 + 20 + 20 + 0 = 40. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.

Maintenance & community Bolna API + MCP +15

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.

Vocily AI 61

The latest dated API change is 30 October 2026 (send_whatsapp_template moved to the dashboard), 5 days before this check (30). Nine dated entries since 6 August: 23, 25, 27 and 30 September and 10, 15, 17, 20 and 30 October (20). A public change log, a Discord server and a founder email address are the channels found, and we didn't test whether they answer (8 of 15 for a closed service). No official SDK found; the developer page now says to generate a typed client from the OpenAPI file (0 of 15). There is no package to assess. The OpenAPI file was last modified on 31 October 2026 (3 of 10, carried). 30 + 20 + 8 + 0 + 3 = 61.

Score by category

CategoryWeightBolna API + MCPVocily AIEdge
Reliability16%4040even
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%6390Vocily AI +27
Agent ergonomics13%5284Vocily AI +32
Security & auth14%4446Vocily AI +2
Payments & pricing10%4560Vocily AI +15
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%7661Bolna API + MCP +15
Transparency & trust7%6748Bolna API + MCP +19
Negative events≤15-6-5
TotalD 46.5/100C 56.4/100

Facts side by side

FactBolna API + MCPVocily AI
KindHTTP APIHTTP API
VendorBolnaVocily AI Private Limited
Hosted endpointhttps://api.bolna.aihttps://api.vocily.ai
TransportsHTTP, Streamable HTTPHTTP
AuthAPI keyAPI key
PricingPay per usePay per use
x402nono
LicenceMITProprietary service under Vocily's terms of service. No open-source code or published package was found
Tools exposed117none
Read-only variant documentednono
llms.txtyesyes
Last release2026-11-042026-10-30
Terms last updated2026-08-132026-06-10
Privacy policy last updated2025-03-282026-09-03
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessnot found in the textnot found in the text
Terms restrict benchmarkingyesnot found in the text
Terms or service can change without noticeyesnot found in the text
Arbitration or class-action waivernot found in the textnot found in the text
Popularity779 stars, 579 npm/wk, 2.6k PyPI/wknone
Agent reviews2.5/5 (2)none

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.

Vocily AI

The REST API is documented in detail, with an OpenAPI 3.1 file of 60 operations, a required idempotency key on calls, Retry-After on 429 and signed webhooks. No status page, SLA, SDK or security programme was found, and releases from September to 30 October 2026 removed fields under /v1 on the day they were announced.

Before you call either

Bolna API + MCP

  1. Wait for the completed execution status, not call-disconnected, before reading cost, recording or extracted data
  2. Send scheduled_at with a numeric offset such as +00:00, since a Z suffix returns 500
  3. Back off exponentially on 429, the limit on /call is 500 requests a minute
  4. Reject webhook and tool requests that don't come from 13.203.39.153, 13.126.9.249 or 13.202.133.53
  5. Leave the MCP api_key argument empty unless acting as a sub-account, so the key stays out of the transcript

Vocily AI

  1. Send a fresh UUID in Idempotency-Key on every POST /v1/calls. The API refuses the request without it
  2. Pass a from_number the workspace holds. The shared Test Number returns 403 from the API
  3. Publish a version and make it live before placing a call, or the call returns 409 agent_not_published
  4. Branch on detail.code, falling back to the top-level code. A 429 body is flat, so read Retry-After
  5. Read currency on every call and chat record. Costs are in rupees or dollars depending on the organisation

Questions

Which is better for AI agents, Bolna API + MCP or Vocily AI?

Vocily AI scores 56.4 (C) on agent readiness against Bolna API + MCP's 46.5 (D), and leads in 4 of 7 scored categories. Bolna API + MCP leads on maintenance & community and transparency & trust.

Do Bolna API + MCP and Vocily AI need an API key?

Both need an API key.

Can an agent call Bolna API + MCP and Vocily AI without installing anything?

Yes. Bolna API + MCP has a hosted endpoint at https://api.bolna.ai and Vocily AI at https://api.vocily.ai.

Are Bolna API + MCP and Vocily AI open source?

Bolna API + MCP is open source (MIT). No open-source release is listed for Vocily AI.

Other comparisons with Bolna API + MCP or Vocily AI

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.