How does an AI agent send and receive iMessage through Claw Messenger?
Your agent sends through the Claw Messenger API, and the message reaches the recipient's phone as iMessage, or as RCS or SMS when iMessage isn't available. When the person replies, the reply comes back to your agent over the same connection, with no Mac, SIM, or iCloud account on your side.
The short answer
The other routes are a Mac you keep online running BlueBubbles, or another managed API. Claw Messenger fits an agent that holds real conversations at modest volume, starting at $5 a month.
- Best for
- AI agents on Linux, Docker, Windows, or cloud servers that text people who expect to hear from them.
- Not for
- Bulk marketing, cold outreach, or voice calls.
At a glance
| Send | REST (POST /api/agent/send-message) or the WebSocket |
|---|---|
| Receive | Replies arrive as events on your WebSocket. A configured webhook is for approved managed setups only. |
| Channels | iMessage first, with automatic RCS and SMS fallback per recipient |
| You need | An API key (starts with cm_live_) and at least one registered contact |
| Hardware | None. No Mac, SIM, iCloud account, or BlueBubbles. |
| Setup time | About five minutes to a first reply |
| Frameworks | OpenClaw, Hermes, n8n (sending), LangChain, CrewAI, a local MCP server, or plain HTTP |
| Price | From $5/month for 250 messages. 7-day trial, card required. |
| Not for | Bulk marketing, cold outreach, voice calls |
What happens when your agent sends a message?
- Your agent calls the API. It sends text, and optionally media from an HTTPS URL, to a phone number in E.164 format. Use REST for one-off sends or the WebSocket for a live agent session.
- Claw Messenger checks the account. It confirms the API key, the monthly message allowance, your registered-contact allowance, and the new-recipient safeguard. A send that fails a check returns a clear error.
- The message goes out from your account's sending number. It is sent as iMessage when the recipient can receive it. If not, it falls back to RCS, then SMS. You don't choose the channel; leave
serviceunset and the route is picked per recipient. - Your agent gets a send result. The status is
accepted,delivery_confirmed,not_confirmed, orfailed. Accepted is not the same as delivered. Delivered, read, and failed events follow when they are reported.
What happens when someone replies?
- The person replies to the number your agent texted from.
- Claw Messenger matches their phone number to the account that registered it. Numbers that no account has registered do not reach any agent.
- The reply is stored first, then pushed to your agent as a
messageevent on the WebSocket. It includes the text, any attachments, the channel used, and group details for group chats. - If your agent is offline, the reply waits. On reconnect your agent receives it, or asks for missed messages with a
syncrequest.
That reply reaching your agent is the real proof that setup works. A delivered or read status on the outbound message is useful, but it is not the same thing.
Which channel does the recipient get: iMessage, RCS, or SMS?
| Recipient | What they get |
|---|---|
| iPhone with iMessage on | iMessage, with typing indicators, read receipts, and tapbacks |
| Android or other phone with RCS | RCS |
| Any other mobile number | SMS |
The fallback happens per recipient, so one agent can talk to iPhone and Android users without separate code paths. Typing indicators, read receipts, and reactions do not count toward your message allowance.
What do you need before you start?
- A Claw Messenger account on a trial or paid plan.
- An API key from the dashboard. Keep it in a server-side secret store.
- At least one registered contact: a phone number you control for the first test. Plans allow 1 (trial and Base), 5 (Growth), 20 (Plus), or 50 (Pro). See how numbers and contacts work.
- A process that can keep a WebSocket open to receive replies. Framework packages for OpenClaw, Hermes, LangChain, and CrewAI handle this for you.
You don't bring a phone number, buy a SIM, or sign in with an Apple ID.
How long does setup take?
About five minutes. Create the key, register your own phone, connect the listener, check readiness, send one plain message, and reply from your phone. The docs quickstart walks through each step. Framework guides cover OpenClaw, Hermes, n8n, LangChain, CrewAI, and MCP.
What do you run, and what does Claw Messenger run?
| Self-hosted Mac bridge (BlueBubbles) | Claw Messenger | |
|---|---|---|
| Hardware | A Mac you keep awake and online | None on your side |
| Apple account | iMessage signed in on that Mac | None of yours |
| SMS fallback | Not supported, per its FAQ | Automatic RCS and SMS fallback |
| Software price | Free | From $5/month |
| Who fixes it at 3am | You | We run the line |
If you already own a Mac that stays on and you only text yourself, BlueBubbles costs nothing extra. Compare the two in detail on BlueBubbles vs Claw Messenger.
What Claw Messenger does not do
- Bulk marketing or cold outreach. It is built for conversations people expect. Limits on new recipients and contacts keep it that way. See limits and reliability.
- Voice calls. It handles text and media attachments, not calls.
- Your own existing number. You don't port in a number or pick an area code. A sending number is assigned for you.
Common questions
Do I need a Mac to use Claw Messenger?
No. We manage the iMessage line upstream, so there's no Mac, no SIMs, no iCloud, and no BlueBubbles on your end. Your agent can run on Linux, Docker, Windows, or any cloud server.
Can my agent text someone first?
Yes. Sending to a new phone number registers that contact for replies, as long as your plan has a free contact slot. New recipients also count toward the self-serve safeguard of 20 distinct outbound recipients in a rolling 24 hours.
Can anyone who texts the number reach my agent?
No. Only phone numbers registered to your account reach your agent. Messages from numbers you have not registered are not delivered to you.
What happens if my agent is offline when a reply arrives?
Claw Messenger stores the reply before it tries live delivery. When your agent reconnects, it can receive the saved reply, or request it with a sync message.
Can Claw Messenger deliver replies to a webhook?
Self-serve plans deliver replies over the WebSocket your agent keeps open. A configured webhook is available only on approved managed setups.
Does it work with group chats?
Yes, on Growth and higher. A group needs at least two registered contacts, so trial and Base accounts cannot open one.
Related pages
Send your agent's first iMessage and get the reply back in about five minutes.
Start the 7-day trial