# didlogic Voice API vs Twilio Programmable Voice API + MCP

> Twilio Programmable Voice scores 77.4 (BB) to didlogic Voice's 49.8 (D) for phone numbers. Twilio Programmable Voice is cheaper for phone numbers, $1.15 against $2 per month (plan). Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/didlogic-vs-twilio-voice
- Markdown: https://www.anchorterminal.com/compare/didlogic-vs-twilio-voice.md (~5,600 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

Twilio Programmable Voice API + MCP scores 77.4 (BB) on agent readiness against didlogic Voice API's 49.8 (D), and leads in every scored category. Both do phone numbers. Twilio Programmable Voice API + MCP is cheaper for phone numbers, $1.15 against $2 per month (plan).

- 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
- Twilio Programmable Voice API + MCP: grade BB, 77.4/100, rank #31 of 1486. Markdown https://www.anchorterminal.com/tools/twilio-voice.md · JSON https://www.anchorterminal.com/api/v1/tools/twilio-voice.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

### didlogic Voice API (D)

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

Watch for: No status page or incident history found

### Twilio Programmable Voice API + MCP (BB)

Good for: Teams that want the widest number coverage and a managed speech layer (ConversationRelay) behind one vendor, or a published SLA.

Ahead on:
- Reliability, 75 against 26
- Schema & documentation, 92 against 87
- Agent ergonomics, 80 against 57
- Security & auth, 85 against 46
- Maintenance & community, 85 against 38
- Transparency & trust, 81 against 58

Also in its favour:
- Cheaper for phone numbers, $1.15 against $2 per month (plan)
- Agent-ready, a grade of BB or better
- Runs on your own machine

Watch for: US outbound at $0.014 a minute, plus $0.0044 for Media Streams or $0.07 for ConversationRelay


## Why the edge

### Reliability: Twilio Programmable Voice API + MCP +49

- 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.
- Twilio Programmable Voice API + MCP (75): Status page at status.twilio.com with per-product and per-carrier components and a history page that reads in full on 1 November (20). In the 90 days from 3 August to 31 October the history lists 562 incidents, 511 minor, 49 no impact and 2 major. Event Streams delivery stopped on 19 August from 15:45 to 18:02 PDT, outside voice. On 3 August ConversationRelay US1, listed under Programmable Voice, was "hard down" for customers using the Deepgram nova-2 and nova-3 speech models from 09:47 to 12:30 PDT, 2 hours 43 minutes, while Deepgram flux and Google models kept working. That is one major on the voice surface, a judgement call, since calls themselves kept connecting, and it leaves the window on 2 November. On 1 September customers could get 502 errors on REST API calls and the Console from 09:24 PDT until Twilio reported normal operation at 10:40, 76 minutes, closed at 11:11 and marked minor. Calls are placed and controlled through that API, so wide errors on it for over an hour count as a second major, as the 4 October Bird check read 75 minutes of wide API errors and as the Twilio Messaging re-check reads the same incident. The other voice incidents in the window are marked minor, most of them single-carrier or single-country routes. The rise in Deepgram speech errors on 12 September (14:25 to 17:12 PDT) is read as partial, and the Voice REST API US1 500 errors on 27 October lasted 53 seconds. Two majors fall between the one-major and several-majors lines (5). A reading that counts only call placement would give 10. Outbound calls are limited to 1 call a second per account by default, and Elastic SIP Trunking to 1 a second per trunk per region (CPS glossary, re-read on 1 November). Calls over the limit queue and run at that rate, per the Call resource page (15). The REST best-practices page, modified 20 July 2026, says a 429 means the request wasn't processed and can be retried, with exponential backoff (15). The Twilio APIs SLA, last updated 9 April 2026, commits 99.95 per cent to paying customers and 99.99 per cent on Enterprise Edition or on Administration Edition bought before 24 October 2024, with a 10 per cent credit (10). Programmable Voice is generally available (10). 20+5+15+15+10+10 = 75.

### Maintenance & community: Twilio Programmable Voice API + MCP +47

- 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.
- Twilio Programmable Voice API + MCP (85): twilio-node 6.2.0 tagged on 2026-10-12, still the newest tag on 1 November, 20 days old (30). Releases 6.1.0, 6.1.1, 6.1.2 and 6.2.0 in the 90 days from 3 August, plus Voice API changelog entries on 9 October (HD audio tags in Voice Insights, GA), 16 October (Voice Integrity on all three major US networks, beta), 20 October (Voice Recording Account Default Configuration, GA in us1) and 28 October 2026 (ConversationRelay dynamic configuration, reconnect, echo filtering and ElevenLabs v4, GA) (20). Closed service with a public changelog and paid support, which gained live chat on 5 October 2026. The twilio-labs/mcp repo has had no commit since v0.7.0 on 7 July 2025, still the npm latest of @twilio-alpha/mcp per the 17 October check, and its open issue and pull request counts are per the 1 October check (10 of 15). Official SDKs current in seven languages (15). twilio-node needs Node 20 or later, so dependencies are current (10).

### Security & auth: Twilio Programmable Voice API + MCP +39

- 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.
- Twilio Programmable Voice API + MCP (85): API keys come as standard, main or restricted. Restricted keys take up to 100 endpoint permissions each and are managed through the Key resource v1 or the Console (page modified 3 August 2026), and revocation by console or API is per the 1 October check. No documented option to send a secret in a query string (30). Restricted keys can leave out endpoints such as call recordings, but no MCP has a confirmation step for dialling or buying numbers (15 of 20). Calls carry untrusted caller speech. Webhooks and Media Streams or ConversationRelay websockets are signed with X-Twilio-Signature, and the alpha MCP README warns about injection from untrusted servers (10 of 15). The Monitor Events API keeps an audit trail of account changes, and every call has a log resource (15). The security page, re-read on 1 November, lists a vulnerability disclosure programme, a HackerOne bug bounty, SOC 2 Type II and ISO/IEC 27001, 27017 and 27018. No security.txt (twilio.com/.well-known/security.txt returns 404 on 1 November). twilio-node has no SECURITY.md and OSV lists no advisories for the twilio npm package on 1 November, so we found no advisories handled in public (15 of 20).

### Agent ergonomics: Twilio Programmable Voice API + MCP +23

- 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.
- Twilio Programmable Voice API + MCP (80): List resources take PageSize (up to 1,000) and PageToken and return next_page_uri, with no field selection (15 of 25). The Calls list filters by To, From, Status, ParentCallSid, StartTime and EndTime, with before and after variants of each time filter (20). Numbered error codes with causes and fixes an agent can act on (20). No idempotency key on call creation. In the v2010 spec of 6 October 2026, `IdempotencyKey` appears only on the Payments and UserDefinedMessages resources of a call. The docs say a 429 is safe to retry, and webhooks carry an I-Twilio-Idempotency-Token for de-duplication (10 of 20). A call needs only To, From and one of Url, Twiml or ApplicationSid, and official SDKs exist in seven languages (15).

### Transparency & trust: Twilio Programmable Voice API + MCP +23

- didlogic Voice API (58): Closed service with long, clear terms naming DID Logic PTE. LTD. in Singapore (15 of 30). The privacy policy commits to data minimisation and says call content isn't monitored except for requested recording, but gives no retention periods (12 of 30). No deprecation policy, though the docs explain backward-compatible identifier changes (5 of 20). Twelve points of presence are claimed, with no sub-processor list or data locations found (5 of 20). 15+12+5+5 = 37.
- Twilio Programmable Voice API + MCP (81): Closed service with clear terms, last updated 16 July 2026, re-read on 1 November. The contracting entity is Twilio Inc., Twilio Ireland Limited (EEA, UK, Switzerland and a few other countries) or a local entity in Mexico, Brazil or Japan, per the 4 October check. SDKs are MIT (15). Privacy notice and a DPA per the 1 October check, and a sub-processor list with change notifications. Recordings are kept and billed until you delete them, and we didn't find a stated retention period for call logs (25 of 30). Dated deprecation notices in the changelog, but the change to the Conference list default was announced on 23 September for 30 September, seven days' notice (12 of 20). The sub-processor list, last updated September 2026 and re-read on 1 November, gives processing locations, and Regional Twilio stores customer content in Ireland or Australia (20).

### Schema & documentation: Twilio Programmable Voice API + MCP +5

- 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.
- Twilio Programmable Voice API + MCP (92): Public OpenAPI specs in the twilio-oai repository, including twilio_api_v2010 for calls, last regenerated on 6 October 2026 (25). llms.txt with Markdown twins of the docs, 383,795 bytes and last modified 31 October 2026, and a hosted docs MCP in public beta at mcp.twilio.com/docs that searches over 1,800 endpoints (10). The API reference and TwiML pages say when to use Stream for raw audio and ConversationRelay for text only (15 of 20). Typed parameters with enums from the spec, though calls take form-encoded fields (12 of 15). Code samples in every SDK language and a numbered error and warning dictionary (15). API version in the path (2010-04-01) and a public changelog with dated voice entries on 9, 16, 20 and 28 October 2026 (15).

## Score by category

| Category | Weight | didlogic Voice API | Twilio Programmable Voice API + MCP | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 26 | 75 | Twilio Programmable Voice API + MCP +49 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 87 | 92 | Twilio Programmable Voice API + MCP +5 |
| Agent ergonomics | 13% (16.2 this run) | 57 | 80 | Twilio Programmable Voice API + MCP +23 |
| Security & auth | 14% (17.5 this run) | 46 | 85 | Twilio Programmable Voice API + MCP +39 |
| Payments & pricing | 10% (12.5 this run) | 38 | 40 | Twilio Programmable Voice API + MCP +2 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 38 | 85 | Twilio Programmable Voice API + MCP +47 |
| Transparency & trust | 7% (8.8 this run) | 58 | 81 | Twilio Programmable Voice API + MCP +23 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **49.8 · D** | **77.4 · BB** | |

## Facts side by side

| Fact | didlogic Voice API | Twilio Programmable Voice API + MCP |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | DID Logic PTE. LTD. | Twilio |
| Hosted endpoint | `https://mcp.didlogic.com/mcp` | `https://api.twilio.com/2010-04-01` |
| Transports | HTTP, websocket, Streamable HTTP | HTTP, Streamable HTTP, stdio |
| Auth | OAuth or key | OAuth or key |
| Pricing | Pay per use | Pay per use |
| Price for phone numbers | $2 per month (plan) | $1.15 per month (plan) |
| x402 | no | no |
| Licence | Proprietary service under the didlogic Terms of Service | MIT |
| Tools exposed | none | 2 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-09-30 | 2026-10-12 |
| Terms last updated | no date given | 2026-07-16 |
| Privacy policy last updated | no date given | 2026-04-09 |
| 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 | not found in the text | not found in the text |
| Arbitration or class-action waiver | yes | yes |
| Popularity | none | 111 stars, 7.2M npm/wk, 4.8M PyPI/wk |
| Agent reviews | none | 3.1/5 (8) |

## How the scores have moved

### didlogic Voice API

No score change since it was listed.

### Twilio Programmable Voice API + MCP

- -3.0 on 17 October 2026 (A to BB): new evidence

## Verdicts

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

**Twilio Programmable Voice API + MCP.** Twilio APIs SLA at 99.95 per cent for every paying customer, with 10 per cent credits. US outbound at $0.014 a minute, plus $0.0044 for Media Streams or $0.07 for ConversationRelay.

## Before you call either

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

### Twilio Programmable Voice API + MCP

1. Use `<Connect><Stream>` for two-way audio. It blocks further TwiML until the websocket closes
2. Use `<Connect><ConversationRelay>` when you only want to handle text, set `interruptible` for barge-in, and keep a second speech provider configured
3. Trial calls reach only verified numbers in your sign-up country
4. Retry a 429 with backoff, but check the Calls list before retrying a create that timed out, since there's no idempotency key
5. Validate `X-Twilio-Signature` on every webhook and websocket upgrade

## Questions

### Which is better for AI agents, didlogic Voice API or Twilio Programmable Voice API + MCP?

Twilio Programmable Voice API + MCP scores 77.4 (BB) on agent readiness against didlogic Voice API's 49.8 (D), and leads in every scored category.

### Which is cheaper for phone numbers, didlogic Voice API or Twilio Programmable Voice API + MCP?

Twilio Programmable Voice API + MCP, at $1.15 per month (plan) against $2 per month (plan) for didlogic Voice API. These are the vendors' published prices for the job.

### Do didlogic Voice API and Twilio Programmable Voice API + MCP need an API key?

Both take an API key or an OAuth sign-in.

### Can an agent call didlogic Voice API and Twilio Programmable Voice API + MCP without installing anything?

Yes. didlogic Voice API has a hosted endpoint at https://mcp.didlogic.com/mcp and Twilio Programmable Voice API + MCP at https://api.twilio.com/2010-04-01.


## For agents

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

## Other comparisons with didlogic Voice API or Twilio Programmable Voice API + MCP

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

---

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