SMS gateway for the USA: published rate, 10DLC, route checks
US SMS is $0.0125 per message all-in on published routes, floor from $0.004, across 149 countries total. This US buyer page covers published rate, 10DLC and related A2P registration reality, why alphanumeric senders fail here, and how to verify routes with a 100-message probe. Destination spine facts stay on /countries/united-states/—link it, do not treat this as a duplicate sheet.
Published rate and segment billing
The published all-in figure for US destinations is $0.0125 per message. The published floor of from $0.004 is the low end across the whole 149-country coverage, not a US route promise; for US destinations treat $0.0125 as the working commercial number unless a specific route quote says otherwise. Coverage context is 149 countries total on the same gateway—US is one destination in that set, not a separate product island. Price-intent queries for sms gateway usa and sms gateway us should start from that published number, then move to registration and measurement, not from a feature tour.
Billing follows standard SMS segment rules. GSM-7 encodes up to 160 characters in a single segment, or 153 characters per segment when concatenated. UCS-2 (for non-GSM characters) encodes up to 70 characters single-segment, or 67 per segment when concatenated. Plan for segment counts in the 1–4 range for typical application traffic; each segment bills as a message unit against the published rate. If your templates mix GSM-7 and UCS-2 by locale, count segments per locale before you forecast spend.
Country-level constants, operator notes, and the living fact row for the United States live on /countries/united-states/. This page does not duplicate that spine. Use the fact sheet when you need destination facts; use this page when you need buyer mechanics, registration posture, and a concrete verification method you can rerun.
SMSRoute's US rate is published, not quoted-on-request: $0.0125 per message all-in.
| Encoding | Single segment | Concatenated per segment |
|---|---|---|
| GSM-7 | 160 | 153 |
| UCS-2 | 70 | 67 |
10DLC reality: registration is sender-side
A2P traffic to US numbers runs through registration regimes. Long-code traffic is expected to ride 10DLC brand and campaign registration. Toll-free originators go through toll-free verification. High-volume or specialized programs may use short codes. These are qualitative regime labels, not a substitute for carrier or aggregator documentation—but the structural point is stable across providers: registration is a sender-side obligation.
No SMS gateway waives that obligation on your behalf. If you hand unregistered or mis-registered traffic to a US route, the honest outcome is degradation: elevated filtering, sudden throughput collapse, or silent non-delivery rather than a clean API error at submit time. Providers differ in how much detail they surface in DLR codes; they do not differ in whether US carriers enforce the regimes. Gateway connectivity alone is not registration.
Treat registration status as part of send-path design, the same way you treat encoding and originator format. Before you load production volume, confirm which regime your traffic falls under and complete the sender-side steps for that class. When delivery quality drops after a template or originator change, re-check registration state first, then probe the route.
| Originator class | Registration regime | Notes |
|---|---|---|
| Local long code | 10DLC | Brand and campaign registration on the sender side |
| Toll-free | Toll-free verification | Verification before sustained A2P use |
| Short code | Short-code program | Separate provisioning path; not a long-code substitute |
Numeric originators only—no alphanumeric for US
State it plainly: alphanumeric sender IDs are not supported for US destinations. US terminating traffic expects numeric originators—long codes, toll-free numbers, or short codes under the regimes above. If your global template defaults to an alphanumeric From value, override it for US MSISDNs or the route will reject or filter the traffic.
This is a destination constraint, not a gateway preference flip. Mixing alphanumeric and numeric policies across a multi-country send path is a common integration bug: the same campaign code works in one market and fails in the US without an obvious submit-time error. Gate US-bound messages to numeric originators only, keep alphanumeric templates for destinations that accept them, and include originator format in your pre-production checklist beside 10DLC status.
SMSRoute cannot waive US registration regimes for anyone - published rates apply to compliant traffic, and the testing cluster verifies the route.
Carrier filtering and how to verify a route
US carriers filter aggressively. Throughput, delivery ratio, and latency are not honest single-number claims on any serious route sheet—the correct answer is that they vary by content class, registration state, originator reputation, time of day, and downstream path. Pages that imply one fixed throughput figure for all US A2P traffic are simplifying past usefulness. Unregistered or poorly aligned traffic degrades; registered traffic can still vary.
The fix is measurement, not brochure comparison. Run a 100-message probe across the candidate route with production-like content and the same originator class you will use at scale. Capture DLR outcomes, classify failures, and build a latency distribution rather than a single average. Watch API responses for HTTP 200 on accept and HTTP 429 under rate pressure so you know whether throttling is at the gateway edge or further downstream.
Drive the probe from a testing cluster you control so results are repeatable and comparable over time. Re-run when you change registration state, template language, originator, or route class. When a path degrades, the 100-message probe plus DLR analysis and latency distribution is how you detect it early—before customer-visible failures accumulate. Throughput after a clean probe still varies; keep sampling rather than freezing a one-time result into capacity plans.
Buying mechanics: signup, top-up, send-only
Access is email-only signup. Minimum top-up is $5. Balances accept crypto: BTC, ETH, USDT, XMR, LTC, and SOL. The product model is send-only: outbound SMS to destination MSISDNs, no rented numbers, no inbound MO path on this stack. If your use case needs two-way numbers, this gateway is the wrong tool; if you need outbound A2P with published pricing and route checks you can rerun, it matches the job.
When you compare list prices across providers, read each provider’s own page. Published list prices elsewhere often exclude carrier passthrough and registration-related fees that appear later in the real bill. Use a dated compare matrix that points at primary sources; do not trust aggregated total-cost figures invented by third parties or by one-page marketing summaries. The $0.0125 all-in figure here is the published commercial number for the US route class described—confirm the live quote at send time.
Operational posture stays simple: top up, authenticate to the API, submit outbound messages with numeric originators under the correct registration regime, and monitor DLR and latency from your side. No inbound inventory means you are not managing number lifecycle on this account. Keep registration and sender compliance work in your own processes where it belongs, and use the 100-message probe whenever you open or change a US route.
Frequently asked
- What is the published SMS gateway rate for the USA?
- The published all-in rate for US destinations is $0.0125 per message; the separate from $0.004 figure is the published floor across all 149 countries, not a US rate. Segment billing follows GSM-7 (160/153) and UCS-2 (70/67), with typical segment counts in the 1–4 range. Destination spine facts live on /countries/united-states/.
- Is 10DLC required to send A2P SMS to US numbers?
- A2P traffic to US numbers runs through registration regimes—10DLC for long codes, toll-free verification for toll-free originators, and short-code programs where applicable. Registration is a sender-side obligation no gateway waives; unregistered routes degrade under carrier filtering.
- Can I use an alphanumeric sender ID for US SMS?
- No. Alphanumeric sender IDs are not supported for US destinations. Use numeric originators only—long code, toll-free, or short code—under the matching registration regime, and verify the path with a 100-message probe before scaling.