Best of · Communication
Best SMS, WhatsApp and messaging APIs for AI agents
The 10 highest-scoring of 14 SMS, WhatsApp and messaging APIs on the Anchor benchmark, with a pick for each need and where each one falls short. Scores come from public evidence, re-checked as vendors change.
- 14 ranked
- 4 agent-ready
- 14 hosted endpoints
- Updated 9 October 2026
Top three
Picks by need
Worked out from the scores, prices and facts, so they change when the research does.
Schema & documentation
93/100 on schema & documentation, against 92 for the overall leader.
Security & auth
88/100 on security & auth, against 85 for the overall leader.
Transparency & trust
83/100 on transparency & trust, against 81 for the overall leader.
The shortlist
| # | Tool | Grade | Best for | Price | Where |
|---|---|---|---|---|---|
| 1 | Twilio API + MCP Twilio |
A 80.4 | Teams that want every channel, wide country coverage and a published SLA behind one vendor and can pay for it. | Pay per use | hosted and local |
| 2 | Bird API + MCP Bird (formerly MessageBird) |
BB 76.5 | Agents that send SMS, WhatsApp and email from one account and need scoped credentials and safe retries. | Pay per use | hosted and local |
| 3 | AWS End User Messaging Amazon Web Services |
BB 74.3 | Teams already on AWS that want SMS, MMS, RCS and WhatsApp under IAM, CloudTrail and per-Region control at carrier-level prices. | $1 / mo | hosted |
| 4 | Telnyx API + MCP Telnyx |
BB 73.6 | Cost-sensitive US SMS and for agents that must onboard and pay without a person. | Pay per use | hosted and local |
| 5 | WhatsApp Business Platform (Cloud API) Meta Platforms, Inc. |
B 67.1 | The direct route to WhatsApp for a business messaging its own customers, with no reseller fee. | Pay per use | hosted |
| 6 | Vonage Messages API + MCP Vonage (Ericsson) |
B 66.8 | Agents that need several chat channels behind one call with SMS failover. | Pay per use | hosted and local |
| 7 | Bandwidth Messaging API + MCP Bandwidth |
B 64.3 | US and Canada senders at volume who want carrier-owned routes and will talk to sales. | Paid | hosted and local |
| 8 | Sinch Messaging APIs + MCP Sinch |
B 63.2 | Teams that want SMS, RCS and WhatsApp through one API with wide country coverage, and those already on Sinch voice or Mailgun. | Pay per use | hosted and local |
| 9 | Sendblue Round One, Inc. |
C 61.7 | An agent that answers people over iMessage on a US number, where blue-bubble threads, typing indicators and reactions matter and the person texts first. | $100 / mo | hosted and local |
| 10 | Plivo API Plivo |
C 60.3 | Cost-sensitive SMS and WhatsApp sends from code, and for teams that also use Plivo voice. | Pay per use | hosted |
4 more are ranked in the full table.
How to choose
- Price per message by countryCheck the price per message for each country the agent will reach, since fees vary by destination and a headline rate can understate the cost of a multi-country workload.
- Sender registration before sendingCheck which sender registrations, such as 10DLC or business verification, must be complete before the first message, since an unregistered sender can be blocked from sending at all.
- Channel coverage and fallbackCheck which channels cover each target country and whether a message can fall back to another channel, since an agent may need a second route to reach a recipient.
- Inbound replies and retriesCheck how inbound replies reach the agent and whether webhook delivery is retried, since a lost reply can leave a conversation waiting on a customer who has already answered.
Each one in detail
Twilio API + MCP
A 80.4/100Programmable Messaging (SMS, MMS, WhatsApp, RCS) and Verify over REST.
Verdict Per-segment US prices, carrier fees by carrier and the $0.001 failed-message fee published without a login. US SMS at $0.0083 a segment plus $0.0035 to $0.005 in carrier fees, with inbound charged at the same rate.
Choose it for Teams that want every channel, wide country coverage and a published SLA behind one vendor and can pay for it.
Strengths
- Per-segment US prices, carrier fees by carrier and the $0.001 failed-message fee published without a login
- Restricted API keys with up to 100 endpoint permissions each
- Twilio APIs SLA at 99.95 per cent for every paying customer, with 10 per cent credits
Weaknesses
- US SMS at $0.0083 a segment plus $0.0035 to $0.005 in carrier fees, with inbound charged at the same rate
- A US long code sends 1 message a second per Twilio's scaling guide, with the excess queued for up to 10 hours
- No idempotency key on message creation
Price Pay per useAuth OAuth or keyx402 nohosted and local
Bird API + MCP
BB 76.5/100Bird's rebuilt developer API sends SMS and WhatsApp (plus email and voice) from one account, with an OpenAPI 3.1 spec, generated SDKs, a CLI and a hosted OAuth MCP server at mcp.bird.com.
Verdict 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.
Choose it for Agents that send SMS, WhatsApp and email from one account and need scoped credentials and safe retries.
Strengths
- API keys with per-product read or write scopes, expiry and CIDR limits, and a read-only default login
- Idempotency-Key with a 3-hour window on SMS and WhatsApp sends and other mutations, Retry-After on 429 and typed error codes
- OpenAPI 3.1 spec, llms.txt and Markdown pages
Weaknesses
- No free SMS or WhatsApp allowance, and we found no way to top up the prepaid balance by API
- About 75 minutes of elevated US API errors and increased latency on 17 September 2026, writes most affected
- Rate-limit quotas aren't published, only returned in headers
Price Pay per useAuth OAuth or keyx402 nohosted and local
AWS End User Messaging
BB 74.3/100AWS's messaging service for SMS, MMS, RCS, WhatsApp, voice and push, formerly the channel APIs of Amazon Pinpoint. Agents call the SMS and Voice v2 API or the Social Messaging API with IAM-signed requests, through the AWS CLI or SDKs.
Verdict IAM policies limit a credential to single actions and resources, CloudTrail can log every send, and enforced monthly spend limits cap cost. New accounts start in a sandbox with a $1 monthly SMS limit and ten verified recipients, production access needs a support case per Region, and the send actions take no idempotency token.
Choose it for Teams already on AWS that want SMS, MMS, RCS and WhatsApp under IAM, CloudTrail and per-Region control at carrier-level prices.
Strengths
- IAM policies per action and resource with condition keys and temporary credentials, and CloudTrail data events for the send actions
- Smithy model published for all 110 SMS and Voice v2 operations, with 69 enumerated types and reason codes on errors
- Enforced monthly spend limits, protect configurations that block destination countries, and a
DryRunflag on sends
Weaknesses
- Sandbox limits new accounts to $1 of SMS a month and ten verified numbers until a support case per Region is approved
- No idempotency token on
SendTextMessage,SendMediaMessageorSendRcsMessage, so a retried send can go out twice - Most actions, the send actions included, default to 1 request a second per account and Region
Price $1 / moAuth OAuth or keyx402 nohosted
Telnyx API + MCP
BB 73.6/100Carrier-owned CPaaS with SMS, MMS, RCS and WhatsApp on one REST API, plus an official hosted MCP server at api.telnyx.com/v2/mcp and a stdio MCP package.
Verdict US long code SMS $0.004 a part outbound and inbound, published with carrier fees and as machine-readable pricing.md. No per-key scopes or read-only keys, and the MCP can send or buy numbers without confirmation.
Choose it for Cost-sensitive US SMS and for agents that must onboard and pay without a person.
Strengths
- US long code SMS $0.004 a part outbound and inbound, published with carrier fees and as machine-readable pricing.md
- Agent signup and x402 or MPP top-ups with no browser
- 429 responses carry Retry-After and x-ratelimit headers, with documented backoff guidance
Weaknesses
- No per-key scopes or read-only keys, and the MCP can send or buy numbers without confirmation
- No free credit, a new account starts at zero
- API-wide 5XX errors for about 2 hours on 2026-09-23, plus messaging latency and delivery incidents through September
Price Pay per useAuth API keyx402 partialhosted and local
WhatsApp Business Platform (Cloud API)
B 67.1/100Meta's WhatsApp Business Platform Cloud API sends and receives WhatsApp messages for a business phone number through the Graph API, with inbound messages and status updates arriving by webhook. Access uses a Meta developer app and OAuth access tokens.
Verdict The first-party WhatsApp API has a public OpenAPI document, Markdown docs with llms.txt, numeric rate limits and a test number that sends without a payment method. Setup needs a person in three Meta dashboards, no idempotency key was found for sends, and Meta's terms restrict general-purpose AI assistants on the platform.
Choose it for The direct route to WhatsApp for a business messaging its own customers, with no reseller fee.
Strengths
- A test WhatsApp Business account and test number are created with the app and send template messages with no payment method on file
- OpenAPI 3.1 document under MIT in facebook/openapi (78 paths, 113 operations), plus llms.txt indexes and a Markdown copy of each docs page
- Limits are published with numbers, including 80 messages a second per number, 5,000 requests an hour per active account and one message every 6 seconds per recipient
Weaknesses
- A person has to create a Meta account, a developer app, a business portfolio and a system user in a browser before any token exists
- No idempotency key for message sends was found in the reviewed documentation or the OpenAPI document, so a retried send can reach the user twice
- Meta's pricing page says the 15 January 2026 terms permit general-purpose AI assistants only where Meta is legally required to allow them
Price Pay per useAuth OAuthx402 nohosted
Vonage Messages API + MCP
B 66.8/100One endpoint (POST /v1/messages) for SMS, MMS, WhatsApp, RCS, Viber and Messenger, with failover between channels.
Verdict POST /v1/messages covers six channels, with SMS failover for WhatsApp and RCS. No idempotency key, and channel rejections arrive only by status webhook after a 202.
Choose it for Agents that need several chat channels behind one call with SMS failover.
Strengths
- POST /v1/messages covers six channels, with SMS failover for WhatsApp and RCS
- OpenAPI 3.0.3 spec for the Messages API (version 1.19.1), and SDK releases in Node and Python through September 2026
- 75 requests a second per API key, with Retry-After and X-RateLimit headers on 429
Weaknesses
- No idempotency key, and channel rejections arrive only by status webhook after a 202
- The sending MCP lives in the Vonage-Community GitHub organisation, last released on 2026-05-26, with no tool annotations
- SMS, WhatsApp and RCS prices sit behind a country selector, and the terms body doesn't render without a browser
Price Pay per useAuth OAuth or keyx402 nohosted and local
Bandwidth Messaging API + MCP
B 64.3/100US carrier's messaging API for SMS, MMS and RCS over 10DLC, toll-free and short codes, with published US rates.
Verdict 10DLC SMS $0.004, toll-free $0.007 and short code $0.008 a message, published. Messaging accounts are onboarded by sales, and the free Build trial covers voice only.
Choose it for US and Canada senders at volume who want carrier-owned routes and will talk to sales.
Strengths
- 10DLC SMS $0.004, toll-free $0.007 and short code $0.008 a message, published
- OAuth 2.0 client credentials with roles, account scope and two-secret rotation
- A full queue returns 429 stating the allowed rate and queue size
Weaknesses
- Messaging accounts are onboarded by sales, and the free Build trial covers voice only
- No callback signing found
- No SLA, sub-processor list or retention periods found
Price PaidAuth OAuthx402 nohosted and local
Sinch Messaging APIs + MCP
B 63.2/100The SMS REST API and the Conversation API, which sends SMS, RCS, WhatsApp, Viber and Messenger through one message format, plus the Verification API.
Verdict The Conversation API covers SMS, RCS, WhatsApp, Viber and Messenger through one message format. The MCP server is a developer preview whose npm release dates from 2026-04-14.
Choose it for Teams that want SMS, RCS and WhatsApp through one API with wide country coverage, and those already on Sinch voice or Mailgun.
Strengths
- The Conversation API covers SMS, RCS, WhatsApp, Viber and Messenger through one message format
- Published limits of 800 requests a second per project and a 500,000-message queue per app
- HMAC-signed callbacks with a nonce and timestamp
Weaknesses
- The MCP server is a developer preview whose npm release dates from 2026-04-14
- 54 MCP tools with no readOnlyHint or destructiveHint annotations
- Separate credential schemes for the SMS, Conversation and Verification APIs, none with scopes
Price Pay per useAuth OAuth or keyx402 nohosted and local
Sendblue
C 61.7/100Sendblue is a hosted API from Round One, Inc. for sending and receiving iMessage, RCS, SMS and MMS from dedicated or shared phone numbers. Agents use a REST API, TypeScript and Python SDKs, a CLI and an MCP server.
Verdict Sendblue sends iMessage with RCS and SMS fallback at a flat $100 a line each month, and its CLI creates a free account and API keys from a terminal once a person texts a code. Proactive outbound messaging is sold through sales, no OpenAPI file is published, and the MCP package the docs install dates from August 2025.
Choose it for An agent that answers people over iMessage on a US number, where blue-bubble threads, typing indicators and reactions matter and the person texts first.
Strengths
- One request to
/api/send-messagesends iMessage and can fall back to RCS or SMS, with no per-message fee on any plan - The CLI creates a free account, a shared line and API keys from a terminal, with no card, once a person texts a one-time code
- Temporary bearer tokens from
/v3/auth/tokenscan be limited to named phone numbers, expire after 900 seconds by default and can be revoked
Weaknesses
- Proactive outbound messaging needs the Blue Ocean plan, which has no public price. The $100 AI Agent plan is inbound-first
- No OpenAPI file was found at any public address, although the SDKs and the reference are generated from one
- The docs install
sendblue-api-mcp, last published on 5 August 2025 with 18 tools. The API now has 54 configured endpoints
Price $100 / moAuth API keyx402 nohosted and local
Plivo API
C 60.3/100CPaaS REST API for SMS, MMS, RCS and WhatsApp in 190+ countries, alongside voice.
Verdict US long code SMS $0.0077 a message and numbers $0.50 a month, with carrier surcharges listed per carrier. No OpenAPI spec.
Choose it for Cost-sensitive SMS and WhatsApp sends from code, and for teams that also use Plivo voice.
Strengths
- US long code SMS $0.0077 a message and numbers $0.50 a month, with carrier surcharges listed per carrier
- Free trial credits with no card
- Published API limit of 300 requests per 5 seconds
Weaknesses
- No OpenAPI spec
- One Auth ID and token per account or subaccount, with no scopes or read-only keys
- The official MCP has one tool and only searches docs
Price Pay per useAuth API keyx402 nohosted
Head to head
- Bird API + MCP vs Twilio API + MCP BB 76.5 vs A 80.4
- AWS End User Messaging vs Twilio API + MCP BB 74.3 vs A 80.4
- Telnyx API + MCP vs Twilio API + MCP BB 73.6 vs A 80.4
- Twilio API + MCP vs WhatsApp Business Platform (Cloud API) A 80.4 vs B 67.1
- AWS End User Messaging vs Bird API + MCP BB 74.3 vs BB 76.5
- Bird API + MCP vs Telnyx API + MCP BB 76.5 vs BB 73.6
- Bird API + MCP vs WhatsApp Business Platform (Cloud API) BB 76.5 vs B 67.1
- AWS End User Messaging vs Telnyx API + MCP BB 74.3 vs BB 73.6
- AWS End User Messaging vs WhatsApp Business Platform (Cloud API) BB 74.3 vs B 67.1
- Telnyx API + MCP vs WhatsApp Business Platform (Cloud API) BB 73.6 vs B 67.1
Questions
What are the highest-rated SMS, WhatsApp and messaging APIs for AI agents?
Twilio API + MCP has the highest benchmark score of the 14 ranked SMS, WhatsApp and messaging APIs, 80.4 (A). Bird API + MCP is second with 76.5 (BB).
How many SMS, WhatsApp and messaging APIs are agent-ready?
4 of the 14 ranked here grade BB or better, the bar for agent-ready on the Anchor benchmark.
Which SMS, WhatsApp and messaging APIs accept x402 payments?
None of the ranked listings here accepts x402 for its main call yet.
How is this list ranked?
By the Anchor benchmark score out of 100, a weighted mean of the scored categories minus deductions for negative events, from public evidence re-checked as vendors change. Listings cannot pay for a place. The latest assessment behind this page is from 9 October 2026.
How this list is made
The order is the Anchor benchmark score, the same number as on each listing and in the top list. Each listing is graded from public evidence against the benchmark checklist, and the picks above are worked out from those grades, prices and facts. No listing pays for its place, and paid audits or listing help never change a score.
Full ranked table · 91 head-to-head comparisons · Best tools in every category