# VirtualSMS, Full-Text Reference

> This is the llms-full.txt corpus for virtualsms.io: real page text concatenated for AI agents and crawlers that want the full content in one document instead of following links. See [/llms.txt](https://virtualsms.io/llms.txt) for the short, link-based index. Every section below reflects the live page it is drawn from at the "Last verified" date on that section; VirtualSMS changes pricing, tool counts, and country coverage regularly, so cross-check numeric claims against the live pages before relying on them for anything time-sensitive.

VirtualSMS is an account verification platform for individuals, developers, and AI agents. It combines one-time SMS verification, dedicated number rentals, matching-country proxies, and private cloud browser sessions behind one API, one MCP server, and one prepaid balance.

---

## Homepage (https://virtualsms.io/)

**Title:** Receive SMS Online | Real SIMs, 145+ Countries | VirtualSMS

**H1:** Skip the retry loop. Get the code.

Real-SIM temporary numbers for WhatsApp, Telegram, Google, Instagram, and 2500+ other platforms across 145+ countries. Numbers come from real carrier-issued SIM cards, not VoIP, so they pass the line-type checks that block cloud numbers on strict platforms. Above-the-fold facts: keep your real number private, 30-60s typical delivery, auto-refund if no code arrives, REST API plus MCP server for programmatic access, 24/7 access, carrier support including T-Mobile-class networks, works with 2500+ platforms.

*Last verified: 2026-07-19*

---

## Products

### One-time SMS verification (https://virtualsms.io/verifications)

**Title:** Buy SMS Verification, 2500+ Services, 145+ Countries | VirtualSMS

**H1:** Buy SMS Verification Codes, 2500+ Services, 145+ Countries

Temporary phone numbers for receiving a single SMS verification code. Choose a service and a country, pay per code from $0.05, and the code lands in the dashboard or via API. No credit card required to create an account; auto-refund if the code never arrives. Works across major platforms (Telegram, WhatsApp, Instagram, Facebook, Google, Discord) and thousands of smaller services.

*Last verified: 2026-07-19*

### Number rentals (https://virtualsms.io/rentals)

**Title:** Rent Virtual Phone Numbers, Long-Term SMS Rental | VirtualSMS

**H1:** Rent Virtual Phone Numbers, Long-Term SMS Rental

Dedicated numbers you keep for an extended period instead of a single code. Two tiers: Full Access rentals (usable for any service) and Platform rentals (locked to one chosen service, sourced via VirtualSMS's global supplier network for extended country reach). Durations run from 1 to 30+ days depending on tier. Each rental includes a private inbox for repeat logins, account recovery, and ongoing SMS access, plus a refund window if no SMS arrives shortly after purchase and the rental can be extended while still active.

*Last verified: 2026-07-19*

### Matching-country proxies (https://virtualsms.io/proxies)

Proxies that match the country of the phone number being verified, so the IP and the SIM tell the same story to a platform's fraud checks. Three pools are sold: datacenter, residential, and mobile. Billed by data usage; catalog and per-country availability are browsable before purchase via the API or MCP server (`list_proxy_catalog`, `list_proxy_locations`). Designed to pair with a rental or activation for platforms that cross-check IP geolocation against the phone number's country, not to be bought as a standalone anonymity product.

*Last verified: 2026-07-19 (positioning source: Design/canonical.json, capabilities[] and notes.proxyPools)*

### Private cloud browser sessions, beta (https://virtualsms.io/cloud-browser)

A country-matched cloud browser session you drive yourself in a live viewer, so the number, the IP, and the browser fingerprint all originate from the same country during signup. Currently in beta and invite-only: it sits behind a server feature flag plus an allowlist, so default accounts do not yet have access. Agent-driven navigation (letting an AI agent control the browser directly, not just a human viewing it) is a separate, further opt-in on top of the base feature. Beta access is requested via the Telegram channel: https://t.me/VirtualSMS_io.

*Last verified: 2026-07-19 (positioning source: Design/canonical.json, notes.cloudBrowser)*

---

## Services catalog (https://virtualsms.io/services)

**Title:** Supported Apps: SMS Verification by Platform | VirtualSMS

**H1:** Supported apps

A browsable catalog covering 2500+ platforms, showing 138+ popular apps by default with a link into the full dashboard catalog for the rest. Organized by category: Messaging, Social Media, Dating, Finance, Crypto, Shopping, Transportation, Food Delivery, Gaming, Entertainment, Travel, and Work and AI. Each listed app shows its icon, name, and starting price (for example "from $1.50"), with a search bar and category filters. Summary stats shown on the page: 2500+ platforms, 145+ countries, from $0.05.

*Last verified: 2026-07-19*

---

## Pricing (https://virtualsms.io/pricing)

**Title:** SMS Verification Pricing, From $0.05 | VirtualSMS

**H1:** Transparent Pricing

Two pricing models are shown on the page:

1. One-time verifications: from $0.05 per code, varying by service and country; popular services (Google, WhatsApp, Telegram) typically range $0.10 to $0.50.
2. Number rentals: tiered daily pricing shown on the page (illustrative tiers for 1, 7, 30, and 90 days; check the live page for the current numbers, since rental pricing varies by service, country, and tier and changes over time).

Volume discounts apply automatically based on trailing monthly spend, in bands from a base "Starter" tier up through a top "Volume" tier for accounts spending $5,000+ per month; the live page is authoritative for the exact percentages per band. The pricing page does not show proxy or cloud browser pricing; those are shown in-product and via the API/MCP tools (`rentals_pricing`, `list_proxy_catalog`).

*Last verified: 2026-07-19*

---

## AI agents & MCP

### AI agents landing page (https://virtualsms.io/agents)

**Title:** VirtualSMS for AI Agents, Real-SIM SMS Verification, x402 and MCP

**H1:** Real SIM SMS verification for AI agents

This page is the canonical entry point cited from [/llms.txt](https://virtualsms.io/llms.txt) for agent integration and self-declares this URL as canonical. It provides one endpoint enabling AI agents to receive OTP codes across 145+ countries and 2500+ services when signing up to platforms like WhatsApp, Telegram, Google, Uber, and Binance, using real carrier-issued SIM cards, not VoIP, which matters for services that aggressively reject virtual numbers.

**Connection method 1, MCP:**
Hosted: `https://mcp.virtualsms.io/mcp` (StreamableHTTP) with an `x-api-key` header. Local: `npx virtualsms-mcp` with a `VIRTUALSMS_API_KEY` environment variable. Tool groups covering discovery, account, and order management (see the [MCP server hub](https://virtualsms.io/mcp) section below for the current full tool breakdown, since this page's own copy has not been refreshed to match it).

**Connection method 2, x402 (USDC, no account):**
1. Agent POSTs to `/api/v1/x402/topup` with no payment and receives an HTTP 402 response with payment options.
2. Agent signs an EIP-3009 `TransferWithAuthorization` (Base) or a partially-signed transaction (Solana).
3. Agent retries the request with an `X-PAYMENT` header.
4. The server verifies and settles the payment, then atomically creates a user account and an API key.
5. The server returns 200 with the `api_key` and starting balance.

Supported networks: Base (USDC), Solana (USDC and USDT), BNB Chain (USDC and USDT via Permit2).

**REST API:** direct endpoints for purchase, order status, and balance checking. No general per-key rate limit; narrow IP-based limits apply to auth and order creation.

**Pricing (as shown on this page):** REST and MCP from $0.05 per activation, $1 minimum deposit. x402 deposits from $2.50 to $10,000 USDC, activations drawn from that balance at $0.05 to $5 per OTP depending on country. SMS bodies retained 7 days; order metadata retained indefinitely.

**Supported MCP clients:** Claude Desktop, Claude Code, Cursor, Windsurf, OpenClaw, Codex, Hermes, Cline, Zed, Continue.dev.

**Package registries:** npm (`virtualsms-mcp`), PyPI, Packagist, RubyGems, NuGet.

**Machine-readable resources under /agents:** `/agents/skill.md` (full markdown spec), `/agents/llms.txt` (its own index), `/agents/.well-known/x402.json` (x402 discovery manifest), and the [MCP server source on GitHub](https://github.com/virtualsms-io/mcp-server) (MIT licensed).

*Last verified: 2026-07-19*

### MCP server hub (https://virtualsms.io/mcp)

**Title:** VirtualSMS MCP Server for AI Agents: Claude, Cursor, Codex, Hermes

**Meta description:** Infrastructure for AI agents that need real-world phone verification. One MCP server for one-time SMS verification, dedicated number rentals, and matching-country proxies, all from one prepaid balance.

**H1:** SMS verification for AI agents

One MCP (Model Context Protocol) server covering one-time SMS verification, dedicated number rentals, matching-country proxies, and private cloud browser sessions, all behind one API and one prepaid balance. As of this verification the hosted server exposes 40 tools across four groups (independently cross-checked against the live server's own tool list on 2026-07-19): 18 activation and account tools (list_services, list_countries, get_price, find_cheapest, search_services, get_balance, get_profile, get_stats, get_transactions, create_order, get_sms, wait_for_sms, get_order, list_orders, order_history, cancel_order, cancel_all_orders, swap_number), 9 rental tools (rentals_pricing, rentals_available, rentals_services, rentals_price, create_rental, list_rentals, get_rental, extend_rental, cancel_rental), 10 proxy tools (list_proxy_catalog, list_proxy_locations, buy_proxy, list_proxies, generate_proxy_endpoint, rotate_proxy, test_proxy, get_proxy_usage, get_proxy_usage_history, set_proxy_targeting), and 3 other tools (retry_order, check_number, start_manual_registration_session).

**Connect (hosted, recommended):** `https://mcp.virtualsms.io/mcp`, transport StreamableHTTP, auth via an `x-api-key` header carrying an API key from Settings > API Keys.

```json
{
  "mcpServers": {
    "virtualsms": {
      "type": "streamableHttp",
      "url": "https://mcp.virtualsms.io/mcp",
      "headers": { "x-api-key": "vsms_your_api_key_here" }
    }
  }
}
```

**Connect (local install alternative):** `npx -y virtualsms-mcp` over stdio with a `VIRTUALSMS_API_KEY` environment variable.

**Supported clients:** Claude Desktop, Claude Code, Cursor, Windsurf, OpenClaw, Codex, Hermes, Cline, Zed, Continue.dev.

**Setup steps:** sign up free and create an API key from Settings > API Keys; paste the MCP configuration JSON into the client's config file; restart the client and verify with a prompt like "What's my VirtualSMS balance?"

*Last verified: 2026-07-19*

### Claude (https://virtualsms.io/mcp/claude-skill)

**Title:** VirtualSMS Claude Skill: SMS verification for Claude Code and Desktop

Recommended (hosted MCP): paste the same hosted JSON config shown above into Claude's MCP settings, insert a real API key, restart.

Local install (Claude Code CLI), a single command:
```bash
claude mcp add --scope user virtualsms -- npx -y virtualsms-mcp -e VIRTUALSMS_API_KEY=your_key
```

Claude Desktop: paste the JSON config into `claude_desktop_config.json` (macOS: `~/Library/Application Support/Claude/`; Windows: `%APPDATA%\Claude\`; Linux: `~/.config/Claude/`), then restart the app.

*Last verified: 2026-07-19*

### Codex (https://virtualsms.io/mcp/codex-config)

**Title:** VirtualSMS Codex Config: SMS verification for OpenAI Codex CLI

Recommended (hosted MCP, HTTP), add to Codex MCP settings:
```
[mcp_servers.virtualsms]
url = "https://mcp.virtualsms.io/mcp"
http_headers = { "x-api-key" = "vsms_your_api_key_here" }
```

Alternative (local Node install), append to `~/.codex/config.toml` (or `%USERPROFILE%\.codex\config.toml` on Windows):
```
[mcp_servers.virtualsms]
command = "npx"
args = ["-y", "virtualsms-mcp"]
env = { VIRTUALSMS_API_KEY = "your_key_here" }
```

Verify with `codex --list-tools | grep virtualsms`.

*Last verified: 2026-07-19*

### Cursor (https://virtualsms.io/mcp/cursor-rules)

**Title:** VirtualSMS Cursor Rules: SMS verification for Cursor

Recommended (hosted MCP, HTTP): paste the hosted JSON config into Cursor's MCP settings (Settings > MCP > Add new MCP Server), insert a real API key, restart Cursor.

Alternative (local Node install): save an MDC rule file to `.cursor/rules/sms-verification.mdc` in the project root, then add the MCP server config as above.

*Last verified: 2026-07-19*

### Hermes (https://virtualsms.io/mcp/hermes-mcp)

**Title:** Hermes Agent MCP: SMS Verification for Nous Research Hermes

Recommended (hosted HTTP): add the hosted JSON config to Hermes MCP settings, insert a real API key, restart Hermes.

Alternative (local Node install):
```json
{
  "mcpServers": {
    "virtualsms": {
      "command": "npx",
      "args": ["-y", "virtualsms-mcp"],
      "env": { "VIRTUALSMS_API_KEY": "your_key_here" }
    }
  }
}
```

*Last verified: 2026-07-19*

### OpenClaw (https://virtualsms.io/mcp/openclaw-skill)

**Title:** VirtualSMS OpenClaw Skill: SMS verification for OpenClaw agents

Recommended (hosted MCP, HTTP): add the hosted JSON config to OpenClaw's MCP settings, insert a real API key, restart the workspace. No Node.js required.

Alternative (local Node install): the `virtualsms-mcp` npm package over stdio, with `VIRTUALSMS_API_KEY` set as a workspace environment variable, then restart the workspace. The API key lives in the workspace environment; agents in that workspace do not see it directly.

*Last verified: 2026-07-19*

### Windsurf (https://virtualsms.io/mcp/windsurf-workflow)

**Title:** VirtualSMS Windsurf Workflow: SMS verification for Codeium Windsurf

Recommended (hosted MCP, HTTP): add the hosted JSON config to Windsurf's MCP settings, then paste the `.windsurfrules` file into the project root and restart Windsurf.

Alternative (local Node install): save `.windsurfrules` as a markdown file in the project root, then add the MCP server config through Windsurf settings the same way.

*Last verified: 2026-07-19*

---

## FAQ (https://virtualsms.io/faq)

**Q: What is VirtualSMS.io?**
A: VirtualSMS.io is a service that provides virtual phone numbers from real physical SIM cards for receiving SMS verification codes, spanning 145+ countries and 2500+ services.

**Q: How does VirtualSMS.io work?**
A: The platform maintains real carrier-issued SIM cards across 145+ countries. When a number is requested, the system reserves one of these SIMs. SMS routes through the cellular network and displays in the account dashboard within seconds.

**Q: How do I sign up?**
A: Account creation needs only an email and a password. No KYC or government ID required. Balance is funded with cryptocurrency or regional payment methods.

**Q: How long does access to a number last?**
A: Single-use activations have a 20-minute order window to receive the verification SMS. Rentals run from 4 hours to multiple weeks.

**Q: What is the difference between an activation and a rental?**
A: An activation is a single-use SMS verification, one inbound SMS, a 20-minute window, the lowest price tier. Rentals reserve the same number for hours or days and accept multiple SMS.

**Q: How much do verifications cost?**
A: Pricing starts at $0.05 per single-use verification, up to roughly $1.50. Rentals from $0.25/day, varying by service, country, and availability.

**Q: What payment methods are accepted?**
A: Cryptocurrency and regional payment methods via third-party processors; the options shown on the deposit screen are authoritative.

**Q: What is the minimum deposit?**
A: Minimum deposit is $2, covering a typical activation plus a small buffer. No maximum, no expiry.

**Q: Are there subscription fees or monthly minimums?**
A: No. The product is purely pay-as-you-go. No monthly fees, no subscription tiers, no usage minimums, no commitment to recurring spend.

**Q: Why is real-SIM pricing higher than VoIP-based competitors?**
A: Operating real cellular SIM cards in 145+ countries costs roughly 5-10x more per number than pulling VoIP from upstream carriers. Real-SIM numbers pass carrier line-type checks that VoIP numbers consistently fail on strict platforms.

**Q: Do you offer volume discounts?**
A: API resellers running consistent monthly volume above $5K negotiate custom pricing case by case. Retail customers receive published per-verification pricing.

**Q: Which services can I verify?**
A: Over 2500+ services, including major platforms (Telegram, WhatsApp, Google, Facebook, Instagram, Discord, TikTok, Snapchat, Twitter/X, LinkedIn), crypto exchanges (Binance, Coinbase, Kraken, KuCoin), finance (PayPal, Revolut, Cash App), shopping (Amazon, eBay, Uber, Lyft), entertainment (Netflix, Spotify, Steam, HBO Max), and many regional or niche services.

**Q: How reliable is verification on WhatsApp and Telegram?**
A: Real-SIM routes pass Telegram and WhatsApp anti-burner detection because the numbers are genuine cellular subscribers rather than VoIP. Measured across 3,720 codes, the median arrival time is 56 seconds on WhatsApp and 70 seconds on Telegram. Common failures stem from country mismatch or platform-side rate limiting.

**Q: Can I use VirtualSMS for Tinder, Bumble, and other dating apps?**
A: Yes. Tinder is the strictest of the major dating platforms because it cross-checks the number against device fingerprints and IP geolocation.

**Q: Will banking and crypto KYC accept these numbers?**
A: Most banking and crypto-exchange flows accept the SMS for the verification step itself, since the carrier-fingerprint check passes because the number is real cellular. Broader KYC depends on identity documents and institution policy.

**Q: What happens when a service is not in your catalog?**
A: Reach out via the Telegram support bot or email with service details. New services get added as customer volume justifies onboarding the routing logic.

**Q: Can I receive long-form SMS or one-time-password codes from custom platforms?**
A: Any platform that delivers a one-time code via standard SMS will work, regardless of code format (4-digit, 6-digit, alphanumeric, or full-sentence-with-link).

**Q: Which countries do you support?**
A: Coverage spans 145+ countries with deep inventory in Europe (United Kingdom, Germany, France, Spain, Italy, Netherlands, Poland, Czech Republic, Lithuania, Estonia, Romania, Bulgaria), North America (United States, Canada, Mexico), Asia (Indonesia, Malaysia, Philippines, Vietnam, Thailand, India, Pakistan, Bangladesh, Hong Kong), and growing weight in Latin America, Africa, and the Middle East.

**Q: How do I pick the best country for a given service?**
A: Country options are sorted by recent success rate. Pair the SIM country with a regional proxy for platforms cross-checking IP/region; use the cheapest available option for region-agnostic platforms.

**Q: Why is country availability dynamic?**
A: Inventory rotates continuously. New country routes get added when customer demand crosses the threshold that justifies operating physical SIMs in that region; existing routes get quarantined when delivery quality on a specific service-country combo drops.

**Q: Do you support phone numbers from the United States?**
A: Yes, US numbers are available, but availability fluctuates because the US verification market has the highest demand and the strictest carrier policies.

**Q: Can I request a country that is not currently listed?**
A: Yes, contact support. New country routes get added when there is a clear customer demand signal, usually within a few weeks for tier-1 markets.

**Q: What happens if no SMS arrives?**
A: If the SMS does not arrive within the 20-minute order window, the activation auto-refunds the full amount to the balance. No support ticket required.

**Q: What if the SMS arrives but the platform rejects the code?**
A: Contact support via the Telegram bot with the order ID; the route gets reviewed and the activation is credited manually if appropriate.

**Q: Can I cancel an order before the SMS arrives?**
A: Yes. Cancellation refunds the full amount to the balance. Cancelled orders don't count against the account.

**Q: Do refunds go back to my crypto wallet or to platform credit?**
A: Refunds always land as platform credit. Crypto deposits are one-way; refunds are instant platform credit.

**Q: Do I need to verify my identity to use VirtualSMS?**
A: No. Account creation needs only an email and a password. No government ID, proof-of-address, or selfie verification required.

**Q: Is my personal information safe?**
A: Only what is needed to operate the service is collected: order metadata (which service, which country, which number), inbound SMS bodies during the active order window, and standard server logs. Data isn't sold or shared.

**Q: What happens to the SMS content after I receive it?**
A: Inbound SMS during the active order window is stored on the platform for viewing in the dashboard. After the order window closes, message bodies are retained briefly for dispute resolution (typically 30 days) and then purged.

**Q: Is VirtualSMS legal to use?**
A: Yes, providing virtual numbers for SMS verification is a legitimate service. Customers are responsible for ensuring their use complies with the terms of service of the platforms they are verifying accounts on, and with applicable local law.

**Q: Is there a REST API?**
A: Yes. The full REST API is documented at virtualsms.io/docs with Bearer-token authentication. There is no general per-key rate limit; narrow IP-based limits apply to specific write actions like auth and order creation.

**Q: What SDKs are available?**
A: Native SDKs are published on npm (`virtualsms-sdk` for JS/TS), PyPI (`virtualsms` for Python), Packagist (`virtualsms/sdk` for PHP), RubyGems (`virtualsms-sdk` for Ruby), and NuGet (`VirtualSMS` for .NET).

**Q: What is the MCP server and how do I use it?**
A: The Model Context Protocol (MCP) server lets AI agents drive the verification flow directly from Claude Desktop, Cursor, Claude Code, and any MCP-compatible client. See the [MCP server hub](https://virtualsms.io/mcp) section above, or github.com/virtualsms-io/mcp-server for the self-hosted source.

**Q: Are there webhooks for inbound SMS?**
A: Webhooks are available on request for accounts running automated workflows. Default is API polling; webhooks are recommended for 100+ orders per hour.

**Q: Can I run the API in a CI/CD pipeline?**
A: Yes, a common use case. Bearer-token authentication works cleanly in CI environments. Avoid embedding tokens in repositories or build logs.

*Last verified: 2026-07-19*

---

## Contact (https://virtualsms.io/contact)

**Title:** Contact VirtualSMS, Telegram, Email and GitHub Support

**H1:** Contact support

- Telegram bot: https://t.me/VirtualSMSioBot?start=support, for orders, balance, order status, refunds, account questions. Bot replies typically under 60 seconds; human escalation within 24 hours.
- Email: support@virtualsms.io, for partnerships, press, enterprise API, or requests needing attachments. Use subject prefixes (Partnership:, Press:, Enterprise:) for faster routing.
- GitHub: github.com/virtualsms-io, for REST API and SDK bugs, public issue reporting.
- Twitter/X: @VirtualSMSio, product announcements only.
- Status page: https://virtualsms.io/status
- API documentation: https://virtualsms.io/docs

*Last verified: 2026-07-19*

---

## Core facts

- Founded: 2022
- Country coverage: 145+ supported in catalog; typically 60+ in live stock at any given moment (varies by inventory)
- Services supported: 2500+
- Not VoIP: all numbers are real carrier-issued mobile SIMs
- Access channels: web dashboard, HTTP API, hosted MCP server, Telegram bot
- Payment: crypto (BTC, USDT, ETH, LTC) and cards; agent payments also available via the x402 protocol (see /llms.txt for the x402 endpoint details)

---

*This document is generated from real page content on virtualsms.io, verified 2026-07-19. It covers the homepage, all four products, the services catalog, pricing, the canonical AI agents landing page (virtualsms.io/agents), the full MCP cluster (hub plus all six per-client setup pages), the FAQ, and the contact page. Deferred from this pass: full blog post bodies (the blog index and all 70 published posts are already linked from /llms.txt) and the complete country/service price list (structured and better served by /pricing.md). For the short, link-based index see [/llms.txt](https://virtualsms.io/llms.txt).*