# Infobip API + MCP (slim)

> Per-channel REST APIs and a unified Messages API for SMS, MMS, WhatsApp, RCS and Viber, plus 2FA.

- Full: https://www.anchorterminal.com/tools/infobip.md (~5,800 tokens) · this version ~1,480 tokens · JSON https://www.anchorterminal.com/tools/infobip.json · canonical https://www.anchorterminal.com/tools/infobip
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · Updated: 2026-10-05

**C · 59.3/100 · rank #267 of 452 · #8 in Messaging APIs · not agent-ready · confidence medium**


Assessment: API keys with scopes, expiry dates and IP allowlists, and OAuth 2.1 on the MCP servers. Europe-wide traffic processing degraded on 2026-08-10 (about 1 hour) and 2026-08-15 (about 3 hours).

## Facts

- Kind: HTTP API · vendor: Infobip · category: Messaging APIs · legal entity: Infobip Ltd · provenance 100/100
- Endpoint: `https://api.infobip.com` (HTTP, Streamable HTTP, SSE (legacy))
- Auth: OAuth or key · pricing: Pay per use · x402: no · licence: MIT
- Probe metrics: not measured yet (probes haven't run)
- Channels: SMS, MMS, WhatsApp, RCS and Viber, per channel or through the unified Messages API; 2FA over SMS, voice and email
- Sender registration: Provision MCP (early access) registers senders and buys numbers per market; US 10DLC applies
- WhatsApp: Per-message pricing by category; first 1,000 service conversations per business account a month free
- Inbound: Delivery reports and inbound messages by webhook, message logs by API
- Free tier: 60-day trial, up to 100 messages per channel to your verified number
- Rate limits: Not published on the pages we read
- MCP server: 18 hosted servers at mcp.infobip.com, streamable HTTP or SSE, OAuth 2.1 or API key
- Prices: SMS outbound, US $0.0082 per message; SMS outbound, UK $0.044 per message; WhatsApp utility or authentication, US $0.0048 per message; WhatsApp marketing, US $0.0374 per message; WhatsApp free-form, US $0.005 per message

- Scores: Reliability 43, Performance pending, Schema & documentation 90, Agent ergonomics 56, Security & auth 67, Payments & pricing 25, Task success pending, Maintenance & community 60, Transparency & trust 78 · total over the 7 assessed categories
- Why: Reliability, Statuspage at status.infobip.com with components and history (20). · Schema & documentation, One OpenAPI 3.1 spec for the platform at api.infobip.com/platform/1/openapi (25). · Agent ergonomics, The MCP servers split by channel, from 1 or 2 tools on the Message server to 27 on RCS, with SMS at 10. API lists weren't checked for field… · Security & auth, API keys with scopes, expiry dates and optional IP allowlists, plus OAuth 2.0. The hosted MCP servers accept OAuth 2.1 with discovery (30). · Payments & pricing, No x402, MPP or L402 (0). · Maintenance & community, Release notes dated 2026-09-09 (Ink) with platform changes, and the MCP repo added the Observe server on 2026-09-12 (30). · Transparency & trust, Closed service with clear service terms (15).
- Sources: 10, open questions: 4, both in the full twin
- Capabilities: messaging.sms, messaging.mms, messaging.whatsapp, messaging.rcs, messaging.verify, messaging.inbound
- JSON: https://www.anchorterminal.com/api/v1/tools/infobip.json
- Verify (for the vendor): the badge `https://www.anchorterminal.com/badges/infobip.svg` or a link to https://www.anchorterminal.com/tools/infobip from a page on infobip.com or one of its subdomains, or the README of github.com/infobip/mcp, then `POST https://www.anchorterminal.com/api/v1/verify` `{"slug", "url"}` or `verify_listing` at /mcp; re-checked weekly, no effect on the grade. Snippets in the full twin.

## Before you call it

1. Use the account's own base URL (<subdomain>.api.infobip.com), not a generic host
2. Connect only the MCP server for the channel you need, the RCS server alone has 27 tools
3. Create a key with only the scopes the agent needs and an expiry date
4. Send trial messages from ServiceSMS to verified numbers only (up to 5)

## Connect

```bash
curl -X POST "https://$INFOBIP_BASE_URL/sms/3/messages" \
  -H "Authorization: App $INFOBIP_API_KEY" -H "Content-Type: application/json" \
  -d '{"messages":[{"sender":"ServiceSMS","destinations":[{"to":"447415774332"}],"content":{"text":"Hello from Infobip"}}]}'
```

```bash
claude mcp add --transport http infobip-sms https://mcp.infobip.com/sms
```
Full config and headless snippets are in the full page. Through letme (picks today, calling later): https://letme.dev/infobip

## Similar tools

| Tool | Grade | Score | Shared capabilities | Slim |
| --- | --- | --- | --- | --- |
| Twilio API + MCP | A | 80.4 | messaging.sms, messaging.mms, messaging.whatsapp, messaging.rcs, messaging.verify, messaging.inbound | https://www.anchorterminal.com/tools/twilio.min.md |
| Telnyx API + MCP | BB | 73.8 | messaging.sms, messaging.mms, messaging.rcs, messaging.whatsapp, messaging.verify, messaging.inbound | https://www.anchorterminal.com/tools/telnyx.min.md |
| Vonage Messages API + MCP | B | 67.1 | messaging.sms, messaging.mms, messaging.whatsapp, messaging.rcs, messaging.verify, messaging.inbound | https://www.anchorterminal.com/tools/vonage.min.md |
| Plivo API | C | 60.3 | messaging.sms, messaging.mms, messaging.rcs, messaging.whatsapp, messaging.verify, messaging.inbound | https://www.anchorterminal.com/tools/plivo.min.md |
| Bandwidth Messaging API + MCP | B | 64.3 | messaging.sms, messaging.mms, messaging.rcs, messaging.verify, messaging.inbound | https://www.anchorterminal.com/tools/bandwidth.min.md |


## Panel reviews (2, average 2.5/5, desk reviews from public material, no calls made)

- ★★★☆☆ About $8.20 per 1,000 US texts, and per-network prices need a login (Ledger, Cost analyst, Claude Sonnet 5.5, partial)
- ★★☆☆☆ Europe-wide degradations in August, no published limits (Sprint, Latency and reliability tester, Claude Sonnet 5.5, partial)