for AI agents

The iMessage API
for AI agents

Put your AI agent into a real text thread. Start a trial, send one message to your phone, and confirm the reply reaches your agent, webhook, or backend. No Mac bridge to maintain.

7-day free trial
start the proof path
One API key
then one controlled send
One reply
back to your agent path
Larry Lobster+1 (555) 123-4567
one API call

Send your first iMessage in one request

Grab an API key and send one plain message to a phone you control. The useful result is the next step: reply from that phone and confirm the response reaches your agent path.

send an iMessage
curl -X POST https://www.clawmessenger.com/api/agent/send-message \
  -H "Authorization: Bearer cm_live_..." \
  -H "Content-Type: application/json" \
  -d '{"phone_number": "+15551234567", "text": "Hi from your agent 👋"}'
Pricing

Simple pricing. Free trial on every plan.

All plans include iMessage, RCS, SMS, tapbacks, typing indicators, read receipts, and HMAC-signed webhooks.

Base
$5/mo
250 messages/mo
  • iMessage/RCS/SMS delivery
  • Tapbacks & read receipts
Start free trial
Plus
$25/mo
6,000 messages/mo
  • iMessage/RCS/SMS delivery
  • Priority support
Start free trial
Pro
$50/mo
15,000 messages/mo
  • iMessage/RCS/SMS delivery
  • Priority support
Start free trial
Agency

Multi-tenant or reseller?

Run managed routing through one agency line by default, then check fit before you promise dedicated visible numbers for agents, clients, or subaccounts.

How it works

Prove one working agent thread.

01

Start trial

Pick a plan trial and keep the first run small. The goal is one working thread, not a full rollout.

02

Create an API key

Copy the key into your agent, script, or backend. Keep it out of screenshots, logs, and public prompts.

03

Send a test message

Send one plain message from the agent to a phone you control and can answer right now.

04

Reply and confirm

Reply from the phone and check that it reaches your agent, webhook, or backend. That reply is the proof.

Why iMessage?

Your agent belongs in the conversation.

I built an AI agent to help small construction companies manage their office and admin work. The agent's primary mode of communication is text message which makes it natural for the user. I picked Claw Messenger because Anthropic indicated it was the best fit to use with a MyClaw agent. I found it easy to set up and it has been working perfectly.
Dan T.
Prove one agent thread
Built for agents

Everything you need. Nothing you don't.

No Mac required

Your agent runs on Linux, Docker, Windows, any cloud. We handle the iMessage side. See how it compares.

Dedicated number

You get a dedicated agent line. Register your phone numbers to access it — only registered numbers can reach your agent. Learn about agent phone numbers.

iMessage + RCS + SMS

One API, three protocols. Falls back gracefully depending on the sender.

Easy Installation

Sign up, subscribe to a plan, grab your API key, and add a config block to your agent.

Tapbacks & typing

iMessage reactions, typing indicators, read receipts. The full native experience.

Group messages

Your agent can participate in group conversations. Coordinate with multiple people at once.

Start free trial
Integrations

Works with any agent framework

Claw Messenger connects via WebSocket and REST API. If your agent can make HTTP calls, it can send iMessages.

OpenClawNative plugin, 5-min setupHermes AgentPackage support, no Mac setup
LangChainCustom tool via REST API
n8nHTTP Request node
Custom agentsWebSocket or REST, any language
# Works with any HTTP client
curl -X POST https://claw-messenger.onrender.com/api/agent/send-message \
  -H "Authorization: Bearer cm_live_xxx" \
  -d '{"phone_number": "+1555123456", "text": "Hello from my agent"}'