INTERFACES

One engine.
Four ways in.

Every Curviate interface talks to the same LinkedIn engine: the same 120+ actions, the same per-account budget, the same caching. Pick the one that matches how you work, or use all four on one seat.

Get startedRead the docs

REST API

/v1 · HTTPS · OpenAPI spec

One Bearer token and an HTTP client. Typed JSON in, typed JSON out, with 20+ webhook event types pushing state changes back to you instead of making you poll.

Best forBackends, workflow platforms, and anything that can make an HTTP request.
Open the REST API

Command line

npm i @curviate/cli

The fastest way to see the engine work. Connect an account, run any action, pipe the JSON into whatever comes next. No project scaffolding, no credentials in code.

Best forFirst runs, one-off jobs, cron, and scripting against a live account.
Open the CLI

MCP server

Agent-native interface

Expose the action catalogue to an agent as tools it can call directly. The agent gets descriptions and typed arguments; you keep the budget guards and audit trail.

Best forClaude, Cursor, and any agent runtime that speaks MCP.
Open the MCP server

TypeScript SDK

npm i @curviate/sdk

Every action as a typed method, with editor autocomplete, typed errors, and retry handling built in. The API surface without hand-writing request shapes.

Best forTypeScript and Node products where LinkedIn is a core dependency.
Open the SDK

All four are included in one subscription. There is no interface tier. See pricing · Browse the 120+ actions