Blue Reacher vs Tuco AI

Compare Blue Reacher and Tuco AI side by side: iMessage features, channels, developer tools, pricing and compliance, checked on each provider's own site.

Blue Reacher

Managed iMessage lines for B2B sales, with API and MCP
Starting price
$199/month per line at 4+ lines; $249/month for 1 to 3 lines
Free plan
Free public sandbox key; simulator only, no real sends

Tuco AI

iMessage follow-up for opted-in leads from your CRM
Starting price
$149/month (Starter, 1 line) plus $335 setup
Free plan
None; docs say no free trials or refunds

Blue Reacher supports 50 of the 77 features compared here, and Tuco AI supports 41.

Feature comparison

FeatureBlue ReacherTuco AI
iMessage messaging
iMessage
SupportedOne-to-one iMessage sends and replies over REST and webhooks.
Supported
Group chats
PartialAPI docs (22 Oct 2026) say not available yet; the site sells group threads opened from the CRM.
Not supportedTuco's llms.txt says it has no group chats.
Group management
PartialAdd, remove and leave are documented, but aPI docs (22 Oct 2026) say not available yet.
Not supportedNo group chat support
Group name and photo
PartialRename and group photo are documented, but aPI docs (22 Oct 2026) say not available yet.
Not supported
Mentions
Not listed
Not supported
Tapbacks
PartialInbound reactions arrive as webhooks; sending the six tapbacks is not available on the API yet.
SupportedSend six classic tapbacks by API; inbound reactions, including custom emoji, arrive as message.reaction.
Threaded replies
PartialSite lists threaded replies; the API reply option sends a quoted reply, not an inline thread.
Not listed
Typing indicators
PartialTyping endpoint is documented, but aPI docs (22 Oct 2026) say not available yet.
PartialStart and stop typing by API, best effort. Inbound typing events not documented.
Read receipts
Partialmessage.read webhooks fire; sending native read receipts is not available on the API yet.
Supportedmessage.opened webhook with readAt when the recipient has read receipts on.
Edit and unsend
Not listed
Not listed
Message effects
Partial8 screen and 4 bubble effects are documented, but aPI docs (22 Oct 2026) say not available yet.
Not listed
Animated text effects
Not listed
Not listed
Stickers
Not listed
Not listed
Formatted text
Not supportedDocs say there is no Markdown rendering on any channel.
Not listed
Attachments
SupportedOne file per message for now. Images and video up to 100 MB, audio and PDF up to 25 MB.
SupportedUp to 2 files per message, 25 MB each. Not allowed on the first message to a contact.
Live Photos
Not listed
Not listed
Rich link previews
SupportedA bare URL renders as a preview card on iMessage, built on the recipient's device.
Not listed
Voice messages
PartialNative voice memo endpoint is documented, but aPI docs (22 Oct 2026) say not available yet.
SupportedvoiceNote sends one audio file as a native voice note bubble.
Contact cards
PartialDocs and site say lines send contact cards; no endpoint appears in the API reference.
Not listed
Polls
Not listed
Not listed
Chat backgrounds
Not listed
Not listed
Location sharing
Not listed
Not listed
iMessage apps
Not listed
Not listed
Live app cards
Not listed
Not listed
Sender name and photo
Not listedDocs say recipients see only the number until they save your contact card.
PartialLine name and photo are set by Tuco staff, at most 3 changes per line per month.
FaceTime calls
PartialFaceTime audio from the line, started by a person; $99/mo add-on. Calls API not available yet.
PartialFaceTime Audio calls as a $100/month per-line add-on. Tuco's llms.txt says it has no FaceTime.
Delivery status
Supportedmessage.sent, delivered, read and failed webhooks, plus a status endpoint.
Supportedqueued, sent, delivered, failed and fallback statuses, with sent, failed and fallback webhooks.
iMessage availability check
PartialCapability lookup for up to 100 numbers is documented, but aPI docs (22 Oct 2026) say not available yet.
SupportedSingle, round-robin and bulk checks, about 70 per line per day.
Focus and Notify Anyway
Not listed
Not listed
Numbers and delivery
Managed lines
SupportedEach line is an Apple ID on Apple hardware run by Blue Reacher.
SupportedEach line is a real iPhone with an eSIM that Tuco hosts. About 48 hours to activate.
Dedicated numbers
SupportedEvery line is a dedicated number with a custom area code.
SupportedOne Apple identity per line. Lines can be ordered by API.
Shared numbers
Not supportedDocs say each line is yours alone, never shared and never recycled.
Not listed
Bring your own number
SupportedPricing lists port-in support for an existing number.
PartialDocs say existing numbers cannot be ported in, but a Linq migration page offers to port Linq numbers.
Line pooling
SupportedOmit the line on a send and load balancing picks one; the site calls it smart routing.
SupportedSends without fromLineId round-robin across active lines.
SMS fallback
Supported
PartialThrough your Twilio, GoHighLevel or webhook provider, or P2P SMS from the line once support enables it.
RCS fallback
PartialSite says iMessage, then RCS, then SMS; the docs say the platform's own fallback is SMS.
Not supportedRCS not offered
Outbound-first messaging
SupportedCold outreach allowed: 30 cold or 50 opted-in new contacts a day per warmed line.
SupportedOutbound to opted-in contacts. Cold lists are refused, and first messages cannot carry links or files.
Calls on the iMessage number
PartialFaceTime audio from the same line. Phone calls need your own provider using the number as caller ID.
SupportedCalls go out from the same number the line texts from. 500 minutes per line per month included.
Other channels
SMS
PartialOnly as automatic fallback from the same line.
PartialSMS through your own Twilio, GHL or webhook provider, or P2P SMS from the line in its eSIM country.
RCS
PartialSite lists RCS fallback; the docs say messages deliver over iMessage or SMS.
Not supportedNot offered
WhatsApp
Not supportedNot offered
Not supported
Telegram
Not supported
PartialTelegram bot for team notifications and replies. Leads are not messaged on Telegram.
Slack
Not supportedNot offered as a channel; a Slack guide forwards replies into Slack.
PartialLead conversations appear as Slack threads the team can reply from. Not a channel to contacts.
Email
Not supportedNot offered. Docs say there is no email-address sender option.
SupportedmessageType email sends email, and an email bridge sends iMessages from your inbox.
Phone calls
PartialDocs cover FaceTime audio only; the pricing page lists 2-way calling with SIP routing.
SupportedOutbound calls with recording, inbound forwarding and a click-to-call API (beta, +1 numbers only).
Apple Messages for Business
Not supportedNot offered; the site describes it as a separate Apple product.
Not supportedNot offered
Unified channel API
SupportediMessage and SMS fallback share one send endpoint and message model.
SupportedOne send endpoint with messageType imessage, sms or email.
Developer tools
REST API
Supported
Supported
TypeScript SDK
Supportednpm package bluereacher, v0.1.0 (Sept 2026), MIT.
Not listedThe iMessage API page shows npm install @tuco-ai/sdk, but no such package is on npm.
Python SDK
SupportedPyPI package bluereacher, v0.1.0 (Sept 2026), MIT.
Not listed
Other SDKs
Not supportedDocs suggest generating Go, Java, Ruby or PHP clients from the OpenAPI spec.
Not listed
CLI
Supportedbluereacher-cli on npm: send, status, conversations and capability checks.
Not listed
Webhooks
Supported
SupportedSent, failed, fallback, opened, reply, reaction, AI draft, handover, call recording and DNC events.
Signed webhooks
SupportedHMAC-SHA256 in X-BlueReacher-Signature.
SupportedHMAC-SHA256 in the X-Tuco-Signature header.
MCP server
SupportedHosted MCP server at api.bluereacher.com/v1/mcp; works with sandbox keys.
Supportedtuco-mcp on npm, run locally with an API key, with about 90 tools.
Open source
PartialSDKs, CLI, a stdio MCP server and an n8n node are MIT on GitHub. The platform is closed.
Partialtuco-mcp is MIT licensed on npm. The platform is closed.
Self-hosting
Not listed
Not listedHosted on Tuco hardware. Self-hosting is not mentioned.
Local testing
SupportedPublic sandbox key runs the API and MCP against a simulator, with simulated inbound replies.
PartialSimulate runs a goal bot against a transcript without sending. Message sends have no sandbox.
Custom channel providers
Not listed
PartialSMS fallback can route through your Twilio, GoHighLevel or a custom webhook.
Event replay
PartialRetries for about a day; undelivered events are kept and support replays them on request.
Supported30-day webhook delivery log with replay from the dashboard or API, plus one automatic retry.
OpenTelemetry
Not listed
Not listed
No-code integrations
SupportedNative GoHighLevel, plus Zapier, Make and n8n guides and an n8n community node.
SupportedGoHighLevel, n8n, Zapier and Make.com.
CRM integrations
SupportedNative HubSpot, Salesforce, Close, Pipedrive, Follow Up Boss and Jobber (beta).
SupportedHubSpot, Salesforce, Close and Pipedrive. One CRM per workspace.
Built for AI agents
Agent framework
PartialBuilt-in AI reply assistant on your own model key, with per-contact controls. No agent SDK.
SupportedHosted goal bots and Knowledge Base replies with tools, in copilot or autopilot mode.
Agent framework integrations
PartialGuide pages for LangChain and the Vercel AI SDK that wrap the API as a tool.
Not listed
Streaming replies
Not listed
Not listed
Agent group chats
Not listed
Not supportedNo group chat support
Human handoff
SupportedPause or snooze the AI assistant per contact while a person replies.
SupportedCopilot drafts need approval, and conversation.handover fires when the AI stops for a person.
Audit logs
PartialDocs mention an exportable opt-out audit trail; no general activity log is documented.
SupportedActivity log of workspace changes, including MCP tool calls.
Message history API
SupportedConversation history per contact, cursor-paginated.
SupportedMessage history, conversations and replies endpoints.
Plans and compliance
Free plan
SupportedFree public sandbox key; simulator only, no real messages sent.
Not supportedDocs say there are no free trials, paid pilots or refunds.
Public pricing
Supported
SupportedStarter $149/month, Growth $299/month, plus $335 setup per line.
No per-message fees
Supported
SupportedNo per-message fees. AI credits and extra call minutes are billed separately.
Uptime SLA
Not listed
Not listedGrowth lists a 4-hour support SLA. No uptime SLA found.
Isolated infrastructure
SupportedDedicated lines per customer, never shared; workspaces logically isolated.
SupportedEach line runs on its own iPhone and Apple ID on dedicated Mac hardware, with no VMs.
SOC 2 Type II
Not supportedTrust page says controls map to SOC 2 but the independent attestation is not complete.
Not supportedSecurity page says Tuco does not hold SOC 2.
GDPR
SupportedGDPR page and a published DPA with Standard Contractual Clauses.
SupportedGDPR page with data rights and Standard Contractual Clauses. DPA availability listed.

Checked on each provider's own site and docs on 2026-10-25. “Not listed” means the provider does not mention it.

Pricing

Blue Reacher

Lines are $249 a month each plus a $449 activation fee, $199 a month each at 4 or more lines, or $1,949 per line per year with activation waived.

Pricing model: flat per line, no per-message fees

Source

Tuco AI

Starter is $149 a month for 1 line and Growth $299 a month for 2 lines, each with a one-time $335 setup fee per line and no per-message fees.

Pricing model: flat per line, plus AI credits and call minute packs

Source

Which should you choose?

Choose Blue Reacher if you need group chats, group management, group name and photo and threaded replies.

Choose Tuco AI if you need sender name and photo, Telegram, Slack and email.

Frequently asked questions