How to build an iMessage agent in 2026
Apple publishes no general iMessage API. Here are the three routes that exist, what each costs, and what you take on with each.
There is no general-purpose iMessage API from Apple. That single fact explains almost everything about how agents on this channel are built, priced and marketed, and it is the thing most vendor pages state last or not at all.
You have three routes. Apple's own Messages for Business programme, which is customer-initiated and reached through an approved provider. A managed third-party API, which operates Apple infrastructure for you from about $5 a month. Or self-hosting a Mac and running an open-source bridge on it.
Route one: Apple Messages for Business
This is the only route Apple 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 means building a full contact-centre platform: Apple's onboarding documentation requires asynchronous conversation support, intent-based routing, a channel connector, a customisable live agent console, bot flows to triage incoming conversations, and 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 the programme is designed to support. Poke's approval as the first independent third-party AI agent on it was notable precisely because it is so unusual.
If your product is customer support for an established brand, this is your route. If your product is an assistant that reaches out, it is not.
Route two: a managed API
This is what most agents in this directory actually run on. You pay monthly, you get a REST API and webhooks, and someone else handles the machinery.
Published entry prices currently run from $5 a month at the metered end to $250–289 a month for a dedicated line. The full comparison, with each figure taken from the provider's own pricing page, is in iMessage API providers, compared.
Three questions decide which one fits, and none of them is price:
- Is the number dedicated or shared? Several providers' cheapest tiers put you in a managed pool where the sender number varies between messages. For a notification that may be fine. For an agent someone saves in their contacts and texts back, it is a different product.
- Can you send first? At least one provider's mid-tier plan is inbound-first, with outbound reserved for a custom-priced enterprise tier. If your agent initiates, check this before comparing anything else.
- What is the daily cap? One provider publishes 50 new conversations and 150 messages per line per day. Scaling past a cap means buying more lines, not a bigger plan.
Route three: self-hosting
An open-source bridge such as BlueBubbles runs on a Mac with Messages signed in and exposes an API. It is free, and it is the honest baseline for understanding what the managed providers charge for.
What you take on is real: a machine that must stay awake, an Apple account whose health is now your problem, updates that can change behaviour, and no support arrangement. Workable for a personal project, poor for anything a customer depends on.
The thing nobody's pricing page frames as a risk
Because Apple offers no general API, a flat monthly fee with no per-message charge means somebody is operating Apple hardware and Apple accounts somewhere. One provider, Tuco, states this openly, its setup fee is itemised as a dedicated Mac mini, a warmed Apple ID and carrier KYC in your business name.
That description applies across the managed category. So the questions worth asking are: whose Apple ID does the agent send from, what happens operationally when it is flagged, how quickly is it restored, and is there a contractual commitment or only an uptime figure in marketing copy. This is platform-dependency risk, and it belongs in your build decision rather than in a footnote.
What the agents in this directory actually did
Of the 33 agents catalogued here, 28 reach iMessage. Nine of those are iMessage-only, with no SMS fallback recorded, meaning that for a recipient on Android they simply do not work. Fourteen pair iMessage with SMS so that a message still lands when the bubble would be green.
And exactly one supports RCS, despite RCS being the industry's stated answer to cross-platform rich messaging and now being supported on iPhone. Whatever the roadmaps say, the products shipping today have not moved.
If you are choosing a route now, that ratio is worth weighing. The cheap fallback path everyone assumes exists is, in practice, almost unused.