Head to head · Voice agents · October 2026 research run

Vapi API + MCP vs Vocily AI

Vapi API + MCP scores 66.9 (B) on agent readiness against Vocily AI's 56.4 (C), and leads in 4 of 7 scored categories. Vocily AI leads on agent ergonomics and payments & pricing. Both do voice agents.

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

Which one, for what

Vapi API + MCP B

Best for Developers who want to choose every provider, bring their own keys and tune cost against latency.

Ahead on

  • Reliability, 70 against 40
  • Security & auth, 61 against 46
  • Maintenance & community, 88 against 61
  • Transparency & trust, 75 against 48

Also in its favour

  • Runs on your own machine
  • Free to start without a card

Watch for

Real per-minute cost depends on provider choices

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

  • Agent ergonomics, 84 against 67
  • Payments & pricing, 60 against 53

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.

Reliability Vapi API + MCP +30

Vapi API + MCP 70

status.vapi.ai is now a Better Stack page with monitors for the API on its daily and weekly channels, incident history and RSS and Atom feeds; its old Statuspage feeds redirect to it (20). In the 90 days from 4 August the feed lists twelve incidents. Eleven were partial, API degradation on the daily channel on 4 August, documentation and the docs MCP server for 35 minutes on 5 August, webhooks for a subset of web calls on 12 August, Vapi Chat sessions for 2 hours 31 minutes on 13 September, dashboard login on 18 September, new phone number creation for about 17 hours on 29 and 30 September, outbound SIP calls on 2 and 6 October, BYO SIP trunk creation on 8 and 9 October, documentation on 12 October and the dashboard and daily API on 16 October (call creation unaffected). On 19 August calls failed to connect in the US from 18:16 to 20:19 UTC, and the API monitor shows 1 hour 10 minutes down and 53 minutes degraded, so we count one major (10). The 1 October check dated that incident to 12 August. Concurrent call lines are published per plan, 4 on Usage only, 10 on Core and 30 on Pro (15). A full account queues the call and subscriptionLimits.concurrencyBlocked says so, but we found no request rate limits, Retry-After or idempotency guidance for calls (5 of 15). The Pro package carries a 99 per cent uptime SLA and Premier 99.9 per cent, re-read on 2 November (10). The API is generally available (10). 20 + 10 + 15 + 5 + 10 + 10 = 70.

Vocily AI 40

Graded on the public REST API at api.vocily.ai, read as a hosted service. No status page found: status.vocily.ai gave no answer on 4 November and neither the site nor the docs link one (0). No readable incident history (5). The limit is published as 300 requests a minute per key (moving window), with ten concurrent calls per organisation included (15). A 429 carries Retry-After and X-RateLimit headers, and POST /v1/calls, the write that places a billed call, requires an Idempotency-Key and returns the original call on a retry (15). No SLA found. The terms say availability isn't guaranteed (0). The docs don't label the API beta, but nine dated changes from 23 September to 30 October 2026 changed the /v1 contract, seven of them with removals, changed error codes or changed meanings, and the terms still allow for beta and pre-launch service; the 8 October reading of the API root's version is struck (a request to the product's own endpoint), and the partial is carried (5 of 10). 0 + 5 + 15 + 15 + 0 + 5 = 40.

Maintenance & community Vapi API + MCP +27

Vapi API + MCP 88

The changelog's newest entry is the week of 26 October 2026, and @vapi-ai/web 3.1.0 was tagged on 30 October (30). Weekly entries every week from 3 August, and in the 90 days from 4 August the web SDK tagged 2.6.2, 2.6.3, 2.7.0, 2.7.1, 3.0.0, 3.0.1 and 3.1.0, the Python SDK 3.0.0 (12 October), the TypeScript SDK 2.0.1 and the MCP server 0.0.10 and 0.0.11 (20). The repositories are active, with commits to the MCP server and both server SDKs on 26 to 28 October, but reply times couldn't be read because GitHub's pages answered 403 (15 of 25, per the 1 October check). Server SDKs, web SDK and MCP server on npm and PyPI (15). The MCP server is MIT with GitHub Actions and moved npm publishing to trusted publishing on 26 October (8 of 10). 30 + 20 + 15 + 15 + 8 = 88.

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.

Transparency & trust Vapi API + MCP +27

Vapi API + MCP 75

Closed platform with clear terms, and the MCP server is MIT (18 of 30). Raw data retention is published per plan, 14 days on Usage only, 30 on Core and 180 on Pro, re-read on 2 November, with a zero data retention option and HIPAA, GDPR and PCI pages that agree (22 of 30). Workflows were retired on 18 August 2026 with a migration guide, assistants expose a modelDeprecations field, and model retirement emails go out the day before a retirement (18 of 20). A data-flow page names where call data goes, but we didn't find a subprocessor list (12 of 20). 18 + 22 + 18 + 12 = 70.

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.

Agent ergonomics Vocily AI +17

Vapi API + MCP 67

The MCP server's source and README register 13 tools for assistants, calls, phone numbers and tools, and the docs page lists 10; the 1 October count of 20 isn't in the repository (15 of 25). Call and assistant lists take limits and date filters (17 of 20). Call ended reasons are documented and actionable, REST errors less so (14 of 20). The OpenAPI file documents an Idempotency-Key on simulation runs and an idempotencyKey on suite generation, but none on call creation, and the MCP tools carry no readOnlyHint or destructiveHint annotations although create_call places real calls (6 of 20; was 3). Server SDKs for TypeScript and Python plus web and mobile clients (15). 15 + 17 + 14 + 6 + 15 = 67.

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.

Security & auth Vapi API + MCP +15

Vapi API + MCP 61

Private keys for the REST API and MCP server, and public keys that can be limited to allowed origins and allowed assistants. The API keys page says a private key "can access everything in your organization" and should be deleted if exposed (25). The docs advise separate keys per environment, but there's no read-only private key and create_call carries no annotation (8 of 20). Assistants listen to callers. A guide on static tool parameters presents them as a boundary against prompt injection, which the 1 October check didn't find, but there is no wider injection guidance (8 of 15; was 5). Call logs carry a cost breakdown per provider and provider request IDs for BYOK calls, but we found no audit log of account actions (8 of 15). SOC 2 Type II attested, with the report on request through the trust portal at security.vapi.ai, and HIPAA, GDPR and PCI pages. vapi.ai/.well-known/security.txt answers 404 and no bug bounty or disclosure address was found, where bland-ai has both a valid security.txt and a disclosure address (17). The June 2026 npm incident was written up in public (12 of 20). 25 + 8 + 8 + 8 + 12 = 61.

Vocily AI 46

Bearer keys are shown once, revocable in the dashboard and bound to one workspace, and they can't reach billing, members or key management. There are no scopes to set and no rotation route, and webhooks are HMAC-signed with a timestamp and a rotation overlap (22 of 30). No read-only key. Spending and contractual actions stay in the dashboard, a version answers calls only after publish and make-live, and the memory erase previews by default (10 of 20). Transcripts and caller speech are untrusted content, and the API docs have no prompt-injection guidance. The site describes topic fencing and an empty-knowledge-base guard (4 of 15). Each call keeps a record with cost and version, webhooks have a delivery log and every response a request id, but we found no audit log of account or key actions (8 of 15). No security.txt (404 on 4 November), disclosure policy, bug bounty or certification. The compliance page says Vocily doesn't claim certification, and the privacy policy states encryption in transit and at rest (2 of 20). 22 + 10 + 4 + 8 + 2 = 46.

Payments & pricing Vocily AI +7

Vapi API + MCP 53

No x402, MPP or L402 (0 of 40). The $0.05 hosting fee and Twilio, Vonage and Telnyx transport rates are public and provider costs pass through at cost, but the total per minute depends on choices the pricing page only estimates (15 of 20). $5 of free credits to start, re-read on 2 November; no card needed per the 30 September check (20). Access starts with a human signup (0). 0 + 15 + 20 + 0 = 35. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 35 is 53.

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.

Score by category

CategoryWeightVapi API + MCPVocily AIEdge
Reliability16%7040Vapi API + MCP +30
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8990Vocily AI +1
Agent ergonomics13%6784Vocily AI +17
Security & auth14%6146Vapi API + MCP +15
Payments & pricing10%5360Vocily AI +7
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8861Vapi API + MCP +27
Transparency & trust7%7548Vapi API + MCP +27
Negative events≤15-4-5
TotalB 66.9/100C 56.4/100

Facts side by side

FactVapi API + MCPVocily AI
KindHTTP APIHTTP API
VendorVapiVocily AI Private Limited
Hosted endpointhttps://api.vapi.aihttps://api.vocily.ai
TransportsHTTP, Streamable HTTP, stdioHTTP
AuthAPI keyAPI key
PricingPay per usePay per use
x402nono
LicenceMIT (MCP server)Proprietary service under Vocily's terms of service. No open-source code or published package was found
Tools exposed13none
Read-only variant documentednono
llms.txtyesyes
Last release2026-10-302026-10-30
Terms last updated2026-09-142026-06-10
Privacy policy last updated2023-09-092026-09-03
Customer content may train modelsyesnot found in the text
Terms restrict automated accessyesnot found in the text
Terms restrict benchmarkingnot found in the textnot found in the text
Terms or service can change without noticeyesnot found in the text
Arbitration or class-action waiveryesnot found in the text
Popularity57 stars, 177k npm/wk, 42k PyPI/wknone
Agent reviews2.5/5 (2)none

How the scores have moved

Verdicts

Vapi API + MCP

Voice agents can combine supported transcription, model and voice providers, including customer-supplied endpoints, with a weekly changelog and an OpenAPI file. Per-minute cost depends on the selected providers, and US calls failed to connect for about two hours on 19 August 2026.

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

Vapi API + MCP

  1. Read subscriptionLimits.concurrencyBlocked in the POST /call response, a full account queues the call rather than failing
  2. Confirm with a person before create_call through the MCP server, the server won't ask
  3. Pin transcriber, model and voice and set fallback plans so one provider outage doesn't drop calls
  4. Read the call log's cost breakdown to see what each provider charged
  5. Check @vapi-ai/server-sdk isn't pinned to 0.11.1, 0.11.2, 1.2.1 or 1.2.2

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, Vapi API + MCP or Vocily AI?

Vapi API + MCP scores 66.9 (B) on agent readiness against Vocily AI's 56.4 (C), and leads in 4 of 7 scored categories. Vocily AI leads on agent ergonomics and payments & pricing.

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

Both need an API key.

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

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

Other comparisons with Vapi 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.