vs

The SMS-Activate alternative built for developers

SMS-Activate closed in December 2025 — here is where its API users went.

SMS-Activate closed on 22 December 2025 and no longer sells numbers.“We have completely ceased our operation since December 22.”This page is kept for the people whose integration pointed at it — the table below compares what it offered against what we do, and the migration section shows the two lines you have to change.

SMS-Activate ran for ten years and pioneered cheap, high-coverage activation numbers. It shut down on 22 December 2025; its site now sells nothing. If you are here with scripts that used to point at it, the short version is that they keep working: Eveses speaks the same handler_api.php protocol, so swapping the host and the key is the whole migration. The longer version is the table below — the same breadth and per-OTP pricing, with typed SDKs, webhooks instead of polling, idempotent orders and automatic refunds for misses.

Feature
Eveses recommended
SMS-Activate closed
Per-OTP pricing
from $0.05
was from $0.05
Country / service coverage
190+ countries · 600+ services
Was very broad
Drop-in migration (keep your code)
Compatible gateway — swap the URL
—
Official typed SDKs (JS/Py/Go/PHP)
✓
✕
MCP server (Claude / Cursor / AI agents)
✓
✕
Webhooks (no polling)
✓
✕
Idempotency keys
✓
✕
Auto-refund on missed OTP
✓
Manual
Crypto + card top-up
✓
✓
No KYC
✓
✓

Why teams move from SMS-Activate to Eveses

1

Clean REST API with idempotency keys, webhooks, and official JS / Python / Go / PHP SDKs.

2

Automatic refunds when an OTP never arrives — you only pay for delivered codes.

3

One wallet, one key, no KYC — top up with crypto or card and start in minutes.

Being fair

When SMS-Activate might still be the better pick: There is no longer a case for choosing SMS-Activate: it stopped serving customers in December 2025. Its own farewell page points readers at hero-sms.com, which we compare separately — and if all you need is the very cheapest one-off activation from a low-level HTTP endpoint, that is the honest place to look next.

Eveses vs SMS-Activate — FAQ

▸What happened to SMS-Activate?
It closed. Its own site says "We have completely ceased our operation since December 22" — that was 22 December 2025, after about ten years. Withdrawals were available until 30 April 2026. The same page points readers at hero-sms.com as "a promising newcomer".
▸Is Eveses a drop-in SMS-Activate alternative?
Literally, yes. We run an sms-activate-compatible gateway: point your existing scripts at https://api.eveses.com/stubs/handler_api.php, swap in your Eveses key, and the same api_key/action query protocol works unchanged — no code rewrite. When you want the cleaner path, native REST + webhooks + typed SDKs are ready too.
▸Was Eveses cheaper than SMS-Activate?
Per-OTP pricing was comparable — both start around $0.05. Eveses also refunds misses automatically, so the cost per delivered code is lower than a headline price suggests.
▸Can I pay with crypto?
Yes — top up the wallet with crypto (via Heleket) or card, no KYC.
More comparisons

Migrate to Eveses in code

Your SMS-Activate code does not have to die with the service. We speak the same handler_api.php protocol — point your existing client at our host, swap the key, done.

Before — SMS-Activate
GET https://api.sms-activate.org/stubs/handler_api.php
    ?api_key=YOUR_SMSACTIVATE_KEY
    &action=getNumber&service=tg&country=0
After — Eveses (drop-in)
GET https://api.eveses.com/stubs/handler_api.php
    ?api_key=YOUR_EVESES_KEY
    &action=getNumber&service=tg&country=0

Same api_key / action / service / country query protocol — no code rewrite. When you’re ready for more, the native REST API (POST /api/v1/numbers/orders), webhooks and typed SDKs are waiting.

Switch from SMS-Activate in an afternoon

REST API, SDKs, webhooks, refunds for misses, no KYC. Top up and ship.