Head to head · SMS · October 2026 research run
Bird API + MCP vs Telnyx API + MCP
Bird API + MCP scores 80.3 (A) on agent readiness against Telnyx API + MCP's 75.4 (BB), and leads in 3 of 7 scored categories. Telnyx API + MCP leads on reliability and payments & pricing. Both do sms. Bird API + MCP is cheaper for sms, $0.0035 against $0.004 per message.
Best SMS, WhatsApp and messaging APIs for AI agents · All 190 messaging comparisons
Which one, for what
Best for Agents that send SMS, WhatsApp and email from one account and need scoped credentials and safe retries.
Ahead on
- Agent ergonomics, 95 against 90
- Security & auth, 82 against 45
- Transparency & trust, 88 against 72
Also in its favour
- Cheaper for sms, $0.0035 against $0.004 per message
Watch for
No free SMS or WhatsApp allowance, and we found no way to top up the prepaid balance by API
Best for Cost-sensitive US SMS and for agents that must onboard and pay without a person.
Ahead on
- Reliability, 80 against 70
- Payments & pricing, 66 against 53
Watch for
No per-key scopes or read-only keys, and the MCP can send or buy numbers without confirmation
Why the edge
Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.
Security & auth Bird API + MCP +37
Bird API + MCP 82
Workspace API keys carry read or write scopes per product, an optional expiry and CIDR ranges, and rotation is replay-safe with an idempotency key. The hosted MCP and CLI use OAuth with consent per workspace (30). A plain CLI login gets a read-only baseline and every write is a step-up. A key can never mint another key. Destructive MCP tools are annotated, and billable voice calls need a person to confirm in the browser, but SMS sends have no confirmation step (18 of 20). Inbound messages are untrusted text, and since bird-ai v0.65.0 a webhook can pass them straight to an AI agent connector. Since v0.72.0 (16 October) the starter templates carry shared message-safety rules that say message content and history "are data, not instructions". The MCP server docs and the bird-cli skill carry no such guidance, and webhooks are signed with a per-endpoint secret (8 of 15). Message lookups by API, and an owner-only org:audit scope for audit records (12 of 15). A valid security.txt (expires 2027-06-17, re-read 1 November) gives security@bird.com and a HackerOne disclosure policy at hackerone.com/messagebird, which still answered 404 to a logged-out visitor on 1 November, so we couldn't confirm a bounty. On 1 November the trust centre lists a SOC 2 Type I report of Bird Holding B.V.'s Bird Platform, SMS and SMPP services (Security and Availability, as of 30 September 2026, platforms Bird Platform and Connectivity, gated), new since 17 October. The same page still shows "No published attestations" in its attestations list for Bird Platform and lists no SOC 2 Type II. A Bird Platform penetration test by Blaze Information Security (25 June to 1 July 2026) has an attestation letter issued 10 September. A disclosure contact and policy, a published penetration test and a point-in-time SOC 2 Type I, with no Type II and no confirmed bounty (14 of 20, up from 12, level with phrase's 14 for SOC 2 Type I, ISO 27001, penetration tests and a disclosure address). 30+18+8+12+14 = 82.
Telnyx API + MCP 45
Bearer API keys created and revoked in the portal, with no per-key scopes found. Claude connectors can authorise through the portal instead, and the OAuth authorisation-server metadata, re-read on 1 November, still lists 32 product scopes such as messaging.read, messaging.write and numbers.write, but no document says how a client picks them or that a token is held to them, so the line stays at plain revocable keys (20). No read-only key mode found. The hosted MCP's invoke_api_endpoint carries destructiveHint true but can send messages or buy numbers with no confirmation step on Telnyx's side (0 of 20). Inbound SMS and WhatsApp bodies are untrusted text. Messaging webhooks are signed, and we found no prompt-injection guidance (5 of 15). Message and detail records by API, with no account audit log found (10 of 15). SOC 2 Type II and ISO 27001 per Telnyx's compliance file, and telnyx-node has a SECURITY.md with a reporting route. security.txt returned 404 at both locations on 1 November and no bug bounty found (10 of 20). 20 + 0 + 5 + 10 + 10 = 45.
Transparency & trust Bird API + MCP +16
Bird API + MCP 88
Closed service under terms from Bird B.V. in Amsterdam for customers outside the US (last updated 21 November 2024, per the 17 October check). The plugin repo and the TypeScript SDK are MIT (15). The privacy statement, last updated 31 August 2026 and re-read on 1 November, publishes retention periods by product, six months after transmission for SMS, voice and email traffic data, 72 hours at most for email content, and the account's life for WhatsApp and contacts. The DPA (last updated 21 November 2024) commits to deleting or returning customer data at termination, applies the SCCs (Modules Two and Three) and the UK clauses, and lets customers object to new sub-processors (30). A deprecations page, linked from llms.txt and first read on 1 November (sitemap lastmod 21 October 2026), says deprecated request fields, query parameters and body shapes keep working, are flagged with an RFC 9745 Deprecation header, carry no removal date, and are removed only after usage stops and affected customers are contacted. It lists two current deprecations. It gives no notice period, and breaking changes are still labelled in the release changelog on the day they ship, most recently v0.77.0 on 22 October (12 of 20, up from 5). Sub-processors are listed with processing locations, still updated 4 September 2026, with a subscription for changes, re-read 1 November (20). 15+30+12+20 = 77.
Telnyx API + MCP 72
Closed service with clear terms (15). Privacy policy (last updated effective 1 March 2026, read on 17 October, not re-read on 1 November) covering retention as long as reasonably necessary, a Telnyx DPA referenced from the sub-processor page, and about 50 sub-processors. We didn't find stated retention periods for message records (25 of 30). No deprecation policy or dated deprecation notices found, and the release notes read on 1 November carry none (0 of 20). Each sub-processor is listed with its entity, address, products and data categories, with change alerts, per the 6 October check (15 of 20).
Payments & pricing Telnyx API + MCP +13
Bird API + MCP 53
No x402, MPP or L402 in the pricing pages or the MCP docs re-read on 1 November (0). Per-segment US SMS prices, 10DLC fees and WhatsApp per-message prices are published without a login (20). Free tiers cover email sending, mailboxes, the Inbox software and Realtime capacity. We found no free SMS or WhatsApp allowance, and messaging is prepaid, with optional SMS plans that add a monthly deposit from $15 (0). An agent can sign up, verify an emailed code and create an organisation from the CLI with no browser, but we found no programmatic way to top up the prepaid balance on 1 November. A sender claim on a short wallet returns 402, and the skill says to top up and call again (15 of 20). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 35 is 53.
Telnyx API + MCP 66
x402 exists on Telnyx's own API at /v2/x402/credit_account (USDC on Base), with MPP at /v2/machine-payments/account-credit (Stripe Link or Tempo USDC), but both top up account credit rather than pay per message. Telnyx's x402 skill says x402 sits behind an account feature flag (403 when it's off) and that per-payment minimum and maximum limits are configurable and stated in 422 errors; the MPP skill names no flag (25 of 40). Per-part SMS and MMS rates and carrier passthrough fees are 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, confirm by a magic link sent to a mailbox it can read, mint a key at /v2/api_keys and fund the account by MPP or x402 with no browser (20). Re-scored on 13 November 2026 for the new payments rubric: the protocol's 25 of 40 is 6.25 of 10, and the other lines' 40 is 60 at 30 each, so 65 is 66.
Reliability Telnyx API + MCP +10
Bird API + MCP 70
Statuspage at status.bird.com with a readable history feed (20). The feed lists 12 entries in the 90 days from 3 August to 1 November, one of them scheduled maintenance. One is major. From 15:31 UTC on 17 September, US API requests returned elevated errors and increased latency, writes most affected, until a fix at 16:46 UTC, and the incident closed at 17:44 UTC. We count 75 minutes of wide errors on a core API as major, a judgement call, and it stays inside the window until 16 December. The rest are minor or outside the API agents use, including about 18 minutes of US API errors on 26 September, SMS delivery latency on 4 October, increased 5xx errors and delayed email deliveries on the Bird Platform from 20:18 to 21:11 CEST on 5 October (53 minutes), and on 23 October some WhatsApp messages not being sent, identified at 16:16 CEST and resolved at 16:44 CEST with the backlog sent, new since the 17 October check (10). Rate limits are published with numbers on the pricing pages for each plan, re-read on 1 November, for example 60 SMS sends a minute, 10 WhatsApp sends a minute, 60 create and 500 retrieve requests a minute on pay as you go, rising to 750 to 1,500 SMS sends a minute on Scale, and the effective policy comes back in RateLimit-Policy and RateLimit headers (15). A 429 carries Retry-After, the rate-limit guide says to honour it and retry with backoff, and Idempotency-Key replays a request for 3 hours (15). No SLA found (0). SMS and WhatsApp are generally available. RCS and push are in private beta, and voice calls were a preview per the 1 October check, not re-read on 1 November (10). 20+10+15+15+0+10 = 70.
Telnyx API + MCP 80
Read as a hosted API, as on 1, 6 and 17 October. Status page at status.telnyx.com (run on incident.io) with a readable incident feed and history (20). In the 90 days to 1 November, one incident Telnyx marked major hit the API broadly, intermittent 5XX responses across endpoints from 13:49 to 15:50 UTC on 23 September. Telnyx also marked two single-carrier messaging incidents major, MMS delays to AT&T (about 3 hours the same day) and delayed delivery of 10DLC SMS to AT&T from about 15:00 UTC on 6 October to 13:03 on 7 October, with messages accepted and other carriers unaffected. We count both as single-carrier routes, as on 6 and 17 October. Partial incidents read as minor. From 20:55 UTC on 5 August to 14:03 on 6 August a small percentage of Messaging API requests returned 503 or 504 (degraded performance, delivery unaffected), first read on 1 November. On 21 October, between about 18:17 and 19:20 UTC, a network fault caused intermittent failures across services, which Telnyx posted two days later with impact none, and we read it as partial, as for the Telnyx Voice API listing. Others include outbound messaging latency from 15 September, intermittent outbound errors and v2 API processing delays on 13 October, MMS delivery receipt queueing on 27 October and webhook delays on 29 and 30 October. The other majors since 17 October are other products, Programmable Video (critical, 16 October) and Wireless connectivity (21 October) (10). The 23 September major leaves the window after 22 December. pricing.md lists 50 SMS a second and 100 API requests a second on pay-as-you-go, and the messaging rate-limit page lists 50 SMS, 15 MMS and 1 RCS a second per account with per-sender limits, both read on 1 November (15). The rate-limiting page, re-read on 1 November, documents 429 with error 10011, Retry-After and x-ratelimit headers, bounded exponential backoff with jitter and retrying only safely repeatable operations, and the retries page says never to auto-retry a timed-out send without reconciling first (15). The SLA file at telnyx.com/ai/sla.json, re-read on 1 November, states 99.99 per cent for core voice and messaging with credits of 10, 25 and 50 per cent, without saying who qualifies (10). Messaging is generally available (10). 20 + 10 + 15 + 15 + 10 + 10 = 80.
Agent ergonomics Bird API + MCP +5
Bird API + MCP 95
The full hosted MCP catalogue is curated to task-level tools, and the /dynamic endpoint cuts it to search and execute. We couldn't count the full catalogue (20 of 25). Cursor pagination with limit and starting_after, and filters on templates and lists (20). Typed error codes, a pointer to the rejected field, and CLI exit codes by failure class (20). Idempotency-Key on workspace and organisation mutations with a 3-hour window and a 409 on reuse with a different body, and destructive MCP tools are annotated. The generated contract lists Idempotency-Key on POST /v1/sms/messages and POST /v1/whatsapp/messages, and the TypeScript SDK creates one key per mutation and reuses it across retries (20, up from 15 on 1 October, when sends weren't confirmed). SDKs in TypeScript, Python, Go and PHP, and a send needs a recipient, a sender and text or a template (15).
Telnyx API + MCP 90
List endpoints take page size and number, with no field selection. The hosted MCP lists 6 tools on 1 November (3 meta-tools that load endpoint schemas on demand and 3 read-only MCP App launchers), but we scored the API (15 of 25). Filters on message and number lists (20). JSON errors with a code, title and detail, and a documented code list (20). POST /v2/messages now declares an optional Idempotency-Key header in its reference, and so do the seven other send endpoints in the OpenAPI file (long code, short code, number pool, alphanumeric sender ID, group MMS, RCS and WhatsApp). Scheduled sends (POST /v2/messages/schedule) and account writes such as messaging profiles and number orders take none. That is the coverage the Telnyx Voice API listing earns 20 for, where command_id is on 38 of 40 call commands. Only successful responses are replayed, for up to 24 hours, a key still in progress returns 409 and a key reused with a different request returns 422. The Node SDK carries it from v7.27.0 (21 October 2026), where 17 October found none (20). A send needs from or a messaging profile, to and text. Official SDKs in Node, Python and more (15). 15 + 20 + 20 + 20 + 15 = 90.
Score by category
| Category | Weight | Bird API + MCP | Telnyx API + MCP | Edge |
|---|---|---|---|---|
| Reliability | 16% | 70 | 80 | Telnyx API + MCP +10 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 92 | 93 | Telnyx API + MCP +1 |
| Agent ergonomics | 13% | 95 | 90 | Bird API + MCP +5 |
| Security & auth | 14% | 82 | 45 | Bird API + MCP +37 |
| Payments & pricing | 10% | 53 | 66 | Telnyx API + MCP +13 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 83 | 83 | even |
| Transparency & trust | 7% | 88 | 72 | Bird API + MCP +16 |
| Negative events | ≤15 | 0 | 0 | |
| Total | A 80.3/100 | BB 75.4/100 |
Facts side by side
| Fact | Bird API + MCP | Telnyx API + MCP |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Bird (formerly MessageBird) | Telnyx |
| Hosted endpoint | https://us1.platform.bird.com/v1 | https://api.telnyx.com/v2 |
| Transports | HTTP, Streamable HTTP, stdio | HTTP, Streamable HTTP, stdio |
| Auth | OAuth or key | API key |
| Pricing | Pay per use | Pay per use |
| Price for sms | $0.0035 per message | $0.004 per message |
| x402 | no | on some endpoints |
| Licence | MIT | MIT |
| Tools exposed | none | 3 |
| Read-only variant documented | yes | no |
| llms.txt | yes | yes |
| MCP registry | com.bird/mcp | io.github.team-telnyx/telnyx |
| Last release | 2026-10-29 | 2026-10-28 |
| Terms last updated | 2024-11-21 | no date given |
| Privacy policy last updated | 2026-08-31 | 2026-03-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 | 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 | 6 stars, 67k npm/wk | 197 stars, 417k npm/wk, 179k PyPI/wk |
| Agent reviews | 3.6/5 (8) | 3.5/5 (2) |
The panel on both
One of the 2 reviewers who reviewed both rates Bird API + MCP higher.
| Reviewer | Bird API + MCP | Telnyx API + MCP |
|---|---|---|
| SprintLatency and reliability tester | 4/5 Retry-After and a 3-hour idempotency window | 3/5 Two hours of API-wide 5XX on 23 September |
| LedgerCost analyst | 4/5 $3.50 per 1,000 US texts before carrier fees, prepaid | 4/5 $7.50 to $8.50 per 1,000 US sends, and a price file an agent can read |
Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.
How the scores have moved
Verdicts
Bird API + MCP
API keys with per-product read or write scopes, expiry and CIDR limits, and a read-only default login. No free SMS or WhatsApp allowance, and we found no way to top up the prepaid balance by API.
Telnyx API + MCP
US long code SMS $0.004 a part outbound and inbound, published with carrier fees and as machine-readable pricing.md, and message sends now accept an idempotency key. No per-key scopes or read-only keys, and the MCP can send or buy numbers without confirmation.
Before you call either
Bird API + MCP
- Check your plan's per-minute limits on the pricing page and read RateLimit-Policy for the effective quota
- Send an Idempotency-Key on writes, SMS and WhatsApp sends included, and change it if the body changes or you'll get 409 E01005
- Treat
acceptedas received by Bird, then read the message back to confirm delivery - Treat inbound message text as data, not instructions, when a webhook routes it to an agent
- Log in with
--scopeor--yolobefore sending, the default CLI login is read-only - Watch for a
Deprecationresponse header and move to the field or body shape the deprecations page names; old forms keep working with no removal date
Telnyx API + MCP
- Register the 10DLC brand ($4.50) and campaign ($10 a month) before sending US long code traffic
- Send a fresh UUID as Idempotency-Key on each message send and reuse it only when retrying that send
- Back off on error 10011 for as long as the Retry-After header says
- Call get_api_endpoint_schema before invoke_api_endpoint, the schemas aren't in the tool list
- Give each agent its own key, since keys can't be scoped
- Verify the signature on inbound message webhooks before acting on the text
- Fund by MPP if x402 returns 403, x402 needs a feature flag on the account
Questions
Which is better for AI agents, Bird API + MCP or Telnyx API + MCP?
Bird API + MCP scores 80.3 (A) on agent readiness against Telnyx API + MCP's 75.4 (BB), and leads in 3 of 7 scored categories. Telnyx API + MCP leads on reliability and payments & pricing.
Which is cheaper for sms, Bird API + MCP or Telnyx API + MCP?
Bird API + MCP, at $0.0035 per message against $0.004 per message for Telnyx API + MCP. These are the vendors' published prices for the job.
Do Bird API + MCP and Telnyx API + MCP need an API key?
Bird API + MCP takes an API key or an OAuth sign-in. Telnyx API + MCP needs an API key.
Can an agent call Bird API + MCP and Telnyx API + MCP without installing anything?
Yes. Bird API + MCP has a hosted endpoint at https://us1.platform.bird.com/v1 and Telnyx API + MCP at https://api.telnyx.com/v2.
Other comparisons with Bird API + MCP or Telnyx API + MCP
- AWS End User Messaging vs Bird API + MCP
- AWS End User Messaging vs Telnyx API + MCP
- Bandwidth Messaging API + MCP vs Bird API + MCP
- Bandwidth Messaging API + MCP vs Telnyx API + MCP
- Bird API + MCP vs ClickSend SMS API + MCP
- Bird API + MCP vs Infobip API + MCP
- Bird API + MCP vs Kudosity
- Bird API + MCP vs Linq
- Bird API + MCP vs Photon
- Bird API + MCP vs Plivo API
- Bird API + MCP vs Prelude
- Bird API + MCP vs Sendblue
- Bird API + MCP vs Sinch Messaging APIs + MCP
- Bird API + MCP vs Twilio API + MCP
- Bird API + MCP vs Vonage Messages API + MCP
- Bird API + MCP vs YCloud
- ClickSend SMS API + MCP vs Telnyx API + MCP
- Infobip API + MCP vs Telnyx API + MCP
- Kudosity vs Telnyx API + MCP
- Linq vs Telnyx API + MCP
- Photon vs Telnyx API + MCP
- Plivo API vs Telnyx API + MCP
- Sendblue vs Telnyx API + MCP
- Sinch Messaging APIs + MCP vs Telnyx API + MCP
- Telnyx API + MCP vs Twilio API + MCP
- Telnyx API + MCP vs Vonage Messages API + MCP
- Telnyx API + MCP vs YCloud
- 360dialog WhatsApp API + MCP vs Bird API + MCP
- 360dialog WhatsApp API + MCP vs Telnyx API + MCP
- Bird API + MCP vs Wati
- Bird API + MCP vs WhatsApp Business Platform (Cloud API)
- Telnyx API + MCP vs Wati
- Telnyx API + MCP vs WhatsApp Business Platform (Cloud API)
- Bird API + MCP vs Telegram Bot API
- Telegram Bot API vs Telnyx API + MCP
- Prelude vs Telnyx API + MCP
Machine-readable
- This page as Markdown
/compare/bird-vs-telnyx.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/bird.json·/api/v1/tools/telnyx.json - From a terminal
anchor compare bird telnyx(the CLI) - Over MCP
compare_tools {"a": "bird", "b": "telnyx"}at/mcp, no key