Head to head · Phone calls · October 2026 research run

Exotel Voice API + MCP vs Voximplant

Voximplant scores 61 (C) on agent readiness against Exotel Voice API + MCP's 45.9 (E), and leads in every scored category. Both do phone calls.

Best phone calling and voice transport APIs for AI agents · All 105 calling comparisons

Which one, for what

Exotel Voice API + MCP E

Best for Voice agents calling Indian numbers that need local compliance and a hosted MCP.

Also in its favour

  • Free to start without a card
  • No incidents deducted, where Voximplant loses 3 points for them

Watch for

Per-minute rates and plan prices not published

Voximplant C

Best for Teams that want speech-to-speech models on the phone without running a media server, and are happy to write call logic in VoxEngine JavaScript.

Ahead on

  • Reliability, 85 against 60
  • Schema & documentation, 71 against 58
  • Agent ergonomics, 45 against 40
  • Security & auth, 60 against 49
  • Payments & pricing, 38 against 30
  • Maintenance & community, 75 against 5
  • Transparency & trust, 72 against 60

Also in its favour

  • Rated higher by the reviewer agents, 3.0 against 2.0 out of 5

Watch for

Scenarios are VoxEngine JavaScript with their own limits (16 MB memory, 1-second callbacks)

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 Voximplant +70

Exotel Voice API + MCP 5

The developer changelog's newest entry is still the docs upgrade of 16 February 2026, and the newest API entry is Gen AI APIs in January 2026, over 180 days ago (0). No dated entries in the last 90 days. The ExotelMCP reference repository took commits on 13 September and 23 to 24 October 2026 with no tag, version or changelog, which aren't releases (0). Support exists, and an outside pull request to the reference repository was merged on 14 September (5 of 15). No official server SDKs (0). No package to judge (0).

Voximplant 75

The Node.js client 5.2.0 and the Python client 2.13.0 were released on 5 November 2026, 6 days before 11 November (30). Since 13 August the Node.js client released 4.11.0 (26 August), 5.0.0 (7 October), 5.1.0 (26 October) and 5.2.0, and the Python client 2.10.0 (26 August), 2.11.0 (22 October), 2.12.0 (26 October) and 2.13.0, five release dates in all (20). No public changelog, and support exists (5 of 15). Official clients for the Management API in six languages, the Node.js and Python ones current (15). Package health not checked beyond the release tags (5 of 10, the earlier partial kept). 30 + 20 + 5 + 15 + 5 = 75.

Reliability Voximplant +25

Exotel Voice API + MCP 60

Statuspage at status.exotel.com with components and history (20). The history feed read on 10 November covers 16 September to 14 November and lists only scheduled maintenance, each announced with a window before it started, including the emergency maintenance in Delhi, Gujarat and Karnataka between 19 and 22 September. The 1 October reading of the same feed back to 1 August listed planned maintenance and no unplanned incidents. Announced maintenance with a stated window isn't an incident, so the 90 days from 12 August are clean (30). Trial accounts get reduced API limits, but no figures are published (0). No 429 or retry guidance found (0). No SLA found (0). The Voice API is generally available, and the MCP overview no longer carries a beta label (10).

Voximplant 85

Statuspage at status.voximplant.com with components and history (20). The history feed, read on 11 November, runs from 20 October. Every Platform incident in it is scoped to one region or carrier (Russia PSTN on 20 and 29 October and 5 and 9 November, US SIP for 43 minutes on 21 October, Kazakhstan PSTN on 22 October, Europe PSTN and SIP on 29 October), and Kit, website and announced maintenance entries are left out. The 13 August to 19 October part of the window wasn't re-read, so the line keeps its recorded minor-only award (20). Per the 30 September check, not re-read on 11 November, limits published with numbers, 50 call attempts, 10 unanswered calls and 3 active HTTP requests per session, 1,000 users per account (15). The StartScenarios method page says the method returns 429 Too Many Requests past 200 concurrent HTTP requests until the number of active requests is reduced, and the Management API error catalogue lists RATE_LIMIT_EXCEED (340) and RETRY_LATER (416, "Repeat after N seconds", a stated wait). No idempotency keys or safe-retry guidance found (10, the value backoff or a stated wait takes). A Service Level Agreement, effective 15 September 2023, sets 99.95% uptime with service credits (10). The platform is generally available (10). 20 + 20 + 15 + 10 + 10 + 10 = 85.

Schema & documentation Voximplant +13

Exotel Voice API + MCP 58

No OpenAPI spec for the Voice API found; a Swagger reference exists for the separate VoiceBot tools (0). developer.exotel.com now serves llms.txt (341 links) and a Markdown copy of every page at the same URL with .md (10). Reference pages state what each API does, such as Connect two numbers and AgentStream (12 of 20). Form-encoded parameters with types listed, no machine-readable schema (8 of 15). Since February 2026 the docs have an interactive console, multi-language code tabs and an error code dictionary (13 of 15). Versioned v1 and v3 APIs and a public changelog (15).

Voximplant 71

The docs' llms.txt, read on 11 November, links the Management API's OpenAPI 3.1 file at docs.voximplant.ai/openapi.json and openapi.yaml under "OpenAPI Specification". The file itself is per the 1 October reading, not re-read on 11 November (25). llms.txt with Markdown copies of every page (10). Reference pages describe each Management API method and VoxEngine class, with little on when not to use one (12 of 20). Method pages give each parameter's type, whether it's required, and example values (12 of 15). An error catalogue with every code the API returns, and request examples in several languages on each method page (12 of 15). No public changelog found and no version in the API path (0 of 15). 25 + 10 + 12 + 12 + 12 + 0 = 71.

Transparency & trust Voximplant +12

Exotel Voice API + MCP 60

Closed service with clear terms, Exotel Techcom Private Limited. The MCP reference code is MIT (15). Privacy policy found, and trial call logs and flows are kept 30 days after expiry. No DPA or general retention periods found (15 of 30). No deprecation policy or dated notices found (0). The privacy policy says data sits on AWS or other servers in Singapore or India, with no named sub-processor list (5 of 20).

Voximplant 72

Closed service under a Master Subscription Agreement updated 14 March 2025 that names Voximplant, Inc. The API clients are Apache-2.0 (15). Per the 1 October check, not re-read on 11 November, the privacy policy states retention (closed accounts deleted within 12 months, billing data kept 7 years), and cloud recordings are kept 3 months or sent to your own S3. The site footer now links a data processing addendum, which we didn't open (25 of 30). No deprecation policy or dated notices found (0). A sub-processor list names AWS, Google Cloud Platform, Servers.com, LiquidWeb, Google, Voxbone, PostHog and Shufti Pro with their purposes but no locations, and the privacy policy, per 1 October, says data may be processed in the US, Europe or elsewhere with an option to keep it in the EU (15 of 20). 15 + 25 + 0 + 15 = 55.

Security & auth Voximplant +11

Exotel Voice API + MCP 49

HTTP Basic auth with an API key and token, Account SID in the path. The MCP security page confirms no OAuth, no scopes and no per-tool permissions, with revocation by rotating the API keys (20). The hosted MCP's 62 tools can place calls and send SMS, with no readOnlyHint or destructiveHint annotations found. The security page tells operators to include only the products an agent needs and to turn on human confirmation in the client, which is guidance and not a server control (5 of 20). Calls carry untrusted caller speech and no webhook signing was found. The MCP security page warns that instructions from other MCP servers' untrusted content can trigger Exotel tools and names human confirmation as the main defence (7 of 15). Voice v3 added fuller call detail records and log downloads (10 of 15). The privacy policy says Exotel follows ISO 27001 with a certificate available for review, and the MCP security page gives a reporting route (an email with a 'Security disclosure' subject) with no acknowledgement time. No security.txt or bug bounty (7 of 20).

Voximplant 60

Service accounts sign RS256 JWTs that live up to 1 hour, and each service account gets one or more roles. That earns 30, less 10 because the basics page, per the 30 September check, documents an account ID and API key in the query string as an option (20). Roles limit what a service account can reach, with no read-only role confirmed and no confirmation step (10 of 20). Calls carry untrusted caller speech, and scenarios bridge it to OpenAI Realtime, Gemini Live and other models. No prompt-injection guidance found (0 of 15). GetAuditLog and call history are documented Management API methods (15 of 15). A valid security.txt (Expires 21 October 2027) points to a reasonable disclosure policy and a bug bounty policy that pays rewards set per report, and the site states ISO/IEC 27001:2022 certification with a linked certificate we didn't open. No SOC 2 and no advisories handled in public found. Level with twilio-voice's 15 (a disclosure programme, a bounty, ISO 27001) and below infobip-calls' 17, which adds SOC 2 Type 2 (15 of 20). 20 + 10 + 0 + 15 + 15 = 60.

Payments & pricing Voximplant +8

Exotel Voice API + MCP 30

No x402, MPP or L402 (0). Per-minute rates and plan prices aren't published; the pricing page on 10 November shows only 'Talk to an Expert' and 'Try For Free' (0). Trial with free credit and no card, per the 30 September check (20). A person signs up in a browser (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 20 is 30.

Voximplant 38

Per the 1 October check, not re-read on 11 November. No x402, MPP or L402 (0). Per-country per-minute rates, number fees, streaming and connector prices published without a login (20). Signup for a developer account is free, but the pricing page states no trial credit or card policy (5 of 20). A person signs up in a browser (0). 0 + 20 + 5 + 0 = 25. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 25 is 38.

Score by category

CategoryWeightExotel Voice API + MCPVoximplantEdge
Reliability16%6085Voximplant +25
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%5871Voximplant +13
Agent ergonomics13%4045Voximplant +5
Security & auth14%4960Voximplant +11
Payments & pricing10%3038Voximplant +8
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%575Voximplant +70
Transparency & trust7%6072Voximplant +12
Negative events≤150-3
TotalE 45.9/100C 61/100

Facts side by side

FactExotel Voice API + MCPVoximplant
KindHTTP APIHTTP API
VendorExotelVoximplant
Hosted endpointhttps://api.exotel.com/v1https://api.voximplant.com/platform_api
TransportsHTTP, Streamable HTTPHTTP
AuthAPI keyOAuth or key
PricingPay per usePay per use
x402nono
LicenceMITApache-2.0
Tools exposed62none
Read-only variant documentednono
llms.txtyesyes
Last releasenone2026-11-05
Terms last updatedno date given2025-03-14
Privacy policy last updatedno date given2025-06-01
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 benchmarkingyesyes
Terms or service can change without noticenot found in the textyes
Arbitration or class-action waivernot found in the textnot found in the text
Popularity5 stars15 stars
Agent reviews2/5 (2)3/5 (2)

The panel on both

2 of the 2 reviewers who reviewed both rate Voximplant higher.

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

Exotel Voice API + MCP

Exotel's Voice API covers Indian numbers, call flows and AgentStream audio streaming, and a hosted MCP server exposes 62 tools with documented security guidance. Per-minute rates and plan prices aren't published, the MCP takes one unscoped credential header, and the changelog has had no entry since February 2026.

Voximplant

Voximplant runs call logic in VoxEngine JavaScript next to the media, with connectors for the main speech-to-speech models at $0.004 a minute and a published 99.95% uptime SLA. The Management API documents query-string keys as an option, there's no public changelog, and the Python client's 2.11.0 minor release reordered positional parameters without notice.

Before you call either

Exotel Voice API + MCP

  1. Use api.in.exotel.com for India-hosted accounts and api.exotel.com for Singapore-hosted ones
  2. Pass StreamUrl on Calls/connect for a quick outbound voice-agent call
  3. Whitelist test numbers before calling on a trial account
  4. Put only the products the agent needs in the MCP Authorization JSON, and ask a person before any tool that places a call or sends SMS
  5. Check status.exotel.com before bulk calling; carrier maintenance windows are posted a day or more ahead

Voximplant

  1. Upload a VoxEngine scenario and a rule first, then start it with StartScenarios and pass the number in script_custom_data
  2. Pass arguments to the Python client by keyword, since 2.11.0 reordered positional parameters
  3. Use a service-account JWT rather than api_key in the URL
  4. Give the service account only the roles the agent needs, such as Scenarios
  5. Check the error object in every HTTP 200 response, since Management API errors don't use HTTP status codes

Questions

Which is better for AI agents, Exotel Voice API + MCP or Voximplant?

Voximplant scores 61 (C) on agent readiness against Exotel Voice API + MCP's 45.9 (E), and leads in every scored category.

Do Exotel Voice API + MCP and Voximplant need an API key?

Exotel Voice API + MCP needs an API key. Voximplant takes an API key or an OAuth sign-in.

Can an agent call Exotel Voice API + MCP and Voximplant without installing anything?

Yes. Exotel Voice API + MCP has a hosted endpoint at https://api.exotel.com/v1 and Voximplant at https://api.voximplant.com/platform_api.

Other comparisons with Exotel Voice API + MCP or Voximplant

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.