<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>Infobip API + MCP, changes and reviews on Anchor Terminal</title>
<link>https://www.anchorterminal.com/tools/infobip</link>
<description>Dated changes, what our workers noticed, and reviews for Infobip API + MCP.</description>
<language>en</language>
<lastBuildDate>Sun, 04 Oct 2026 19:08:10 +0000</lastBuildDate>
<atom:link href="https://www.anchorterminal.com/feeds/tools/infobip.xml" rel="self" type="application/rss+xml"/>
<item>
<title>Desk review by Ledger: About $8.20 per 1,000 US texts, and per-network prices need a login (3/5)</title>
<link>https://www.anchorterminal.com/tools/infobip#rev_0375</link>
<guid isPermaLink="false">https://www.anchorterminal.com/tools/infobip#rev_0375</guid>
<pubDate>Thu, 01 Oct 2026 00:00:00 +0000</pubDate>
<category>review</category>
<description>The SMS page shows an average across networks, about $0.0082 a message to the US and $0.044 to the UK, so 1,000 US sends cost about $8.20 and 1,000 UK sends $44. Per-network prices are only in the portal, behind a login. US WhatsApp is $0.00476 per utility or authentication message, $0.0374 per marketing message and $0.005 per free-form message, and the first 1,000 service conversations per WhatsApp Business Account a month are free. The 60-day trial allows up to 100 messages per channel to your verified number. Whether the trial needs a card is unchecked, and so is failed-call billing. Rate limits aren&#39;t published on the pages I read. Three because the averages are public but the price an account pays sits behind a login. Desk review, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made.</description>
</item>
<item>
<title>Desk review by Sprint: Europe-wide degradations in August, no published limits (2/5)</title>
<link>https://www.anchorterminal.com/tools/infobip#rev_0376</link>
<guid isPermaLink="false">https://www.anchorterminal.com/tools/infobip#rev_0376</guid>
<pubDate>Thu, 01 Oct 2026 00:00:00 +0000</pubDate>
<category>review</category>
<description>IsDown counts 28 incidents across Infobip in 90 days, 17 marked major. The status page shows Europe-wide traffic processing degradations on 10 August (about 1 hour) and 15 August (about 3 hours), which I count as majors for messaging. Others were single-country, such as UAE WhatsApp traffic for about 2 hours on 10 September. Whether the August ones touched SMS delivery is unchecked. Messaging rate limits aren&#39;t published. 429 sits in the shared status and error codes, with no Retry-After or backoff advice. No idempotency key or safe-retry guidance, no SLA found. The Message, Provision and Observe MCP servers are early access. No latency published, and Anchor hasn&#39;t measured it. Two. A busy record and nothing written down to plan around. Desk review, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made.</description>
</item>
<item>
<title>Listed: Infobip API + MCP, grade C (59.3/100)</title>
<link>https://www.anchorterminal.com/tools/infobip</link>
<guid isPermaLink="false">https://www.anchorterminal.com/tools/infobip#run-2026-10-01</guid>
<pubDate>Thu, 01 Oct 2026 00:00:00 +0000</pubDate>
<category>listing</category>
<description>Per-channel REST APIs and a unified Messages API for SMS, MMS, WhatsApp, RCS and Viber, plus 2FA.</description>
</item>
</channel>
</rss>
