November 18, 2026 · 8 min read

One API for iMessage, RCS and SMS from an AI agent

Connect your agent once, reach people on iPhone and Android, and receive their replies in your backend.

Claw Messenger gives AI agents one API for iMessage, RCS and SMS. Your agent sends a message to a phone number, and Claw routes it through iMessage, RCS or SMS according to what the recipient can receive. All three channels are included on every plan, starting at $5 per month. Your agent can run on a cloud server without a Mac.

One API reaches iPhone and Android

When an appointment assistant texts two customers, their choice of phone should not require two agent integrations. Claw manages delivery while your backend keeps the booking, conversation and reply together.

iMessage reaches recipients with iMessage enabled. RCS reaches supported recipients, including Android users, and SMS provides a fallback when the richer channels are unavailable. The person reads and answers in their messaging app, without opening your chatbot on a website.

RCS is not exclusive to Android. Apple supports RCS on compatible iPhones with a supporting carrier. Its explanation of iMessage, RCS and SMS describes the differences. Route by available service, rather than assuming every iPhone conversation uses iMessage.

Messages route from iMessage to RCS to SMS

Leave the optional service field out when you want Claw to choose delivery for each recipient. The fallback order is iMessage, then RCS, then SMS.

The send interface accepts "iMessage" (the documented default), "RCS" or "SMS". For the first integration test, omit the field so a recipient without iMessage can still receive the text through RCS or SMS.

Send results expose requestedService, selectedService, fallbackAllowed and fallbackReason. These explain the routing decision; selectedService: "auto" does not identify the final handset channel. Use status and deliveryStageto follow the send, and keep listening for the reply.

Tapbacks, typing indicators and read receipts are included on every plan. The selected channel determines which messaging features the recipient can use; SMS fallback does not turn an SMS into an iMessage.

Connect your model and receive replies

Your model generates the response, and Claw carries it to the recipient. Incoming replies return to your backend so the same agent can continue the conversation with its existing history and business data.

For an appointment assistant, your application can read the booking, send a confirmation request and pass the customer's answer back to the model. The booking integration belongs in your application; the messaging API supplies the send and reply path.

After registering the recipient and connecting a listener, send text through the REST endpoint. This example leaves serviceout for automatic routing:

curl -X POST https://claw-messenger.onrender.com/api/agent/send-message \
  -H "Authorization: Bearer $CLAW_API_KEY" \
  -H 'Content-Type: application/json' \
  -d '{
    "phone_number": "+15551234567",
    "text": "Your appointment is tomorrow at 2pm. Reply to confirm.",
    "claim_route": false
  }'

Self-serve replies arrive as message events over an authenticated WebSocket. Run this listener on your backend before sending; it logs the reply text for a controlled test:

// Run on your backend with Node.js 22 or later.
const socket = new WebSocket(
  "wss://claw-messenger.onrender.com/ws?key=" +
    encodeURIComponent(process.env.CLAW_API_KEY)
);

socket.onmessage = ({ data }) => {
  const event = JSON.parse(data);
  if (event.type === "ping") {
    socket.send(JSON.stringify({ type: "pong" }));
    return;
  }
  if (event.type === "message") {
    // Match this reply to the conversation in your application.
    // Pass its text and conversation history to your agent.
    console.log("Reply reached the backend:", event.text);
  }
};

Keep the API key on the server and redact the WebSocket URL from logs. In production, match each inbound event to its conversation before calling your model. Keep the listener connected while the agent waits for the person to answer.

Approved managed setups can receive a signed webhook instead. A self-serve send request does not register a webhook URL. The receiving documentation explains that contract, and the integration docs cover OpenClaw, Hermes, n8n, LangChain, CrewAI and custom agents.

How other routes compare

Choose by the channels your users need and the infrastructure you want to run. The prices below come from providers' own sites, checked November 18, 2026; Twilio rates are for the United States.

RouteWhat it reachesPublished cost
Twilio SMS and RCS APIsSMS and RCS recipients. Its messaging channel list does not include ordinary iMessage.US long-code SMS and RCS Rich text: $0.0083 per segment inbound or outbound, before carrier fees. Number and applicable onboarding fees are additional.
Google RCS Business Messaging directlySupported RCS recipients. Your application supplies another delivery route, such as SMS, when RCS is unavailable.Carrier rate cards determine charges by destination and billing category. Google does not publish one universal per-message price.
Mac-based bridge such as BlueBubblesiMessage through a macOS server you operate. Its setup guide also describes SMS/RCS forwarding through an iPhone with a phone number.Free, open-source software. Budget separately for the Mac or macOS host, power and maintenance.
Other managed iMessage APIs, such as SendblueSendblue offers iMessage with RCS and SMS fallback, without your own Mac.Sendblue AI Agent: $100 per line per month; the recipient texts first. Full outbound messaging is on custom-priced Enterprise.

Sources: Twilio channels, Twilio SMS and RCS pricing, Google RCS delivery, Google carrier billing, BlueBubbles software, BlueBubbles requirements, Sendblue channels and Sendblue pricing.

An SMS-only API can reach both kinds of phone, but it delivers SMS. An RCS-only API needs a separate fallback path for recipients without RCS. Neither adds iMessage simply because the recipient uses an iPhone. See the full iMessage API comparison for more providers and buyer-specific options.

Test a complete conversation

An accepted send proves that Claw took the request. A reply from your test phone proves that your agent can hear the person it just texted.

  1. Register a test recipient. Use a phone you control and register its number in your Claw account.
  2. Start the reply listener. Connect the WebSocket and keep it running throughout the test.
  3. Check receiver readiness. Call GET /api/agent/readiness and wait for ready: true with action: "send_controlled_test".
  4. Send a recognizable prompt. Omit service and ask the recipient to reply with a unique test phrase.
  5. Receive the matching reply. Answer from the phone and confirm that its message reaches your connected agent.

Repeat with a controlled Android recipient to exercise the RCS or SMS path, within your plan's registered-number allowance. Inspect the routing fields and delivery events for each send. ok: truemeans accepted, not handset delivery, and a delivery receipt alone does not prove the inbound integration. The complete quickstart supplies the registration and readiness commands.

All three channels are included in every plan

Choose a Claw plan for message volume and registered recipients. RCS is included from Base upward, so adding Android recipients does not require buying another channel.

Self-serve planMonthly priceMessages per monthRegistered numbers
Base$52501
Growth$152,000Up to 5
Plus$256,000Up to 20
Pro$5015,000Up to 50

Registered numbers are the recipients connected to your account. Group chats start on Growth. Self-serve monthly quotas are hard caps, with no overage. First-time self-serve customers can start a 7-day trial; a card is required. See current plans for signup and Agency for separate client workspaces at $199 per month per subtenant.

A monthly allowance and a per-segment API rate measure different things. Compare your expected sends and replies, recipient count, number fees and carrier charges before comparing headline prices.

FAQ

Can I connect my own AI model to iMessage and RCS?

Yes. Your backend can call Claw Messenger over HTTP and receive replies over an authenticated WebSocket. You choose the model, prompts, conversation history and business integrations. OpenClaw, Hermes, n8n, LangChain, CrewAI and custom agents have integration paths in the docs.

Does an Android recipient need an iMessage app?

No. Claw Messenger can reach that recipient over RCS or SMS in their messaging app. Automatic routing chooses an available channel for the recipient when your agent does not pin a service.

Can a webhook deliver replies to my chatbot?

Approved managed Claw Messenger setups can receive replies through a signed webhook. Self-serve integrations receive message events over a persistent authenticated WebSocket. The send endpoint does not accept a caller-supplied webhook URL.

Do I need a Mac to run an iMessage and RCS agent?

No. With Claw Messenger, your agent can run on Linux, Docker, Windows or a cloud server. Claw Messenger manages the messaging infrastructure, so you do not operate a Mac for delivery.

Does RCS cost extra on a Claw Messenger plan?

No. Every plan includes iMessage, RCS and SMS. Self-serve plans start at $5 per month for 250 messages and one registered number. Their monthly message quota is a hard cap, with no overage charges.

How can my customer support chatbot hand a conversation to a human?

Build the handoff in your application: pause automatic replies for that conversation, send its history to your support queue, and let a person respond through your backend. Claw Messenger carries the messages; your application decides when the person takes over and when the agent resumes.

Can this API support appointment reminders and customer follow-ups?

Yes. Your agent can send a reminder to a registered recipient, receive their reply and use it in your booking or customer system. Keep the conversation attached to the correct customer record so a reply such as 'tomorrow works' updates the right appointment.

Start building

Connect your agent to iMessage, RCS and SMS, then send one text and receive the reply. Start with the 7-day trial; a card is required.

Start the 7-day trial

Building for clients or a managed deployment? Describe the first managed rollout.

Try Claw Messenger free for 7 days — iMessage API for AI agents. No Mac required.