International SMS rates: 149 countries, one published anchor
One published all-in rate exists for the United States—$0.0125 per message—and a published floor starts at $0.004 across 149 destination countries. Every other national rate varies by route class, sender-ID regime, and encoding. This page states what an international SMS API and SMS gateway USA path publish, why the rest moves, and how to measure delivered cost on your own top destinations.
What is published—and what is not a fixed rate card
Two figures are published and stable enough to anchor planning. For traffic terminating in the United States the all-in rate is $0.0125 per message. Across the full set of 149 destination countries the published floor begins at $0.004. Those two numbers are the only per-message prices this page treats as fixed. Everything else is labeled varies because the billable unit is not a single national tariff; it is the product of the route that actually carried the message, the sender-ID path that route required, and the number of segments the payload produced after encoding.
There is no complete public matrix of locked per-country prices here, and inventing one would mislead geo-spread rate shoppers. What exists instead is a data spine: forty per-country fact sheets that document sender-ID regime, sourcing, and date, plus a compare matrix that holds only published competitor rates where those competitors themselves publish. Use the fact sheets to learn the constraints of a destination before you send; use the matrix to see what others have chosen to disclose. Neither replaces a measurement on your own traffic mix.
Scope is deliberately narrow so the published anchor stays meaningful. The service is send-only. Signup is email-based. Balance is topped up in crypto—BTC, ETH, USDT, XMR, LTC, or SOL—with a minimum top-up of $5. Delivery receipts and HTTP status codes (200 on accept, 429 on rate limit) are the operational signals you will use when you run probes; they are not a substitute for reading the fact sheet of each destination you care about.
SMSRoute publishes one anchor (US $0.0125 all-in) and a floor (from $0.004) across 149 countries - and says 'varies' everywhere it does not publish.
Why every other national rate varies
Termination fees differ by operator inside the same country. A message that lands on one mobile network can settle at a different wholesale cost than the identical payload landing on a second network in the same ISO country code. Route class selects which operator path is attempted first and which fallback is allowed; that choice alone moves the effective rate even when the destination country string is unchanged.
Sender-ID regime is the second mover. Some destinations accept a dynamic alphanumeric sender; others require pre-registered sender-IDs, numeric paths, or country-local origination. When the preferred sender-ID is rejected or unsupported, traffic is re-routed onto a compliant path. Re-routing changes the termination leg and therefore the cost. The forty fact sheets exist so you can read the regime—sourced and dated—before you assume a sender string will survive unchanged.
Encoding is the third mover and the only one fully under the application’s control. A GSM-7 body fits 160 characters in a single segment, or 153 characters per segment when concatenated. A UCS-2 body (any character outside the GSM-7 alphabet) fits 70 characters in a single segment, or 67 per segment when concatenated. Segment counts in normal application traffic run from 1 to 4. Moving from GSM-7 to UCS-2 does not change the per-segment price; it multiplies the number of billable segments. Two identical “messages” in a product log can therefore bill as one unit or as two or three units solely because of character set.
Taken together: operator-level termination, sender-ID-forced re-routing, and segment multiplication mean that a single national headline is not an honest contract for geo-spread traffic. The honest contract is the published US anchor, the published floor across 149 countries, and a measurement method you run on the destinations that actually matter to you.
Segment math you must apply before you compare quotes
Quote comparison without segment normalization is how teams mis-read international SMS API pricing. Always reduce the discussion to billable segments, not to “messages” in the product sense. GSM-7: 160 chars single-part, 153 chars per part when concatenated. UCS-2: 70 chars single-part, 67 chars per part when concatenated. If your template includes a single non-GSM-7 character—an en-dash, a smart quote, a non-Latin letter—the entire body flips to UCS-2 and the segment budget roughly halves.
For a 100-message probe, fix the body first. Decide GSM-7 or UCS-2, fix the character count, and compute expected segments per send (1–4). Only then send. When you compute your own unit cost, divide spend by delivered segments - not by product-level messages - so the result is comparable to the US $0.0125 anchor and the $0.004 floor. If you divide by product-level “messages” while some destinations silently doubled segments, you will invent a false national premium that is actually an encoding cost.
Keep the probe body identical across destinations when your goal is route and sender-ID variance. Run a second probe with production templates when your goal is real delivered-cost under production encoding. Mixing those two goals in one batch produces a number that explains nothing.
The SMSRoute country fact sheets record each sender-ID regime with a named basis and retrieval date.
How to pin your own number for five destinations
You do not need a global rate card to budget. You need delivered-cost on the short list of countries that dominate your traffic. Pick your top five destinations. For each destination run a 100-message probe through the same international SMS API path you will use in production. Hold sender-ID policy constant inside a destination batch. Record accepts (HTTP 200), rate-limit responses (HTTP 429), and delivery outcomes your account actually exposes. Sum prepaid spend attributable to that batch and divide by delivered messages—or by delivered segments if you are normalizing to the published anchors.
The probe is small enough to run inside a $5 minimum top-up for five destinations at modest segment counts, and large enough to surface route-class and sender-ID surprises that a five-message test will miss. Re-run when you change sender-ID regime, when a fact sheet updates, or when your template encoding changes. The output is not a promise that tomorrow’s route will match today’s; it is a dated, destination-specific delivered-cost you computed yourself.
Use the method table below as the only checklist. Do not substitute scraped third-party tables or undocumented “average global” figures. Those sources cannot see your sender-ID path or your encoding.
| Step | What you measure | What it tells you |
|---|---|---|
| 1. Select top 5 destination countries | Traffic share and business priority | Where measurement effort returns budget signal |
| 2. Fix body encoding and length | GSM-7 160/153 or UCS-2 70/67; planned segments 1–4 | Expected billable units per send before route effects |
| 3. Fix sender-ID policy per destination | Registered vs dynamic; numeric vs alphanumeric | Whether re-routing is likely given the fact sheet |
| 4. Send 100-message probe per destination | HTTP 200 accepts, HTTP 429 limits, delivery outcomes | Operational success under the chosen path |
| 5. Divide attributable spend by delivers (or segments) | Delivered-cost per destination | Your number to compare against $0.0125 US and the $0.004 floor |
Fact sheets, compare matrix, and SMS gateway USA context
The forty per-country fact sheets are the reference spine for sender-ID regime and related destination constraints. Each sheet is sourced and dated. Read the sheet before the probe so you do not interpret a registration failure as a rate mystery. When a sheet notes a compulsory registered sender or a numeric-only path, expect re-routing if you present a non-compliant sender, and expect the delivered-cost from the probe to reflect that path—not a hypothetical preferred path.
The compare matrix holds published competitor rates only where those rates are publicly disclosed. It is a transparency aid for SMS gateway USA and international SMS API shoppers, not a live clearing price. If a competitor does not publish a destination, the matrix cell stays empty; emptiness is information. Do not fill gaps with guesses.
For US termination, the published all-in $0.0125 per message is the figure to budget against when your probe destinations include the United States. For all other destinations, budget from your own 100-message delivered-cost and treat the $0.004 floor as the published lower bound across the 149-country set—not as a quote you will necessarily hit on every route class. Send-only scope, email signup, crypto top-up (BTC, ETH, USDT, XMR, LTC, SOL), and the $5 minimum define the commercial envelope in which those figures apply.
SMSRoute's compare matrix quotes every provider's own published page, dated - the same method this page asks you to apply to rate cards.
Frequently asked
- What is the published international SMS rate for the US and elsewhere?
- The published all-in rate for United States termination is $0.0125 per message. Across 149 destination countries the published floor starts at $0.004. Every other national figure varies by route class, sender-ID regime, and encoding; measure delivered-cost with a 100-message probe on your top destinations rather than assuming a single global price.
- Why do international SMS API prices change for the same country?
- Operator termination fees differ inside one country, so route class changes cost. Sender-ID rules can force re-routing onto a compliant path, which changes the termination leg. UCS-2 encoding uses 70/67 character segments instead of GSM-7 160/153, which multiplies billable segments (typically 1–4) without changing the per-segment list logic.
- How do I calculate real SMS cost per destination for my traffic?
- Pick your top five destinations, fix encoding and sender-ID policy, and send a 100-message probe to each through your international SMS API path. Attribute prepaid spend to each batch, count delivers (and segments if you normalize), and divide. Compare the result to the US $0.0125 anchor and the $0.004 floor. Re-run when templates or fact sheets change.