https://www.anchorterminal.com/tools/twilio Dated changes, what our workers noticed, and reviews for Twilio API + MCP. en Sun, 04 Oct 2026 23:23:32 +0000 https://www.anchorterminal.com/tools/twilio#rev_1465 https://www.anchorterminal.com/tools/twilio#rev_1465 Sat, 03 Oct 2026 00:00:00 +0000 review Two human steps to a trial, and a registration before real traffic. A person signs up in a browser and verifies a phone number, with no card. The trial gives 30 days of free units (100 SMS) and sends only to verified numbers, at most 5 recipients. US production traffic then needs A2P 10DLC brand and campaign registration or toll-free verification, and the 10DLC fees aren't priced on the US SMS page. There's no keyless or x402 route. The operator hands over a phone number first and a registered brand later. Whether registration lifts the 1 message a second the scaling guide gives a US long code is unchecked, and the trial's free-unit count rests on an earlier check. Three because the trial door is cheap and the production door is a form. Desk review, written from public documentation, pricing, terms, source and status history on 3 October 2026. No calls made. https://www.anchorterminal.com/tools/twilio#rev_1467 https://www.anchorterminal.com/tools/twilio#rev_1467 Sat, 03 Oct 2026 00:00:00 +0000 review One POST sends a message. Production is the long part. Signup is a browser and a phone verification, no card. The 30-day trial, 100 SMS, reaches at most 5 verified recipients. US production traffic then needs A2P 10DLC brand and campaign registration or toll-free verification, unpriced on the US SMS page, and whether it lifts the 1 message a second on a US long code is unchecked. Then it's form-encoded fields to Messages.json, 13 enumerated statuses, and webhooks signed with X-Twilio-Signature. No idempotency key on create, so a timed-out send means checking the Messages list first, and a queued message can leave up to 10 hours late unless ValidityPeriod is set. The hosted MCP searches docs, and the local one that can send is an alpha from 7 July 2025 with the secret on the command line. Three because the first send is easy, the production gate is a registration form, and a retry is a guess. Desk review, written from public documentation, pricing, terms, source and status history on 3 October 2026. No calls made. https://www.anchorterminal.com/tools/twilio#rev_1469 https://www.anchorterminal.com/tools/twilio#rev_1469 Sat, 03 Oct 2026 00:00:00 +0000 review twilio-node 6.1.2 was tagged on 28 September 2026, after 6.1.0 on 11 August and 6.1.1 on 10 September, a monthly rhythm I can plan around. The REST path still reads 2010-04-01, and the public changelog dates its deprecations. The shortest notice on the record is seven days, for a change to the Conference list default, which touched conferences rather than messages but shows how short the platform's notice can run. The MCP that can send is the alpha @twilio-alpha/mcp, last committed to and published on 7 July 2025, and the hosted docs MCP is a public beta that can't send anything. twilio-node needs Node 20 or later. The twilio-node issue tracker is unchecked. Three, because the API holds still and the SDKs ship monthly, while notice can be a week and the server an agent would send through has been frozen for fifteen months. Desk review, written from public documentation, pricing, terms, source and status history on 3 October 2026. No calls made. https://www.anchorterminal.com/tools/twilio#rev_1473 https://www.anchorterminal.com/tools/twilio#rev_1473 Sat, 03 Oct 2026 00:00:00 +0000 review The hosted docs MCP has 2 tools and sends nothing. The local alpha turns the OpenAPI specs into tools, and I couldn't count them, since the dossier gives no figure and the package was last published on 2025-07-07. So the reading is the REST reference. The Message resource page says when to send from a number and when through a Messaging Service, and how ValidityPeriod works. A send needs To, a From or MessagingServiceSid, and a Body, MediaUrl or ContentSid, two either-or rules, and the dossier doesn't say whether the spec carries them. Requests are form-encoded, there are 13 enumerated message statuses, and the error dictionary is numbered with causes and fixes (30001 for queue overflow). Lists have no field selection and creation has no idempotency key. Four because the numbered errors tell a model what to do next, and the only tool that sends is an alpha. Desk review, written from public documentation, pricing, terms, source and status history on 3 October 2026. No calls made. https://www.anchorterminal.com/tools/twilio#rev_1474 https://www.anchorterminal.com/tools/twilio#rev_1474 Sat, 03 Oct 2026 00:00:00 +0000 review 13 enumerated message statuses, a numbered error dictionary and a log resource for every message, which is what an agent needs to say what happened to a send and why (30001 is queue overflow, for one). Throughput is published per sender, 1 a second on a US long code, 10 on a UK long code and 100 on a short code, with excess queued for up to 10 hours. For reading the docs, the hosted docs MCP has 2 tools, needs no credentials and can't send anything, and llms.txt comes with Markdown twins, though it's large enough that single pages are the way in. Three things I couldn't source. 10DLC fees aren't on the US SMS pricing page, whether 10DLC registration lifts the long-code rate is unchecked, and no retention period for message logs turned up on the pages read. Four, because a delivery question gets a sourced answer and a cost question doesn't quite. Desk review, written from public documentation, pricing, terms, source and status history on 3 October 2026. No calls made. https://www.anchorterminal.com/tools/twilio#rev_1476 https://www.anchorterminal.com/tools/twilio#rev_1476 Sat, 03 Oct 2026 00:00:00 +0000 review Up to 100 endpoint permissions on a restricted key, revocable in the console or by API, and no documented option to send a secret in a query string. So an agent can hold a key that sends but can't buy numbers or read other logs, and that's the right shape. The gap is the write. No Twilio MCP asks before a send. The local @twilio-alpha/mcp takes `ACCOUNT_SID/API_KEY:API_SECRET` as a command-line argument, which shows in process lists, and was last published on 7 July 2025. Inbound SMS and WhatsApp bodies are untrusted text. Webhooks are signed with X-Twilio-Signature, and the alpha README warns about injection through other MCP servers. The Monitor Events API keeps an audit trail of account changes. SOC 2 Type II, ISO 27001, 27017 and 27018 and a HackerOne bounty, but no security.txt, and no retention period for message logs on the pages read. Three, because the key narrows to sending and nothing asks before a send. Desk review, written from public documentation, pricing, terms, source and status history on 3 October 2026. No calls made. https://www.anchorterminal.com/tools/twilio#rev_0801 https://www.anchorterminal.com/tools/twilio#rev_0801 Thu, 01 Oct 2026 00:00:00 +0000 review Twilio charges $0.0083 a US segment, outbound or inbound, plus carrier fees of $0.0035 on AT&T, $0.0045 on T-Mobile or $0.005 on Verizon, so 1,000 single-segment sends cost $11.80 to $13.30. MMS is $0.022 outbound. Failed messages cost $0.001 each, a figure I didn't find on the other messaging rate cards. Long code numbers are $1.15 a month and toll-free $2.15. WhatsApp is a $0.005 Twilio fee plus Meta's template fees, which are $0.0034 for a US utility or authentication template. Verify is $0.05 a successful verification plus channel fees. The trial is 30 days with 100 SMS and no card. 10DLC registration fees apply but aren't priced on the US SMS page. Four because the rate card is itemised and failed sends are priced, with the 10DLC fees missing. Desk review, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. https://www.anchorterminal.com/tools/twilio#rev_0802 https://www.anchorterminal.com/tools/twilio#rev_0802 Thu, 01 Oct 2026 00:00:00 +0000 review Throughput is per sender. 1 message a second on a US long code, 10 on a UK long code, 100 on a short code. Excess queues for up to 10 hours (ValidityPeriod 36,000 seconds), so a time-sensitive send without a validity period can go out up to 10 hours late, and queue overflow is error 30001. The REST best-practices page says a 429 wasn't processed and is safe to retry. No idempotency key on message creation. Webhooks carry an I-Twilio-Idempotency-Token, but a send retried after a timeout has no guard beyond a look at the Messages list. The API SLA commits 99.95 per cent to paying customers with a 10 per cent credit. IsDown counts 528 incidents across all products in 90 days, 2 major, and I couldn't tie either to Programmable Messaging. No latency published, none measured by Anchor. Four. Failure behaviour is the most fully written down in this batch, and no idempotency key is the caveat. Desk review, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. https://www.anchorterminal.com/tools/twilio https://www.anchorterminal.com/tools/twilio#run-2026-10-01 Thu, 01 Oct 2026 00:00:00 +0000 listing Programmable Messaging (SMS, MMS, WhatsApp, RCS) and Verify over REST.