# 46elks Voice API vs Infobip Calls API + MCP (slim)

> Infobip Calls scores 65.9 (B) to 46elks Voice's 44.4 (E) for phone calls. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/46elks-vs-infobip-calls.md (~4,950 tokens) · this version ~2,930 tokens · JSON https://www.anchorterminal.com/compare/46elks-vs-infobip-calls.json · canonical https://www.anchorterminal.com/compare/46elks-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 46elks Voice API's 44.4 (E), and leads in every scored category. Both do phone calls.

- 46elks Voice API: E 44.4, rank #1203 of 1486 · https://www.anchorterminal.com/tools/46elks.min.md
- Infobip Calls API + MCP: B 65.9, rank #394 of 1486 · https://www.anchorterminal.com/tools/infobip-calls.min.md
- 46elks Voice API, good for European teams that want EU-resident calling and numbers with a simple REST API and a WebSocket bridge to an AI agent.
- 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 47; Schema & documentation, 90 against 66; Agent ergonomics, 62 against 51; Security & auth, 72 against 40; Payments & pricing, 30 against 20; Maintenance & community, 60 against 12; Transparency & trust, 82 against 62.

| Category | 46elks Voice API | Infobip Calls API + MCP |
| --- | --- | --- |
| Reliability (16%) | 47 | 62 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 66 | 90 |
| Agent ergonomics (13%) | 51 | 62 |
| Security & auth (14%) | 40 | 72 |
| Payments & pricing (10%) | 20 | 30 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 12 | 60 |
| Transparency & trust (7%) | 62 | 82 |

| Fact (where they differ) | 46elks Voice API | Infobip Calls API + MCP |
| --- | --- | --- |
| Vendor | 46elks AB | Infobip |
| Hosted endpoint | `https://api.46elks.com/a1` | `https://api.infobip.com/calls/1` |
| Transports | HTTP, websocket | HTTP, Streamable HTTP, SSE (legacy) |
| Auth | API key | OAuth or key |
| Price for phone calls | $0.017 per minute of call | not published |
| Licence | Proprietary service under the 46elks Terms of Service (effective 12 March 2024). Example code and the Swagger file are in the public 46elks-getting-started repository | MIT |
| Read-only variant documented | no | yes |
| MCP registry | not listed | `com.infobip/mcp` |
| Terms last updated | 2024-03-12 | no date given |
| Privacy policy last updated | 2018-05-20 | 2026-01-22 |
| Terms or service can change without notice | yes | not found in the text |
| Popularity | none | 36 stars, 18k npm/wk |
| Agent reviews | none | 2/5 (2) |

Why the edge:
- Maintenance & community, Infobip Calls API + MCP +48: 46elks Voice API 12 (No changelog, release notes or dated API change was found, the sitemap's newest blog post is from 2014, and the Swagger file predates Realtime Voice (0). No dated changes in the 90 days from 8 August (0). Support by phone and email on workdays with a typical 60-minute response stated, and 24/7 error reporting (10 of 15). No official SDK (0). The public examples repository answers, but its history wasn't read (2 of 10). 0+0+10+0+2 = 12.); 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.)
- Security & auth, Infobip Calls API + MCP +32: 46elks Voice API 40 (HTTP Basic credentials per account, with separate credentials per subaccount and no scopes found (18 of 30). Subaccounts separate traffic, with no read-only credential or confirmation for paid actions (6 of 20). Callers' speech, DTMF and SMS replies reach the agent as untrusted input. The docs show how to verify callback origin, with no prompt-injection guidance (5 of 15). Call, SMS and recording history through the API for 90 days (8 of 15). A registered Swedish telecom operator, but no security.txt (404), disclosure policy, bug bounty or certification was found (3 of 20). 18+6+5+8+3 = 40.); 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.)
- Schema & documentation, Infobip Calls API + MCP +24: 46elks Voice API 66 (A Swagger 2.0 file with 28 operations is linked from the docs, but it covers no Realtime Voice messages and isn't versioned with the API (18 of 25). An llms.txt written for agents, with a task-to-endpoint table and webhook payloads, while docs pages are HTML (10). Each docs page explains parameters and when webhooks fire, such as `voice_start` loading only once a call connects (14 of 20). Form-encoded parameters with types in the Swagger file and few enums (9 of 15). Examples in many languages and a JSON error shape, with no error list (10 of 15). The `/a1/` path, with no changelog found (5 of 15). 18+10+14+9+10+5 = 66.); 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).)
- Transparency & trust, Infobip Calls API + MCP +20: 46elks Voice API 62 (Closed service with clear terms naming 46elks AB with its Swedish registration (15 of 30). The privacy policy gives concrete retention, 60 days of traffic data under Swedish law, 14 days of troubleshooting logs and a 90-day history for the customer, with EU storage, and a GDPR page and data protection page exist (24 of 30). No deprecation policy or dated notices found (0 of 20). Data stated to stay in the EU on 46elks's own servers in Sweden, with no sub-processor list found (10 of 20). 15+24+0+10 = 49.); 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.)
- Reliability, Infobip Calls API + MCP +15: 46elks Voice API 47 (Graded on the hosted REST and Realtime Voice APIs with the hosted lines. A status page exists, linked from 46elks.com/status on UptimeRobot (20). It draws its data by script from a path its robots.txt disallows, so no history was readable (5). SMS sending speed is documented in the FAQ, but no limit for calls, numbers or WebSocket sessions was found (5 of 15). llms.txt says to retry 5xx with exponential backoff and not to retry 4xx unchanged, with no Retry-After or idempotency for `POST /calls` (7 of 15). The SLA page commits to support hours and 24/7 error reporting with no uptime figure, and extended SLAs are by sales (0). Voice and Realtime Voice carry no beta label (10). 20+5+5+7+0+10 = 47.); 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.)
- Agent ergonomics, Infobip Calls API + MCP +11: 46elks Voice API 51 (Compact JSON responses, and call actions returned as small JSON objects (18 of 25). History endpoints list calls and recordings, with paging parameters not confirmed (10 of 20). Errors carry `error` and `detail` (12 of 20). No idempotency key on `POST /calls` or number allocation (3 of 20). Three required fields to place a call, no official SDK, examples in 12 or more languages (8 of 15). 18+10+12+3+8 = 51.); 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).)