API & MCP
The REST API is for the systems you build and maintain. MCP is for the AI assistant you already talk to. Both run on the same lead database, the same enrichment, the same sequences and the same credit balance as the app.
Which door
Pick the API when a program needs to call Leadspicker on a schedule or from inside your product. Pick MCP when a person wants to get something done without leaving the tool they are typing in. Many teams use both.
| REST API | MCP server | |
|---|---|---|
| Who calls it | Your backend, your CRM, a cron job, an n8n or Make scenario, anything that speaks HTTP. | A person in Claude Code, Codex, OpenCode, Cursor, Grok Bot or any other MCP-capable assistant. |
| How you sign in | An API key you create in the app, sent as X-API-Key. Revoke it from the same page. | OAuth with your normal Leadspicker login. The assistant only ever sees your own account. |
| What you write | HTTP requests against a typed OpenAPI schema. Generate a client in your language from it. | Plain language. The assistant picks the tool, fills the parameters and reads the result back. |
| What it reaches | The app's surface: lists, contacts, enrichment, sequences and steps, replies, routines, exclusion lists, webhooks, CRM sync, team. | Most of the same surface, through dedicated tools: finding, enriching, lists, sequences and steps, replies in the Unified Inbox, sending a message under your name, routines, webhooks. Tools that send messages or start paid work in a list, such as imports and enrichment, are flagged as destructive, so a client that confirms such calls asks you first. |
| Keeping up | The API changelog in the app and its public RSS feed announce every change, breaking ones with an effective date. | Tools update on the server. Re-run the installer to refresh the skills it copied to your machine. |
| Plans | Growth, Scale and Enterprise. | Every plan, Explorer included. |
REST API
Create a key, read the interactive docs, make a call. The schema is public, so you can generate a client before you even sign up.
https://app.leadspicker.com/app/sb/api/X-API-Key: <your key>. Create and revoke keys under User → Integrations → API Keys.# 1. Create a list for this week's product signups curl -X POST https://app.leadspicker.com/app/sb/api/lists \ -H "X-API-Key: $LEADSPICKER_API_KEY" \ -H "Content-Type: application/json" \ -d '{"name": "Signups · week 43", "timezone": "Europe/Prague"}' → 201 {"id": 48213, "name": "Signups · week 43", ...} # 2. Push the contacts straight from your product (project_id = the list id) curl -X POST https://app.leadspicker.com/app/sb/api/persons/bulk \ -H "X-API-Key: $LEADSPICKER_API_KEY" \ -H "Content-Type: application/json" \ -d '{"project_id": 48213, "persons": [ {"first_name": "Jana", "last_name": "Nováková", "email": "jana@acme.io", "company_name": "Acme", "company_website": "acme.io", "position": "Head of Sales"} ]}' # 3. Hear about replies and bounces in your own system curl -X POST https://app.leadspicker.com/app/sb/api/webhooks \ -H "X-API-Key: $LEADSPICKER_API_KEY" \ -H "Content-Type: application/json" \ -d '{"name": "Replies → CRM", "url": "https://hooks.example.com/leadspicker", "features": ["email_reply", "linkedin_reply", "email_bounced"], "project_ids": [48213], "fire_test_payload": true}'
MCP server
Leadspicker MCP is a remote server at https://app.leadspicker.com/mcp. Your assistant authenticates against your own account over OAuth, and the platform shows up as tools it can call: search the lead database, build and enrich lists, draft sequences, ask what a run will cost.
The installer finds every supported AI tool on your machine (Claude Code, Codex, OpenCode, Cursor), registers the server in each one, adds the assistant skills and starts the login where the tool allows it (Codex, OpenCode); in Claude Code you finish with /mcp, in Cursor under Settings → Tools & MCP. If Grok Bot is installed, it prints the steps to connect it. Prefer to do it by hand? Each tool is one command or one config entry, and any other MCP client connects to the same URL through its own “add a remote server” flow.
# macOS / Linux — run in your terminal $ curl -fsSL https://app.leadspicker.com/install.sh | bash # Windows — run in PowerShell > irm https://app.leadspicker.com/install.ps1 | iex
/mcp to finish; in Cursor, open Settings → Tools & MCP → leadspicker → Connect. If Grok Bot is installed, the installer prints the steps to connect it.$ claude mcp add --transport http --scope user leadspicker https://app.leadspicker.com/mcp
/mcp inside Claude Code to finish authentication. Works in the Claude Code CLI, the desktop app and the IDE extensions.$ codex mcp add leadspicker --url https://app.leadspicker.com/mcp $ codex mcp login leadspicker
$ opencode mcp add → remote server, name: leadspicker, URL: https://app.leadspicker.com/mcp $ opencode mcp auth leadspicker
# ~/.cursor/mcp.json (Windows: %USERPROFILE%\.cursor\mcp.json), next to any servers already there
{ "mcpServers": { "leadspicker": { "url": "https://app.leadspicker.com/mcp" } } }
~/.agents/skills, where it puts them.# Add a remote (streamable HTTP) MCP server in your client's settings URL https://app.leadspicker.com/mcp Auth OAuth 2.0 — the client discovers it from the server, log in with your Leadspicker account
https://app.leadspicker.com/cursor/mcp and sign in when the browser opens.What you can reach
Each tile names the API operations and the MCP tools behind one job. The docs list every parameter; this is the map.
Search 70M+ companies and 500M+ people by industry, size, revenue, location, role and seniority, or by similarity to a company you already win with. Count before you import.
Buying signals, job ads with the reason for hiring, funding rounds, exact financials, executive changes, technology, e-shops and podcasts.
Create lists, push contacts in bulk from your product or CRM, read them back with filters and labels, copy them between lists.
Verified emails, phone numbers, LinkedIn and company data, website summaries, and AI columns that classify, score or write. Quote the cost before you run.
Create a sequence, add email and LinkedIn steps with follow-ups, connect a list onto it, read stats and the send forecast.
Every reply from every outreach account with its sentiment: positive, maybe, not interested, out of office, bounced. Mark, archive, export, answer, or clone the repliers into a new list.
Scheduled scrapers that keep a list topped up from LinkedIn searches, posts, job postings or job changes, and signal routines that watch for buying signals.
Webhooks for replies, sends and bounces. Native two-way sync with HubSpot, Pipedrive, Attio, Salesforce, Zoho CRM, Dynamics 365, Raynet and Daktela. Team members, exclusion lists, API keys.
Buy the domains and mailboxes an outreach sequence sends from, and start the subscription. The order is assembled over the API; the customer pays it on a checkout link and the mailboxes connect themselves once they are set up.
Plans
Access is a plan feature; the work itself is priced in credits, and a call over the API or MCP costs exactly what it costs in the app. One credit is one cent in your billing currency, US dollar or euro.
| Included | Explorer | Growth | Scale | Enterprise |
|---|---|---|---|---|
| MCP access | ✓ | ✓ | ✓ | ✓ |
| CRM and other integrations | ✓ | ✓ | ✓ | ✓ |
| REST API access | – | ✓ | ✓ | ✓ |
| Webhooks | – | ✓ | ✓ | ✓ |
The other direction
Building on Leadspicker also means plugging your own sources in. If a provider is not built in, you bring it, and if the data is not public at all, you can still target over it.
Add a column that calls your own endpoint for every contact, with the contact's fields as variables, and keeps the answer. Product usage, account history, an internal scoring service: it becomes a filterable column like any other.
Connect a remote MCP server, your own or an n8n MCP trigger, and the assistant can call it alongside Leadspicker's tools. Segments your competitors cannot buy, because the data was never for sale.
Run AI columns on models from your own provider account. Those columns are billed by that provider, not in credits, and the keys are stored encrypted.
FAQ
MCP is included on every plan, Explorer included. The REST API is on Growth, Scale and Enterprise, and webhooks from Growth up. Metered work costs the same credits either way.
No. Calls are free. Enrichment, AI columns, lead-database imports and routines cost credits, exactly as they do in the app, from the same balance. One credit is one cent in your billing currency, US dollar or euro, and both doors can quote a run before you start it.
No. Your assistant logs in over OAuth with your normal Leadspicker login, so there is nothing to generate, store or rotate. API keys are only for the REST API, and you manage them under User → Integrations → API Keys.
The OpenAPI 3 schema is public, so you can generate a typed client for your language with the generator you already use. The interactive docs let you try every operation in the browser first.
Every new endpoint or field, every changed response and every breaking change is published on the API changelog page in the app, with the effective date for anything that breaks. Subscribe to its public RSS feed, which needs no sign-in, to hear about changes before you upgrade an integration.
750 reads and 150 writes per minute, and 600,000 reads and 60,000 writes per day, per user. Over the limit you get a 429 and can retry after a short wait. If an integration needs more, talk to us.
Yes, through their HTTP modules and webhook triggers: any tool that can send an HTTP request with a header and receive a webhook works with the API. The in-app connectors can also take an n8n MCP trigger as a data source for the assistant.
Yes, if you let it. The server has a send tool for email, LinkedIn messages and InMail, and Unified Inbox tools for reading and answering replies, so the assistant can send under your name. The send tool is flagged as destructive, so a client that confirms such calls asks you first, and the assistant is instructed to show you the final text and send only once you confirm it. It reads and changes only your own account. Sequences can be created and edited over MCP too, and their stats read back.
Create a key under User → Integrations → API Keys, open the docs, and create your first list from the browser.
Run the installer, log in when it asks, then ask your assistant for companies that look like your best customer.
Start for free and try both, or book a demo and we will walk through your integration with you.