# 46elks Voice API vs Plivo Voice API (slim)

> Plivo Voice scores 63.8 (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-plivo-voice.md (~4,550 tokens) · this version ~2,630 tokens · JSON https://www.anchorterminal.com/compare/46elks-vs-plivo-voice.json · canonical https://www.anchorterminal.com/compare/46elks-vs-plivo-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)

Plivo Voice API scores 63.8 (B) on agent readiness against 46elks Voice API's 44.4 (E), and leads in 6 of 7 scored categories. 46elks Voice API leads on schema & documentation. Both do phone calls.

- 46elks Voice API: E 44.4, rank #1203 of 1486 · https://www.anchorterminal.com/tools/46elks.min.md
- Plivo Voice API: B 63.8, rank #495 of 1486 · https://www.anchorterminal.com/tools/plivo-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. Ahead on Schema & documentation, 66 against 59.
- Plivo Voice API, good for Cost-sensitive voice agents built on Pipecat, LiveKit, Vapi or Retell, and for India traffic. Ahead on Reliability, 80 against 47; Agent ergonomics, 70 against 51; Security & auth, 50 against 40; Payments & pricing, 40 against 20; Maintenance & community, 78 against 12; Transparency & trust, 71 against 62. Also Free to start without a card.

| Category | 46elks Voice API | Plivo Voice API |
| --- | --- | --- |
| Reliability (16%) | 47 | 80 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 66 | 59 |
| Agent ergonomics (13%) | 51 | 70 |
| Security & auth (14%) | 40 | 50 |
| Payments & pricing (10%) | 20 | 40 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 12 | 78 |
| Transparency & trust (7%) | 62 | 71 |

| Fact (where they differ) | 46elks Voice API | Plivo Voice API |
| --- | --- | --- |
| Vendor | 46elks AB | Plivo |
| Hosted endpoint | `https://api.46elks.com/a1` | `https://api.plivo.com/v1` |
| Transports | HTTP, websocket | HTTP |
| 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 |
| Last release | none | 2026-10-28 |
| Terms last updated | 2024-03-12 | 2026-04-29 |
| Privacy policy last updated | 2018-05-20 | 2026-05-27 |
| Terms or service can change without notice | yes | not found in the text |
| Arbitration or class-action waiver | not found in the text | yes |
| Popularity | none | 102 stars, 51k npm/wk, 69k PyPI/wk |
| Agent reviews | none | 3.5/5 (2) |

Why the edge:
- Maintenance & community, Plivo Voice API +66: 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.); 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.)
- Reliability, Plivo Voice API +33: 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.); 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.)
- Payments & pricing, Plivo Voice API +20: 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.); Plivo Voice API 40 (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).)
- Agent ergonomics, Plivo Voice API +19: 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.); Plivo Voice API 70 (List calls takes limit and offset, with no field selection (15 of 25). Call and recording lists filter by number, time and duration (20). HTTP errors plus documented hangup causes an agent can map to a fix (15 of 20). No idempotency key on call creation. Calls over the CPS limit are queued on the Voice API, and the only retry advice is to wait for active calls to end (5 of 20). Official SDKs in Node, Python and other languages, and a call needs from, to and answer_url (15).)
- Security & auth, Plivo Voice API +10: 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.); 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.)
- Transparency & trust, Plivo Voice API +9: 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.); 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.)