For AI Agents · Voice + SMS · API-first

A real US phone number
for your AI agent, by API.

Real US mobile numbers, owned and managed in the US by MEISIM USA LLC, a Wyoming company run from Los Angeles.

Give your agent a real mobile number on a national US carrier, not a virtual number. Inbound texts reach your webhook or the API, replies go out with one call, and voice runs over SIP with the number as caller ID. Ordered by API and billed by the month.

Apply for API access → Read the API docs
100%
Real carrier numbers
Seconds
For a number from stock
$35
Per number a month

What the line is

A real US mobile number on T-Mobile, a national carrier. It is the same kind of number a person carries. The SIM sits in our gateway instead of a handset, so your agent uses the line over an API:

Step-by-step guides: how to give your AI agent a phone number and a real US phone number for voice AI, over SIP.

Why a real mobile number, not a VoIP one

Your agent can write code, browse the web and book a table. Then it has to call or text a person, and the number it uses decides whether anyone answers. Here is the difference:

VoIP number providers

VoIP / cloud telephony providers
  • ✗ Shows as VoIP on caller ID, not as a mobile
  • ~ $1 to $3 a month per number
  • ✓ Excellent for B2B enterprise calling, IVR, contact centers
  • ✓ Strong programmable voice APIs
  • ✗ No mobile number of its own on the carrier networks

MeiSIM USA

Real carrier prepaid lines, API-provisioned
  • ✓ A real mobile number on a national carrier, the same kind a person carries
  • ✓ $35 a number a month for texts, $45 with voice over SIP, all inclusive. For hundreds of lines, write to us for a price
  • ✓ eSIM QR + ICCID + LPA delivered via API in <60 seconds
  • ✓ Receives texts over the API or a webhook on a T-Mobile API line, or on the handset for a carrier eSIM
  • ✓ Voice over SIP on T-Mobile API lines: calls in and out, caller ID is the number, one call at a time per line
  • ✓ Crypto, card, PayPal payment for international AI startups

Built for the new generation of AI agents

If your product gives an AI a phone, we're the layer that makes it actually work in the real world.

Voice AI

AI calling / phone agents

Voice over SIP: voice lines connect directly in trunk mode. Each line has a login of its own at sip.meisimusa.com, your platform or PBX sends calls there with digest authentication and no registration, and incoming calls are forwarded to the SIP address you set. Your agent calls a restaurant for a reservation, and the restaurant sees a real US mobile number, not "Unknown VoIP." You bring the voice stack; we provide the number, its caller-ID identity and the trunk.

AI companions

A companion with its own phone

A companion or character platform gives each companion a real number, bound to the one user who pays for it. The companion texts first, the user answers from the lock screen, and it can call. How it works for companion platforms →

Personal AI

AI executive assistants

Personal AI that screens your calls, answers spam, schedules with humans. Customer gives the assistant a real MeiSIM number; assistant routes calls, transcribes voicemails, replies by text, all from a number that's indistinguishable from a human's line.

Multi-channel agents

SMS-first customer service bots

A number your customers will trust, a real mobile line. Inbound SMS on a T-Mobile API line is delivered to your webhook, or polled over the API. Outbound texts go out from the same line with one REST call; sending is switched on per account, each number carries a monthly allowance, and the answer is "accepted by the carrier", since a mobile line has no delivery receipt.

How it connects, and setup in five steps

Texts

Register a webhook with POST /api/v1/sms/webhook and each incoming text is pushed to your URL as it arrives. GET /api/v1/sms/messages is the record behind it, for polling or catching up.

Calls over SIP

A voice line connects in trunk mode through our SIP bridge at sip.meisimusa.com. Each line has a login of its own: you send calls there with digest authentication, no registration, and set the SIP address where incoming calls go. Hosted voice-agent platforms that only take SIP trunks fit this directly, with no PBX of your own in between. The voice AI guide walks through both modes.

Setup

  1. Apply for API access. A person approves the account, usually the same day, and the API key arrives with the approval.
  2. Fund the prepaid wallet by card or USDT.
  3. Order numbers with POST /api/v1/sms/order: a count, an area code or ZIP if you like, and "voice": true for calls. Numbers from stock go live in seconds.
  4. Point the texts at your agent with a webhook, or read them with the MCP server or the n8n node below.
  5. For voice, switch the line to trunk mode with POST /api/v1/sms/lines/:number/sip/mode, keep the login it returns, and set where incoming calls go.

Every endpoint is in the API reference.

Three lines of code, one real US number

Authenticated REST, prepaid balance, per-key rate limits. No SDK to install, just plain HTTP calls. To read texts from an agent framework, use the MCP tools below.

curl
JavaScript
Python
# 1. Find a plan: free, no key needed curl "https://api.meisimusa.com/mm/products" # 2. Provision that plan as a real US line curl -X POST https://api.meisimusa.com/v1/numbers/provision \ -H "Authorization: Bearer $MEISIM_API_KEY" \ -H "Content-Type: application/json" \ -d '{"plan_id": "p3:2:631", "label": "agent-build-table-bot"}' # Response { "id": "8901240...", "phone": "4155551234", "carrier": "AT&T", "lpa": "LPA:1$smdp.example.com$...", "iccid": "8901240...", "cost_usd": 32, "balance_usd": 168 }

Or skip the code: connect over MCP

MeiSIM runs a hosted Model Context Protocol server. Point any MCP client, a desktop AI assistant, a code editor or your own agent, at one URL with your API key and it can list your numbers, read the texts they receive, wait for the next one, send texts and buy more. No SDK, no polling loop, no glue code.

# Add to your MCP client config: streamable HTTP, nothing to install { "mcpServers": { "meisim": { "type": "http", "url": "https://mcp.meisimusa.com/mcp", "headers": { "Authorization": "Bearer YOUR_API_KEY" } } } } # or, in Claude Code, one line: claude mcp add --transport http meisim https://mcp.meisimusa.com/mcp --header "Authorization: Bearer YOUR_API_KEY"

Tools your agent gets with your API key:

list_my_numbers read_messages wait_for_message send_message get_account get_number_pricing buy_numbers get_order

And without a key, the retail tools (travel eSIMs and US plans paid by card):

search_plans get_quote search_us_numbers purchase get_activation topup_lookup topup_start

Open source: github.com/Shauliko/meisimusa-mcp, on npm as meisimusa-mcp. Purchases your agent makes run on your prepaid wallet; a retry with the same reference never orders twice, and the agent cannot add money.

Or no code at all: the n8n node

An n8n workflow can start the moment a text arrives on one of your numbers, answer it with an AI agent node, and send the reply from the same number. The community node is open source and free. In n8n open Settings, then Community Nodes, and install n8n-nodes-meisim.

# A texting agent in three nodes 1. MeiSIM USA Trigger # a text arrives: signed webhook, or the polling trigger 2. AI Agent # prompt {{ $json.text }}, memory key {{ $json.from }} 3. MeiSIM USA, Message, Send # from {{ $json.number }} to {{ $json.from }} # What the node does with your API key Message: send, get many Line: get many, update, renew, auto-renew, daily stop Order: create, get, get many Account: get, SIP login, webhook

Open source: github.com/Shauliko/n8n-nodes-meisim, on npm as n8n-nodes-meisim.

Pricing that makes sense at scale

A monthly price per number, all inclusive: no per-message or per-minute charges. Need hundreds of lines? Write to us with how many you need and we will send you a price. Two ways to receive: a T-Mobile API line reads its own SMS over the API with webhook push, and a carrier eSIM delivers its texts to the device you install it on.

Texts only

$35
per number, per month · all inclusive
  • A real mobile number on a national US carrier, bound to one agent or one user
  • Texts in and out over the API, pushed to your webhook as they arrive
  • Ordered one at a time or in batches by API; prepaid by card or USDT
  • Two months minimum on the first term, then month by month
  • Email support · 4h response
Apply for access

What it is not for

These lines are for conversations people expect: calls they asked for, texts they answer. No robocalling, no auto-dialing, no bulk calls and no bulk texting. Every call or text that US law requires consent for needs that consent first. A line used any other way is blocked and the account is closed. The API and lines terms spell it out.

Works with everything you'd actually use

Plain HTTP and standard SIP, nothing to install. Any agent framework or automation tool that can make an HTTP request reads and sends texts. Voice over SIP: voice lines connect directly in trunk mode. Each line has a login of its own at sip.meisimusa.com, your platform or PBX sends calls there with digest authentication and no registration, and incoming calls are forwarded to the SIP address you set.

🎙️

PBX or softphone

Registers the SIP login; the number rings whatever is registered

📞

Realtime voice APIs

A function tool that buys a number and reads its texts

💬

Companion platforms

One number per companion, bound to its user

🌐

Browser agents

The agent's own user confirms a number the agent holds

🧠

Agent frameworks

Python + JS tool definitions

🔔

Webhooks

Every inbound text pushed to your URL, signed

⚡

n8n node

Live: install n8n-nodes-meisim. Zapier is next.

🪢

MCP server

For any MCP client

Questions developers actually ask

How do I give my AI agent a phone number?

Apply for API access, fund the prepaid wallet, and order a number with one call to POST /api/v1/sms/order. Register a webhook so the number's texts reach your agent. For calls, order a voice line, switch it to trunk mode and connect its SIP login. The step-by-step guide has the details.

Can an AI agent receive texts on a real US number?

Yes, on a T-Mobile API line. Two products, and the difference is where the SIM physically is.

T-Mobile API line: a real T-Mobile number, and we receive its SMS. The SIM lives in a gateway rather than in a handset, so the message reaches us and we pass it on: webhook push to your URL (POST /api/v1/sms/webhook to set it, HMAC-signed as X-MeiSIM-Signature) with GET /api/v1/sms/messages as the record behind it. A real carrier number that your code can read is the combination most stacks cannot offer.

Carrier eSIM: you install it on a device, and its texts go to that handset. Not to us, and no provider can change that; it is how a SIM works. Right for a phone somebody uses, wrong for code that needs to read the message.

Does it work over SIP?

T-Mobile API line with voice: yes, both directions, over SIP. Each line gets its own SIP login (host, port, user, password) at sip.meisimusa.com. Your platform or PBX sends calls there with digest authentication and no registration, and incoming calls are forwarded to the SIP address you set. Platforms that only accept SIP trunks, such as Vapi, Retell, ElevenLabs, LiveKit and OpenAI Realtime, connect directly in trunk mode, no PBX. Tested end to end with Vapi (setup guide) and with LiveKit; the presets for the other three are in place and verified with you on first use. Outbound shows the line's own number, a real mobile. The monthly price includes calls and texts; each line carries one call at a time, so ten simultaneous calls means ten lines.

Carrier eSIM: calls ring the handset it is installed on, like any phone.

The rule that comes with it: a line used for robocalling, unsolicited calls or texts, or fraud is blocked the moment we see it and the account is closed for good, no warning, no refund. Legitimate agents never notice this rule exists.

Why a real mobile number instead of a VoIP number?

A VoIP number works for many voice agents. A real mobile number is the same kind of number a person carries: it shows as a mobile on caller ID, sends and receives texts like any phone, and stays your agent's own number for as long as the plan runs. Pick it when your agent talks with people by phone and by text.

How fast do I get a number?

Numbers from stock go live in seconds, and new ones in minutes. We keep numbers ready in advance, so you are not waiting on the carrier for every request.

Can I order a pool of numbers by API?

Yes. One order takes a count, so a platform can give each of its users or agents a number of its own. Send a customer_reference and a retry never orders twice. Hundreds of lines run on one account; for more than that, talk to us.

Is there a temporary US mobile number API?

Lines are rented by the month, not by the day. The first term is two months. After that each number renews month by month from your wallet, or ends on its day if renewal is off. Lines are prepaid and cannot be returned early.

How much does it cost?

$35 a number a month for texts, $45 with voice over SIP. All inclusive: no per-message or per-minute charges. Two months minimum on the first term, then monthly. Need hundreds of lines? Write to support@meisimusa.com with how many you need and we will send you a price.

What payment methods do you accept?

Credit or debit card, PayPal, Apple Pay, Google Pay, USDT crypto (TRC20 and ERC20), Alipay and WeChat Pay. We deliberately accept crypto because a lot of our AI-agent customers are international startups that struggle with US payment rails.

What happens if a number gets shut down by the carrier?

Carriers occasionally deactivate prepaid lines for inactivity, suspected fraud or quota issues. We watch every line, tell you when one goes down, and issue the replacement. Texts are not forwarded across the swap: a code sent to the old number in that window is lost, so ask for it again after the swap.

Related

Real numbers. Real API. Real users.

Prepaid, by card, crypto, wire or Zelle, from a single number up. Apply, a person approves the account (usually the same day), the API key arrives with the approval, and you can be in production the same afternoon.

Apply for API access →

Every account agrees to the API and lines terms: one-to-one use, no bulk traffic, KYC on every buyer.