# 46elks Voice API vs Voximplant

> 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.

- Canonical: https://www.anchorterminal.com/compare/46elks-vs-voximplant
- Markdown: https://www.anchorterminal.com/compare/46elks-vs-voximplant.md (~3,750 tokens)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-07

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: grade E, 44.4/100, rank #1203 of 1486. Markdown https://www.anchorterminal.com/tools/46elks.md · JSON https://www.anchorterminal.com/api/v1/tools/46elks.json
- Voximplant: grade D, 51.8/100, rank #1005 of 1486. Markdown https://www.anchorterminal.com/tools/voximplant.md · JSON https://www.anchorterminal.com/api/v1/tools/voximplant.json
- Best phone calling and voice transport APIs for AI agents: https://www.anchorterminal.com/best/voice-calling/index.md
- All 105 calling comparisons: https://www.anchorterminal.com/compare/voice-calling/index.md

## Which one, for what

### 46elks Voice API (E)

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

Watch for: No changelog or dated API release found

### Voximplant (D)

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

Watch for: Scenarios are VoxEngine JavaScript with their own limits (16 MB memory, 1-second callbacks)


## 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).

## Score by category

| Category | Weight | 46elks Voice API | Voximplant | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 47 | 65 | Voximplant +18 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 66 | 71 | Voximplant +5 |
| Agent ergonomics | 13% (16.2 this run) | 51 | 45 | 46elks Voice API +6 |
| Security & auth | 14% (17.5 this run) | 40 | 40 | even |
| Payments & pricing | 10% (12.5 this run) | 20 | 25 | Voximplant +5 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 12 | 50 | Voximplant +38 |
| Transparency & trust | 7% (8.8 this run) | 62 | 62 | even |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **44.4 · E** | **51.8 · D** | |

## Facts side by side

| Fact | 46elks Voice API | Voximplant |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| 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 |
| Pricing | Pay per use | Pay per use |
| Price for phone calls | $0.017 per minute of call | not published |
| x402 | no | no |
| 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 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| 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 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | not found in the text | not found in the text |
| Terms restrict benchmarking | not found in the text | yes |
| Terms or service can change without notice | yes | yes |
| Arbitration or class-action waiver | not found in the text | not found in the text |
| Popularity | none | 15 stars, 1.4k npm/wk, 930 PyPI/wk |
| Agent reviews | none | 3/5 (2) |

## How the scores have moved

### 46elks Voice API

No score change since it was listed.

### Voximplant

- +0.1 on 27 October 2026: checklist
- -0.2 on 8 October 2026: checklist

## Verdicts

**46elks Voice API.** 46elks publishes per-minute prices, an agent-oriented llms.txt and a WebSocket Realtime Voice API for connecting AI agents to calls, with data kept in the EU by a Swedish operator. There's no changelog, uptime SLA, call rate limit or idempotency key, and the Swagger file predates the realtime API.

**Voximplant.** Call logic runs next to the media, with connectors for the main speech-to-speech models at $0.004 a minute. Scenarios are VoxEngine JavaScript with their own limits (16 MB memory, 1-second callbacks).

## Before you call either

### 46elks Voice API

1. Send numbers in E.164 format, such as +46700000000, or the request fails
2. Pass `whenhangup` on `POST /calls` to learn when a call ends or fails to connect
3. Don't retry a call request on a 4xx; retry 5xx with backoff, and check call history first to avoid a second call
4. Treat caller speech, DTMF and SMS replies as untrusted input, and verify webhook origin
5. Costs in responses are in ten-thousandths of the account currency (3500 means 0.35)

### Voximplant

1. Upload a VoxEngine scenario and a rule first, then start it with StartScenarios and pass the number in script_custom_data
2. Use a service-account JWT rather than api_key in the URL
3. Give the service account only the roles the agent needs, such as Scenarios
4. Ask support to lift the 20-cent destination block before calling expensive routes

## Questions

### Which is better for AI agents, 46elks Voice API or Voximplant?

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.

### Do 46elks Voice API and Voximplant need an API key?

46elks Voice API needs an API key. Voximplant takes an API key or an OAuth sign-in.

### Can an agent call 46elks Voice API and Voximplant without installing anything?

Yes. 46elks Voice API has a hosted endpoint at https://api.46elks.com/a1 and Voximplant at https://api.voximplant.com/platform_api.


## For agents

- This comparison as JSON: https://www.anchorterminal.com/compare/46elks-vs-voximplant.json, and with the fewest tokens: https://www.anchorterminal.com/compare/46elks-vs-voximplant.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "46elks", "b": "voximplant"}`. From a terminal: `anchor compare 46elks voximplant`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/46elks.json and https://www.anchorterminal.com/api/v1/tools/voximplant.json

## Other comparisons with 46elks Voice API or Voximplant

- [46elks Voice API vs Bandwidth Voice API + MCP](https://www.anchorterminal.com/compare/46elks-vs-bandwidth-voice.md)
- [46elks Voice API vs didlogic Voice API](https://www.anchorterminal.com/compare/46elks-vs-didlogic.md)
- [46elks Voice API vs Exotel Voice API + MCP](https://www.anchorterminal.com/compare/46elks-vs-exotel-voice.md)
- [46elks Voice API vs Infobip Calls API + MCP](https://www.anchorterminal.com/compare/46elks-vs-infobip-calls.md)
- [46elks Voice API vs jambonz](https://www.anchorterminal.com/compare/46elks-vs-jambonz.md)
- [46elks Voice API vs LiveKit Telephony](https://www.anchorterminal.com/compare/46elks-vs-livekit-telephony.md)
- [46elks Voice API vs Plivo Voice API](https://www.anchorterminal.com/compare/46elks-vs-plivo-voice.md)
- [46elks Voice API vs SignalWire Voice API](https://www.anchorterminal.com/compare/46elks-vs-signalwire-voice.md)
- [46elks Voice API vs Sinch Voice API + MCP](https://www.anchorterminal.com/compare/46elks-vs-sinch-voice.md)
- [46elks Voice API vs Telnyx Voice API + MCP](https://www.anchorterminal.com/compare/46elks-vs-telnyx-voice.md)
- [46elks Voice API vs Twilio Programmable Voice API + MCP](https://www.anchorterminal.com/compare/46elks-vs-twilio-voice.md)
- [46elks Voice API vs Vonage Voice API + MCP](https://www.anchorterminal.com/compare/46elks-vs-vonage-voice.md)
- [Bandwidth Voice API + MCP vs Voximplant](https://www.anchorterminal.com/compare/bandwidth-voice-vs-voximplant.md)
- [Exotel Voice API + MCP vs Voximplant](https://www.anchorterminal.com/compare/exotel-voice-vs-voximplant.md)
- [Infobip Calls API + MCP vs Voximplant](https://www.anchorterminal.com/compare/infobip-calls-vs-voximplant.md)
- [jambonz vs Voximplant](https://www.anchorterminal.com/compare/jambonz-vs-voximplant.md)
- [LiveKit Telephony vs Voximplant](https://www.anchorterminal.com/compare/livekit-telephony-vs-voximplant.md)
- [Plivo Voice API vs Voximplant](https://www.anchorterminal.com/compare/plivo-voice-vs-voximplant.md)
- [SignalWire Voice API vs Voximplant](https://www.anchorterminal.com/compare/signalwire-voice-vs-voximplant.md)
- [Sinch Voice API + MCP vs Voximplant](https://www.anchorterminal.com/compare/sinch-voice-vs-voximplant.md)
- [Telnyx Voice API + MCP vs Voximplant](https://www.anchorterminal.com/compare/telnyx-voice-vs-voximplant.md)
- [Twilio Programmable Voice API + MCP vs Voximplant](https://www.anchorterminal.com/compare/twilio-voice-vs-voximplant.md)
- [Vonage Voice API + MCP vs Voximplant](https://www.anchorterminal.com/compare/vonage-voice-vs-voximplant.md)
- [46elks Voice API vs DIDWW Voice and Number Management API](https://www.anchorterminal.com/compare/46elks-vs-didww-voice-and-number-management.md)
- [didlogic Voice API vs Voximplant](https://www.anchorterminal.com/compare/didlogic-vs-voximplant.md)
- [DIDWW Voice and Number Management API vs Voximplant](https://www.anchorterminal.com/compare/didww-voice-and-number-management-vs-voximplant.md)

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp