Vonage through Squiid

What Vonage is

Vonage, formerly Nexmo, provides communications APIs across several channels. Messages covers SMS, MMS, WhatsApp, Viber and Facebook Messenger through one API, Voice handles calls with call control objects, Verify runs multi-channel one-time passcodes that can fall back from WhatsApp to SMS to voice, and the Video API supports multi-party video sessions. Number Insight returns carrier and portability data for a number before you use it. Applications group credentials and webhooks, so a product with several sending identities keeps them separate rather than sharing one number.

Its strength for AI-coded products is reach and channel fallback. If your users are outside North America and Europe, delivery rates vary a lot by country and carrier, and being able to try WhatsApp before SMS materially improves whether a verification code arrives. That matters more than API elegance when the alternative is a user who cannot sign up. Number Insight is worth running before a bulk send, because messaging a landline or a disconnected number costs the same as messaging a real customer.

Why connect it through Squiid

Vonage is on the Squiid roadmap. When it lands, Squiid will provision the account, hold the API key and secret, and route calls through https://api.squiid.io/v1/vonage/... with Authorization: Bearer $SQUIID_API_KEY, with official SDKs working by base URL swap (gateway convention). Messages, minutes and verification attempts will meter against prepaid credits at Vonage's listed price on your single Squiid invoice, with the same protection that applies to every messaging provider: the credential stays with Squiid and your spending stops at the balance you funded. Verification attempts are billed on completion, which makes a failed channel cheaper than it would be if every attempt counted.

• One account, one key, one bill, one dashboard. Vonage sits beside every other service your project uses, on the same invoice and the same credit balance.
• Key custody. Squiid holds the Vonage credentials. Your code carries SQUIID_API_KEY, so VONAGE_API_KEY, VONAGE_API_SECRET, VONAGE_APPLICATION_ID, VONAGE_PHONE_NUMBER never land in a repository, a preview deployment or an agent’s context.
• Metering you can see. Every call is counted per service and per day, so you know what Vonage costs before the month ends.
• Pause on zero. When prepaid credits run out the gateway stops authorizing usage instead of running up a bill you did not fund.
• One rotation. Rotating the Squiid key cuts off every agent, worker and deployment at once, with no provider key to hunt down.

What you get

• A provisioned Vonage account with credentials held by Squiid
• SMS, WhatsApp, Viber and voice through one API
• Multi-channel verification with fallback
• Video sessions on the same account
• Vonage list pricing, no markup

How to connect Vonage

One variable replaces the provider credentials this service would normally need. Requests go to the gateway and the official SDKs work by pointing their base URL at it (gateway convention).

# .env
# replaces VONAGE_API_KEY, VONAGE_API_SECRET, VONAGE_APPLICATION_ID, VONAGE_PHONE_NUMBER
SQUIID_API_KEY=sq_live_xxxxxxxxxxxxxxxxxxxxxxxx

# every request: https://api.squiid.io/v1/vonage/...
# header:       Authorization: Bearer $SQUIID_API_KEY

Pricing through Squiid

Vonage charges per message, per minute and per verification attempt with country-specific rates, at the provider's listed price. Squiid passes that through at par: one dollar of prepaid credit is one dollar of Vonage usage, with no markup and no per-request margin.

Vonage has no subscription attached on Squiid today. If a plan is required for a feature you need, it passes through at the provider’s listed price with no Squiid fee.

Squiid adds no markup to provider prices. There is a free plan at $0 a month with a 15% fee when you top up credits, Solo at $19.97 a month with a top-up fee that starts at 8% and falls to 3.5% as your spend grows, Team from $29.97 a seat a month with the same ladder one point lower, and Custom with a rate of 3% or less. Credits are prepaid, so Vonage usage stops when the balance reaches zero rather than producing an invoice you did not fund. Auto top-up with a cap keeps production running without handing anyone an open-ended card.

If you leave

Export: channels, keys and delivery configuration are re-created in your own Vonage account from the documented setup. Squiid never owns your code, your schema or your domain, and the gateway speaks Vonage's own API, so the client change is a base URL. The handover page lists what happens for every provider in the catalogue.

Works with every coding agent

Vonage through Squiid is just an HTTP call with a bearer token, so every agentic coding tool can use it with the single key already in your environment:

• Claude Code
• Cursor
• ChatGPT
• Codex
• Grok
• Gemini CLI
• GitHub Copilot
• Windsurf
• Perplexity
• Devin
• Replit
• v0
• Lovable
• Cline

Vibe coding a feature on Vonage usually means asking for it in plain language and letting the agent write the integration. Because the key is Squiid’s rather than the provider’s, it can do that without ever holding a credential that could be leaked, logged or committed.