# 46elks Voice API vs didlogic Voice API

> didlogic Voice scores 49.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-didlogic
- Markdown: https://www.anchorterminal.com/compare/46elks-vs-didlogic.md (~4,350 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

didlogic Voice API scores 49.8 (D) on agent readiness against 46elks Voice API's 44.4 (E), and leads in 5 of 7 scored categories. 46elks Voice API leads on reliability. 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
- didlogic Voice API: grade D, 49.8/100, rank #1074 of 1486. Markdown https://www.anchorterminal.com/tools/didlogic.md · JSON https://www.anchorterminal.com/api/v1/tools/didlogic.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:
- Reliability, 47 against 26

Watch for: No changelog or dated API release found

### didlogic Voice API (D)

Good for: Teams that need numbers and SIP termination in many countries and a WebSocket bridge to a voice agent.

Ahead on:
- Schema & documentation, 87 against 66
- Agent ergonomics, 57 against 51
- Security & auth, 46 against 40
- Payments & pricing, 38 against 20
- Maintenance & community, 38 against 12

Also in its favour:
- Free to start without a card

Watch for: No status page or incident history found


## Why the edge

### Maintenance & community: didlogic Voice API +26

- 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.
- didlogic Voice API (38): Release notes dated by month, the newest September 2026 (click-to-call API and WebSocket calls), about 37 to 67 days before this check (20). Entries in August and September and the July self-service API within the 90 days, dated by month only, so fewer than three dated changes can be confirmed (10). Release notes, phone and email support, and a partner programme, with no evidence read of reply times (8 of 15). No official server-side SDK, and the MCP server isn't in the official registry (0). No package to assess (0). 20+10+8+0+0 = 38.

### Reliability: 46elks Voice API +21

- 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.
- didlogic Voice API (26): Graded on the hosted API and MCP server with the hosted lines. The footer's network status page carries no components or incidents, and no other status page was found (0). No readable incident history (5). Rate limits are given only for recording lookups (one a second, one lookup a minute) (5 of 15). Those endpoints document 429 with Retry-After and X-RateLimit headers, with no backoff guidance or idempotency elsewhere, including number purchases and click-to-call (6 of 15). The site claims 99.999 per cent voice uptime, but no SLA was found in the Terms (0). The API and click-to-call carry no beta label, while the new buy experience is rolling out gradually (10). 0+5+5+6+0+10 = 26.

### Schema & documentation: didlogic Voice API +21

- 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.
- didlogic Voice API (87): Public OpenAPI 3.0.3 file with 53 operations (25). llms.txt and Markdown pages (10). Every operation is described, and the descriptions explain cross-version identifiers and when to poll, such as click-to-call progress (16 of 20). Typed request bodies with required fields and enums in the spec (12 of 15). Examples, a standard error envelope (`{"errors":{"base":[...]}}`) and 401, 403, 404 and 422 responses on most operations (12 of 15). Paths versioned v1 and v2, and release notes dated by month (12 of 15). 25+10+16+12+12+12 = 87.

### Payments & pricing: didlogic Voice API +18

- 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.
- didlogic Voice API (38): No x402, MPP or L402 (0). Per-minute call rates and monthly number prices are public by country, marked as indicative (18 of 20). Free test credit with no card, and a 30-day trial number for verified company emails (20). Signup and key creation happen in the portal (0). 0+18+20+0 = 38.

### Agent ergonomics: didlogic 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.
- didlogic Voice API (57): Call records take filters and CSV export, and numbers search by country, region and city (18 of 25). Filtering on calls and numbers, with paging not confirmed on every list (14 of 20). One error envelope with field messages and 404 for unknown ids (14 of 20). No idempotency key on purchases or click-to-call. MCP annotations weren't readable without a sign-in (3 of 20). Few required fields, no official SDK beyond the browser Voice SDK (8 of 15). 18+14+14+3+8 = 57.

### Security & auth: didlogic Voice API +6

- 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.
- didlogic Voice API (46): Revocable bearer keys created in the portal, each with full account access by the vendor's own warning. MCP OAuth mints a separate key per sign-in (18 of 30). SIP accounts can be limited to allowed IPs, with no read-only key and no confirmation on purchases (6 of 20). Caller audio and SMS are untrusted, and no prompt-injection guidance was found (3 of 15). Call detail records, transaction history and risk-check logs through the API, with no audit log of API calls (7 of 15). ISO/IEC 27001:2022 and ISO 9001 certificates from TÜV AUSTRIA Hellas with registration numbers. No security.txt or bug bounty found (12 of 20). 18+6+3+7+12 = 46.

## Score by category

| Category | Weight | 46elks Voice API | didlogic Voice API | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 47 | 26 | 46elks Voice API +21 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 66 | 87 | didlogic Voice API +21 |
| Agent ergonomics | 13% (16.2 this run) | 51 | 57 | didlogic Voice API +6 |
| Security & auth | 14% (17.5 this run) | 40 | 46 | didlogic Voice API +6 |
| Payments & pricing | 10% (12.5 this run) | 20 | 38 | didlogic Voice API +18 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 12 | 38 | didlogic Voice API +26 |
| Transparency & trust | 7% (8.8 this run) | 62 | 58 | 46elks Voice API +4 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **44.4 · E** | **49.8 · D** | |

## Facts side by side

| Fact | 46elks Voice API | didlogic Voice API |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | 46elks AB | DID Logic PTE. LTD. |
| Hosted endpoint | `https://api.46elks.com/a1` | `https://mcp.didlogic.com/mcp` |
| Transports | HTTP, websocket | HTTP, websocket, Streamable HTTP |
| Auth | API key | OAuth or key |
| Pricing | Pay per use | Pay per use |
| Price for phone calls | $0.017 per minute of call | $0.0175 per minute of call |
| 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 | Proprietary service under the didlogic Terms of Service |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | none | 2026-09-30 |
| Terms last updated | 2024-03-12 | no date given |
| Privacy policy last updated | 2018-05-20 | no date given |
| 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 | not found in the text |
| Terms or service can change without notice | yes | not found in the text |
| Arbitration or class-action waiver | not found in the text | yes |

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

**didlogic Voice API.** didlogic pairs a public OpenAPI file with 53 described operations, published per-minute and number prices and free test credit with WebSocket calls for voice AI and a remote MCP server. There's no status page or SLA, keys carry full account access, and purchases and calls have no idempotency key.

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

### didlogic Voice API

1. Create the key under API & Webhooks in the portal; ignore the older get-started line about asking an account manager
2. Confirm with the user before `POST /api/v2/numbers/purchase` or click-to-call; both spend the prepaid balance with no idempotency key
3. For WebSocket calls, set `a_type: stream` and implement didlogic's message protocol on your endpoint
4. Back off on 429 from recording endpoints using Retry-After
5. Expect the MCP server only on the Plus plan

## Questions

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

didlogic Voice API scores 49.8 (D) on agent readiness against 46elks Voice API's 44.4 (E), and leads in 5 of 7 scored categories. 46elks Voice API leads on reliability.

### Which is cheaper for phone calls, 46elks Voice API or didlogic Voice API?

They cost about the same, $0.017 per minute of call for 46elks Voice API and $0.0175 per minute of call for didlogic Voice API. These are the vendors' published prices for the job.

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

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

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

Yes. 46elks Voice API has a hosted endpoint at https://api.46elks.com/a1 and didlogic Voice API at https://mcp.didlogic.com/mcp.


## For agents

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

## Other comparisons with 46elks Voice API or didlogic Voice API

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