Iridium vs. Fintalio
Short answer: these two products do different jobs. Fintalio sends outbound sequences from an agent. Iridium works the inbox those sequences land in. Fintalio's own documentation says its MCP has no inbox read, so if managing DMs is the job, it is the wrong tool. Everything below is from each vendor's own pages, checked 1 September 2026.
The line that decides it
Fintalio's documentation lists what its MCP server leaves out:
"What Fintalio MCP does not expose in v0.0.1: no profile-scraping tool, no feed reader, no post-publishing, no inbox read, no LinkedIn-search MCP tool."
The closest thing is get_contact, which returns the last ten messages for one contact you already name. You cannot ask what came in today, which threads are unanswered, or who you ghosted. If that is the work you wanted help with, stop here. No feature comparison rescues a tool that cannot see the inbox.
Fintalio does not hide this. It is in their own docs. Their product is outbound.
Side by side
| Fintalio | Iridium | |
|---|---|---|
| Price for one person | €69/mo, one plan | $20/mo |
| Trial | No card to start. Length not published. | 7 days, no card |
| Reads your inbox | No | Yes |
| Sends DMs | Yes | Yes, after you approve |
| Published daily caps | 50 messages, 50 connections | 25 outreach sends, 14 invites, 90 invites per rolling 7 days |
| Approval before a send | A confirm=true parameter the calling agent supplies | A separate approve call. No auto-approve mode exists. |
| Sequences | Yes | Shipped disabled on purpose |
| Privacy, terms, security pages | /privacy, /terms, /security all 404 | Published, with subprocessors named individually |
| Stated retention period | None published | Published |
What "approval" means in each product
Both products use the word. They mean different things by it.
Fintalio's launch_sequence takes confirm=true. That flag arrives inside the tool call, and the tool call is written by the agent. The agent confirms its own send. No separate human step is documented. If the model decides to pass the flag, the sequence launches.
In Iridium, drafting and sending are different calls. A draft is written, stored, and does nothing. Approving it is a second call, and it is the only thing that creates a scheduled send. There are four code paths that can create one and all four sit downstream of an explicit approve. There is no auto-approve setting to turn on. Caps are enforced on the server, not suggested in a prompt, so an agent that tries to exceed one gets the send deferred to the next morning rather than fired.
What each vendor publishes about your data
Your LinkedIn inbox holds other people's private messages. Whatever you connect inherits them, so the published policy is part of the product.
Fintalio publishes none. As of 1 September 2026, /privacy, /terms and /security all return 404. There is no stated retention period and no subprocessor list. Their own security post tells readers to "Ask for the specific time-to-purge SLA in writing", which is good advice and is currently advice you would have to take with them.
Iridium publishes a privacy policy and terms. Subprocessors are named individually with what each one does. Discovered profile and post data is purged by a daily job, seven days by default. Deleting your account destroys the LinkedIn session immediately, revokes every session on every device, and erases your personal data within thirty days, reversible during those thirty days if you change your mind. The terms are pinned by a SHA-256 hash of the exact bytes served, recorded against your account. That proves the wording you agreed to, not merely that you clicked.
Neither product is SOC 2 certified. Neither claims to be.
What Fintalio is genuinely good at
Fintalio is a developer-first outbound tool and it is honest about being one. It ships sequence tools, it publishes its limits in a machine-readable plan endpoint rather than burying them, and 50 connection requests a day is a higher ceiling than Iridium allows. If you want an agent that runs outreach campaigns and you are happy assembling the workflow yourself, it is a reasonable buy.
Iridium cannot do that job. Its sequence tools return 501 and are hidden from the tool list, because an enrolled sequence would step around the per-recipient cap and the draft check that every other send passes. That is a deliberate limit, not a roadmap item.
Where Iridium fits
Iridium starts at the inbox. Your agent can sort what arrived, tell you which threads are waiting on you and which ones you left hanging, search message bodies with real operators, summarize a long thread, and draft a reply from the full history. Replies inside an existing thread do not count against the daily cap, because answering someone is not a new connection.
Every outgoing message is a draft first. The activity log is append-only by design and scoped to your account, so you can ask what was sent yesterday and read the exact text back.
It is $20 a month for one LinkedIn account, with a seven-day free trial and no card.
Questions people ask next
Can Fintalio read my LinkedIn inbox?
No. Their documentation lists "no inbox read" among the things v0.0.1 does not expose. The get_contact tool returns the last ten messages for one contact you already name. There is no way to ask what came in today.
What does Fintalio cost compared with Iridium?
Fintalio has one plan at €69 a month with no card required to start. Iridium is $20 a month with a seven-day free trial and no card. Fintalio's plan endpoint also publishes its limits: 50 messages and 50 connections per day.
Is Fintalio's confirm flag a human approval step?
Not as documented. launch_sequence takes confirm=true, and that parameter is supplied by the calling agent in the same tool call. The agent confirms its own send. In Iridium, drafting and approving are different calls and only approval creates a scheduled send.
Does Fintalio publish a privacy policy or terms?
Not as of 1 September 2026. Their /privacy, /terms, /security and /docs paths all return 404, there is no published retention period, and there is no subprocessor list. Their own security post advises readers to "Ask for the specific time-to-purge SLA in writing".
When is Fintalio the better choice?
When you want an agent to run outbound sequences and you are comfortable wiring it up yourself. Fintalio is developer-focused, ships sequence tools, and allows 50 connection requests a day. Iridium ships its sequence tools disabled on purpose, so it cannot do that job.
Why does Iridium ship sequences disabled?
An enrolled sequence would bypass the per-recipient cap and the draft check that every other send passes through. create_sequence and enroll_prospect return 501 and are hidden from the tool list. Bulk templated messaging is also against LinkedIn's terms.
Your LinkedIn inbox, in Claude
7-day free trial. No credit card. Cancel anytime.
Start free → Compare all six