# 46elks Voice API vs Sinch Voice API + MCP (slim)

> Sinch Voice scores 66.3 (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-sinch-voice.md (~4,900 tokens) · this version ~2,880 tokens · JSON https://www.anchorterminal.com/compare/46elks-vs-sinch-voice.json · canonical https://www.anchorterminal.com/compare/46elks-vs-sinch-voice
- 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)

Sinch Voice API + MCP scores 66.3 (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
- Sinch Voice API + MCP: B 66.3, rank #375 of 1486 · https://www.anchorterminal.com/tools/sinch-voice.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.
- Sinch Voice API + MCP, good for Teams already on Sinch messaging, or voice agents that want a managed STT and TTS relay with barge-in without running their own speech stack. Ahead on Reliability, 60 against 47; Schema & documentation, 85 against 66; Agent ergonomics, 81 against 51; Security & auth, 55 against 40; Payments & pricing, 35 against 20; Maintenance & community, 79 against 12; Transparency & trust, 73 against 62. Also Runs on your own machine.

| Category | 46elks Voice API | Sinch Voice API + MCP |
| --- | --- | --- |
| Reliability (16%) | 47 | 60 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 66 | 85 |
| Agent ergonomics (13%) | 51 | 81 |
| Security & auth (14%) | 40 | 55 |
| Payments & pricing (10%) | 20 | 35 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 12 | 79 |
| Transparency & trust (7%) | 62 | 73 |

| Fact (where they differ) | 46elks Voice API | Sinch Voice API + MCP |
| --- | --- | --- |
| Vendor | 46elks AB | Sinch |
| Hosted endpoint | `https://api.46elks.com/a1` | `https://voice.api.sinch.com/v2` |
| Transports | HTTP, websocket | HTTP, stdio |
| 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 | Apache-2.0 |
| Last release | none | 2026-10-28 |
| Terms last updated | 2024-03-12 | 2026-06-01 |
| Privacy policy last updated | 2018-05-20 | 2025-12-12 |
| Terms or service can change without notice | yes | not found in the text |
| Popularity | none | 1 stars, 16k npm/wk, 11k PyPI/wk |
| Agent reviews | none | 3/5 (2) |

Why the edge:
- Maintenance & community, Sinch Voice API + MCP +67: 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.); Sinch Voice API + MCP 79 (Java SDK 2.4.0 (28 October 2026) adds Voice v2 helpers, Node 1.7.0 (15 October) and Python 2.3.0 (14 October) changed Voice v2, and the MCP server's 0.0.1-beta.7 (30 October) moved its voice tools to Voice API v2 (30). In the 90 days, Node 1.6.0 (23 September) and Python 2.2.0 (21 September) added Voice v2, Java 2.3.0 (15 October) did the same, and Java 2.2.0, .NET 1.5.1 (2 September) and the 28 October releases followed (20). v1 voice release notes stop in October 2022 and v2 has an undated what's-new page, while the SDK changelogs are dated (5 of 15). Official SDKs in four languages, with Voice v2 in Node, Python and Java (15). CI on the SDK repositories, with CodeQL and dependency review on Java and an audit job on Node (9 of 10). 30 + 20 + 5 + 15 + 9 = 79.)
- Agent ergonomics, Sinch Voice API + MCP +30: 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.); Sinch Voice API + MCP 81 (v2 lists take `page_size`, with no field selection (15 of 25). The v2 call list pages by link and filters by from, to, call type, time range, result and reason (18 of 20). v1 error reference with codes, and v2 errors carry a type and instance per the SDKs (15 of 20). v2 call, batch and service writes take an Idempotency-Key that returns the cached response for repeats within 10 minutes, and the webhook guide says to deduplicate on `ce-id` and `ce-source` (18 of 20). Official SDKs in Node, Python, Java and .NET, but a v2 dial is a nested commands document rather than a few fields (15). 15 + 18 + 15 + 18 + 15 = 81.)
- Schema & documentation, Sinch Voice API + MCP +19: 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.); Sinch Voice API + MCP 85 (The v2 reference links an OpenAPI 3.1.1 file (version 2.0.59), read on 2 November with 11 paths and 17 operations (25). llms.txt with Markdown pages for v1 and v2 (10). Reference pages describe each SVAML action or v2 command, with a migration page on why to move to v2 (12 of 20). Typed fields with enums for call type, result and reason, and bounded integers such as maxCps and ttlSeconds (13 of 15). A v1 error and troubleshooting reference, request examples, and problem-details error answers (400, 401, 403, 404, 429, 500) documented on the v2 operations (15). Two API generations, v1 release notes last updated 2022-10-06 and an undated v2 what's-new page (10 of 15). 25 + 10 + 12 + 13 + 15 + 10 = 85.)
- Security & auth, Sinch Voice API + MCP +15: 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.); Sinch Voice API + MCP 55 (Voice v2 takes a project access key over Basic auth or as an OAuth 2.0 token. v1 uses an application key and secret with signed requests recommended. We found no per-key scopes (25 of 30). No read-only mode or confirmation step. The official MCP server's tool allow-list (--tags, or MCP_TAGS since 0.0.1-beta.7, 30 October) can leave out whole groups, and its released version runs over stdio only, as the Sinch messaging listing reads it (5 of 20). Calls carry untrusted caller speech. Callbacks are signed in v1 and v2, and we found no prompt-injection guidance (5 of 15). Call lookup and call lists by API, no audit log found (10 of 15). The trust centre lists ISO 27001:2022 and SOC 2 Type 2 reports, PCI and HIPAA, and Sinch's security contact for reports. No security.txt (404 on 2 November), no bug bounty and no advisories for @sinch/sdk-core, @sinch/mcp or sinch in OSV (10 of 20, as the Sinch messaging listing). 25 + 5 + 5 + 10 + 10 = 55.)
- Payments & pricing, Sinch Voice API + MCP +15: 46elks Voice API 20 (No x402, MPP or L402 (0). Per-minute prices by destination are public without login, also in kronor, with incoming calls free (20). No free credit; only SMS to the test number +46700000000 costs nothing, and accounts are prepaid or invoiced against a deposit (0). A person signs up in a browser and copies the credentials (0). 0+20+0+0 = 20.); Sinch Voice API + MCP 35 (No x402, MPP or L402 (0). The voice pricing page, re-read on 2 November, gives domestic outbound from $0.01 a minute with a downloadable Voice API price list, and only illustrative inbound, SIP, recording and number prices (15 of 20). Test credits and a test number on signup, with a payment method needed only to upgrade (20). A person signs up in a browser (0). 0 + 15 + 20 + 0 = 35.)
- Reliability, Sinch Voice API + MCP +13: 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.); Sinch Voice API + MCP 60 (Statuspage at status.sinch.com with Voice components and history (20). Read from its own history and incident pages on 2 November (the 1 October count from IsDown, a third-party copy of the page, is struck). From 4 August to 2 November the calling incidents each name one region, one channel or a subset of calls. Calling in AP-Southeast-1 degraded from 04:50 to 07:23 UTC on 22 September (labelled critical, one region), PSTN outbound calls saw failed attempts from 05:51 to 09:05 UTC on 2 October (one channel, no region named, posted with no impact level), and Elastic SIP Trunking in US East had non-completed calls for 8 minutes on 9 September. On 26 October a planned change took the customer dashboard down and blocked traffic for a subset of accounts. Partial incidents read as minor, so minor only (20). No account rate limits published for voice. Batch calls take a maxCps setting (1 to 1,000 calls a second), which is a requested pace, not a published limit (0 of 15). The v2 OpenAPI file, readable on 2 November, documents a 429 answer with a Retry-After header on 15 of 17 operations, and an Idempotency-Key header (16 to 128 characters) whose repeats within 10 minutes return the cached response (15). No SLA found (0). Voice API v1 is generally available, but the v2 overview, llms.txt ("recommended for new builds/preview") and the pricing page (Voice Relay and Streams in Public Preview) label v2, the listed surface, as preview, and tell projects that must be GA to use v1. Mixed surfaces take part of the line, as gemini-api's 5 (5 of 10). 20 + 20 + 0 + 15 + 0 + 5 = 60.)