Everything VerifyRelay does, stated plainly.
Sends route across Twilio, Vonage, and more in live score order. Provider outages become retries, not incidents.
Per-route delivery rates with smoothing, so new routes start at a sensible prior instead of 0%.
Growth: SMS → voice. Scale adds WhatsApp. Critical codes get through when SMS is down.
Twilio status callbacks (signature-verified) and Vonage DLRs feed scoring and your audit trail.
Brand + campaign filing handled on every plan; provider filing fees passed through at cost.
Per-route delivery rates, attempt history per verification, degradation alerts.
Invalid numbers are rejected with a 400 before they cost you anything.
One endpoint to send, two webhook receivers, one health check. Stdlib-only server, no framework magic.
99.5% monthly delivery target measured from provider webhooks, with service credits — see terms.
POST /v1/verify/send — the number is E.164-validated before anything is billed.
The best-scoring provider for the destination sends first.
The provider's delivery receipt reports a hard failure — the send re-routes instantly, with no code change on your side.
The next provider in score order delivers it, and the receipt is written to your audit trail.
The failed attempt lowers that route's live score, so the next send already knows.
We'd rather tell you what's roadmap than let you discover it after signup.
| Area | v1 reality |
|---|---|
| Carrier network | We are not a carrier. Every message goes through a third-party provider's network. |
| Providers | Twilio + Vonage adapters are implemented in code; no provider account is configured yet, so live SMS delivery is not available today — it starts only after provider credentials are provisioned and 10DLC registration completes. Telnyx/Sinch adapters are roadmap — the router is provider-agnostic by design. |
| Vonage webhooks | Ingested; signature verification is roadmap. Use an IP allowlist until then. |
| Scale tier escalation step; template approval per Meta's rules applies. |
provider_not_configured response — no message is sent and no delivery is claimed.