# 46elks Voice API vs Voximplant (slim)

> Voximplant scores 51.8 (D) 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-voximplant.md (~3,750 tokens) · this version ~1,880 tokens · JSON https://www.anchorterminal.com/compare/46elks-vs-voximplant.json · canonical https://www.anchorterminal.com/compare/46elks-vs-voximplant
- 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)

Voximplant scores 51.8 (D) on agent readiness against 46elks Voice API's 44.4 (E), and leads in 4 of 7 scored categories. 46elks Voice API leads on agent ergonomics. Both do phone calls.

- 46elks Voice API: E 44.4, rank #1203 of 1486 · https://www.anchorterminal.com/tools/46elks.min.md
- Voximplant: D 51.8, rank #1005 of 1486 · https://www.anchorterminal.com/tools/voximplant.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 Agent ergonomics, 51 against 45.
- Voximplant, good for Teams that want speech-to-speech models on the phone without running a media server, and are happy to write call logic in VoxEngine JavaScript. Ahead on Reliability, 65 against 47; Schema & documentation, 71 against 66; Payments & pricing, 25 against 20; Maintenance & community, 50 against 12.

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

| Fact (where they differ) | 46elks Voice API | Voximplant |
| --- | --- | --- |
| Vendor | 46elks AB | Voximplant |
| Hosted endpoint | `https://api.46elks.com/a1` | `https://api.voximplant.com/platform_api` |
| Transports | HTTP, websocket | HTTP |
| 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-08-26 |
| Terms last updated | 2024-03-12 | 2025-03-14 |
| Privacy policy last updated | 2018-05-20 | 2025-06-01 |
| Terms restrict benchmarking | not found in the text | yes |
| Popularity | none | 15 stars, 1.4k npm/wk, 930 PyPI/wk |
| Agent reviews | none | 3/5 (2) |

Why the edge:
- Maintenance & community, Voximplant +38: 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.); Voximplant 50 (The listing records a release on 2026-08-26, 36 days ago, which we didn't re-check (20). Release count in the last 90 days not established (5 of 20). No public changelog. Support exists (5 of 15). Official Node and Python API clients (15). Package health not checked (5 of 10).)
- Reliability, Voximplant +18: 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.); Voximplant 65 (Statuspage at status.voximplant.com with components and history (20). Incidents in the history feed since 30 July are regional, PSTN delays in some regions for 46 minutes on 3 September, Russian and Kazakh carrier problems on 24, 28 and 30 September, and outages in the separate Kit product, so minor only (20). Limits are published with numbers, 50 call attempts, 10 unanswered calls and 3 active HTTP requests per session, 1,000 users per account, and a block on destinations above 20 cents a minute (15). No 429 or retry guidance found (0). No SLA found (0). The platform is generally available (10).)
- Agent ergonomics, 46elks Voice API +6: 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.); Voximplant 45 (List methods such as call history take count and offset. We didn't confirm field controls (10 of 25). Filters not confirmed this run (10 of 20). Management API errors page with codes (15 of 20). No idempotency key or safe-retry guidance found (0). Official Node and Python API clients, but a first call needs an uploaded VoxEngine scenario and a rule before StartScenarios (10 of 15).)
- Schema & documentation, Voximplant +5: 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.); Voximplant 71 (OpenAPI spec for the Management API at docs.voximplant.ai/openapi.json and .yaml (25). llms.txt with Markdown pages (10). Reference pages describe each Management API method and VoxEngine class, with little on when not to use one (12 of 20). Typed parameters from the spec (12 of 15). A Management API errors page and examples (12 of 15). No public changelog found and no version in the API path (0 of 15).)
- Payments & pricing, Voximplant +5: 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.); Voximplant 25 (No x402, MPP or L402 (0). Per-country per-minute rates, number fees, streaming and connector prices published without a login (20). Signup for a developer account is free, but the pricing page states no trial credit or card policy (5 of 20). A person signs up in a browser (0).)