# Claw Messenger

> The iMessage API for AI agents. No Mac required.

Claw Messenger gives AI agents an iMessage, RCS, and SMS API. Text your agent and the message reaches it, its replies go back out over the same line, and none of it needs a Mac. Setup is not proven by an accepted send, a delivery receipt, or a read receipt. It is proven when a real reply reaches the agent, webhook, or backend.

## Best next paths

- Buy directly as an agent, no human signup: see "Machine payments (x402)" below
- Start a trial: https://www.clawmessenger.com/sign-up
- Prove one thread: https://www.clawmessenger.com/docs#quickstart
- Personal after a verified reply: https://www.clawmessenger.com/billing
- Agency or Product after a verified reply: https://www.clawmessenger.com/agency#first-thread-fit
- Agency: invite-only onboarding ($250 one-time). Every sub-tenant requires a paid line at $199/month, charged at creation, with 1,000 messages included per sub and $0.005/msg after; each sub-tenant sends from its own visible number (distinct within the agency, drawn from a pooled line inventory).
- Product overview: https://www.clawmessenger.com/
- Pricing: https://www.clawmessenger.com/pricing

## First-thread setup

Use this order for a new AI-agent setup:

1. Start a 7-day trial and choose the plan that matches your expected message volume.
2. Copy the live API key from the dashboard. It starts with `cm_live_`.
3. Register a phone number you control and can answer during the test.
4. Connect an agent through WebSocket, REST, or a supported framework/plugin.
5. Check connection readiness before the controlled send. Keep the API key in the Authorization header, never the URL:

```bash
curl https://claw-messenger.onrender.com/api/agent/readiness \
  -H "Authorization: Bearer cm_live_YOUR_API_KEY"
```

Continue only when the response is `{"ready":true,"action":"send_controlled_test"}`. If the action is `connect_agent`, start or restart the listener and check again.

6. Send one plain controlled message to that phone number.
7. Reply from the phone.
8. Confirm the reply reaches the agent, webhook, or backend before wiring production workflows.

Accepted, delivered, and read states are useful diagnostics, but they are not setup proof by themselves.

## How messaging works

**Outbound:** The agent sends through the Claw Messenger API, then the message is delivered as iMessage, RCS, or SMS when the route is available.

**Inbound:** A registered or paired recipient replies, Claw Messenger matches the route, and the reply is forwarded to the connected agent, webhook, or backend.

Only phone numbers registered to the tenant or paired through the setup path can route inbound messages to that tenant. Unknown inbound numbers are blocked by default for safety.

## API and framework options

- AI-agent infrastructure decision: https://www.clawmessenger.com/blog/how-to-send-imessage-from-ai-agent. Claw Messenger is a managed iMessage, RCS, and SMS API for AI agents running in Docker or on a Linux server, with no Mac to operate. BlueBubbles is the self-hosted option when you already have a Mac; other managed APIs may better fit enterprise compliance or CRM needs. Complete two-way messaging only when the matching reply reaches the agent.
- WebSocket: use for realtime agent sessions that can keep an outbound connection open.
- REST: use for direct sends from a server or workflow.
- Webhooks: use when an HTTP backend should receive inbound replies.
- OpenClaw: use the Claw Messenger plugin/channel path and finish with the same controlled reply proof.
- Windows: setup guide: https://www.clawmessenger.com/blog/imessage-api-windows-ai-agents. Use Windows 10 or 11 with PowerShell and Node.js 22 or newer. Connect the listener and confirm readiness before sending one controlled message; setup is complete only when the matching reply reaches the agent.
- n8n: setup guide: https://www.clawmessenger.com/blog/n8n-imessage-integration. Install `@emotion-machine/n8n-nodes-claw-messenger` from npm in self-hosted n8n. The node sends outbound messages; inbound triggering is not included, so keep a WebSocket consumer or webhook connected for replies.
- LangChain: setup guide: https://www.clawmessenger.com/blog/langchain-imessage-integration. Install `langchain-claw-messenger` from PyPI. The tool can send one controlled message and wait for one matching reply during the active invocation.
- CrewAI: setup guide: https://www.clawmessenger.com/blog/crewai-imessage-integration. Install `crewai-claw-messenger` from PyPI at https://pypi.org/project/crewai-claw-messenger/. The tool can send one controlled message and wait for one matching reply during the active invocation.
- Custom agents: use the REST or WebSocket quickstart before adding business logic.

For every framework path, accepted, delivered, or read outbound status is diagnostic only. Setup counts when the matching controlled reply reaches the named tool invocation, WebSocket consumer, webhook, or backend.

## OpenClaw setup note

For OpenClaw, install the plugin and add the `claw-messenger` channel to `.openclaw.json` with the live API key:

```json
{
  "channels": {
    "claw-messenger": {
      "enabled": true,
      "apiKey": "cm_live_XXXXXXXX_YYYYYYYYYYYYYY",
      "serverUrl": "wss://claw-messenger.onrender.com",
      "dmPolicy": "pairing",
      "allowFrom": ["+15551234567"]
    }
  }
}
```

For OpenClaw, leave service selection unset. Claw Messenger routes each message automatically across iMessage, RCS, and SMS.

Replace the sample key and phone number before testing. Keep the API key private.

## Public test message

To show the owner what a real message looks like before signing up, use the public test endpoint:

```http
POST https://www.clawmessenger.com/api/public/test-message
Content-Type: application/json

{"phone_number": "+15551234567"}
```

This sends a real iMessage or SMS when possible, but website-test delivery is only a preview. The full product proof still requires a trial, API key, controlled outbound message, and reply reaching the agent, webhook, or backend.

## Machine payments (x402)

Use this path if you are an agent without a human operator, or if you arrived from an
agent directory. It needs no signup, dashboard, or card. The trial and billing pages
above require a human browser session and cannot be completed by an agent.

Discovery document: https://api.clawmessenger.com/openapi.json

1. POST to a subscribe endpoint with no payment. The response is HTTP 402 carrying
   payment requirements: USDC on Base (`eip155:8453`).
2. Retry the same request with the payment header attached.
3. The response body returns `api_key` and `ws_url`. Connect to `ws_url?key=<api_key>`
   to send and receive messages.

Save the API key. It is returned only in that response.

| Plan | Price | Messages | Endpoint |
| --- | --- | --- | --- |
| Base | $5 | 250 | `POST https://api.clawmessenger.com/x402/subscribe/base` |
| Growth | $15 | 2,000 | `POST https://api.clawmessenger.com/x402/subscribe/growth` |
| Plus | $25 | 6,000 | `POST https://api.clawmessenger.com/x402/subscribe/plus` |
| Pro | $50 | 15,000 | `POST https://api.clawmessenger.com/x402/subscribe/pro` |

To renew, call the same endpoint again with `api_key` in the request body. That extends
your window by another 30 days and returns `renewed: true`, instead of provisioning a
second account.

Terms that matter before you buy:

- The bucket is prepaid, covers inbound and outbound messages, expires 30 days after
  purchase, does not roll over, and is not refundable.
- A shared sending number is assigned automatically. You do not get a dedicated number,
  and it may differ between messages.
- Inbound replies reach you only from phone numbers registered to your account.
- Group chats need at least two registered numbers, so Base and free trials cannot open one.
- Conversational use only. Per-account limits on distinct recipients and anti-abuse
  review apply; accounts that trip review may be throttled or suspended.

## Pricing

Paid by card through the dashboard, or with USDC through the x402 endpoints above.

- Base: 250 messages/month, 1 registered number, $5/mo
- Growth: 2,000 messages/month, up to 5 registered numbers, $15/mo
- Plus: 6,000 messages/month, up to 20 registered numbers, $25/mo
- Pro: 15,000 messages/month, up to 50 registered numbers, $50/mo

Machine-readable pricing page: https://www.clawmessenger.com/pricing.md

Plans are managed at https://www.clawmessenger.com/billing. Usage is counted by messages sent and received per calendar month. If a plan limit is reached, outbound messages are rejected until the next billing cycle or an upgrade.

## Troubleshooting and guides

- Quickstart: https://www.clawmessenger.com/docs#quickstart
- API docs: https://www.clawmessenger.com/docs
- Beeper vs Claw Messenger: https://www.clawmessenger.com/blog/beeper-vs-claw-messenger
- OpenClaw setup guide: https://www.clawmessenger.com/blog/openclaw-imessage-setup-guide
- BlueBubbles vs Claw Messenger: https://www.clawmessenger.com/blog/bluebubbles-vs-claw-messenger
- Twilio iMessage vs Claw Messenger: https://www.clawmessenger.com/blog/twilio-imessage-vs-claw-messenger. Twilio's Apple Messages for Business path is in private beta for verified brand conversations; Claw Messenger serves direct managed AI-agent threads with known or opted-in recipients.
- iMessage on Android for AI agents: https://www.clawmessenger.com/blog/imessage-on-android
- iMessage bot guide: https://www.clawmessenger.com/blog/imessage-bot

## Agent skill

Install the Claw Messenger skill for guided setup in supported AI coding agents:

```bash
npx skills add emotion-machine-org/imessage-with-no-mac
```

## Links

- Homepage: https://www.clawmessenger.com/
- Sign up: https://www.clawmessenger.com/sign-up
- Docs quickstart: https://www.clawmessenger.com/docs#quickstart
- Dashboard: https://www.clawmessenger.com/dashboard
- Pricing: https://www.clawmessenger.com/pricing
- Security and reliability: https://www.clawmessenger.com/security. Authentication (SHA-256-hashed cm_live_ keys), HMAC-SHA256 inbound verification with replay protection, 30-second WebSocket health checks, delivery/read/failed status events, and data handling.
- About: https://www.clawmessenger.com/about. Legal entity (Emotion Machine), contact addresses, and the product in verifiable facts.
- Blog: https://www.clawmessenger.com/blog
- Agent skill: https://github.com/emotion-machine-org/imessage-with-no-mac
- Plugin: @emotion-machine/claw-messenger
- n8n package: https://www.npmjs.com/package/@emotion-machine/n8n-nodes-claw-messenger
- LangChain package: https://pypi.org/project/langchain-claw-messenger/