# didlogic Voice API vs Infobip Calls API + MCP (slim)

> Infobip Calls scores 65.9 (B) to didlogic Voice's 49.8 (D) for phone numbers. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/didlogic-vs-infobip-calls.md (~4,900 tokens) · this version ~2,830 tokens · JSON https://www.anchorterminal.com/compare/didlogic-vs-infobip-calls.json · canonical https://www.anchorterminal.com/compare/didlogic-vs-infobip-calls
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-07
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Infobip Calls API + MCP scores 65.9 (B) on agent readiness against didlogic Voice API's 49.8 (D), and leads in 6 of 7 scored categories. didlogic Voice API leads on payments & pricing. Both do phone numbers.

- didlogic Voice API: D 49.8, rank #1074 of 1486 · https://www.anchorterminal.com/tools/didlogic.min.md
- Infobip Calls API + MCP: B 65.9, rank #394 of 1486 · https://www.anchorterminal.com/tools/infobip-calls.min.md
- didlogic Voice API, good for Teams that need numbers and SIP termination in many countries and a WebSocket bridge to a voice agent. Ahead on Payments & pricing, 38 against 30. Also Free to start without a card.
- Infobip Calls API + MCP, good 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 Reliability, 62 against 26; Agent ergonomics, 62 against 57; Security & auth, 72 against 46; Maintenance & community, 60 against 38; Transparency & trust, 82 against 58.

| Category | didlogic Voice API | Infobip Calls API + MCP |
| --- | --- | --- |
| Reliability (16%) | 26 | 62 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 87 | 90 |
| Agent ergonomics (13%) | 57 | 62 |
| Security & auth (14%) | 46 | 72 |
| Payments & pricing (10%) | 38 | 30 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 38 | 60 |
| Transparency & trust (7%) | 58 | 82 |

| Fact (where they differ) | didlogic Voice API | Infobip Calls API + MCP |
| --- | --- | --- |
| Vendor | DID Logic PTE. LTD. | Infobip |
| Hosted endpoint | `https://mcp.didlogic.com/mcp` | `https://api.infobip.com/calls/1` |
| Transports | HTTP, websocket, Streamable HTTP | HTTP, Streamable HTTP, SSE (legacy) |
| Price for phone numbers | $2 per month (plan) | not published |
| Licence | Proprietary service under the didlogic Terms of Service | MIT |
| Read-only variant documented | no | yes |
| MCP registry | not listed | `com.infobip/mcp` |
| Last release | 2026-09-30 | none |
| Privacy policy last updated | no date given | 2026-01-22 |
| Arbitration or class-action waiver | yes | not found in the text |
| Popularity | none | 36 stars, 18k npm/wk |
| Agent reviews | none | 2/5 (2) |

Why the edge:
- Reliability, Infobip Calls API + MCP +36: didlogic Voice API 26 (Graded on the hosted API and MCP server with the hosted lines. The footer's network status page carries no components or incidents, and no other status page was found (0). No readable incident history (5). Rate limits are given only for recording lookups (one a second, one lookup a minute) (5 of 15). Those endpoints document 429 with Retry-After and X-RateLimit headers, with no backoff guidance or idempotency elsewhere, including number purchases and click-to-call (6 of 15). The site claims 99.999 per cent voice uptime, but no SLA was found in the Terms (0). The API and click-to-call carry no beta label, while the new buy experience is rolling out gradually (10). 0+5+5+6+0+10 = 26.); 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.)
- Security & auth, Infobip Calls API + MCP +26: didlogic Voice API 46 (Revocable bearer keys created in the portal, each with full account access by the vendor's own warning. MCP OAuth mints a separate key per sign-in (18 of 30). SIP accounts can be limited to allowed IPs, with no read-only key and no confirmation on purchases (6 of 20). Caller audio and SMS are untrusted, and no prompt-injection guidance was found (3 of 15). Call detail records, transaction history and risk-check logs through the API, with no audit log of API calls (7 of 15). ISO/IEC 27001:2022 and ISO 9001 certificates from TÜV AUSTRIA Hellas with registration numbers. No security.txt or bug bounty found (12 of 20). 18+6+3+7+12 = 46.); 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.)
- Transparency & trust, Infobip Calls API + MCP +24: didlogic Voice API 58 (Closed service with long, clear terms naming DID Logic PTE. LTD. in Singapore (15 of 30). The privacy policy commits to data minimisation and says call content isn't monitored except for requested recording, but gives no retention periods (12 of 30). No deprecation policy, though the docs explain backward-compatible identifier changes (5 of 20). Twelve points of presence are claimed, with no sub-processor list or data locations found (5 of 20). 15+12+5+5 = 37.); 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.)
- Maintenance & community, Infobip Calls API + MCP +22: didlogic Voice API 38 (Release notes dated by month, the newest September 2026 (click-to-call API and WebSocket calls), about 37 to 67 days before this check (20). Entries in August and September and the July self-service API within the 90 days, dated by month only, so fewer than three dated changes can be confirmed (10). Release notes, phone and email support, and a partner programme, with no evidence read of reply times (8 of 15). No official server-side SDK, and the MCP server isn't in the official registry (0). No package to assess (0). 20+10+8+0+0 = 38.); 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.)
- Payments & pricing, didlogic Voice API +8: didlogic Voice API 38 (No x402, MPP or L402 (0). Per-minute call rates and monthly number prices are public by country, marked as indicative (18 of 20). Free test credit with no card, and a 30-day trial number for verified company emails (20). Signup and key creation happen in the portal (0). 0+18+20+0 = 38.); Infobip Calls API + MCP 30 (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).)
- Agent ergonomics, Infobip Calls API + MCP +5: didlogic Voice API 57 (Call records take filters and CSV export, and numbers search by country, region and city (18 of 25). Filtering on calls and numbers, with paging not confirmed on every list (14 of 20). One error envelope with field messages and 404 for unknown ids (14 of 20). No idempotency key on purchases or click-to-call. MCP annotations weren't readable without a sign-in (3 of 20). Few required fields, no official SDK beyond the browser Voice SDK (8 of 15). 18+14+14+3+8 = 57.); Infobip Calls API + MCP 62 (Call and log lists take page and size, with no field selection (15 of 25). Filters on call lists and voice logs (15 of 20). An error code reference and a handling-errors guide that says which errors to retry (15 of 20). No idempotency key, but the handling-errors guide says a retried send may run twice and to check logs or delivery reports first (10 of 20, as scalekit-agentkit and deepl-api read documented retry semantics without a key). Every call needs a calls configuration, an event subscription and the account's own base URL. The official Python client (6.0.0, 22 January 2026) covers the Calls API, while the JavaScript SDK hasn't been released since 2023, which the Infobip messaging listing reads as 8 of 15; one point less for the configuration and subscription every call needs (7 of 15).)