What Apple's terms say about all this

Almost every iMessage agent runs on infrastructure Apple did not sanction. Nobody writes about what that means, and the reason is structural: everyone selling in this market has an interest in not raising it, and everyone buying would rather not know.

This page reports what Apple's published terms say, what Apple has actually done, and what remains genuinely unresolved. It does not tell you that anyone is in breach of anything. That is a legal conclusion about specific companies, we are not lawyers, and we are not going to imply one.

Three different positions, not one

The market gets discussed as though it were uniform. It is not, and the differences matter more than anything else here.

Your Mac, your Apple Account. An open-source bridge such as BlueBubbles runs on a machine you own, signed in to an account that is yours, sending messages you are entitled to send. Whatever else is arguable, this is the position furthest from anything Apple's terms address.

Somebody else's Mac, an account operated on your behalf. This is the managed category, and it is what almost every agent in this directory runs on. One provider itemises it plainly: its setup fee buys a dedicated Mac mini, a warmed Apple Account and carrier KYC in your business name. Others describe the same arrangement less directly or not at all.

Neither, via the protocol itself. Reverse-engineered clients that speak iMessage without Apple hardware. Beeper was the prominent example; open-source projects such as pypush continue in the same space.

What Apple's terms actually say

From the iCloud Terms and Conditions, quoted rather than characterised:

On sharing, section IV.A: "You are solely responsible for maintaining the confidentiality and security of your Account... you should not share your Account and/or password details with another individual."

On ownership, section IV.C: "Nothing in this Agreement shall be construed to convey to you any interest, title, or license in an Apple Account." And IV.D: "Your Account is non-transferable."

On resale, section IV.E: "You agree that you will not reproduce, copy, duplicate, sell, resell, rent or trade the Service (or any part thereof) for any purpose."

On automated access, section V.B.10, users agree not to "interfere with or disrupt the Service (including accessing the Service through any automated means, like scripts or web crawlers)."

On termination, section VII.B: "Apple may at any time, under certain circumstances and without prior notice, immediately terminate or suspend all or a portion of your Account and/or access to the Service."

Two things are worth reading carefully rather than skimming. The sharing clause says should not, not must not, which is softer language than people assume. And the automated access clause is scoped to conduct that interferes with or disrupts the Service, which is narrower than a flat prohibition on automation. Neither observation resolves anything, and both are the kind of detail that gets flattened in casual retellings.

The clause with the most obvious bearing on a paid managed service is IV.E, on resale of the Service. What that means for a company charging monthly to operate Apple infrastructure on your behalf is not something we are going to answer for you.

What Apple has actually done

Terms are one thing and enforcement is another, and here there is a real, public record.

Beeper reverse-engineered the iMessage protocol to bring blue-bubble messaging to Android. Apple blocked it repeatedly through late 2023 and into 2024, Beeper eventually gave up, and Apple stated publicly that it had taken "steps to protect our users by blocking techniques that exploit fake credentials in order to gain access to iMessage." The episode was cited by the US Department of Justice in its 2024 antitrust suit as an example of Apple controlling third-party behaviour.

Read Apple's own wording there. It targets fake credentials, which describes the protocol-reverse-engineering position and does not obviously describe a provider running real Apple Accounts on real Macs. That is a meaningful distinction and it is the one Apple itself drew.

We are not aware of public enforcement against the managed-API category. Absence of reported enforcement is not permission, and it is not a prediction. It is simply what the public record currently shows.

What nobody knows

Several things, and it is more honest to list them than to write around them.

Whether operating an Apple Account on a customer's behalf, at scale, for a fee, falls within the resale clause. Whether an individual account being flagged is a terms decision or an anti-spam heuristic. What Apple would do if the category grew large enough to matter to it. Whether the DOJ litigation changes Apple's appetite for enforcement in either direction.

Nobody selling into this market will tell you, and most of them have not been asked.

What to actually do about it

Treat it as platform-dependency risk and price it. Your agent's ability to reach anyone depends on an arrangement Apple has not blessed and could disrupt. That is not a reason to avoid the channel. It is a reason not to build a business with no path off it.

Ask your provider three questions. Whose Apple Account sends your messages. What happens operationally when it is flagged. Whether anything contractual backs the answer. In our comparison of nine providers, exactly one publishes an uptime SLA and exactly one publishes a recovery commitment, which tells you how often these questions get asked.

Know which position you are in. Running your own Mac, buying a managed line, and building on a reverse-engineered client are three different exposures. Vendors will happily let you not think about which one you have bought.

Have a fallback that works. Nine of the thirty three agents in this directory do not function at all for someone on Android. If iMessage access became difficult tomorrow, those products would have no channel. Blue bubble or green covers what fallback actually costs.

The sanctioned route exists and is narrow: Apple Messages for Business, customer-initiated, through an approved provider. One independent AI agent has ever been approved. Everything else in this market is operating in a space Apple has not endorsed and has not, so far, closed.