Keiki vs Linq for iMessage AI Agents
Compare Keiki and Linq on agent hosting, iMessage features, group chats, testing and pricing. Already on Linq? Import your lines into Keiki without porting.
Should I use Keiki or Linq for an iMessage AI agent?
Choose Keiki for an iMessage AI agent: Keiki runs the agent, testing and team handoff, while the Linq API only delivers messages to an app you build and run. If your numbers are already on Linq, Keiki can import them without porting.
Key takeaways
- Choose Keiki for a customer-facing iMessage agent, hosted on Keiki or your own, with Eval Studio, traces and team takeover.
- Linq is a messaging API. Your own app still has to run the agent, test it and hand conversations to your team.
- Keiki can import the lines on your Linq account. The numbers stay on Linq; this is not a port.
- Imported Linq lines support tapbacks, effects and threaded replies in Keiki. For iMessage groups, use a line bought in Keiki.
- Published pricing on November 19, 2026: Keiki plans start at $20/mo with lines billed per line; Linq Business is $260 per month.
Keiki vs Linq at a glance
You don't always have to pick one. Keiki can import the lines on your Linq account, so an agent on Keiki can answer on numbers you already have.
| What you're choosing | Keiki | Linq |
|---|---|---|
| Agent runtime | Hosted agent with memory, tools and logs, or your own agent loop with Keiki handling delivery. | The Partner API sends and receives messages and webhooks. Your application runs the agent. |
| iMessage features | Tapbacks, effects and threaded replies on every iMessage line, imported Linq lines included. Group chats run on Photon or Blooio lines, not on Linq lines. See Keiki channels. | Group chats, threaded replies, tapbacks and custom reactions, effects, polls and typing indicators, per Linq's API docs. |
| Testing and operations | Eval Studio replays cases and traces tool calls. Teammates can take over the conversation. | Webhooks for delivery, read receipts, reactions and inbound messages, and W3C trace IDs on every request. Agent tests and tool traces live in the stack you build. |
| Other channels | The same agent on WhatsApp, Slack, Telegram and email, plus Microsoft Teams, X and phone calls. | WhatsApp, Payments and Voice are separate Linq APIs, each with its own base URL and credentials. |
| Published pricing (November 19, 2026) | Plans start at $20/mo, with a promotional $1/mo for the first 3 months on Starter. Dedicated lines are $300, $150 or $99 per line per month by plan, billed separately. See Keiki pricing. | Hobby is $0 for up to 20 contacts. Business is $260 per month with a dedicated line, payments and group messaging. Enterprise is custom. The page does not say whether Business is priced per line. See Linq pricing. |
Already on Linq? Import your lines
Already using Photon instead? See Photon alternatives for iMessage agents, including connecting your existing project to Keiki.
If your numbers already live on a Linq account, you don't need new ones to try Keiki. An owner or admin opens Channels → Buy line, chooses the Linq import and pastes a Linq API key.
Keiki lists the numbers on that Linq account with your key, adds each one as an imported line, and registers the inbound webhooks so customer texts reach your Keiki agent. The numbers stay on your Linq account, so Linq's plan and terms still apply. This is not a port. Moving a number off its current provider is a separate, support-led porting process.
A few rules apply to the import:
- Create an agent first. The import needs your organization's active Keiki API key.
- One Linq account at a time. Keiki refuses a key from a different Linq account until you delete the lines imported from the first one.
- Numbers already active in another Keiki organization are skipped and counted as "already in use elsewhere".
- Imported lines ignore iMessage group messages and don't get iMessage app cards. Buy a line in Keiki for those.
If inbound routing can't be set up, Keiki says how many lines it imported and that inbound routing isn't live yet, so you can retry or contact support.
What Keiki adds on top of the line
A line API gets the text to your server. The rest is up to you: who the customer is, which tools the agent may call, what happens while a long job runs, and how a teammate steps in.
Keiki covers that layer. The agent answers with memory and your tools, every turn is traced, and a teammate can take over the thread and hand it back. You can test the whole conversation in Eval Studio before customers see it, then connect the same agent to WhatsApp or email without rebuilding it.
For eligible physical goods and services, Keiki can also send an Apple Pay card inside Messages. The customer approves it with Face ID on their iPhone without leaving the thread. This requires Keiki Vault on the customer's iPhone and a business set up to accept payments through Grosso.
FAQ
Can I use my Linq numbers with Keiki without porting them? Yes. The Linq import connects the numbers on your Linq account using your API key. They stay on Linq, and Keiki registers inbound webhooks so your agent answers on them. Porting is a separate process for moving a number to Keiki.
Do I still need a Linq plan after importing? Yes. Imported lines stay on your Linq account, and Keiki sends through them with your Linq key, so Linq's plan applies to those numbers.
Can I keep my own agent and still use Keiki? Yes. The external harness keeps your agent's turn loop in your app while Keiki delivers messages on connected channels and records each turn.
Do both reach Android users? Yes, through RCS or SMS fallback rather than iMessage. Linq lists RCS and SMS fallback on its pricing page. On Keiki, the line's provider delivers to those contacts over SMS or RCS, and the agent sends plain text and files. Rich iMessage features don't carry over, so test both paths on your line.
Sources
Retrieved November 19, 2026 (Pacific time):
- Linq pricing: linqapp.com/pricing
- Linq Partner API docs: docs.linqapp.com/channel/imessage
- Linq API index and channels: docs.linqapp.com/llms.txt
- Keiki pricing: onkeiki.com/pricing
- Keiki docs: Channels compared, Cloud agents, Port an existing iMessage number, External harness
Try it on the line you already have
Build an agent on Keiki or bring the one you already run. If you're on Linq, import a line, send it a real customer question, and hand the thread to a teammate before you decide. For the wider field, see Keiki vs Sendblue.