11 iMessage API providers, compared from their own pages

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 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.

What separates the last two rows is worth reading twice. 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 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.

The add-ons are 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 provider depends entirely on which pieces you need.

This page read Linq Blue until the addresses were corrected. There is no product called Linq Blue: the name was ours, taken from the blue bubble the company sells.

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 at any tier, so budgeting for Linq means a sales conversation first.

On uptime, read the status page next to the SLA. The API page states a 99.95% SLA. Linq's own status page, at status.linqapp.com, reports 99.87% uptime for both the V3 and V2 APIs across June to September 2026, with the web dashboard and the CRM integrations at 100%. What the SLA covers, how it is measured and what it excludes is not published anywhere we could read, so these are two published numbers rather than a breach, and the gap is the thing to ask about rather than to conclude from.

Both figures are on Linq's own pages, which is the point: it publishes a status page at all, which is more than most of this set does.

The disclosure is unusually deep and it stops in one place. Linq holds SOC 2 Type I and Type II with reports published for 2022, 2024, 2025 and 2026 plus a March 2026 bridge letter, runs 70 controls with live pass status on a trust centre, tests its incident response plan and runs penetration testing annually, and publishes a vulnerability disclosure process anybody can read.

It names five subprocessors: AWS for compute, storage and key management, Cloudflare for CDN and TLS, Grafana Labs for logging, Sentry for error tracking and Hex for analytics. What that list does not include is anything about how iMessage itself is reached: no Apple relationship, no account arrangement, no hardware. For a route that exists because Apple publishes no general API, the question of whose Apple identity your messages leave from is the one thing this otherwise thorough page does not answer.

Behind it is Linq Technologies Incorporated, founded in 2019 by three former Shipt executives, Elliott Potter as chief executive, Patrick Sullivan as chief technology officer and Jared Mattsson as president. It began as a digital business card with lead capture for sales teams, which is still visible on the status page as a separately monitored Legacy Digital Business Card Platform.

It raised a $20M Series A in February 2026 led by TQ Ventures with Mucker Capital. Coverage of that round put the platform at over 30 million messages a month across more than 100 customers. The API page says 200M+ messages and 1,000+ teams. Both are the company's own figures, counted differently, and neither is dated on the page it appears on.

One disclosure belongs on this listing, corrected on 11 September 2026. This page said Linq operates imessage.store, a competing directory of iMessage agents. It does not, on the evidence: the store's iOS app is published by Soar Intelligence Inc., whose travel agent holds the store's paid top slot, and the store's own privacy policy names Linq once, as the messaging provider that delivers texts to and from its number. Linq carries the store's messages; somebody else runs it. The store's blog assesses iMessage infrastructure providers, Linq first, as an independent user, without saying whose site it is on.

On 18 September 2026 its account named six agents it powers: Poke, Tomo, Orchid, Ditto, Lindy and Slash. Three of those already carried Linq on this site from other sources; Ditto is also named by Photon, Lindy's policy names other carriers, and Slash is not listed here.

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, which the page attributes to Apple rather than to itself. Scaling means buying lines: Starter is one at $149 a month, Growth two at $299, and Enterprise a quote, each line carrying the $335 setup. The same page says what it is not: not SOC 2 certified, no HIPAA business associate agreement, stated on a limitations page it links from its pricing.

Its pricing page also argues with two of its competitors by name, quoting Sendblue's $100 tier as inbound-first and Blooio's $39 tier as a shared number capped at five new contacts a day, with a capture date of 15 May 2026. Both quotes match what those providers' pages said when this directory read them, and both are on their own rows here for a reader to check without taking either side's word.

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

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.

The open source is not a side project, it is the product. The photon-hq organisation was created on 6 September 2025 and now holds 86 public repositories. Spectrum, the framework that connects an agent to a channel, is MIT licensed with about 1,650 stars and was pushed to this week; the iMessage SDK underneath it has about 1,450. Since we last read this page the positioning has widened from iMessage to iMessage, WhatsApp, Telegram, Slack, Discord and more, which is a different product from the one the tables here were built to compare.

Photon names its customers in prose rather than on a logo wall, which is rare enough to be worth using: Rho, Vercel, Hermes Agent, Ditto, Fae and FlipText, with a sentence about each. A seventh named it back: Slashy's security page lists Photon in its subprocessor table as the agent messaging integration for iMessage, which is the only listing here whose own pages name who carries its messages. Three of those are listings in this directory, and their entries now record Photon as the vendor on the strength of that page. It also claims more than 10 million iMessage API calls a day.

The uptime claim is the one to check yourself. Its engineering blog argues that Photon speaks the protocol rather than driving a Mac, and concludes that if Apple's iMessage is up, Photon's API is up. Its own status page reports 99.84% for iMessage across June to September 2026, alongside 99.992% for infrastructure and 99.86% for the foundation layer. The same post also describes macOS relay nodes and managed fleets on AWS, so the architecture is not purely protocol-native either. None of this is hidden, and all of it is on Photon's own pages.

The trust centre is the thinner half. It claims SOC 2 Type 1, SOC 2 Type 2 and HIPAA across three frameworks and lists 25 internal policies, and it publishes zero subprocessors and zero documents, so there is no audit report to request and no list of who else touches the traffic. The legal entity behind it is Something Great Inc.

On 1 October 2026 TechCrunch reported a $4.5 million seed round co-led by Gradient and A*, with Vercel, HongShan, Z Fellows, Llama Ventures and Karman taking part. The company told it that more than 40,000 developers had signed up, that revenue grew tenfold in four months, and that the open-source version still accounts for 98% of use; it named Boardy, Ditto, Rho, Flip and Slashy among its customers. Those figures are the company's, relayed by the press.

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.

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.

Chert is the newest of the managed iMessage providers here and the most explicit about what it is for: an API and workflow layer for sending, receiving, routing and observing iMessage conversations, with fallback to SMS or RCS when the recipient is not on iMessage and visibility into which channel a message actually went out on. It launched through Y Combinator and lists Z Fellows, Betafund and OpenAI among its backers, with angels from Nvidia, LinkedIn, Scale AI, Anthropic and Grafana.

What it does not publish is the part worth noting, because it is the same gap as most of this market rather than a peculiarity of this company. There is no price at any tier and no compliance certification. Two things the first read recorded as unknown its FAQ does answer. Threads start from its side, "blue-bubble threads from verified numbers", so sending first is included. And on deliverability it says "we rotate sending identities, warm them gradually, and cap volume per identity per day", which is a description of a shared pool, recorded as one; nothing on the site offers a number that is yours. The same FAQ says anyone promising unlimited blast volume "is one ban away from disappearing", which is the most candid line about Apple's limits on any provider page here apart from Tuco's.

It does publish its customers, which is unusual here: ten named teams on the front page. For a category where most providers show no logos at all, a list of people willing to be named is a real signal, and it is not a substitute for a price.

Inkbox sells the agent an identity rather than a line: an email inbox of its own, a public address other software can reach, an agent-to-agent channel, and, on every plan, iMessage on a shared line with phone calls, with a dedicated iMessage number from the $200 plan. The pitch is the other direction from most of this page: not "send iMessages from your product" but "let people, apps and other agents reach your agent by any channel, and keep the memory of one person across all of them".

Two things the pricing page says that the front page does not. Below $200 the agent cannot start an iMessage conversation; the recipient has to write first, and the shared line is capped at three unique recipients a month on the free plan and ten on the $30 one, so the cheap tiers are for an agent that answers rather than one that reaches out. And SMS on the VoIP numbers is a separate thing from iMessage: 300 messages and 30 call minutes a month per number, US and Canada, with 10DLC registration handled for $20 a month per campaign.

It is built to be set up by the agent itself: the front page carries a prompt to paste into Grok Bot, Claude, ChatGPT or Hermes so the agent signs itself up, and plugins for Claude Code, Codex and OpenCode. Vectorly, Inc. doing business as Inkbox, San Francisco, backed by Y Combinator. No status page found; no compliance claim on the pages read.