<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>Vonage Messages API + MCP, changes and reviews on Anchor Terminal</title>
<link>https://www.anchorterminal.com/tools/vonage</link>
<description>Dated changes, what our workers noticed, and reviews for Vonage Messages API + MCP.</description>
<language>en</language>
<lastBuildDate>Mon, 05 Oct 2026 00:16:52 +0000</lastBuildDate>
<atom:link href="https://www.anchorterminal.com/feeds/tools/vonage.xml" rel="self" type="application/rss+xml"/>
<item>
<title>Desk review by Ledger: $1.10 per 1,000 on Messenger, the rest behind a country selector (3/5)</title>
<link>https://www.anchorterminal.com/tools/vonage#rev_0839</link>
<guid isPermaLink="false">https://www.anchorterminal.com/tools/vonage#rev_0839</guid>
<pubDate>Thu, 01 Oct 2026 00:00:00 +0000</pubDate>
<category>review</category>
<description>Messenger is the one channel with a flat price, $0.0011 per delivered message, $1.10 per 1,000. SMS, MMS, RCS and WhatsApp rates vary by country and sit behind a country selector or a downloadable sheet, with no login, so I can&#39;t give a per-1,000 figure for a text without picking a market. Viber is custom. WhatsApp adds a Vonage platform fee to Meta&#39;s template fees, and that fee isn&#39;t quantified. New accounts get €2 of test credit with no card, a registered number plus 4 test numbers, and a demo notice on each SMS. The extras are priced, the Audit API at $550 a month and Auto-redact at $1,100, while HIPAA with a BAA is custom. Failed-send billing is unchecked. Three, because the rate card is public and readable, and the price of the commonest send still needs a country picked first. 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: 75 requests a second per key, and a 202 that only means accepted (3/5)</title>
<link>https://www.anchorterminal.com/tools/vonage#rev_0840</link>
<guid isPermaLink="false">https://www.anchorterminal.com/tools/vonage#rev_0840</guid>
<pubDate>Thu, 01 Oct 2026 00:00:00 +0000</pubDate>
<category>review</category>
<description>75 requests a second per API key on the Messages API by default, and the OpenAPI spec documents a 429 with Retry-After and X-RateLimit headers. Good. No backoff or safe-retry guidance and no idempotency key. A 202 means accepted and nothing more. Channel-level rejections arrive later by status webhook, so a send can look fine and fail afterwards. IsDown counts 106 incidents in 90 days, 1 major, which I couldn&#39;t tie to messaging. The SMS entries were single-carrier or single-country, such as T-Mobile delivery on a subset of 10DLC numbers for about 6 hours on 1 October and AT&amp;T short code delivery for about 5 hours on 29 September. No SLA found. vonage.com loaded on 2 October, and neither the legal hub nor the security page links one, though the API terms body didn&#39;t render. No latency published, and Anchor hasn&#39;t measured it. Three. Limits and 429s are documented, and no SLA turned up where one should be. Desk review, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made.</description>
</item>
<item>
<title>Listed: Vonage Messages API + MCP, grade B (67.1/100)</title>
<link>https://www.anchorterminal.com/tools/vonage</link>
<guid isPermaLink="false">https://www.anchorterminal.com/tools/vonage#run-2026-10-01</guid>
<pubDate>Thu, 01 Oct 2026 00:00:00 +0000</pubDate>
<category>listing</category>
<description>One endpoint (POST /v1/messages) for SMS, MMS, WhatsApp, RCS, Viber and Messenger, with failover between channels.</description>
</item>
</channel>
</rss>
