Aimfox Overview
What a seat buys, the weekly limits you set on each profile, and how much of the product you can reach from its API and MCP server.
Aimfox is a web app that runs LinkedIn campaigns from the profiles you connect to it. You pick who to reach from a search, a post, an event or a group. Aimfox then sends connection requests, InMails and messages on a schedule you set, and the replies from every profile land in one inbox. You pay per connected profile, $49 a month for a seat, and a public REST API and a hosted MCP server reach most of the campaign and inbox work.
On this page
What Aimfox is
The homepage title calls it an “AI-Powered LinkedIn Outreach & Lead Generation Platform”, and the hero names the buyers in one line: “Lead-gen agencies, sales teams & GTM experts”. The footer names the company behind it, SocialGrowth LLC FZ. The social proof is a single count, “Trusted by more than 10,000 outreach experts”.
Under the positioning it is campaign software. A campaign holds a list of LinkedIn members, runs from one or more connected profiles, and sends those members connection requests, InMails or messages. Replies from every profile collect in a shared inbox the vendor calls the Unibox. The feature grid on the pricing page adds voice notes, attachments and videos, A/B testing, auto-translation, sending in the target’s time zone, user and company blacklists, labels and reporting.
Every plan carries “Unlimited team members”, so the bill follows the LinkedIn profiles in the workspace and a colleague costs nothing.
How a campaign runs
Six steps take a campaign from a connected profile to a sent message, and the vendor documents each one.
- The profile connects through your browser or with a password. The pricing FAQ offers both: “use our Google Chrome Extension to sync an existing LinkedIn session from your browser with Aimfox. No password required. Alternatively, you can always connect using your credentials.”
- Each profile gets an IP address from Aimfox’s pool, or one you bring. The same page describes the pool twice, as “over 70 countries” in the feature grid and as proxies “from over 60 countries” in the FAQ. “Bring-your-own IPs” is ticked on every plan.
- A list supplies the people. The sources are a LinkedIn search, a Sales Navigator search, post engagers, event attendees, group members or a custom list. Sales Navigator campaigns need “an active Sales Navigator subscription on Linkedin for at least one profile connected to your workspace”.
- Each campaign has one outreach type. The API reference names three:
connectsends connection requests with an optional note,inmailsends InMails, anddripmessages existing first-degree connections, which the app calls an inbound campaign. The note needs a paid LinkedIn plan: “In order to send notes with connection requests, you need to have a Premium or Sales Navigator licence”. - A schedule decides when anything leaves. “All campaign communication, including Connection Notes, Messages, and InMails will be delivered only during the campaign’s working hours or Schedule.” Schedules are set per campaign, with “up to two working slots in a single day”, in one time zone or in each recipient’s own.
- Campaigns on one profile share its budget. “When running multiple active campaigns, Aimfox distributes interactions evenly across campaigns until all leads have been reached.”
Replies come back into the Unibox, and an inbox privacy setting can “Allow access only to conversations generated through Aimfox”.
Aimfox pricing
The billing unit is a seat, and a seat is one connected LinkedIn profile. An individual or a small team buys Outreach seats at $49 a month each. An agency buys a block of 20 seats from $499 a month, adds seats one at a time above that, and gets the onboarding and white-label extras.
| Plan | Billed monthly | Billed yearly | What comes with it |
|---|---|---|---|
| Outreach seat | $49 per seat | $490 per seat | One connected profile, inbound and outbound campaigns, the Unibox, integrations with other tools |
| Agency, first 20 seats | From $499 | From $4,490 | Slack onboarding, white-label options, team collaboration, help moving existing profiles in |
| Agency, each seat above 20 | $20 | $180 | The same features as the block |
The yearly toggle is labelled “up to -25%”, and the yearly prices are shown against struck-through figures of $600 and $6,000. Against twelve monthly payments, which is our arithmetic, the Agency block saves 25% a year ($4,490 against $5,988) and a single seat saves about 17% ($490 against $588).
The trial comes with the seat plan: “On signup, every client gets a 14-day trial of Outreach Seat. For this step you don’t need to add a payment method.” Each account gets one, and when it lapses without a subscription “any created campaigns will be paused until you reactivate your subscription.” No free plan is listed.
One line on the pricing page reads two ways. The Agency card lists “Full whitelabel”, and the comparison table ticks six branding items for that plan, from dashboard branding to a branded knowledge base. The FAQ on the same page answers “We don’t provide a full whitelabel” and adds “A full whitelabel is in the pipeline!” Both readings were live on 15 October 2026.
The limits Aimfox publishes
Aimfox publishes its ceilings per week and per profile: 200 connection requests and 200 message requests a week on a seat, and a lower weekly cap you set on each profile.
- 200 connection requests a week per seat. The pricing table prints “200/week” in the Outreach seat and Agency columns.
- 200 message requests a week per seat. A message request is the help centre’s term for a message “to LinkedIn group members or event attendees”. Messaging sequences are listed as “Unlimited”.
- A weekly cap per profile, from 10 to 200. The help centre lets you set “Connection Requests: 10-200 per week”, with the same range for message requests and InMails, and spreads it into daily numbers by schedule and warm-up state: “This means Aimfox dynamically adjusts daily actions so your account never exceeds the weekly cap.”
- An optional warm-up. Three speeds, “Fast (7 days)”, Medium at 14 days and Slow at 30, each with its own limits that apply while warm-up is on.
- A cooldown when LinkedIn limits an action. The profile “is automatically placed into a Cooldown state for that action”. The connection-request cooldown “resets weekly” and the InMail one “resets monthly”, profile views carry on, and paused work resumes on its own.
The per-profile cap is where the vendor’s own surfaces part ways. The help centre sets it weekly, from 10 to 200. The API accepts connect and inmail values “between 1 and 1000”, recommends 50 to 200 and names no period, and its v3 notes say message_request was removed from the setting. The MCP tool list calls the same setting “daily action limits”. Warm-up differs too: the help centre reaches the full limit in 7, 14 or 30 days, while the API raises it “by 100 every 4 weeks (LOW), 2 weeks (MEDIUM, the default) or week (HIGH)”. A script should read GET /accounts/:account_id/limits and size a campaign on what comes back.
How Aimfox’s published controls sit next to the rest of the field, vendor by vendor, is on the safest LinkedIn automation tools.
LinkedIn’s own invitation ceilings, and the daily pace figures the field works to, are covered with their sources on LinkedIn connection limits.
The Aimfox API
Aimfox has a public REST API at api.aimfox.com, documented at docs.aimfox.com. Version 3 is the recommended one and version 2 is marked deprecated in the documentation’s version switcher. The v3 reference lists 84 requests in 14 groups, authenticated with a bearer key and capped at 60 requests a minute.
Keys come from the workspace settings, and “API keys do not expire but can be deleted at any time.” The key goes in an Authorization: Bearer header. A master key runs the seven routes that assign seats, manage workspaces and their tokens and generate a white-label client token, and a normal key runs the rest. Mixing them up often shows as a 500 error, which the documentation calls “A frequent source of confusion”. The rate limit is “60 requests per minute across all endpoints”, with a 429 above it.
- Campaigns, lists and leads, 52 requests. Campaigns (15), lists (10), leads (11), labels (4), templates (5) and the blacklist (7). A list source “immediately starts collecting the matching LinkedIn profiles” from a search, a post, an event, a group, a Sales Navigator URL or a CRM import from Instantly, Smartlead or EmailBison.
- Messages, 12 requests. List and read threads, start a conversation, send a message, a voice note or a file, mark a thread read, react, edit and delete.
- Accounts, 5 requests. List and read the connected profiles, read and set their limits, and fetch a file through one.
- Analytics and webhooks, 6 requests. Interactions and recent leads, plus webhook management.
- Workspace administration, 9 requests. Seats, workspaces, white-label clients and login tokens, the agency plumbing.
Two details decide how far a script gets. A campaign created over the API starts in the INIT state, and the reference says “the schedule and connection flows will need to be configured separately through the Aimfox dashboard”. Once it is ready, the API can start, pause or archive it by changing its state. And no route sends a single connection request or InMail: those go out only through a campaign of the matching type, while messages, to an existing thread or a new one, can be sent directly. No route connects a new LinkedIn profile either, so that step stays in the app.
One behaviour to know before a bulk script: on Start Conversation, “Adding multiple recipients does not send individual messages to each recipient.” It creates one group conversation with all of them.
Webhooks are marked beta. The documentation lists 17 event types, from account_logged_in and account_logged_out through connect, accepted, message and the reply events to campaign_started and campaign_ended. A failed delivery is retried “up to 6 times”, from one minute after the failure to a day after the previous retry.
The Aimfox MCP server
Aimfox runs a hosted MCP server at https://mcp.aimfox.com, connected with OAuth. Its help article lists 56 tools in 12 groups, describes the server as “a pass-through to the Aimfox API”, and says that using it takes “a valid Aimfox account with an active Subscription to any plan”.
Setup guides cover Claude, ChatGPT, Codex, Raycast and Cursor. In Claude Code it is one command, claude mcp add aimfox https://mcp.aimfox.com --transport http, then /mcp to sign in, and no API key is pasted anywhere in the documented flow.
| Group | Tools | Names |
|---|---|---|
| Account management | 3 | list_accounts, get_account_limits, set_account_limits |
| Custom variables | 3 | get_campaign_custom_variables, get_target_custom_variables, add_custom_variables_to_target |
| Campaign operations | 7 | list_campaigns, get_campaign, create_campaign, update_campaign, add_profile_to_campaign, remove_profile_from_campaign, add_multiple_profiles_to_campaign |
| Lead management | 11 | search_leads, get_lead_details, get_lead_custom_variables, search_leads_facets, get_total_leads_count, add_label_to_lead, remove_label_from_lead, list_lead_notes, create_lead_note, update_lead_note, delete_lead_note |
| Labels | 4 | list_labels, create_label, update_label, delete_label |
| Templates | 5 | list_templates, get_template, create_template, update_template, delete_template |
| Conversations | 9 | list_conversations, get_conversation, get_lead_conversation, start_conversation, send_message, mark_conversation_read, react_to_message, edit_message, delete_message |
| Analytics | 2 | get_campaign_analytics, get_account_analytics |
| Webhooks | 4 | list_webhooks, create_webhook, update_webhook, delete_webhook |
| Blacklist | 6 | list_blacklist, add_to_blacklist, remove_from_blacklist, list_blacklist_companies, add_companies_to_blacklist, remove_company_from_blacklist |
| Token management | 1 | generate_login_token |
| Workspaces | 1 | list_workspaces |
Five tools act on a LinkedIn conversation directly: start_conversation, send_message, react_to_message, edit_message and delete_message. The campaign tools reach LinkedIn one step removed. add_profile_to_campaign puts a member on a campaign’s list and update_campaign changes its state, and the invitations and InMails leave when that campaign runs, inside its schedule and the profile’s weekly cap. No tool sends a connection request or an InMail by itself, and the help article describes no confirmation step before an agent’s message goes out.
The vendor says agents “can access most tools available in our official Docs”. Measured against the v3 reference, the gaps include the ten list routes, voice notes and file uploads, deleting a campaign or exporting its targets, and seat, workspace and client administration. The tool names follow the v2 routes, with add_profile_to_campaign and add_multiple_profiles_to_campaign matching the v2 audience endpoints that v3 replaced with targets. The help article does not say which version the server calls, so that reading rests on the names alone.
The shape of job it fits
Aimfox fits a team or an agency running LinkedIn campaigns across several of its own profiles from one workspace, with one inbox for the replies. The seat price follows the profiles while teammates are free, and the Agency block adds white-label options for client work. The API and the MCP server make the campaign and inbox side scriptable: an agent can load leads into a campaign, start or pause it, read the analytics and answer the conversations.
The edges come from the same design. A campaign’s schedule and flow are built in the dashboard, so a fully scripted setup stops there. Invitations and InMails leave only through campaigns. The per-profile cap is printed three ways across the help centre, the API and the MCP tool list. And the whole API shares 60 requests a minute.
Aimfox alternatives
GTM API is our own product, so it is listed first. The other four are described from their own pages, read on 14 and 15 October 2026, 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, so each account keeps its own session, driven over REST or MCP | Per connected account: free plan with one account and no card, then from $10/account | Typed REST, one contract with the MCP tools, limits checked on the server before each call | Hosted, 250+ typed tools, OAuth or an API key, sends return a preview to confirm |
| 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 generated in the app |
| Linked API | “Each LinkedIn account gets its own full browser in the cloud” | Per seat, one account: $49 a month billed annually, $69 month to month | Workflows over REST, plus an Admin API for per-account limits | Hosted, part of every plan |
| SalesRobot | Cloud app with “dedicated IPs for each LinkedIn account” | Per LinkedIn account: $59 a month on Basic | REST, including Send Connection Request, Quota Setting and Schedule Setting | Hosted at mcp.salesrobot.co, API key |
| Snov.io | LinkedIn automation sold as a slot inside an email suite | Per LinkedIn slot: $69 a month, sold separately from the suite plans | REST API and webhooks | Hosted, sends connection requests, messages and InMails |
Read the table by job. For campaigns across many sender accounts from one workspace, HeyReach and SalesRobot are priced per account the way Aimfox is. Where email leads and LinkedIn rides along, Snov.io sells LinkedIn as a slot inside its suite. Where LinkedIn has to run inside your own product or behind an agent, with an invitation or a message as one call, GTM API and Linked API are built for that.
Frequently Asked Questions
What is Aimfox used for?
Running LinkedIn campaigns from profiles you connect. A campaign takes its people from a LinkedIn search, a Sales Navigator search, post engagers, event attendees, group members or an uploaded list, sends them connection requests, InMails or messages on a per-campaign schedule, and collects every reply in a shared inbox called the Unibox. The vendor names lead-gen agencies, sales teams and GTM experts as its buyers.
How much does Aimfox cost?
An Outreach seat, one connected LinkedIn profile, is $49 a month or $490 a year. The Agency plan starts at $499 a month for 20 seats plus $20 for each seat above that, or $4,490 a year plus $180 per extra seat. Team members are unlimited on every plan, and a 14-day trial of the seat plan needs no payment method.
What are Aimfox’s LinkedIn limits?
The pricing page lists 200 connection requests and 200 message requests a week per seat. The help centre lets you set a lower weekly cap per profile, from 10 to 200, for connection requests, message requests and InMails, and Aimfox spreads it into daily numbers by schedule and warm-up state. Warm-up is optional, at 7, 14 or 30 days. The API accepts 1 to 1,000 for the same setting and recommends 50 to 200, without naming the period.
Does Aimfox have an API?
Yes. A REST API at api.aimfox.com, with v3 recommended and v2 marked deprecated. The v3 reference lists 84 requests in 14 groups covering campaigns, lists, leads, messages, accounts, analytics, webhooks and workspace administration, with a bearer API key that does not expire and a limit of 60 requests a minute. A campaign created over the API still needs its schedule and flow set in the dashboard, and connection requests go out only through campaigns.
Does Aimfox have an MCP server?
Yes. It is hosted at mcp.aimfox.com, connects with OAuth and needs an active subscription to any plan. The help article lists 56 tools in 12 groups, covering accounts and their limits, campaigns, leads, labels, templates, conversations, analytics, webhooks and blacklists. Its tools can start, send, edit and delete messages and add people to campaigns, and none of them sends a connection request by itself.
Do I have to give Aimfox my LinkedIn password?
No. The vendor’s answer is that you can connect through its Chrome extension, which syncs the LinkedIn session already open in your browser with no password, or connect with your credentials if you prefer. Each connected profile then runs on an IP address from Aimfox’s pool or on one you bring.
What are the alternatives to Aimfox?
GTM API is our own product, listed first: a LinkedIn API where each connected account runs in its own cloud browser, invitations and messages are typed REST calls or MCP tools, and limits are checked on the server before every call, with a free plan and then from $10/account. HeyReach and SalesRobot are campaign apps priced per LinkedIn account, like Aimfox. Snov.io sells LinkedIn as a slot inside an email suite, and Linked API runs each account in a cloud browser behind an API and an MCP server.
Sources & Further Reading
- Aimfox, homepage (the positioning line, the stated buyers, the 10,000 count and the company name) · pricing (the plans, the yearly prices, the feature grid and the FAQ answers on passwords, proxies and white-label), read 14 and 15 October 2026
- Aimfox help centre, interaction limits · pacing and multiple campaigns · schedule and timezone · cooldowns · free trial, read 14 and 15 October 2026
- Aimfox, API documentation (the v3 and v2 references, keys, the rate limit, account limits and warm-up, campaign states, list sources and webhooks) · MCP server (the 56 tools and the plan requirement) · MCP with Claude, read 15 October 2026
- HeyReach, pricing · MCP. Linked API, pricing · safety · admin limits. SalesRobot, pricing · homepage · API reference index. Snov.io, pricing · MCP. Read 14 October 2026
- SalesRobot, MCP setup (the hosted URL and API key sign-in), read 15 October 2026
- gtm-api.com, product · pricing · docs: MCP server · connecting a client · smart limits and warm-up · cloud browsers and proxies · billing and plans (our own numbers), read 15 October 2026
- Related: Best LinkedIn automation tools · Best LinkedIn API · LinkedIn MCP server · LinkedIn connection limits · HeyReach overview · Linked API overview · Scaling LinkedIn automation · Safest LinkedIn automation tools
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: October 2026 · Definitions and benchmarks verified at time of publication