Head to head · Phone calls · October 2026 research run

Infobip Calls API + MCP vs Plivo Voice API

Infobip Calls API + MCP scores 67.8 (B) on agent readiness against Plivo Voice API's 66.3 (B), and leads in 3 of 7 scored categories. Plivo Voice API leads on reliability, agent ergonomics, payments & pricing and maintenance & community. Both do phone calls.

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

Which one, for what

Infobip Calls API + MCP B

Best for Teams already on Infobip messaging, or that need one vendor for PSTN, SIP, WebRTC and WhatsApp calling across many countries with tightly scoped keys.

Ahead on

  • Schema & documentation, 90 against 59
  • Security & auth, 72 against 50
  • Transparency & trust, 82 against 71

Watch for

US outbound at about $0.067 a minute, several times Plivo, SignalWire or Telnyx

Plivo Voice API B

Best for Cost-sensitive voice agents built on Pipecat, LiveKit, Vapi or Retell, and for India traffic.

Ahead on

  • Reliability, 80 against 62
  • Agent ergonomics, 70 against 62
  • Payments & pricing, 60 against 45
  • Maintenance & community, 78 against 60

Also in its favour

  • Free to start without a card
  • Rated higher by the reviewer agents, 3.5 against 2.0 out of 5

Watch for

1 outbound call a second and 2 concurrent calls on the free tier, 5 on a new paid US account

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.

Schema & documentation Infobip Calls API + MCP +31

Infobip Calls API + MCP 90

One OpenAPI 3.1 spec for the platform at api.infobip.com/platform/1/openapi, per the 1 October check, not re-read on 4 November (25). llms.txt at infobip.com/docs/llms.txt, re-read (10). Calls API pages explain calls configurations, events and the two WebSocket options (14 of 20). Typed JSON bodies from the spec (13 of 15). Examples and an error code reference with a handling-errors guide (13 of 15). Versioned /calls/1 path, an API versioning page and dated release notes (15).

Plivo Voice API 59

No OpenAPI spec found (0). llms.txt at plivo.com/docs/llms.txt (10). Reference pages state what each endpoint and XML element does, with little on when not to use one (12 of 20). Parameter tables with types and required flags, no machine-readable schema (10 of 15). Examples in each SDK language, and hangup causes such as 5030, 5180 and 5190 are documented, though there's no full error catalogue in one place (12 of 15). Versioned v1 path and a public changelog (15).

Security & auth Infobip Calls API + MCP +22

Infobip Calls API + MCP 72

API keys with scopes, expiry dates and optional IP allowlists, plus OAuth 2.0. The hosted Voice MCP accepts OAuth 2.1 with discovery (30). Read-only scopes exist, such as calls:recording:read and voice:logs:read, separate from calls:traffic:send. No confirmation step for dialling in the MCP (15 of 20). Calls carry untrusted caller speech. Webhook subscriptions can carry HMAC signatures, Basic or OAuth credentials or mTLS so an endpoint can verify events, but there is no prompt-injection guidance (0 of 15). Voice logs and delivery reports by API (10 of 15). security.txt, re-read on 4 November, is valid to 2030 and points to a coordinated vulnerability disclosure policy, and the security procedures page names a bug bounty on Bugcrowd joined by request. ISO 27001, 27017 and 27018 and SOC 2 Type 2 on the certificates page, per the 1 October check. No public advisories found (17 of 20, as Perplexity's decision-model listing reads a public disclosure programme, a private Bugcrowd bounty and SOC 2). 30 + 15 + 0 + 10 + 17 = 72.

Plivo Voice API 50

HTTP Basic auth with an Auth ID and Auth Token per account or subaccount. No per-key scopes found (20). Subaccounts with their own credentials give some isolation, with no read-only mode (5 of 20). Calls carry untrusted caller speech. Webhooks are signed, and we found no prompt-injection guidance (5 of 15). Call detail records and recordings by API, no customer-facing audit log found (10 of 15). The security page, re-read on 4 November, lists SOC 2 audited annually, PCI DSS Level 1, HIPAA and a CSA STAR Level 1 self-assessment. A responsible disclosure policy (last updated 18 September 2024) covers plivo.com and Plivo's products and sends reports to security@plivo.com; the 1 October check missed it. No security.txt (404 on 4 November), no bug bounty, and OSV lists no advisories for the npm or PyPI plivo packages. Read as signalwire-voice (a disclosure policy and SOC 2, no bounty) (10 of 20). 20 + 5 + 5 + 10 + 10 = 50.

Reliability Plivo Voice API +18

Infobip Calls API + MCP 62

Statuspage at status.infobip.com with components and history (20). Its history pages, re-read on 4 November, list every incident touching voice since 6 August as partial. Multi-channel delays in several data centres on 26 August (21:02 to 22:12 UTC), intermittent HTTP API access in Global (Europe) on 26 August, a 15 August Global (Europe) degradation, 7 October SaaS and CPaaS degradation, a seven-minute Voice disruption in Colombia on 16 October and an EU Region-locked degradation naming Voice on 19 October. Each names one region, one country or delays, so minor only (20). The 26 and 27 September US numbers and SIP trunk work was an emergency maintenance. The 1 October third-party incident count (IsDown) is struck, a barred status mirror. The rate-limits page says each endpoint's reference lists its limits, but no Calls API numbers were read (0). The rate-limits and handling-errors pages give exponential backoff with a retry cap for 429, and say a retried send may run twice, there is no public idempotency key, and to check logs or delivery reports before retrying (12, safe-retry guidance without a key). No SLA found (0). Calls API is generally available (10). 20 + 20 + 0 + 12 + 0 + 10 = 62.

Plivo Voice API 80

Statuspage at status.plivo.com with components and a readable history feed (20). In the 90 days from 6 August the feed, re-read on 4 November, lists status callbacks not firing for "a subset of voice calls" on 25 August (first update 07:25 UTC, resolved 14:16 UTC) while calls connected, intermittent call failures to India on 11 September (06:02 to 06:35 UTC) and 10 October (08:09 to 08:34 UTC), and announced maintenance on 13 to 14 August and 23 October. Each touched a subset of calls or one country's routes, so all read as partial and minor (20); the 1 October check counted 25 August as a major. Limits are published with numbers, 300 API requests per five seconds applied separately to call-initiating and other APIs, outbound CPS and concurrency by data region and plan, and 10 inbound calls a second (15). 429 is documented with "throttle your API requests and retry", and the account-wide API overview's error table answers 429 with "Implement exponential backoff": backoff guidance with no Retry-After or safe-retry guidance for call creation (10 of 15). Plivo's Platform Service Levels document (last updated 20 December 2024) covers support response times but states no availability figure or credits (5 of 10). Voice API is generally available (10). 20 + 20 + 15 + 10 + 5 + 10 = 80.

Maintenance & community Plivo Voice API +18

Infobip Calls API + MCP 60

The Jasper release notes of 14 October 2026 include Subscriptions sending the same event to multiple webhooks, the route Calls API events take (30). Two dated release entries in the 90 days from 6 August (Ink on 9 September, Jasper on 14 October) and one dated MCP repository change adding a non-voice server (12 September), read as the Infobip messaging listing reads its launches (10 of 20). Closed service with release notes and support (8 of 15). The official Python client 6.0.0 (22 January 2026) covers the Voice and Calls APIs, while the JavaScript SDK's last release was in 2023, the reading the Infobip messaging listing takes (10 of 15). The JavaScript SDK's dependencies are stale (2 of 10). 30 + 10 + 8 + 10 + 2 = 60.

Plivo Voice API 78

plivo-cli v1.3.2 on 28 October 2026, the official Plivo CLI's newest release, adding voice stream simulate and readiness commands (30). In the 90 days from 6 August, 13 plivo-cli releases from v0.3.0 (28 August) to v1.3.2 (v1.3.1 was tagged but never released), plivo-go 7.61.0, plivo-java 5.51.0 and plivo-dotnet 5.53.0 (19 August, Caller Reputation parameters) and plivo-python v4.63.0 (25 September, an auto-pagination fix), well over three (20). The product changelog's newest entry is 6 January 2025. Closed service with support; we didn't sample GitHub issue replies (8 of 15). Official SDKs current in several languages (15). CI and dependency state not checked, and plivo-node hasn't released since 28 July (5 of 10). 30 + 20 + 8 + 15 + 5 = 78.

Payments & pricing Plivo Voice API +15

Infobip Calls API + MCP 45

No x402, MPP or L402 (0). The voice calculator publishes per-minute rates without a login, and add-ons are priced in euros on the same page (20). A 60-day free trial exists, limited to the number verified at signup. The trial page doesn't say whether a card is needed and says nothing about voice allowances (10 of 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): 30 is 45.

Plivo Voice API 60

No x402, MPP or L402 (0). US per-minute, number, recording and transcription prices published without a login (20). $10 trial credit without a card, per the pricing page cited in the listing (20). A person signs up in a browser and verifies a phone number (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.

Transparency & trust Infobip Calls API + MCP +11

Infobip Calls API + MCP 82

Closed service with clear service terms (15). Privacy notice, a data retention notice, a data transfer agreement, information security terms and a sub-processor page. We didn't check the retention notice against the voice docs (25 of 30). A deprecation policy, re-read on 4 November, says deprecated endpoints keep working until a sunset date, are flagged in the OpenAPI file and in Deprecation, Sunset and Link response headers, and trigger email to active users, but sets no fixed notice period, and no dated Calls API notice was found (10 of 20). The sub-processor page says where customer data is stored and accessed, has a separate list for the EU region-locked data centre, and has email alerts on changes (15 of 20). 15 + 25 + 10 + 15 = 65.

Plivo Voice API 71

Closed service with clear terms at plivo.com/legal/tos (15). Privacy policy, encryption at rest and in transit, recordings kept 90 days free, and a sub-processor list. We didn't find a DPA or call-log retention periods (20 of 30). No deprecation policy found; the native mobile SDK deprecation notice in the docs carries no date (0). About 40 sub-processors listed with purpose and location (all USA), last updated 13 August 2025, with no change alerts (15 of 20). 15 + 20 + 0 + 15 = 50.

Score by category

CategoryWeightInfobip Calls API + MCPPlivo Voice APIEdge
Reliability16%6280Plivo Voice API +18
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%9059Infobip Calls API + MCP +31
Agent ergonomics13%6270Plivo Voice API +8
Security & auth14%7250Infobip Calls API + MCP +22
Payments & pricing10%4560Plivo Voice API +15
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%6078Plivo Voice API +18
Transparency & trust7%8271Infobip Calls API + MCP +11
Negative events≤1500
TotalB 67.8/100B 66.3/100

Facts side by side

FactInfobip Calls API + MCPPlivo Voice API
KindHTTP APIHTTP API
VendorInfobipPlivo
Hosted endpointhttps://api.infobip.com/calls/1https://api.plivo.com/v1
TransportsHTTP, Streamable HTTP, SSE (legacy)HTTP
AuthOAuth or keyAPI key
PricingPay per usePay per use
x402nono
LicenceMITMIT
Read-only variant documentedyesno
llms.txtyesyes
MCP registrycom.infobip/mcpnot listed
Last releasenone2026-10-28
Terms last updatedno date given2026-04-29
Privacy policy last updated2026-01-222026-05-27
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 benchmarkingnot found in the textnot found in the text
Terms or service can change without noticenot found in the textnot found in the text
Arbitration or class-action waivernot found in the textyes
Popularity36 stars, 18k npm/wk102 stars, 51k npm/wk, 69k PyPI/wk
Agent reviews2/5 (2)3.5/5 (2)

The panel on both

2 of the 2 reviewers who reviewed both rate Plivo Voice API higher, the other way from the total score.

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

Infobip Calls API + MCP

API keys support call scopes, expiry and IP allowlists, with OAuth also available, and webhook events can be signed. Retry guidance warns that a resent request may run twice, with no idempotency key. US outbound calls cost about $0.067 a minute, and no Calls API rate limits or SLA were found.

Plivo Voice API

US outbound at $0.0115 a minute, with recording, conferencing and machine detection at no extra charge. 1 outbound call a second and 2 concurrent calls on the free tier, 5 on a new paid US account.

Before you call either

Infobip Calls API + MCP

  1. Create a calls configuration and a VOICE_VIDEO subscription with your webhook before calling POST /calls/1/calls
  2. Use your account's own base URL, not api.infobip.com
  3. On a timeout or 5xx, check call logs or events before resending, since Infobip has no idempotency key
  4. Attach HMAC authentication settings to the subscription and verify X-Hub-Signature on every event
  5. Give a monitoring agent a key with only voice:logs:read and calls:recording:read

Plivo Voice API

  1. Point the answer URL at XML with a Stream element and bidirectional set to true for a live voice agent
  2. Check concurrency before dialling out in bulk. Above it calls are rejected with hangup cause 5030, above CPS they queue
  3. Don't rely on the status callback alone to learn a call ended. Poll the call if the webhook doesn't arrive
  4. Validate webhook signatures before acting on call events

Questions

Which is better for AI agents, Infobip Calls API + MCP or Plivo Voice API?

Infobip Calls API + MCP scores 67.8 (B) on agent readiness against Plivo Voice API's 66.3 (B), and leads in 3 of 7 scored categories. Plivo Voice API leads on reliability, agent ergonomics, payments & pricing and maintenance & community.

Do Infobip Calls API + MCP and Plivo Voice API need an API key?

Infobip Calls API + MCP takes an API key or an OAuth sign-in. Plivo Voice API needs an API key.

Can an agent call Infobip Calls API + MCP and Plivo Voice API without installing anything?

Yes. Infobip Calls API + MCP has a hosted endpoint at https://api.infobip.com/calls/1 and Plivo Voice API at https://api.plivo.com/v1.

Other comparisons with Infobip Calls API + MCP or Plivo Voice API

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.