For companion and character platforms · SMS + voice · API

Your companion can text first.
From its own real number.

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

Give each companion a real US mobile number, bound to the one user who pays for it. The companion texts the user's actual phone, the user answers from the lock screen, and it can make and take calls. Your model does the talking. We provide the line.

Apply for API access → Read the API docs

Line per companion, bound to its user

Minutes

From API call to a live number

$35

Per number a month

What the user gets

A companion that lives in an app stops existing when the app is closed. A companion with a phone number does not.

Texts first

A text from a friend, not a push

The companion's message arrives as a normal text from a saved contact. It shows on the lock screen even when your app is closed, and the reply comes straight back to your model.

A real number

Saved in the contacts as a mobile

Not a VoIP number and not a short code. A real mobile number on a national US carrier, which is what a phone, a carrier and a contact app all treat as a person.

Calls

It can call, and be called

On a voice line the companion calls the user's phone from its own number, and the user can call it back. Your voice stack answers over SIP; the caller ID is the companion's number.

Off switch

The user stays in charge

The user turns it off in your app, you clear the line or stop its charges, and the number goes quiet. Nothing is sent that your model did not write.

What your platform controls

Every line is yours to bind, cap, name and switch off. We keep the carrier side honest.

One line, one user Set allowed_contacts on the line and it will only ever text the user who paid for it. Anything else is refused by us, whichever way a send is attempted.

Inbound to your webhook Every text the user sends lands on your URL, signed, within seconds, with the full history behind it over the API.

Send caps per line Each number carries a monthly sending allowance sized for a conversation, never for a blast. Caps are raised per account, by a person.

Your content, your rules Your model, your prompts, your moderation. We never read the conversation except on an abuse report or when you ask for support.

Named lines Label each number with your own reference so your database and ours agree on which companion holds it.

Prepaid, per line A wallet pays for lines by the month. No contract beyond the months paid; the same price at any volume.

Four calls, one companion with a phone

Plain HTTP with an API key. The full reference is in the API docs.

Order a line when the user upgrades

POST /api/v1/sms/order with count: 1, billing: "monthly" and your own customer_reference. A number from stock is on the account at once; a new one usually within fifteen minutes.

Bind it to the user

PATCH /api/v1/sms/lines/{number} with allowed_contacts: ["2125551234"] and a label. From now on the line texts that user and nobody else.

Point the texts at your model

POST /api/v1/sms/webhook with your URL. Each inbound text arrives signed; your model writes the reply.

Let the companion speak

POST /api/v1/sms/lines/{number}/send with to and message. For calls, register the line's SIP credentials from your voice stack.

curl -X PATCH https://api.meisimusa.com/api/v1/sms/lines/3475550101 \
  -H "x-api-key: $MEISIM_KEY" -H "content-type: application/json" \
  -d '{"allowed_contacts":["2125551234"],"label":"Mia for user 8812"}'

curl -X POST https://api.meisimusa.com/api/v1/sms/lines/3475550101/send \
  -H "x-api-key: $MEISIM_KEY" -H "content-type: application/json" \
  -d '{"to":"2125551234","message":"Good morning. Did you sleep?"}'

Pricing for platforms

A price per line, by the month. Prepaid from a wallet, by card or USDT. Texts only $35 a number a month, $45 with voice.

Texts only

$35

per number, per month

Lines ordered one at a time or in batches, as users upgrade
Allowed contacts, labels, webhook; texts in and out over the API
Auto-renew per line while the user keeps paying you
Email support, 4h response

Apply

Voice + texts

$45

per number, per month

Everything in Texts only, plus calls in and out over SIP with the number as caller ID
Priority webhook delivery
Shared channel, 1h response; hundreds of lines on one account, more than that, talk to us

Talk to us

One line or a thousand, the price is the same: $35 a month for texts, $45 with voice. Every month paid is delivered in full: lines are prepaid and are not returned or refunded.

The rules that keep the lines alive

A carrier number stays a carrier number only while it behaves like one. These are the terms every platform agrees to, in full at API and lines terms.

The user opted in The user asked for a companion that texts and calls, from inside your app, and can turn it off at any time. When they do, you act on it.

One to one A companion line talks to its user. It is never a broadcast channel, a marketing sender or a notification pipe.

Adults only for romance Romantic or adult companions are for adults, between adults. Nothing involving minors, nothing that impersonates a real person without consent, nothing that threatens or harasses.

Not for emergencies These lines cannot text 911 and a companion is not a way to reach help. Your app says so where the number is offered.

Your platform is verified We know who runs every account. API keys are issued by a person after a short check, usually the same day.

Abuse ends the line A line used for spam, fraud or harassment is stopped the moment we see it, without refund. Platforms that keep to the rules never notice this one exists.

Questions companion platforms ask

Does the number show up as VoIP?

No. It is a mobile number on a national US carrier, and number-type lookups say so. It saves in the contacts like any mobile.

Can one companion have more than one user?

The allowed list holds up to ten numbers, so a shared companion for a couple or a family works. Most platforms bind one line to one user.

What happens if a stranger texts the companion's number?

Inbound is open: the text reaches your webhook like any other, and your model decides what to do with it. Outbound is bound: the line cannot reply to anyone outside the allowed list, so a wrong number never becomes a conversation.

How does the companion call the user?

A voice line comes with SIP credentials. Your voice stack registers them and places the call; the user sees the companion's own number. When the user calls back, the same registration rings your stack. One call at a time per line.

What does the user see when they cancel?

You clear the line's allowed list and stop its charges, or let the month run out. A stopped line is released. If the user comes back later, their companion gets a new number.

Can we try it before we build?

Yes. Apply, say it is for a companion platform and roughly how many users would upgrade, and we open the account with a test mode where orders return test numbers and nothing is charged. Then one real line on the daily rate costs a few dollars.

Your companion can text first.From its own real number.