Pick your play.
Put LinkedIn on autopilot.
Curviate turns 120+ LinkedIn actions into something your team can actually run, through an API, a CLI, an MCP server or a TypeScript SDK. Whatever your role, the work below runs on actions that exist today. Find yours and start in minutes.
Give your agent hands on LinkedIn.
You build the judgment; Curviate provides the hands: 120+ typed actions your model can call to search, read, message, invite, publish and recruit. Structured errors and standard RateLimit headers mean your agent branches on failure and paces itself instead of guessing, so a run you kick off at midnight is still sane at 6am.
search.people()streamed as NDJSONtriage()score against your criteriainvites.send()note previewed firstawait webhookconnection.acceptedmessages.open()reply with contextThe TypeScript SDK inside your agent's code, the CLI inside Claude Code or Codex loops, the MCP server for chat-first agents. One API key works across all of them.
Drop LinkedIn into the pipeline you already run.
Curviate is the LinkedIn arm of the loop you run in Clay, n8n or your own scripts. Lists come in, enriched outreach goes out, events flow back; no browser bot to babysit and no release that silently breaks your flow. Sales Navigator search and lead lists are first-class actions, not screen-scrapes.
Stop maintaining a headless Chrome that snaps every time LinkedIn ships a UI tweak. A versioned, documented contract means the automation you wrote in January still runs in December.
The REST API from your workflow tool, webhooks for the return path. 20+ event types cover the loop's feedback edge.
Walk in to a pipeline that already did the boring part.
Your saved Sales Navigator searches re-ran overnight. New matches are already in the right lists, replies are sorted, and follow-ups are drafted and waiting for your yes. You spend your morning talking to people, not clicking through search filters.
No code required: you drive it in plain language through Claude. Power users can wire the same actions into Claude Code or Codex for fully hands-off runs, but you never have to.
MCP in Claude for the review-and-approve style; the API for the parts you want fully scripted. The premium surface most tools ignore is where Curviate is deepest: 30+ actions dedicated to Sales Navigator and Recruiter.
Spend your day on candidates, not data entry.
Sourcing to first call is where the hours go: searching, saving keepers, moving records, keeping the ATS honest. Curviate does the moving so you do the judging. Outreach still reads like you wrote it, because you (or your agent, under your review) did.
Recruiter is Curviate's single deepest action group at 23 actions: hiring projects, pipelines, job postings, Recruiter search and messaging. Non-coders run it from Claude; power users script the whole requisition in Claude Code or Codex.
MCP in Claude for recruiters who do not code; the API for ATS integrations. Read the pipeline over the API and your system of record stays in sync automatically.
Run your LinkedIn presence like a newsroom.
Publish across personal profiles and company pages, answer every comment from one queue, and watch engagement without opening a single tab. Schedule a week of content, invite the people who actually engaged, and keep the page inbox moving, all as actions, all from where you already work.
Your calendar lives in a spreadsheet and your engagement lives in ten browser tabs. Bring both into one loop: scheduled from cron or the API, replied to from a single queue.
We shipped webhooks for every state change on the platform: here's the 3-minute teardown of how our own team wired them into Slack.
The CLI for scheduled jobs, the API for your content tooling, MCP in Claude for drafting and replying in plain language. Same seat, same token as everything above.
Questions, answered
How fast can I be live?
Minutes. Sign up, connect a LinkedIn account, and make your first action, whether that is a call from the SDK, a command in the CLI, or a message sent through Claude over the MCP connector. There is no partner application, no review cycle and no sales gate between you and your first result.
Will automating LinkedIn get my account restricted?
You operate your own account, and Curviate is built to keep that account healthy: actions run at human pace, standard RateLimit headers expose exactly how much headroom you have, and new seats warm up gradually rather than firing at full volume on day one. The full approach, with the specific limits we respect, is on the safety & compliance page.
I don't write code. Can I really run this?
Yes. Add the Curviate MCP connector to Claude, ChatGPT or Cursor (that is pasting one URL) and you operate LinkedIn in plain language: “find heads of RevOps in Berlin and draft intros for me to approve.” The 120+ actions appear as tools your assistant can call, scoped to the account you connected. Developers get more surface with the API, SDK and CLI, but a seller or recruiter with Claude is fully operational.
Can one workspace serve different roles at once?
Yes. Seats are per LinkedIn account, and one API key operates all of them. An agency can run a Sales seat for outreach and a Recruiting seat for sourcing side by side, each scoped to its own LinkedIn identity, with webhooks fanning events to different systems.
Which interface should my team start with?
Non-technical roles: MCP in Claude. Engineers embedding LinkedIn in a product: the TypeScript SDK. Ops and agent loops in the terminal: the CLI. Workflow tools like n8n: the REST API plus webhooks. All four are views over the same 120+ actions, so a mixed team shares one platform.
What happens when LinkedIn changes something under the hood?
That is our problem, not yours. And it is the whole reason to use an API instead of a browser bot. When LinkedIn shifts, we absorb it behind the same typed actions and versioned surface, so your integration keeps running. Breaking changes are versioned and announced; your code does not silently start failing after a UI redesign.
Every workflow above runs on rows in the actions catalogue, with webhooks closing the loop; seat pricing is on the pricing page.