TL;DR

• BeReach sells an AI outreach agent with an API around it: campaigns, a contacts CRM, drafted DMs you approve, scheduled sends. Curviate, a LinkedIn API, CLI, MCP server and TypeScript SDK for AI agents, gives raw LinkedIn actions to your own agent (Claude, ChatGPT, Claude Code, Codex, Cursor) or your own software. If your agent should decide each action, Curviate is the BeReach alternative.
• BeReach's public OpenAPI file (version 2.4.0) has 103 operations; Curviate's has 159. Curviate has 197 query parameters to BeReach's 59, and 869 request-body fields to 450. BeReach's SDK README lists 140 operations, but the full reference is behind sign-in.
• Recruiter, job posting management, groups, notifications, InMail and webhook management are only in Curviate's API.
• BeReach costs EUR 99 a month for a 2-account workspace (from EUR 79 billed yearly) and runs on a credit pool. Curviate costs EUR 20 per account a month (EUR 16 billed annually), excl. VAT, and meters no actions.

If you are looking for a BeReach alternative because your own AI agent should work LinkedIn through an API, CLI or MCP server, this page is for you, and it goes deep on the API. I build Curviate. On October 2, 2026 I pulled BeReach's public OpenAPI file from api.bereach.ai (version 2.4.0) and read its pricing and docs pages next to ours.

Should you choose BeReach or Curviate?

Pick Curviate when your own agent or software decides each LinkedIn action. Pick BeReach when you want its agent to decide and wait for your approval.

BeReach suits you if you want a finished outreach agent that finds and scores prospects, drafts each first message and waits for your OK. It also has 7 public endpoints for people, company and post data without connecting a LinkedIn account, which Curviate does not offer.

Curviate suits you if your agent or software should run every LinkedIn action with no vendor workflow in between. It covers what BeReach's OpenAPI file does not list: Recruiter, creating and publishing job postings, reading applicants, groups, notifications, InMail and a company page inbox you can reply from. You get an agent-oriented CLI next to the API, MCP server and SDK. If you embed LinkedIn in your own product, you connect your users' accounts by API, set a safety policy per account and receive webhooks. And you pay a flat price per account, with no credit pool that stops work when it runs out.

How do Curviate and BeReach compare at a glance?

Curviate has the larger public API, the lower price per account and no credit pool. Sources: BeReach's pricing page, its docs and OpenAPI file, and Curviate's pricing page and OpenAPI document, all as of October 2, 2026. "Not listed" means I did not find it there, which does not prove the product lacks it.

Is BeReach an agent or an API for your agent?

BeReach is an agent first. Its llms.txt says it "drafts personalized outreach you approve", and its list of things it does not do includes "No automated follow-up sequences". The API exposes that product. You create campaigns, upsert contacts and log their activities, create draft DMs, approve or reject them in batches, schedule them, store context entries for the agent, and read an agent session snapshot. If approval-gated outreach is what you want, BeReach has made the decisions for you.

Curviate's API gives your agent LinkedIn actions and stops there. There are no campaigns, CRM or drafts on top. The workflow guidance lives in open skills you can read, fork and change: the Curviate plugin (MIT, 9 skills) and my own linkedin-plugin (MIT, 10 skills for posts, comments, DMs and the inbox).

How does the BeReach API compare to Curviate's?

Curviate's public API is larger on every count below: 159 operations against 103 in BeReach's public OpenAPI file (2.4.0). I counted both files with a script. An operation is a path plus an HTTP method. Fields are every property in the JSON schemas after resolving references, with each union branch counted, success responses only. BeReach's SDK README lists 140 operations and its full reference is behind sign-in, so the public file is not all of BeReach.

• Query parameters: 197 against 59. I left out path parameters, because Curviate repeats the account ID in every account-scoped path (259 against 7 with them).
• Request-body fields: 869 against 450.
• Response fields: 4,903 against 3,019, a median of 22 against 18 per operation.
• Authentication: a bearer token on both.

The table sorts every operation by what it acts on.

Both save you repeat reads, in different places. BeReach's profile visit returns cached when the result is "served from a local cache rather than a fresh LinkedIn API call", and charges 0 credits for it. Its docs do not say whether that also spares the daily visit cap. Its public lane spends "none of an account's action budget", at one credit per public read. On Curviate, a profile read again within the 12-hour default, and any stored chat or message, comes from your workspace's store, with no LinkedIn request and no action budget spent (caching guide).

Which LinkedIn actions are not in BeReach's API?

These seven are missing from BeReach's public OpenAPI file (2.4.0):

• Recruiter, creating job postings, applicants and groups. "Recruiter" appears only in a field description. BeReach does search job postings, and "Group" appears only as a Sales Navigator filter for group membership.
• Notifications. Conversations carry a notification status field, but there is no notifications endpoint.
• Webhook management. One setting takes a webhook URL for two events, connection accepted and conversation updated. Nothing creates, lists or tests webhooks, though its pricing page lists "API and webhooks". Curviate's API manages webhooks with 19 delivered event types.
• Publishing a post, withdrawing or declining an invitation. The file has edit post and accept invitation, and its own tag text and post limits mention publishing. BeReach's SDK README lists publishing, declining and withdrawing, so these may exist in the product and just be missing from the spec.
• InMail, endorsements, editing or deleting a message, sending attachments.
• Connecting an account by API. BeReach's docs have you paste your li_at session cookie into its app. On Curviate, POST /v1/auth/intent and its checkpoint endpoints let your own UI connect your users' accounts with a login or a cookie (custom authentication).
• A safety policy you can write. BeReach reports quota status and documents safeguards that "You can't turn them off". Curviate exposes a per-account safety policy you read and edit, plus a log of limit hits.

Does BeReach have a CLI like Curviate's?

BeReach ships a TypeScript SDK, and I could not find a CLI: its npm package installs no command, and bereach-cli returns 404. Curviate's CLI is built for agents that have a terminal. It prints JSON when piped, has stable exit codes, and takes --fields, plus --preview on writes.

# A search is a read, so it just runs
curviate search people --keywords "AI engineer" --account acc_1 --limit 10 --json
# Preview the invitation, nothing is sent
curviate connect "$SOME_ID" --account acc_1 --note "Hi, I'd love to connect." --preview

The same actions are on the API, the MCP server and the SDK, on one key. On npm the gap is wide. In the week of September 24 to 30, 2026, @curviate/cli had 766 downloads and @curviate/sdk 504; bereach had 26 (counts include CI).

How much does BeReach cost compared to Curviate?

BeReach bills per workspace, in EUR before tax. Pro is EUR 99 a month for 2 LinkedIn accounts (EUR 89 quarterly, EUR 79 billed yearly). Max is EUR 199 for 3 (179, 159), Max+ EUR 299 for 5 (269, 239). Usage runs on credits, "one credit, one action", for profile reads, invitations, messages and search pages. Reading your inbox and feed and talking to the agent are free. When a plan's monthly pool runs out, work stops until it refills.

Per month, monthly billing first, yearly second:

• 1 account: BeReach Pro EUR 99 or 79, since its smallest paid plan covers two. Curviate EUR 20 or 16.
• 2 accounts: BeReach Pro EUR 99 or 79. Curviate EUR 40 or 32.
• 5 accounts: BeReach Max+ EUR 299 or 239. Curviate EUR 100 or 80.
• 10 accounts: BeReach prices anything above 5 accounts on request. Curviate EUR 200 or 160.

BeReach's price includes its own AI model. With Curviate you bring the agent you already run (Claude, ChatGPT, Codex), on its own subscription or API tokens.

Is Curviate a BeReach alternative for your own agent?

Yes, when your own agent should run the workflow. BeReach's own agent proposes each message and waits for approval. With Curviate the workflow lives in your skills, and your agent calls the LinkedIn actions underneath. The 3-day trial needs no card, so connect an account and hand your agent the API, CLI, MCP or SDK.

Not affiliated with LinkedIn Corporation. BeReach prices and features above are as published on its pages on October 2, 2026.