messages.dev

An iMessage, RCS and SMS API built for AI agents

Advanced API
Screenshot of messages.dev, An iMessage, RCS and SMS API built for AI agents

What is messages.dev?

messages.dev is a REST API and TypeScript SDK that lets AI agents send and receive iMessage, RCS and SMS, with webhooks, reactions, typing indicators and managed infrastructure, plus a free sandbox of 50 messages per day.

messages.dev is a developer-focused messaging API that lets AI agents talk to people over iMessage, RCS and SMS through a single integration. Instead of wiring up separate carriers or protocols, a team sends and receives messages through one REST API or a TypeScript SDK, installed from npm, and the platform handles the delivery details behind it. The product is aimed at developers and startups building conversational agents, assistants and automated workflows that need to reach users in the apps they already open every day. A typical use is a personal assistant that answers a question such as what is on today's calendar, delivered as a native-looking text thread rather than a custom chat widget. Features that make the thread feel native include tapback reactions, typing indicators and read receipts, all supported across conversations. In practice, a developer creates an account in the web app, gets an API key and sends a first message from the SDK or a plain HTTP call. Incoming messages, reactions and receipts arrive through real-time webhooks, which the agent's own code consumes to decide what to reply. A sandbox environment provides 50 free messages per day for building and testing before going live. Provisioning, scaling and monitoring are run by the vendor, so the customer's work is limited to the agent logic itself. Security measures listed include end-to-end encryption, scoped API keys and webhook signature verification. Among alternatives, messages.dev sits between general SMS platforms, which are mature but built around phone-number messaging, and do-it-yourself iMessage bridges, which demand hardware and upkeep. Its narrow focus on agents and on blue-bubble style conversations is the main differentiator. Teams that only need plain SMS or voice, or that want a visual no-code builder, will find the scope tighter than broad communications suites. Production pricing is not described on the homepage, so cost planning requires checking the app or docs.

How do you use messages.dev?

  1. 1Create an account and get an API key
    Open the web app, sign up and generate an API key. Scope the key to the access the agent needs.
  2. 2Install the TypeScript SDK
    Run npm install @messages-dev/sdk in the project that hosts the agent, then initialize the client with the API key. The REST API works as an alternative from any language.
  3. 3Send a first message in the sandbox
    Use the sandbox, which allows 50 free messages per day, to send a test message over iMessage, RCS or SMS and confirm delivery.
  4. 4Set up webhooks for incoming events
    Register a webhook endpoint to receive messages, reactions and receipts, and verify the webhook signature on each request.
  5. 5Add agent logic and conversation cues
    Connect the webhook to the agent's reasoning code, then add typing indicators, tapbacks and read receipts so replies feel natural before moving to production.

Pros and cons

Pros

  • One API covers iMessage, RCS and SMS, so agents do not need separate integrations per channelAI
  • Native conversation features: tapbacks, typing indicators and read receipts across all threadsAI
  • Real-time webhooks deliver incoming messages, reactions and receipts to agent code in millisecondsAI
  • Free sandbox with 50 messages per day allows building and testing before going liveAI
  • Managed provisioning, scaling and monitoring leave developers to write only agent logicAI

Cons

  • Aimed squarely at developers; there is no visible no-code builder for non-technical usersAI
  • Production pricing is not stated on the homepage, which makes cost planning harderAI
  • The official SDK is TypeScript only, so other languages must use the raw REST APIAI
  • The sandbox cap of 50 messages per day limits realistic load or user testingAI
  • Reliance on a managed third-party service means messaging depends on the vendor's uptimeAI

How much does messages.dev cost?

Free trial

A sandbox environment gives 50 free messages per day for building and testing an integration before going live.

Learn more

Pricing

The homepage mentions a sandbox with 50 free messages per day for testing. Production pricing is not stated on the homepage.

Learn more

Support

Documentation is available at the docs site. The homepage does not describe other support channels.

Learn more

Integrations

Integrates through a REST API, a TypeScript SDK on npm and webhooks for incoming messages, reactions and receipts. No third-party app integrations are listed on the homepage.

Learn more

Features

One API for iMessage, RCS and SMS, TypeScript SDK and REST API, real-time webhooks, tapback reactions, typing indicators, read receipts, managed infrastructure, end-to-end encryption, API key scoping and webhook signature verification.

Frequently asked questions about messages.dev

  • How much does messages.dev cost?
    The homepage mentions a sandbox with 50 free messages per day for testing. Production pricing is not stated on the homepage.
  • Does messages.dev offer a free trial?
    A sandbox environment gives 50 free messages per day for building and testing an integration before going live.
  • Does messages.dev have an API?
    Yes, messages.dev offers an API.
  • How do you use messages.dev?
    The walkthrough on this page covers 5 steps: 1. Create an account and get an API key 2. Install the TypeScript SDK 3. Send a first message in the sandbox 4. Set up webhooks for incoming events 5. Add agent logic and conversation cues.
  • What platforms does messages.dev support?
    messages.dev is available on Web App.
  • What does messages.dev integrate with?
    Integrates through a REST API, a TypeScript SDK on npm and webhooks for incoming messages, reactions and receipts. No third-party app integrations are listed on the homepage.

Status

StatusActive
Views0
Outbound clicks0
Added10/20/2026

Platforms

Web App

Pricing

Freemium