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

> Telnyx Voice scores 74.3 (BB) to 46elks Voice's 44.4 (E) for phone calls. Telnyx Voice is cheaper for phone calls, $0.002 against $0.017 per minute of call. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/46elks-vs-telnyx-voice.md (~5,000 tokens) · this version ~2,930 tokens · JSON https://www.anchorterminal.com/compare/46elks-vs-telnyx-voice.json · canonical https://www.anchorterminal.com/compare/46elks-vs-telnyx-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)

Telnyx Voice API + MCP scores 74.3 (BB) on agent readiness against 46elks Voice API's 44.4 (E), and leads in every scored category. Both do phone calls. Telnyx Voice API + MCP is cheaper for phone calls, $0.002 against $0.017 per minute of call.

- 46elks Voice API: E 44.4, rank #1203 of 1486 · https://www.anchorterminal.com/tools/46elks.min.md
- Telnyx Voice API + MCP: BB 74.3, rank #87 of 1486 · https://www.anchorterminal.com/tools/telnyx-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.
- Telnyx Voice API + MCP, good for Cost-sensitive US outbound voice agents and for agents that must onboard and pay without a person. Ahead on Reliability, 75 against 47; Schema & documentation, 93 against 66; Agent ergonomics, 90 against 51; Security & auth, 45 against 40; Payments & pricing, 65 against 20; Maintenance & community, 83 against 12; Transparency & trust, 72 against 62. Also Cheaper for phone calls, $0.002 against $0.017 per minute of call; Agent-ready, a grade of BB or better; Runs on your own machine.

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

| Fact (where they differ) | 46elks Voice API | Telnyx Voice API + MCP |
| --- | --- | --- |
| Vendor | 46elks AB | Telnyx |
| Hosted endpoint | `https://api.46elks.com/a1` | `https://api.telnyx.com/v2` |
| Transports | HTTP, websocket | HTTP, Streamable HTTP, stdio |
| Auth | API key | OAuth or key |
| Price for phone calls | $0.017 per minute of call | $0.002 per minute of call |
| x402 | no | payer tooling only |
| 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 |
| Tools exposed | none | 6 |
| Read-only variant documented | no | yes |
| MCP registry | not listed | `io.github.team-telnyx/telnyx` |
| Last release | none | 2026-10-28 |
| Terms last updated | 2024-03-12 | no date given |
| Privacy policy last updated | 2018-05-20 | 2026-03-01 |
| 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 | 197 stars, 417k npm/wk, 179k PyPI/wk |
| Agent reviews | none | 3.5/5 (8) |

Why the edge:
- Maintenance & community, Telnyx Voice API + MCP +71: 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.); Telnyx Voice API + MCP 83 (telnyx-node v7.29.0 tagged on 2026-10-28, after v7.27.0 and v7.28.0 on 21 and 22 October (30). 17 telnyx-node releases in the 90 days to 1 November, from v7.13.0 on 4 August to v7.29.0 (20). Closed service with public release notes, the newest dated 30 October 2026 (voice entries on 20 October for AssemblyAI keyterms on Voice AI Assistants and 28 October for Pipecat agents on Telnyx Edge), and a support channel. We couldn't read GitHub issue replies (8 of 15). Current official SDKs, and the MCP is in the official registry as io.github.team-telnyx/telnyx, though the newest registry version is still 6.29.3 of March 2026 (15). Release automation runs in CI (10). 30 + 20 + 8 + 15 + 10 = 83.)
- Payments & pricing, Telnyx Voice API + MCP +45: 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.); Telnyx Voice API + MCP 65 (x402 exists on Telnyx's own API at /v2/x402/credit_account (USDC on Base), with MPP at /v2/machine-payments/account-credit, but both top up account credit rather than pay per call. The x402 skill says x402 is behind a per-account feature flag and returns 403 where it isn't enabled, while the MPP skill names no such flag. Per-payment limits are stated only in 422 errors (25 of 40). Per-minute voice, SIP, number and add-on rates published without a login, also as pricing.md (20). No free credit, a new account starts at zero (0). An agent can sign up through /v2/bot_challenge and /v2/bot_signup, collect the email link, mint a key at /v2/api_keys and fund the account by MPP with Tempo USDC, or x402 where enabled, with no browser (20).)
- Agent ergonomics, Telnyx Voice API + MCP +39: 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.); Telnyx Voice API + MCP 90 (List endpoints take page size and number, with no field selection (15 of 25). Filters and pagination on list endpoints (20). JSON errors with a code, title and detail, and a documented code list (20). Call commands take a command_id, and Telnyx ignores a repeat with the same command_id on the same call, so a retried command is safe (20). Official SDKs in Node, Python and more, and a call needs connection_id, to and from (15).)
- Reliability, Telnyx Voice API + MCP +28: 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.); Telnyx Voice API + MCP 75 (Status page at status.telnyx.com (run on incident.io) with a readable incident feed and history (20). Two incidents Telnyx itself marked major hit voice or the API in the 90 days to 1 November. One-way or degraded audio on inbound and outbound calls from 16:00 UTC on 10 September, marked resolved at 01:43 on 11 September, and intermittent 5XX responses across API endpoints and portal 2FA login for about 2 hours on 23 September. Minor ones included one-way or dead air audio, call drops and missing recordings on 7 August (partial outage, mitigated after 34 minutes), delayed call recordings and conferences on 9 and 10 September, 1 hour 18 minutes of API v2 processing delays on 13 October, and on 28 October about an hour of 503s on credential creation only (POST /v2/telephony_credentials). On 21 October, between about 18:17 and 19:20 UTC, a network fault caused intermittent failures across services, with some outbound call setups failing and Call Control dials intermittently returning 500. Telnyx posted it two days later with no impact level, and the portal's outages totalled about 20 minutes. Intermittent errors on some calls read as partial, so it isn't counted as a third major. Two majors fall between the checklist's one major and several, so we gave half the one-major mark (5). Outbound dials are capped at 30 a second, counted over fixed 5-second windows of 150 per region, re-read on 1 November (15). The rate-limiting page documents 429 with error code 10011, Retry-After and x-ratelimit headers, bounded exponential backoff with jitter, and retrying only safely repeatable operations, per the 17 October check, not re-read on 1 November (15). A machine-readable SLA at telnyx.com/ai/sla.json states 99.99 per cent for core voice and messaging, with credits of 10, 25 and 50 per cent below 99.99, 99.9 and 99.0. pricing.md lists a custom SLA on committed plans and credits on Enterprise, so who qualifies is unclear (10). Voice API is generally available (10). 20 + 5 + 15 + 15 + 10 + 10 = 75.)
- Schema & documentation, Telnyx Voice API + MCP +27: 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.); Telnyx Voice API + MCP 93 (Public OpenAPI 3 spec in the team-telnyx/openapi repository, synced from Telnyx's internal repository on 16 October 2026 (25). llms.txt on both developers.telnyx.com and telnyx.com, with Markdown doc pages and machine-readable pricing (10). One reference page per call command with purpose and parameters, but little guidance on when not to use a command (15 of 20). Typed JSON bodies with enums, for example the stream track and bidirectional mode (13 of 15). Request examples per command and a page of API error codes (15). Versioned /v2 path and public release notes (15).)
- Transparency & trust, Telnyx Voice API + MCP +10: 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.); Telnyx Voice API + MCP 72 (Closed service with clear terms (15). Privacy policy covering retention, a Telnyx DPA referenced from the sub-processor page, and a list of sub-processors re-read on 17 October. We didn't find stated retention periods for call records and recordings (25 of 30). No deprecation policy or dated deprecation notices found for voice (0 of 20). Each sub-processor is listed with its entity, address, products and data categories, AI sub-processors are separated and apply only when enabled, and the page has change alerts (15 of 20).)