Chert iMessage API
Shares rank 5 of 6 messaging APIs by recommenders
Lets businesses and agents message customers over iMessage, with SMS/RCS fallback. Critics say it violates Apple's terms and could be shut down overnight.
Lets businesses and agents message customers over iMessage, with SMS/RCS fallback. Critics say it violates Apple's terms and could be shut down overnight.
39 people gave an opinion
- recommend it
- 5
- criticize it
- 34
- approval share
- 13%
Recommended in 1 of 13 months
- November 2025: not recommended
- December 2025: not recommended
- January 2026: not recommended
- February 2026: not recommended
- March 2026: not recommended
- April 2026: not recommended
- May 2026: recommended
- June 2026: not recommended
- July 2026: not recommended
- August 2026: not recommended
- September 2026: not recommended
- October 2026: not recommended
- November 2026: not recommended (month in progress)
Why it doesn’t carry the badge
- 5 people recommend itNeeds 10 or more, not met.
- 0.1 recommenders for every criticNeeds 2 to 1 or better, not met.
- Recommended in 1 of 13 monthsNeeds 4 or more, not met.
The same three rules apply to every product, and the badge can’t be bought. How the badge works
What people say about it
The reasons people give, with the number of comments that give each one. Open a reason to read what they said.
Why people recommend it
Each mark is one comment
Lets agents reach iMessage users
“giving agents the ability to interact with iMessage users, which is something that fundamentally can't be done on the current interface”
Comment from 25 May 2026 in “Launch HN: Chert (YC P26) – Twilio for iMessage” “allowing agents to interact with humans on iMessage, which is something that the current iMessage interface cannot do”
Comment from 25 May 2026 in “Launch HN: Chert (YC P26) – Twilio for iMessage” “Our goal behind this is to make it easier for people to conversationally interact with agents”
Comment from 25 May 2026 in “Launch HN: Chert (YC P26) – Twilio for iMessage” Scale, stability and SMS/RCS fallback
“we're more focused on 2-way conversational business use cases such as customer service that require scale and stability”
Comment from 25 May 2026 in “Launch HN: Chert (YC P26) – Twilio for iMessage” “we have SMS/RCS fallback systems in place so no conversations get stopped or lost”
Comment from 25 May 2026 in “Launch HN: Chert (YC P26) – Twilio for iMessage”
What people warn about
Each mark is one comment
Makes bots look like people
“This impersonates a person on a platform which has generally prevented that... so people will be more likely to have a conversation, as they don't expect it to be a bot.”
Comment from 26 May 2026 in “Launch HN: Chert (YC P26) – Twilio for iMessage” “So the business is to trick people into thinking they’re speaking with a real person”
Comment from 25 May 2026 in “Launch HN: Chert (YC P26) – Twilio for iMessage” “yet another attempt at blurring the distinction between bots and human interactions”
Comment from 25 May 2026 in “Launch HN: Chert (YC P26) – Twilio for iMessage” SIM farm and spam concerns
“which to me resembles the SIM farms that are a scourge when it comes to consumer fraud and abuse”
Comment from 25 May 2026 in “Launch HN: Chert (YC P26) – Twilio for iMessage” “I get enough text and call spam I can't prevent even with reporting every single one of them.”
Comment from 26 May 2026 in “Launch HN: Chert (YC P26) – Twilio for iMessage” “these guys are running a massive e-sim farm that sits on top of a rest api”
Comment from 26 May 2026 in “Launch HN: Chert (YC P26) – Twilio for iMessage” Risks harming iMessage trust
“Exploiting the trust users have in iMessage by injecting unsupported business messages into it degrades the value of the channel”
Comment from 26 May 2026 in “Launch HN: Chert (YC P26) – Twilio for iMessage” “Are you worried your users will ruin the trust of the blue bubble thus killing your product”
Comment from 25 May 2026 in “Launch HN: Chert (YC P26) – Twilio for iMessage” “The absolute last thing I need or want is for the same thing to happen to iMessage.”
Comment from 25 May 2026 in “Launch HN: Chert (YC P26) – Twilio for iMessage” Could be shut down by Apple
“Apple will close you down just like they did with every other service that bypassed their walled gardens.”
Comment from 25 May 2026 in “Launch HN: Chert (YC P26) – Twilio for iMessage” “they need to grow into a more robust business than just being an API that can get shut down overnight”
Comment from 25 May 2026 in “Launch HN: Chert (YC P26) – Twilio for iMessage”
Other messaging APIs people recommend
The four most recommended other messaging APIs, with the same counts for each, so you can compare like for like. The tick on each bar marks the 2 to 1 line the badge needs.
| Product | Recommend | Criticize | Approval | Months | Owned | Badge |
|---|---|---|---|---|---|---|
| Twilio API | 15 | 32 | 32% | 8 | 3 yrs3 owners | — |
| Telegram Bot API | 11 | 1 | 92% | 7 | — | Approved |
| Kapso | 10 | 1 | 91% | 2 | — | — |
| Telnyx API | 6 | 6 | 50% | 5 | — | — |
| Chert iMessage APIThis page | 5 | 34 | 13% | 1 | — | — |
What people said
40 of the 51 comments that mention it, newest first. Each links to the original comment.
“That's not what it's for, you don't have the authority to do that, and it's going to get someone in trouble at some point.”
“Exploiting the trust users have in iMessage by injecting unsupported business messages into it degrades the value of the channel”
“these guys are running a massive e-sim farm that sits on top of a rest api”
“your business model relies on continuously violating Apple's terms of use with impunity”
“I get enough text and call spam I can't prevent even with reporting every single one of them.”
“This impersonates a person on a platform which has generally prevented that... so people will be more likely to have a conversation, as they don't expect it to be a bot.”
“they need to grow into a more robust business than just being an API that can get shut down overnight”
“The entire business model depends on Apple turning a blind eye”
“Apple will close you down just like they did with every other service that bypassed their walled gardens.”
“what happens when Apple decides to shut it down?”
“this startup idea also allows non-sanctioned entities access to iMessage”
“it is trying to avoid the registration/vetting process implemented by iMessage for Business”
“allowing agents to interact with humans on iMessage, which is something that the current iMessage interface cannot do”
“giving agents the ability to interact with iMessage users, which is something that fundamentally can't be done on the current interface”
“That is obvious from all the upvotes your comments get on here.”
“Apple already has a feature built for this exact purpose”
“They are a photon + linq wrapper. Very surprised YC backed this actually”
“Our goal behind this is to make it easier for people to conversationally interact with agents”
“If you get shut down I have to redo this setup using Apple ?”
“if I were evaluating it for use in my business, it is obviously not something I can rely on”
“anyone who depended on their service would/should probably run away kicking and screaming”
“this is going to get banned the moment anyone from Apple sees it”
“So the business is to trick people into thinking they’re speaking with a real person”
“This service should not exist, you should feel bad for creating it”
“Why would yc fund them given how obvious the risk is ?”
“This is a foothold business living entirely at Apple's discretion.”
“they should probably ignore you and continue working on it seeing as they got accepted into YC”
“I think this is bad and antisocial and you should shut it down.”
“Are you worried your users will ruin the trust of the blue bubble thus killing your product”
“which to me resembles the SIM farms that are a scourge when it comes to consumer fraud and abuse”
“how is it possible to build this whole thing and not know there is a very rich first party api”
“Isn't this a direct violation of Apple's terms of service?”
“yet another attempt at blurring the distinction between bots and human interactions”
“People don't report our phone lines to be spam because the use cases that we focus on are either mostly inbound”
“we're more focused on 2-way conversational business use cases such as customer service that require scale and stability”
“It's good YC is funding you because it acts as a later of protection from legal threats by apple”
“we have SMS/RCS fallback systems in place so no conversations get stopped or lost”
“For iPhone only users, so right off the bat your product is targeting 50% ish of a companies customer base.”
“The absolute last thing I need or want is for the same thing to happen to iMessage.”
“I want fewer messages not more.”
Counts come from 1,795,640 Hacker News comments, November 2025 to November 2026. How we count. Report a mistake.