Reply.io Overview
How LinkedIn runs as one channel of a Reply.io sequence, what each plan charges for it, the daily limits per action, and what its API and MCP server reach.
Reply.io is a sales engagement platform that mixes email, LinkedIn, calls, SMS and WhatsApp steps in one sequence. On LinkedIn it runs nine kinds of action from your own connected account, inside a daily limit per action that you set. LinkedIn is included from $89 per user a month on the Multichannel plan, or $69 per account as an add-on. Its REST API can send a LinkedIn invitation or message directly, while its MCP server reaches sequences and the inbox but has no LinkedIn send tool.
On this page
What Reply.io is
Reply describes itself as “an AI-powered sales engagement platform”. The core is the sequence: “Reply mixes email, LinkedIn, call, SMS, WhatsApp, task, and Zapier steps in one sequence”. Around it sit a shared inbox, CRM sync and Jason AI SDR, an AI agent that writes and answers messages. A newer site, agents.reply.io, packages the same platform as “Headless Jason AI SDR”, an API for AI agents, and calls itself “a product concept built on a real platform”.
LinkedIn sends from the customer’s own connected account. Reply offers three ways to connect it: “session cookie via the Findy extension, credentials, or a shareable invite link for accounts you do not have direct access to”. With credentials you can also store the account’s 2FA secret, and then “Reply passes authenticator checks for you and can reconnect the account automatically later”. An invite link “is valid for 7 days”. Reply asks that the account be used “from one device and location”, and its pages read on 3 November 2026 do not say where LinkedIn actions run: in Reply’s cloud, through a proxy or in your browser.
How LinkedIn runs in a sequence
“Reply runs LinkedIn as a sequence channel with nine automatic action types: connection requests, messages, InMail, voice and AI voice messages, profile views, post likes, endorsements, and follows.” A sequence steps through them on its schedule, between email and call steps, and Jason AI SDR can draft and answer LinkedIn messages in a review mode or on its own.
- Sizes. A message body runs “up to 8,000 symbols”, a connection note “up to 300 symbols” and an InMail subject “up to 200 characters”, with “one attachment per message, 3 MB maximum” and voice messages “up to 60 seconds”.
- Direct sends. A single invitation, InMail or message can also go out on demand, outside any sequence, from the app or the API.
- Language. “Reply’s LinkedIn automation is fully supported only in English.”
A LinkedIn step stops when the session cookie expires, a Sales Navigator subscription lapses, a contact has no valid profile URL or a limit is reached. When LinkedIn asks for a check Reply cannot pass, the account is marked disconnected and you get a notification to reconnect it.
Reply.io pricing
Reply sells three families of plans, each metered by active contacts: “the number of unique contacts you can send 1 first-step email and an unlimited number of follow-ups per month”. Whether LinkedIn is included depends on the plan. Prices are in US dollars.
| Plan | Billed yearly | Billed monthly | |
|---|---|---|---|
| Email Volume | From $49 per user a month, 1,000 contacts | From $59 per user a month | Add-on, $69 a month per account |
| Multichannel | From $89 per user a month | From $99 per user a month | “1 / user included”, with unlimited active contacts |
| AI SDR Starter | $500 to $1,000 a month, 1,000 to 3,000 contacts | $800 to $1,500 a month | 2 to 7 accounts included |
| AI SDR Growth | $1,500 or $3,000 a month, 5,000 or 10,000 contacts | $2,500 or $5,000 a month | 10 or 25 accounts included |
| AI SDR Enterprise | From Reply’s sales team | On request | 25 or 50 accounts |
| Agency Core | From $210 a month | Not published | Optional, $69 a month per account |
| Agency AI SDR | From $500 a month per client | Not published | Included |
Email Volume prices climb with the contact tier, to $899 a month billed yearly at 100,000 contacts. Calls and SMS cost $29 a month per account where they are not included. There is a 14-day trial and no free plan, and the trial’s limits are not published.
Reply’s own pages disagree in two places. The comparison table in the same pricing file starts Agency at $166, against $210 in the plan block, and agents.reply.io quotes engagement plans “from $59/user/month (billed annually)”, against $49 billed yearly in the pricing file.
The limits Reply.io sets
Reply caps each automatic action type per day, per connected account. In its dynamic mode, ranges “pick a random number each day”, suggested at 25 to 35 for most actions and 35 to 50 for messages, while “the static mode uses one fixed number, 30 by default”. “Any limit can be raised to 100. A hit limit pauses that action until the next day.”
| Setting | What Reply.io publishes |
|---|---|
| Action types with their own limit | 9: connections, profile views, post likes, messages, InMail, detections, revoked connections, endorsements, follows |
| Suggested daily range | 25 to 35 for most actions, 35 to 50 for messages |
| Static mode | One fixed number, 30 by default |
| Ceiling | 100 a day per action type |
| Who sets it | The user, per action type, with edits taking effect the next day. Reply also “sets recommended safe limits for each action type” |
| Reset | “Limit counters reset according to the UTC time zone.” |
| When a limit is reached | “Reply pauses that action, notifies you in the sequence Log tab, and resets everything the next day.” |
| Revoking pending requests | After 7 days by default, settable from 1 to 180 |
| What does not count | “Manual actions never count”, and “Direct actions do not count toward safety limits” |
Reply also prints its own estimates of LinkedIn’s caps, and labels them as estimates: “LinkedIn does not publicly disclose its own limits”, and “the figures below are Reply’s recommendations based on testing and experience.” For a new account it advises starting at 10 to 15 connection requests a day and moving to 20 to 30 after a week or two. LinkedIn’s own published numbers are compiled on LinkedIn automation statistics.
The Reply.io API
Reply publishes a REST API, version 3, at api.reply.io/v3, with a Bearer key in the header and a personal API key as the preferred, scoped credential. Its limits are “100 requests per minute, 3,000 per hour and 150,000 per week, per user”, with reporting endpoints capped at 500 an hour and the monthly request quota “set by your plan”.
The OpenAPI file lists 433 operations in 53 groups, counted on 3 November 2026, and 27 of them concern LinkedIn.
- Direct LinkedIn sends. Five endpoints send to one contact outside a sequence: a connection request, an InMail, a message, a voice message and an AI voice message.
- LinkedIn accounts. Fourteen operations list, connect, reconnect and remove accounts, switch them on and off, and set each account’s limits and revoke window.
- Sequences and reporting. Assigning accounts to sequences, LinkedIn statistics and enrichment by LinkedIn URL make up the rest.
- Webhooks. Eight LinkedIn events, from a connection request sent or accepted to a message replied, a reply categorized and an account alert that “flags a channel that needs human attention”.
A command-line tool, reply-cli, and 18 agent skills wrap the same API.
The Reply.io MCP server
Reply runs a hosted MCP server at https://mcp.reply.io/ over streamable HTTP, signed in with a Bearer key or OAuth. It exposes 71 tools, 32 marked read-only and 39 marked destructive, and its limits are 120 calls a minute, 3,000 an hour and 150,000 a week.
- What it covers. Sequences, contacts, the inbox, tasks and, with 31 tools, Jason AI SDR, including its approval queue.
- LinkedIn. It can list connected LinkedIn accounts and assign one to a sequence. It has no tool that sends a LinkedIn invitation or message directly, so LinkedIn messages leave through a sequence or as a reply in an existing inbox thread.
- Confirmation. Calls run at once: “Reply MCP executes a successful call immediately”, and “there is no undo”. Reply’s agent guide tells the assistant to “confirm with the user before anything that sends to a prospect” and marks nine tools as high-stakes.
The shape of job it fits
Reply.io fits a sales team that runs outreach as sequences across several channels and wants LinkedIn as one step among email, calls and messaging, with the replies in one inbox and the CRM in sync. The AI SDR plans fit a team that wants an agent to write and answer at volume, with LinkedIn accounts bundled in. For a product of your own, the REST API is unusual in this category: it can send a LinkedIn invitation, InMail or message directly, and set each account’s limits.
The edges sit in a few places. Where LinkedIn actions run is not published. An account connects through a cookie, a password with a stored 2FA secret, or an invite link. Direct and manual sends do not count toward the safety limits. And an agent working through the MCP server reaches LinkedIn only by way of sequences and inbox replies, with no server-side confirmation step.
Reply.io alternatives
GTM API is our own product, so it is listed first. The others are described from their own pages, in alphabetical order. They split by job: campaign apps priced per LinkedIn account, a LinkedIn slot inside an email suite, and APIs for building LinkedIn into your own product or agent.
| Tool | How it runs | Price unit and entry | API | MCP server |
|---|---|---|---|---|
| gtm-api.com, ours, listed first | A cloud browser and proxy per connected account, driven over REST or MCP | Per connected account: free plan with one account and no card, then from $10/account | Typed REST, sends included, limits checked on the server before each call | Hosted, 250+ typed tools, sends return a preview to confirm |
| Aimfox | Cloud app running campaigns from the profiles you connect | Per profile: $49 a month for a seat | REST v3, 60 requests a minute | Hosted |
| HeyReach | Cloud app that rotates one campaign across many connected senders | Per sender: $79 a month on Growth, teammates free | API and webhooks on every plan | Hosted, per-workspace URL |
| SalesRobot | Cloud app with a dedicated IP per LinkedIn account | Per LinkedIn account: $59 a month on Basic | REST, including connection requests | Hosted |
| Snov.io | LinkedIn automation from Snov.io’s cloud, sold as a slot next to an email suite | Per LinkedIn slot: $69 a month | REST, no LinkedIn sends | Hosted, sends invitations and messages |
Read the table by job. Where LinkedIn is one channel of a sequence, Reply.io and Snov.io both put it next to email. For campaigns across many LinkedIn accounts from one workspace, Aimfox, HeyReach and SalesRobot are priced per account. Where LinkedIn has to run inside your own product or behind an agent, with a send as one call through an API or an MCP server, GTM API is built for that. Each campaign tool is read against the same eight safety controls on the safest LinkedIn automation tools.
Frequently Asked Questions
How much does Reply.io cost with LinkedIn?
The Multichannel plan includes one LinkedIn account per user and starts at $89 per user a month billed yearly, or $99 billed monthly. On the Email Volume plan LinkedIn is an add-on at $69 a month per account, and the AI SDR plans include 2 to 50 LinkedIn accounts depending on the tier.
Does Reply.io have a free plan?
No. Reply offers a 14-day trial, and the trial’s limits are not published. A $0 API package on agents.reply.io is labelled by Reply as coming soon and illustrative.
What are Reply.io’s LinkedIn limits?
Reply caps each of nine LinkedIn action types per day and per account. It suggests a random daily range of 25 to 35 for most actions and 35 to 50 for messages, or a fixed 30, and any limit can be raised to 100. Counters reset at midnight UTC, and manual and direct sends do not count.
Can the Reply.io API send LinkedIn messages?
Yes. Version 3 of the API has five direct-send endpoints for a connection request, an InMail, a message, a voice message and an AI voice message, plus endpoints to manage LinkedIn accounts and their limits. It allows 100 requests a minute per user.
Does Reply.io have an MCP server?
Yes, hosted at mcp.reply.io with 71 tools for sequences, contacts, the inbox, tasks and Jason AI SDR. It has no tool that sends a LinkedIn message directly, and calls run immediately with no undo, so Reply tells the assistant to confirm sends with the user.
What are the alternatives to Reply.io for LinkedIn?
Aimfox, HeyReach and SalesRobot price LinkedIn campaigns per account, and Snov.io sells LinkedIn as a slot next to its email suite. GTM API, our own product, is an API and MCP server for building LinkedIn into your own product or agent, from $10/account with a free plan.
Sources & Further Reading
- Reply.io, pricing file (last modified 2026-07-30) · LinkedIn outreach · connecting LinkedIn · LinkedIn limits · when LinkedIn steps fail · limits reference · integrations, read 2026-11-03
- Reply.io developer documentation, API introduction · OpenAPI file · MCP overview · MCP tools · MCP agent guide, read 2026-11-03
- Reply.io, agents.reply.io · about · API packages · webhook events, read 2026-11-03
- Related: Safest LinkedIn automation tools · Free LinkedIn automation tools · LinkedIn automation tools list · LinkedIn automation API · LinkedIn automation statistics · HeyReach overview · Snov.io overview
LinkedIn actions as typed API calls.
Connect an account server-side, send a connection request or a message as one endpoint, and read the limits before the call goes out. The same contract runs as an MCP server for your agent. Free plan with one connected account, then from $10/account.
Last updated: November 2026 · Definitions and benchmarks verified at time of publication