• 228 destinations
  • No KYC, ever
  • Bitcoin, Monero, USDT and 4 more

Any traffic

Ship SMS today.
No contract, no sales call, no company file.

Build the whole integration against a test key that never bills, then fund a small balance in crypto and go live. Six endpoints, an OpenAPI file, samples in six languages.

01In short

For a startup or a side project, SMSMeteor removes the steps that usually sit between an idea and a delivered text: there is no business verification, no minimum commitment and no monthly fee. Every account has an sk_test_ key that validates and prices requests without sending, so the integration can be finished before any money moves; going live means switching keys and funding the balance in one of seven cryptocurrencies.

Recommended settings

To start
Email address and password
Before paying
sk_test_ key: validates, prices, never sends
Commitment
None: no contract, no monthly fee
API
Six REST endpoints, OpenAPI 3.1
Limits
50 requests per second per key; 1,000 messages per API request
Reach
228 destinations from one integration

02How it works here

From nothing to delivered, in 4 moves.

  1. 01Create the account

    An email address and a password. No company name, no documents, no call.

  2. 02Build on the test key

    Same validation, prices and webhook events as production, with status test and no billing.

  3. 03Fund a small balance

    USDT on a low-fee network is the cheapest way to move a modest amount. Credit never expires.

  4. 04Switch keys and ship

    Replace the test key with a live one. Nothing else in your code changes.

03What matters

What you skip

Most messaging vendors were built for enterprises: identity and business verification, sender registration programmes, a sandbox limited to verified numbers, support behind a paid plan. For a product that is three people and a repository, each of those is a week. Here the path is an email address, a test key and a rate card you can read before you sign up.

What you still owe the world is the content rule: consent for marketing, no impersonation, no spam. That is the whole of the compliance conversation.

04In practice

An API that survives production

The API is small on purpose: send, batch, retrieve, list, rates, balance. It has the properties that matter when things go wrong: idempotency keys so retries are safe, stable error codes, rate-limit headers, signed webhooks with retries and replays, and a request id on every response. The OpenAPI file generates a typed client in any language, so there is no SDK to keep updated.

05What it costs

1,000 messages, priced per destination.

One segment each at today's published rates. The same unit price applies to one message or a million; there is no plan, no setup fee and no monthly fee.

Rate card last updated 22 September 2026

DestinationRate per SMS1,000 messages
United States$0.0084$8.40
United Kingdom$0.0130$13.00
Germany$0.0238$23.80
India$0.0256$25.60
Brazil$0.0042$4.20
Indonesia$0.0698$69.80

Other destinations: cost calculator

06A message that works

What it looks like on the phone, and in the request.

The first message most products send.

MYAPPAny message
MyApp: your login code is 204 913. It expires in 10 minutes.
60 characters1 segment, GSM-7
cURLPOST /v1/messages
# 1. Build against the test key: validates and prices, never sends
curl https://api.smsmeteor.com/v1/messages \
  -H "Authorization: Bearer sk_test_..." \
  -H "Idempotency-Key: signup-1042-otp-1" \
  -d to="+14155550142" -d from="MYAPP" \
  -d text="MyApp: your login code is 204 913."

# -> { "id": "msg_...", "status": "test", "segments": 1, "price": "0.0084" }

# 2. Go live: same request with sk_live_...

07Pitfalls

Three mistakes we see, and how to avoid them.

  • A live key in the front end

    Keys belong on your server. Anything shipped to a browser or an app is public.

  • No idempotency key

    The first production timeout will teach you why. Add it on day one.

  • Testing only to your own country

    Sender rules differ by destination. Check the countries you plan to serve on the coverage page first.

09Questions, answered

SMS for startups, indie developers and side projects: questions, answered.

Can I try the API for free?

Yes. The test key validates requests, returns real prices and segment counts and fires test webhook events, without sending or billing. Live messages need a funded balance.

Is there a monthly fee or a minimum spend?

No. You pay per message at the published rate. An unused balance stays on the account indefinitely.

Do I need a registered company?

No. Individuals, sole traders and unincorporated projects can open an account with an email address.

Is there an SDK?

There is no SDK to install: the API is six endpoints of plain JSON. An OpenAPI 3.1 file generates a typed client in TypeScript, Python, Java and others, and samples exist in six languages.

How much do 1,000 messages cost?

It depends on the destination: $8.40 to the United States, $13.00 to the United Kingdom, $25.60 to India at today's rates.

What happens when my project grows?

Nothing changes: the same rate applies from the first message to the millionth, batches take 1,000 messages per API request, and there is no tier to negotiate.