iMessage API providers, compared

This is the only route Apple actually sanctions, and it is not what most people mean by an iMessage API. A business does not integrate with it directly. It selects an Apple-approved Messaging Service Provider, and the MSP holds the connection.

Becoming an MSP yourself is a substantial undertaking: Apple's own onboarding documentation requires a messaging platform supporting asynchronous conversations and intent-based routing, a channel connector, a customisable live agent console, and bot flows to triage incoming conversations, plus a team able to integrate each brand's CRM and back-end systems.

The structural constraint matters more than the paperwork. Conversations are customer-initiated: the person messages the brand first. An agent that texts you first is not something this programme is designed to support, which is why almost every product in our [agents directory](/agents) reaches iMessage some other way. Poke's approval as the first independent third-party AI agent on the programme was notable precisely because it is so unusual.

Sendblue publishes the clearest pricing of any managed provider we checked, and it is the one most often used as the reference point by everyone else's comparison pages.

Three tiers: a free sandbox limited to 10 verified contacts with no dedicated number and no outbound messaging; an AI Agent plan at $100 a month per dedicated line, with a dedicated number, 1,000 inbound contacts a day, webhooks, and support for media, typing indicators and reactions; and a custom-priced Enterprise tier.

The detail worth reading twice is what separates those last two. The $100 plan is described as inbound-first, and full outbound messaging appears in the Enterprise column. If your agent needs to send the first message, the published price is not the price you will pay. Sendblue states no per-message fees, no A2P registration charge, no carrier surcharges and no SMS fallback fees, and claims SOC 2 Type II certification, with HIPAA support on Enterprise.

Blooio has the lowest published entry price in this comparison and the widest gap between that entry price and the price of the thing most people actually want.

The published ladder: a free trial capped at 20 messages, Starter at $39 a month, Commercial Shared at $89, Inbound at $109, Commercial Dedicated at $289 per line, and Enterprise Dedicated from $195 per line once you are buying six or more.

The distinction that matters is shared versus dedicated. Blooio's own pricing page states that the Starter and Commercial Shared tiers use managed number pools, and that the sender number may vary between messages. For a transactional notification that may be acceptable. For an agent someone is meant to build a relationship with, where the person saves the number, texts it back and expects the same thread, a number that changes between messages is a different product. That is a jump from $39 to $289, and it is the single most consequential number on this page.

No per-message fees on any plan. Custom area codes are $75 per number as a one-off.

LoopMessage prices by unique active daily contacts rather than by messages, and unbundles more of the product into add-ons than anyone else here.

Dedicated sender plans: a free sandbox limited to 5 contacts, Light at $59.99 a month for up to 300 unique active daily contacts, and Regular at $99.99 for up to 1,000. There is also a shared sender option at $20 a month starting from 50 monthly contacts, and a free tier restricted to schools and non-profits.

Then the add-ons, which is where the comparison gets interesting. A sender name is $15. A phone number is $15 a month. SMS and RCS fallback with call forwarding is another $15 a month. WhatsApp is $10 a month. And initiating conversations, meaning the agent sending the first message, is $30 a month on top.

For a proactive agent on a dedicated number with fallback, the real monthly figure is meaningfully above the headline. Whether that is better or worse than a bundled competitor depends entirely on which pieces you need, which is the honest answer and not one any vendor comparison gives you.

Linq publishes the most capable feature list in this comparison and the least pricing information.

The capabilities, as stated on its own page: blue-bubble messaging, triggering tapbacks, read receipts and typing indicators, creating and managing group threads programmatically, photos, videos and voice notes, starting and scheduling FaceTime calls, RCS with automatic SMS fallback, and sharing or requesting live location through Find My. If your agent needs to feel native rather than merely functional, that is the list to compare others against.

Pricing is not published. There is a sandbox, an Enterprise tier, a 7-day trial and a form. A competitor's comparison page states roughly $250 a month plus a $1,000 setup fee. We have not been able to verify that from Linq, and we are not going to present a rival's number as fact.

Two disclosures belong on this listing. First, Linq states it is the only SOC 2 Type II compliant iMessage API, while Sendblue separately claims SOC 2 Type II certification, we report both claims and adjudicate neither. Second, Linq operates imessage.store, a competing directory of iMessage agents, which is worth knowing when reading its own comparisons of this market.

Tuco is the most architecturally transparent provider in this comparison, and that transparency is the reason to read it even if you buy elsewhere.

Its $335 setup fee is itemised as a dedicated Mac mini, a warmed Apple ID, and carrier KYC completed in your business name. Its own marketing draws the contrast explicitly: real hardware rather than, in its words, a SaaS API on top of someone else's pool. Every line gets its own Apple ID and Mac mini, and it commits to resolving Apple ID problems within 24 to 48 hours.

That is a description of how most of this market actually works, stated plainly. When a provider quotes you a flat monthly price with no per-message fee, something is running a Mac and an Apple account somewhere, and the questions that follow apply to every managed provider on this page, not only the one that says so: whose account, what happens when it is flagged, and how quickly it is restored.

The published limits are firm: 50 new conversations and 150 messages per line per day. Scaling means buying lines. Pricing beyond the setup fee is inconsistent between Tuco's own pages, which we have noted rather than resolved.

Photon has the most generous free tier in this comparison and the widest gap between its cheap tiers and its dedicated one.

The ladder: Free at $0 with unlimited daily messages, RCS and SMS fallback, up to 10 users and shared managed numbers; Pro at $25 a month for the same iMessage capabilities with up to 100 users; Business at $250 per dedicated line per month, adding dedicated numbers, up to 50 new contacts daily for cold outreach, full group messaging API access and unlimited users; and a custom Enterprise tier described as having the lowest throttling.

It also documents an open-source path that uses your own iCloud account number rather than one of Photon's, which sits somewhere between the managed and self-hosted routes and is worth understanding before choosing either.

Two limits deserve attention. Shared managed numbers apply to everything below Business, with the same consequences described under Blooio, a sender number you do not control is a different product from one you do. And the group messaging API is unavailable on Free, limited on the open-source path, and only fully available on Business and Enterprise, which matters a great deal if the agent is meant to join group threads.

Claw is the odd one out, and usefully so: it is the only provider in this comparison that meters messages rather than selling a line at a flat rate.

Published tiers: Base at $5 a month for 250 messages, Growth at $15 for 2,000, Plus at $25 for 6,000, Pro at $50 for 15,000, and an Agency plan at $199 a month per subtenant including 1,000 messages. It offers iMessage, RCS and SMS through one interface, assigns phone numbers to agents, and supports tapbacks, typing indicators, read receipts, group messages and HMAC-signed webhooks.

It also states that no Mac is required and that it runs on Linux, Docker, Windows or any cloud.

The metered model changes how you compare it. At a few hundred messages a month it is by far the cheapest option here. At volume the arithmetic inverts: 15,000 messages for $50 is competitive, but a flat-rate provider with no per-message ceiling stops caring about volume entirely while Claw keeps charging. Where your usage sits on that curve decides the answer, which is exactly the kind of comparison a vendor page will not do for you.

BlueBubbles is an open-source project that brings iMessage to Windows, Linux and Android by running a server on a Mac that already has Messages signed in. Clients ship through the Microsoft Store, Snap and Flathub, and Google Play. It is free, with donations.

It belongs in this comparison because it is the honest baseline. Every managed provider here is, at bottom, operating something equivalent on your behalf and charging for the operations, the recovery and the API surface on top. If you want to know what you are paying $100 to $289 a month for, this is it.

What you take on by self-hosting is real: a machine that must stay awake and online, an Apple account whose health is now your problem, updates that can change behaviour, and no support arrangement of any kind. That is manageable for a personal project and a poor fit for anything a customer depends on. Its documentation is oriented toward users wanting iMessage on a non-Apple device rather than toward developers building agents, so treat the API surface as something to evaluate in the code rather than from a datasheet.