smsroute is a SMS gateway provider delivering A2P SMS to any US mobile number from $0.0125 per message — 10DLC compliance included at no extra cost. TCR brand vetting, campaign registration, and carrier trust-score handling are managed for you, so your SMS gateway integration ships in minutes instead of weeks. Routes cover all three national carriers (Verizon, AT&T, T-Mobile) with 99.0% delivery success and 212 ms median latency from our North American POP, verified against our rolling 90-day performance data. Pay in Bitcoin, USDT, Ethereum, Litecoin, Monero, or Solana. No KYC at signup.
How to Send SMS to the United States
SMS gateway for United States: A US SMS gateway is a service that routes text messages from your application to US mobile carriers (Verizon, AT&T, T-Mobile) through their SMS networks. smsroute acts as your SMS gateway provider — you send messages via our REST API, and we deliver them to any US mobile number in under 220 milliseconds on average, with 99.0% delivery success. Unlike consumer SMS apps, a gateway gives you an API and campaign management for automated, high-volume SMS routing.
Sending SMS to US mobile numbers requires a valid E.164 formatted number, a registered 10DLC campaign (or shared campaign), and an API key (available from your SMS gateway dashboard). Here's the fastest path from zero to message delivered:
Step 1 — Sign up at smsroute.cc
Create a free account with just an email address. No KYC, no corporate documents, no ID upload. Once registered, you can access the dashboard and view your API key immediately.
Step 2 — Top up with cryptocurrency
Deposit a minimum of $5 using Bitcoin, USDT (TRC-20), Ethereum, Litecoin, Monero, or Solana. USDT TRC-20 credits within about one minute. All six payment methods are accepted at the same $0.0125 per-message rate — no hidden markups by coin.
Step 3 — Send via REST API or dashboard
POST to https://api.smsroute.cc/sms/send (see our SMS gateway API
documentation) with your API key in the
Authorization: Bearer header. Include the destination in E.164 format (e.g.
+14155552671), your sender number, the campaign_id, and the message body.
Prefer a UI? The smsroute dashboard includes a web-based message composer for one-off sends and CSV upload for batch campaigns. Every send — API or UI — requires a campaign ID for US destinations.
import os, requests
r = requests.post(
"https://api.smsroute.cc/sms/send",
headers={"Authorization": f"Bearer {os.environ['SMSROUTE_API_KEY']}"},
json={
"to": "+14155552671",
"from": "+15551230001",
"campaign_id": "CMP_01HXYZABC",
"body": "Your verification code is 384921. Do not share.",
},
)
print(r.json())
curl -X POST https://api.smsroute.cc/sms/send \
-H "Authorization: Bearer $SMSROUTE_API_KEY" \
-d '{
"to": "+14155552671",
"from": "+15551230001",
"campaign_id": "CMP_01HXYZABC",
"body": "Your verification code is 384921. Do not share."
}'
import fetch from "node-fetch";
const apiKey = process.env.SMSROUTE_API_KEY;
const res = await fetch("https://api.smsroute.cc/sms/send", {
method: "POST",
headers: {
Authorization: `Bearer ${apiKey}`,
"Content-Type": "application/json",
},
body: JSON.stringify({
to: "+15551234567",
from: "+15551230001",
campaign_id: "CMP_01HXYZABC",
text: "Your verification code is 384921",
}),
});
console.log(await res.json());
package main
import (
"bytes"
"encoding/json"
"fmt"
"io"
"net/http"
"os"
)
func main() {
payload, _ := json.Marshal(map[string]string{
"to": "+15551234567",
"from": "+15551230001",
"text": "Your verification code is 384921",
})
req, _ := http.NewRequest("POST",
"https://api.smsroute.cc/sms/send",
bytes.NewBuffer(payload))
req.Header.Set("Authorization", "Bearer "+os.Getenv("SMSROUTE_API_KEY"))
req.Header.Set("Content-Type", "application/json")
resp, err := http.DefaultClient.Do(req)
if err != nil { panic(err) }
defer resp.Body.Close()
body, _ := io.ReadAll(resp.Body)
fmt.Println(string(body))
}
'+15551234567',
'from' => '+15551230001',
'text' => 'Your verification code is 384921',
], JSON_UNESCAPED_UNICODE);
$ch = curl_init('https://api.smsroute.cc/sms/send');
curl_setopt_array($ch, [
CURLOPT_POST => true,
CURLOPT_RETURNTRANSFER => true,
CURLOPT_HTTPHEADER => [
'Authorization: Bearer ' . $apiKey,
'Content-Type: application/json',
],
CURLOPT_POSTFIELDS => $payload,
]);
echo curl_exec($ch);
curl_close($ch);
from across all messages.
If that number is attached to a campaign whose approved use case is "2FA" and you send an order confirmation
through it, Verizon will filter the message as use-case mismatch. Route marketing and transactional traffic
through separate campaigns.
US Phone Number Format
Every US mobile number follows the North American Numbering Plan: +1 followed by a 3-digit area code and a 7-digit subscriber number (10 digits total). When sending SMS via API, use strict E.164 format — a plus sign, the country code 1, then the full 10-digit number.
Examples: +12125551234 (New York City), +13105551234 (Los Angeles),
+14155552671 (San Francisco).
US mobile and landline ranges share prefix space, so you cannot distinguish them by number alone. smsroute
performs an HLR lookup at send time to confirm the destination is a wireless line before billing. Landline
destinations return invalid_destination_type and are not charged.
A2P 10DLC — The Registration Process Nobody Explains Well
Every message you send from an application to a US mobile number on a 10-digit long code is A2P 10DLC traffic, and since late 2023 the three major carriers enforce 100% registration. Unregistered A2P is dropped silently on Verizon and T-Mobile and surcharged plus throttled on AT&T. There is no grace period left.
Here's the deal: Brand registration. Register your sending entity with The Campaign Registry (TCR). Costs $4 one-time. Requires legal company name, EIN (or SSN for sole proprietors), address, website URL, and a named representative. TCR passes the brand to a third-party vetting provider that returns a numeric trust score from 0 to 100.
Campaign registration. A campaign is the use case — "2FA", "Marketing", "Account Notification", "Low Volume Mixed", etc. Each campaign costs $10 one-time and $2-$10/month depending on use case. Plan 5-7 business days from brand submission to all three carriers returning "approved."
Per-message surcharges. Once approved, every message carries a per-segment carrier surcharge: T-Mobile ~$0.003, Verizon ~$0.0025, AT&T ~$0.002. These are included in smsroute's $0.0125 rate.
Sole-proprietor vs standard brand. Sole proprietors skip vetting (same-day approval) but are capped at ~1,000 messages/day lifetime. Standard brands with EIN unlock higher throughput. For production, register as a standard brand — form a single-member LLC for $100 and file with the EIN. The vetting improvement pays back within a week.
Shared campaigns. smsroute operates pre-registered shared campaigns for OTP, customer-care, and low-volume alerts up to ~200 messages/day per account. Above that, file your own brand through the smsroute dashboard.
10DLC Throughput Tiers — What TPS Your Trust Score Unlocks
Trust score (0-100) determines messages-per-second per carrier:
| Tier | Score | T-Mobile TPS | Verizon daily cap | AT&T TPS |
|---|---|---|---|---|
| Low | 0-39 | 0.25 | ~4,500/day | 0.5 |
| Standard | 40-74 | 1-3 | ~200,000/day | 1-2 |
| High | 75-100 | 10+ | unlimited (soft) | 4-8 |
Verizon's Low-tier daily cap (~4,500 messages) is the most common throughput gotcha. The fix is vetting, not retries. TCR Fast-Track Vetting (~$40 extra) returns a trust score in under 4 hours.
TCPA Consent — What Actually Holds Up in Court
The Telephone Consumer Protection Act (47 USC § 227) is privately enforceable at $500 per non-consenting message, tripled to $1,500 for willful violations. Class actions routinely settle at 8- and 9-figure sums.
Prior express consent. The consumer gave you their number where SMS was reasonably expected (e.g., "SMS me order updates" checkbox). Sufficient for transactional messages: OTP codes, delivery notifications.
Prior express written consent. An affirmative written agreement stating (a) they will receive SMS, (b) SMS may use automated systems, (c) consent is not a condition of purchase, (d) standard rates apply. Required for marketing. Pre-checked boxes do not qualify.
Autodialed marketing. Must include all four elements above, be electronically captured with a timestamp, and be retrievable for five years. Statute of limitations: four years under 28 USC § 1658.
Mobile Operators in the United States
US mobile is a tight triopoly: Verizon (37%), T-Mobile (34%), AT&T (29%), plus MVNOs reselling on these networks.
Verizon Wireless. Verizon has the most aggressive trust-score enforcement. Daily cap of ~4,500 msgs/day at low-trust tier. Strictest sample-message review. Median latency 180 ms from our POP.
T-Mobile US. Most transparent throughput tiers. Content-based spam filtering blocks URL shorteners (bit.ly, t.co). Median latency 224 ms.
AT&T Mobility. Most lenient on content filtering. No hard daily cap at low-trust tier. Median latency 205 ms.
MVNOs (Mint, Cricket, Metro, Visible, US Mobile, Spectrum Mobile) inherit their host network's A2P rules. smsroute handles all MVNO traffic automatically.
Supported Networks in the United States
smsroute connects directly to the three national carriers and their MVNOs (detailed in our mobile operator breakdown above). Beyond the big three, the following networks and operators are reachable through our US routes:
AT&T Mobility, Verizon Wireless, T-Mobile US, US Cellular, Cricket Wireless, Metro by T-Mobile, Mint Mobile, Visible, Spectrum Mobile, Xfinity Mobile, Boost Mobile, Consumer Cellular, Straight Talk, TracFone, Net10, Google Fi, Ting, Republic Wireless, TextNow, FreedomPop, Ultra Mobile, Red Pocket, H2O Wireless, Lycamobile, Tello Mobile, Reach Mobile, Twigby, Gen Mobile, Good2Go Mobile, Page Plus Cellular, Total Wireless, Simple Mobile, Walmart Family Mobile, Jethro Mobile, Bluegrass Cellular, Carolina West Wireless, Cellcom, Chariton Valley, Chat Mobility, Copper Valley, Cross, GCI, Golden State Cellular, Illinois Valley Cellular, Indigo Wireless, Nex-Tech, Northeast Colorado Cellular, Northwest Missouri Cellular, PACE, Panhandle, Pine Belt, Pioneer, Plateau, RINA, Sagebrush, SI Wireless, Snake River PCS, South Central, Standing Rock, STRATA, Thumb Cellular, Uintah Basin, Union Telephone, Viaero, West Central, WestLink.
This includes all networks that interconnect via the national carriers. smsroute routes to every operator on this list at the same $0.0125/msg rate with no per-network surcharges.
Who Uses SMS in the United States
Businesses across every industry use bulk SMS to reach US mobile subscribers. Here are the most common use cases we see on the smsroute platform:
Two-factor authentication and OTPs. Login codes, password resets, and transaction verification for SaaS platforms, crypto exchanges, and online services. OTP delivery to US handsets averages 200 ms.
E-commerce and retail. Order confirmations, shipping updates, delivery notifications, and abandoned cart reminders. SMS open rates exceed 90% within 3 minutes.
Appointment reminders. Healthcare clinics, dental offices, auto repair shops, and service businesses reduce no-shows by 30-50% with SMS reminders.
Banking and finance. Fraud alerts, balance notifications, payment confirmations, and due-date reminders. Financial services is the single largest vertical for A2P SMS in the US.
Marketing and promotions. Time-sensitive offers, flash sales, loyalty program updates, and event announcements. SMS marketing campaigns achieve 10-20% conversion rates.
Alerts and notifications. System outage alerts, security warnings, school closures, weather alerts, and emergency notifications.
Bulk SMS Sending Best Practices
To maximize delivery rates to US carriers, follow these guidelines:
Use a registered 10DLC campaign. Unregistered A2P traffic is filtered at the carrier level. Register your brand and campaign with TCR before sending any application-to-person traffic.
Include opt-out instructions. Every marketing message must include "Reply STOP to opt out." Transactional messages should include opt-out instructions per carrier requirements.
Use clear opt-in language. Your signup form or consent checkbox must clearly state that the user agrees to receive SMS messages. Pre-checked boxes do not count as consent.
Keep your message samples accurate. Verizon, AT&T, and T-Mobile all review campaign sample messages. If your actual traffic differs from the samples, messages may be filtered. Submit samples that closely match real traffic.
Avoid SHAFT content. All three carriers block Sex, Hate, Alcohol, Firearms, and Tobacco content at the network level. Messages containing these keywords will be dropped without delivery receipt.
Use a branded short domain for links. T-Mobile filters messages containing link shorteners (bit.ly, t.co, ow.ly). Use a branded domain shortener pointing to your own website.
Separate campaign IDs by use case. Marketing and transactional traffic should use different campaigns. Sending a promotional message through a "2FA" campaign triggers Verizon's use-case mismatch filter.
Alternative Ways to Send SMS to the United States
Beyond developer SMS APIs, several other methods can reach US mobile numbers:
Email-to-SMS. Every major US carrier provides an email-to-SMS gateway. Send to
number@vtext.com (Verizon), number@tmomail.net (T-Mobile), or
number@txt.att.net (AT&T). Free for low volumes but no delivery receipts, carrier-specific
formatting, and no 10DLC compliance.
Free VoIP apps. TextNow and TextFree offer free US numbers with SMS over Wi-Fi. Suitable for personal use but lack API access, SLAs, and 10DLC compliance.
Bulk SMS providers. BulkSMS.com ($0.0321/msg), ClickSend, LabsMobile, Zigatext, and Localphone offer web-based bulk sending at higher per-message prices than API-first providers.
Developer SMS gateways. Twilio ($0.0083/msg), Bandwidth ($0.0178), Vonage ($0.0182), and Sinch ($0.0198) offer similar API functionality. Most require KYC and bank/card payments. smsroute differentiates with crypto-only billing, no KYC, a $5 minimum, and same-price access to 149 countries.
Pricing vs Competitors
Let's be honest: Twilio undercuts smsroute on the US per-message rate — their direct carrier interconnects give them volume discounts smaller aggregators cannot match. Here is an honest comparison of US SMS pricing:
| Provider | Price per SMS | KYC Required | Min Top-Up | Crypto OK |
|---|---|---|---|---|
| smsroute | $0.0125 | No | $5 | Yes (6 coins) |
| Twilio | $0.0083 | Yes | $20 | No |
| BulkSMS.com | $0.0321 | Yes | -- | No |
| Bandwidth | $0.0178 | Yes | -- | No |
| Vonage | $0.0182 | Yes | $20 | No |
| Sinch | $0.0198 | Yes | -- | No |
| ClickSend | $0.0159 | Yes | $10 | No |
| Localphone | $0.0150 | No | $10 | No |
Where smsroute wins: $5 minimum (vs $20+ on competitors), crypto-native billing with no KYC, privacy-first architecture, and same-price access to 148 other country routes — most of which Twilio prices 30-50% higher. If your traffic is multi-country, the blended cost favors smsroute.
SMS Gateway USA — Provider Comparison by Compliance, Deliverability & Support
Choosing the right SMS gateway provider for US traffic means comparing more than per-message price. Compliance (10DLC registration), deliverability rates, and customer support quality vary significantly between providers. Here is a side-by-side comparison of the major SMS gateway providers serving the US market:
| Provider | Compliance | Deliverability | Customer Support | Best For |
|---|---|---|---|---|
| smsroute | 10DLC shared campaigns included; no KYC at signup; crypto-only billing | 99.0% rolling 90-day; 212 ms median; direct Verizon/AT&T/T-Mobile routes | Email + dashboard; developer docs; no phone support (crypto-native) | Privacy-focused devs, multi-country traffic, crypto users |
| Twilio | Full 10DLC TCR registration required; KYC mandatory; $20 minimum | 99.5%+ (largest US aggregator); carrier-level SLAs available | 24/7 support with paid plans; extensive docs; phone + email + chat | Enterprise, US-only high volume, teams needing phone support |
| BulkSMS.com | KYC required; 10DLC registration available but not managed | ~95-97% (aggregator-based routing); no direct carrier interconnects | Email + phone + knowledge base; G2-rated 9.2/10 | Web-based bulk sending, non-developer teams |
| Bandwidth | Full 10DLC with direct TCR integration; KYC required | 99.0%+ with direct carrier connections; own IP network | Enterprise support with account manager; phone + email | High-volume enterprise, CPaaS platforms |
| Vonage | 10DLC registration managed via Vonage API; KYC required | ~98.5%; multiple carrier routes; global POPs | 24/7 support; phone + ticket; developer community | Existing Vonage customers, voice + SMS needs |
| Sinch | Full 10DLC support; KYC required; campaign management | ~98%; strong in Europe; US routes via aggregation | Enterprise support; email + phone; 24/7 for premium plans | European businesses expanding to US |
Enterprise pricing comparison. For high-volume senders (100,000+ messages/month), most SMS gateway providers offer volume discounts. Twilio's enterprise plans start around $0.0055-$0.0065/msg at 1M+ monthly volume. Bandwidth negotiates custom rates for 500K+. smsroute's $0.0125/msg is flat with no volume tiers — the same price whether you send 10 or 10,000 messages. This makes smsroute most cost-effective for multi-country traffic at moderate volumes, while Twilio wins for US-only high-volume enterprise deployments.
Delivery Times and Reliability
From our production POP in Ashburn, Virginia, here are the real-world median latencies we measure daily across millions of SMS deliveries:
- Verizon: 180 ms
- AT&T: 205 ms
- T-Mobile: 224 ms
Rolling 90-day delivery success rate (operator-acknowledged delivery): 99.0%. Failures concentrate on carrier-filtered content (SHAFT violations) and 10DLC campaigns where sample messages do not match actual traffic.
Frequently Asked Questions
Do I need a 10DLC campaign for OTPs and password-reset codes?
Yes, if you send the OTP from a 10-digit long code. The Campaign Registry does not exempt transactional traffic — even a one-time login code must be attached to a registered campaign. The only way around TCR registration is to send from a toll-free number (8xx) or a short code. smsroute routes low-volume OTP traffic through pre-registered shared campaigns so individual users do not have to file themselves.
What is a TCR trust score and how is it calculated?
The Campaign Registry assigns every registered brand a numeric trust score from 0-100 at vetting time. The score is produced by a third-party vetting provider (Aegis Mobile or WMC Global) and reflects company age, EIN legitimacy, web presence, opt-in practice language, and historical spam flags. A score of 75+ unlocks High tier throughput (~10 TPS to T-Mobile). 40-74 is Standard. Below 40 is Low and capped aggressively.
How long does 10DLC registration actually take?
Brand registration: 1-2 business days for TCR to return a vetting score. Campaign registration: another 1-3 business days per carrier (Verizon reviews separately from AT&T and T-Mobile). Plan 5-7 business days end-to-end for a standard campaign. Sole-proprietor is faster (same-day) but caps at 1,000 messages/day lifetime.
Can I use a toll-free number instead of 10DLC?
Yes. Toll-free SMS (8xx numbers) has its own verification process run by each carrier via Somos, not TCR. Verified toll-free unlocks 3 messages/second steady. smsroute provisions verified toll-free numbers from $2/month with a 3-5 business day verification turnaround. Toll-free traffic has no TCR campaign requirement.
What's the TCPA statute of limitations?
Four years from the date of the last violating message under 28 USC § 1658. Each non-consenting SMS is a separate violation at $500 statutory damages (tripled to $1,500 for willful violations). Keep dated consent records for at least 5 years and use double opt-in where possible.
What format should US mobile numbers be in?
Strict E.164: +1 followed by the 10-digit number. US mobile and landline ranges share the same prefix space, so smsroute performs an HLR lookup at send time to confirm the destination is a wireless line before billing. Landline destinations return error code invalid_destination_type and are not charged.
Is alphanumeric sender ID supported in the United States?
No. Alphanumeric sender IDs are unsupported for A2P traffic in the US. Your sender must be a 10-digit long code, a toll-free number (8xx), or a 5-6 digit short code. Short codes are expensive ($500-$1,500/month lease) and reserved for very high-volume senders; 10DLC is the default for everyone else.
What happens if I send SMS to the US without registering 10DLC?
Traffic from unregistered long codes is filtered at the carrier level. Verizon and T-Mobile drop unregistered A2P silently. AT&T applies a surcharge and throttles. Since late 2023 the three carriers enforce 100% 10DLC registration for A2P with no grace period. Unregistered OTP traffic through smsroute's shared campaigns is the only way around self-filing.
How do enterprise SMS gateway API providers compare in pricing?
Enterprise SMS gateway pricing varies significantly by provider and volume. For US traffic at 100,000+ messages per month, Twilio offers the lowest per-message rate (~$0.0055-$0.0065/msg with enterprise discount) due to their direct carrier interconnects. Bandwidth negotiates custom rates starting around $0.005-$0.007/msg at 500K+ monthly volume. BulkSMS.com volume discounts bring their $0.0321 base rate to ~$0.015-$0.020/msg at high volumes. smsroute charges a flat $0.0125/msg with no volume tiers or commitments — the same price whether you send 100 or 10,000 messages. For cost-effective enterprise SMS gateway pricing, compare not just the per-message rate but also hidden costs: KYC overhead, 10DLC registration fees ($4 brand + $10 campaign + monthly campaign fees), carrier surcharges ($0.002-$0.004/msg on top of base rate), and support plan costs. smsroute includes 10DLC compliance and carrier surcharges in the $0.0125 flat rate with no KYC costs.
How do I send bulk SMS to multiple US numbers?
Use the smsroute dashboard CSV upload tool to send to thousands of US numbers in a single campaign. Each number must be in E.164 format. The dashboard handles campaign ID assignment, carrier routing, and delivery reporting automatically. For programmatic batch sends, use the REST API with an array of recipient numbers — each message is individually routed and tracked.