Rent for 20 minutes Referral program 🤑 Numbers rental from 1 day API Customer Service

Buy a number Transaction history Customer Service Referral program 🤑 Numbers rental from 1 day API

It seems you are offline. Please check your connection and try again.

Last updated: 10.08.2026

For AI agents

Phone numbers for AI agents: a fresh one for every signup

Your agent picks a country and a service, gets a private number over the API, reads the verification code, and hands the number back. Pay per code that arrives, not per month.

Get an API key Read the agent skill

agent : sv number api

# order a private number in Indonesia for Telegram
$ curl '…/handler_api?action=getNumber&service=tg&country=6&lang=en'
ACCESS_NUMBER:234242:6283812345678

# poll until the SMS lands
$ curl '…/handler_api?action=getStatus&id=234242&lang=en'
STATUS_WAIT_CODE
STATUS_OK:123456

# close it, or cancel and get the money back
$ curl '…/handler_api?action=setStatus&id=234242&status=6&lang=en'
ACCESS_ACTIVATION

211

countries your agent can pick a number from

1094

services with a ready code, from Telegram and WhatsApp to Google

$0.43

typical price of one verification. The cheapest sit at $0.01, and you pay only when the code arrives

20 min

the number belongs to your agent and nobody else, then it goes back

Counts read from the API on 06 August 2026. Live prices and availability sit in the buying widget.

What your agent does with a number

Three jobs, one API key. No human has to be at the keyboard for any of them.

Sign up where the service expects a local number

Most verification checks look at the country the number comes from. An agent registering an Indonesian marketplace account with a US number gets refused before the SMS is even sent. Pick the country in the request and that whole class of failure disappears.

Countries, operators and what is online right now come from getCountryAndOperators and getServicesAndCostWithStatistics. Your agent chooses on live data instead of a list pinned in its prompt.

Pick a country

Indonesia India Brazil United Kingdom United States Viet Nam Nigeria + 204 more

Same request shape for every one of them: country=<id>.

Read the code, not an inbox

The API hands back the verification code itself, already parsed out of the SMS. Your agent polls one endpoint and gets STATUS_OK:123456 back. There is no message text to pick the digits out of, and no regex to fix when a service rewrites its wording.

The number belongs to your agent alone for those 20 minutes. Nobody else sees the code, because nobody else holds the number.

Telegram 4 s ago

Your login code: 123456. Do not give this code to anyone, even if they say they are from Telegram.

123456

Returned by getStatus as STATUS_OK:123456

Carry the second factor too

An account is only finished when the second factor is handled. When the service shows an authenticator secret, your agent stores it next to the API key and computes the six digits locally, by RFC 6238, in thirty-second windows. No third party ever sees the secret.

The recipe with working code is in the agent skill, next to the calls that order a number and read the SMS.

Authenticator code

418 209

Computed from the stored secret. Nothing leaves the machine.

Give your agent a number in minutes

Hand the skill to Claude Code or Codex, connect the MCP server, or call the API directly. The runner changes; the four calls underneath do not.

Claude Code

claude code

# hand the skill to your agent and give it the key
$ curl -O https://sms-verification-number.com/en/agent-skill/
$ export SVN_API_KEY=your_key_here

# then just ask
> Read skills.md and register me a Telegram account on an Indonesian number.

Codex

codex

# the skill is plain markdown, any agent runner can read it
$ curl -O https://sms-verification-number.com/en/agent-skill/
$ export SVN_API_KEY=your_key_here

# point the agent at the file and let it work the API itself
> Follow skills.md. Order a number in Brazil for WhatsApp and give me the code.

MCP server

mcp

# nine native tools instead of raw HTTP: list_countries, list_services,
# order_number, wait_for_code, finish_activation, cancel_activation, totp_code
$ claude mcp add sv-number --env SVN_API_KEY=your_key_here -- npx -y sv-number-mcp

# the key stays in the environment and never reaches the model

Same tools in Codex, Cursor or anything that reads an MCP config.

Plain curl

curl

# 1. what is available and how well it delivers
$ curl '…?action=getServicesAndCostWithStatistics&country=6&lang=en'

# 2. take a number (maxPrice guards against demand spikes)
$ curl '…?action=getNumber&service=tg&country=6&maxPrice=1.50&lang=en'

# 3. poll every 3-5 s
$ curl '…?action=getStatus&id=234242&lang=en'

# 4. finish (6) or cancel and be refunded (8)
$ curl '…?action=setStatus&id=234242&status=6&lang=en'

Get an API key Read the API documentation

Why one permanent number stops being enough

A single phone number is fine while an agent talks to one person. It stops working the moment the agent starts creating accounts.

One number, kept forever

The second signup on the same number is the one that gets refused: services remember which number already verified an account. Registering in another country is off the table entirely, and when several agents are handed the same phone number, the codes that arrive on it are not only yours.

A new number for each signup

Every activation starts clean, in the country the service expects, held by nobody but your agent. When the code has been read, the number goes back and you stop paying for it.

Need a phone number that stays for a while, for an account that keeps receiving codes? Rent one from a day.

How SV Number compares with the carrier products

Each page reads what the other side publishes and puts it next to ours, including the rows where they win.

SV Number vs AgentLine: United States and Canada on their side, 211 on ours
SV Number vs AgentPhone: United States and Canada on their side, 211 on ours
SV Number vs AgentNumber: United States on their side, 211 on ours
SV Number vs OP: United States on their side, 211 on ours

What it costs

No subscription and no seat fee. You top up a balance and spend it per code.

Pay per code

$0.43 / verification, from $0.01

Private phone number, 211 countries, full API access
No code in 20 minutes and the money returns to your balance automatically
150 requests per second; what you can run is bounded by your balance

Get an API key

Rent from a day

The same number keeps receiving codes
For accounts that have to stay reachable
Ordered from the site; prices sit in the widget

See rental prices

What happens when it goes wrong

Verification fails sometimes. What matters is who pays for it.

If the code never arrives

If nothing arrives within the 20 minutes, the money goes back to your balance on its own. Your agent does not have to wait that long: setStatus=8 ends the activation right away and returns the money in full. Terms are in the refund policy.

How often the code actually arrives

getServicesAndCostWithStatistics returns, for each app and country, the share of codes that reached other users, alongside how many numbers are live right now. Where the share is measured, your agent can move to a better country before it spends anything instead of finding out by waiting.

Method names your code already knows

The methods are the ones used across this market: getNumber, getStatus and setStatus. An existing client mostly needs a new base URL, plus the lang parameter on every call: it picks the currency of the answer, and the default is not dollars.

Questions agents ask first

How does my agent get an API key?

A human registers an account, tops up the balance and copies the key from the profile page. After that the agent works on its own, with no confirmation step and no personal phone number required from anyone.

What happens if the SMS never arrives?

Cancel the activation and the money goes back to your balance in full. Your agent can do it as soon as it decides the code is not coming, and it does not have to cancel at all: an activation nobody closes expires after 20 minutes and refunds itself.

Can the number stay longer than 20 minutes?

Not as an activation. That one is built for a single verification and expires on its own. When an account needs to keep receiving codes, rent a number by the day from the site instead.

Can my agent send SMS or make calls from the number?

No. These numbers receive verification codes and nothing else. If your agent has to text people or hold phone calls, you need a carrier product, not this one.

Who else can see the code?

Nobody. The number is your agent's for the whole activation: while it holds the number, nobody else can be given it, and nobody else sees the code. That is what you are paying for.

Which countries and services are available?

211 countries and 1094 service codes as of 06 August 2026, and both lists move, so read them from getCountryAndOperators and getServicesAndCost rather than pinning them in your prompt.

How many activations can run at once?

The documented limit is 150 requests per second, and no daily quota is documented at all, so how much your agent can run comes down to your balance. Poll each order every three to five seconds rather than in a tight loop.

Give your agent a number it can use anywhere

Top up once, hand over the key, and let it work.

Get an API key Read the agent skill