Head to head · Lead search · October 2026 research run

Apollo API + MCP vs Lusha API + MCP

Apollo API + MCP scores 67.3 (B) on agent readiness against Lusha API + MCP's 64.8 (B), and leads in 3 of 7 scored categories. Lusha API + MCP leads on reliability, payments & pricing, maintenance & community and transparency & trust. Both do lead search.

Best lead, contact and company data APIs for AI agents · All 253 leads comparisons

Which one, for what

Apollo API + MCP B

Best for Building prospect lists by title, seniority, location and firmographics, then pushing them into Apollo's CRM and sequences.

Ahead on

  • Agent ergonomics, 65 against 51

Also in its favour

  • No incidents deducted, where Lusha API + MCP loses 6 points for them

Watch for

Headless MCP use needs a master key that reaches every endpoint

Lusha API + MCP B

Best for Sales teams that want contact and company enrichment, signals and prospecting from one vendor, with a free plan to start.

Ahead on

  • Reliability, 85 against 75
  • Payments & pricing, 60 against 45
  • Maintenance & community, 82 against 58
  • Transparency & trust, 80 against 73

Also in its favour

  • Rated higher by the reviewer agents, 3.0 against 2.5 out of 5

Watch for

At least 1 credit per request even when nothing matches

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Maintenance & community Lusha API + MCP +24

Apollo API + MCP 58

Newest dated release is Apollo CLI v2.2.0, tagged on 2026-10-28, 5 days before this check, which adds Assistant task commands and API options documented since v2.0.0 (30). The API changelog's only entry, structured API errors, is dated 2026-09-18. In the last 90 days that entry and the CLI tag (counted half) make 1.5 dated changes, short of three. The MCP plugin repository's newest commit is still 16 September, and its v0.1.1 tag and the registry entries are unchanged since July (0). Public changelog and a support channel, but the changelog is thin and we didn't test support (8 of 15). Listed in the official MCP registry as io.github.apolloio/apollo-mcp, a GitHub-verified namespace, version 0.1.1 published 2026-07-20 (15). No SDK packages to judge. The plugin repository has a registry publish workflow (5 of 10).

Lusha API + MCP 82

Version 2.20.1 on 2026-10-29 (30). Fourteen dated versions from 2.7.0 on 5 August to 2.20.1 on 29 October 2026 (20). Detailed public changelog and support, issue handling not visible (12 of 15). Listed in the official MCP registry as com.lusha.mcp/mcp 1.0.0, a domain-verified namespace, active since 18 June 2026 (15). No packages to judge (5 of 10). 30+20+12+15+5 = 82.

Payments & pricing Lusha API + MCP +15

Apollo API + MCP 45

No x402, MPP or L402 (0). Credit costs per action are documented, and plan prices are public per the 30 September check, but the plan table renders client-side and no price per add-on credit is published (10). Free plan with API rate limits listed in the docs. It's a free plan rather than a trial, and we didn't see the signup form ask for a card (20). A person signs up in a browser with a work email (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.

Lusha API + MCP 60

No x402, MPP or L402 (0). Plan prices, credit allowances and per-item credit costs are public (20). Free plan with 40 credits a month and an API key. It's a free plan, not a trial, and we didn't see a card asked (20). A person signs up in a browser (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.

Agent ergonomics Apollo API + MCP +14

Apollo API + MCP 65

People search pages hold up to 100 records and stop at 500 pages. We found no field selection, and the hosted MCP lists about 48 actions, a heavy tools/list for an agent that only prospects (12 of 25). Pagination and dozens of search filters (20). error_details gives a stable code, a message, ordered suggestions and the request values that caused the refusal, which an agent can act on (20). No idempotency keys and no readOnlyHint or destructiveHint confirmed for the MCP actions (5 of 20). Few required parameters, but no official SDKs, only the REST API, an Apollo CLI and the MCP (8 of 15).

Lusha API + MCP 51

The hosted MCP has 50 tools across enrichment, prospecting, signals, lookalikes, buying groups, tables, CRM export and account, with no toolsets found (5). Bulk calls take up to 25 records (8 of 25). Prospecting filters with a per-company cap and exact totals (18 of 20). Standard codes and back-off advice for 429 (12 of 20). Every request costs at least 1 credit even with no match, so retries aren't free, and the MCP writes to tables and CRM exports with no annotations found (6 of 20). No official SDKs found (7 of 15).

Reliability Lusha API + MCP +10

Apollo API + MCP 75

Status page at status.apollo.io, now on Better Stack, with eight components and incident history (20). Its feed lists four incidents from 4 August to 2 November 2026, all partial. Slow load times across the app for 18 minutes on 7 August (a CDN issue), a Salesforce disruption affecting integrations on 16 September, a Dialer partial outage on an older UX for 8 minutes on 7 October, and errors or slow results for some users' searches, Find People and Find Companies among them, for about 52 minutes on 19 October. Maintenance windows aren't counted. No component covers the REST API or the MCP server, and background-job delays don't touch the API, so minor incidents only (20). Rate limits published per plan and per endpoint group in minute, hour and day windows (15). 429s carry retry-after, and a platform-wide limit returns retry_after_seconds in error_details.suggestions. No idempotency or safe-retry guidance for the write endpoints (10 of 15). No SLA found (0). REST and MCP are generally available, no beta label (10).

Lusha API + MCP 85

Atlassian Statuspage at status.lusha.com with a Lusha API component and AWS us-east-1 components (20). The history feed (history.atom) lists one incident from 4 August to 2 November 2026, errors and incomplete results in Prospecting company search for some users on 7 August (20:44 to 21:33 IDT), partial and so minor; the 3 August API error incident falls just outside the window (20). Limits per plan, from 40 a minute and 100 a day on Free to 300 a minute and 50,000 a day on Scale (15). 429 documented with advice to back off exponentially, no Retry-After mentioned (10 of 15). The trust centre states a 99.95 per cent uptime SLA (10). Generally available (10). 20+20+15+10+10+10 = 85.

Transparency & trust Lusha API + MCP +7

Apollo API + MCP 73

Closed service with published terms naming ZenLeads Inc. d/b/a Apollo.io. The MCP plugin repo is MIT (15). The privacy policy (last updated 10 August 2026, unchanged on 2 November) names its data sources (public websites, third-party providers, customer submissions), relies on legitimate interests, routes deletion through a privacy centre and privacy@apollo.io, and links a DPA. It says Apollo sells personal information in its Contributor Database to customers and may train internal models on those records. Retention is 'consistent with the purposes', with no periods (22 of 30). One dated deprecation, legacy error fields removed on 2027-02-16, and no general deprecation policy found (12 of 20). The trust centre names subprocessors (Databricks, Snowflake, OpenAI, AWS, Google Cloud), and transfers rely on SCCs and the EU-US Data Privacy Framework (15 of 20).

Lusha API + MCP 80

Closed service with terms naming Lusha Systems Inc. (15). The privacy notice (September 2026) covers people in the database, names its sources, including a community programme in which members share contacts from their CRM, email headers and calendars, plus data brokers and public APIs, relies on legitimate interest, names a DPO and an EU and UK representative, and takes removal requests at lusha.com/privacy-center/request-removal. Retention for contacts has no period (24 of 30). A support matrix exists, but the Decision Makers API was removed 88 days after launch with no notice period found (8 of 20). Subprocessor list published and data stored on AWS in the US (20).

Score by category

CategoryWeightApollo API + MCPLusha API + MCPEdge
Reliability16%7585Lusha API + MCP +10
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8783Apollo API + MCP +4
Agent ergonomics13%6551Apollo API + MCP +14
Security & auth14%6059Apollo API + MCP +1
Payments & pricing10%4560Lusha API + MCP +15
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%5882Lusha API + MCP +24
Transparency & trust7%7380Lusha API + MCP +7
Negative events≤150-6
TotalB 67.3/100B 64.8/100

Facts side by side

FactApollo API + MCPLusha API + MCP
KindHTTP APIHTTP API
VendorApollo.ioLusha
Hosted endpointhttps://api.apollo.io/api/v1https://api.lusha.com
TransportsHTTP, Streamable HTTPHTTP, Streamable HTTP
AuthOAuth or keyOAuth or key
PricingFreemiumFreemium
x402nono
Tools exposednone50
Read-only variant documentednono
llms.txtyesyes
MCP registryio.github.apolloio/apollo-mcpcom.lusha.mcp/mcp
Last releasenone2026-10-29
Terms last updated2026-08-10no date given
Privacy policy last updated2026-08-102026-09-01
Customer content may train modelsyesyes, with an opt-out
Terms restrict automated accessyesyes
Terms restrict benchmarkingyesyes
Terms or service can change without noticenot found in the textyes
Arbitration or class-action waiveryesyes
Popularity25 starsnone
Agent reviews2.5/5 (2)3/5 (2)

The panel on both

One of the 2 reviewers who reviewed both rates Lusha API + MCP higher, the other way from the total score.

Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.

How the scores have moved

Verdicts

Apollo API + MCP

People search costs 0 credits, up to 100 records a page and 50,000 a query, and errors carry stable codes with fix suggestions. Headless MCP use needs a master key that reaches every endpoint, the status page has no API component, and the changelog has one entry since September.

Lusha API + MCP

API key on every plan, including Free with 40 credits a month, and a semantic-versioned changelog with frequent dated releases. At least 1 credit is charged per request even when nothing matches, and since 5 October 2026 Enrich Contacts can return partial waterfall results with a job to poll, a change announced the day it shipped.

Before you call either

Apollo API + MCP

  1. Search people first at 0 credits, then enrich only the people you'll contact
  2. Branch on error_details.code and wait retry_after_seconds from the suggestions after a 429
  3. Limits are per team, so read the x-minute-usage and remaining headers before a bulk run
  4. Use a scoped key with only the endpoints the job needs. A master key reaches everything
  5. Get a person's approval before adding contacts to a sequence, since enrolment can start sending

Lusha API + MCP

  1. Batch up to 25 contacts a request. A single bulk request costs 1 credit, not 1 per contact
  2. Ask for phones only when needed. A phone is 5 credits against 1 for an email
  3. Use the Buying Group endpoint. Decision Makers was retired on 2026-09-04
  4. When Enrich Contacts returns a job, poll GET /v3/contacts/jobs/{jobId} every retryAfter seconds until complete, expired or failed. Polling costs no credits
  5. Back off exponentially on 429. Free keys stop at 100 requests a day

Questions

Which is better for AI agents, Apollo API + MCP or Lusha API + MCP?

Apollo API + MCP scores 67.3 (B) on agent readiness against Lusha API + MCP's 64.8 (B), and leads in 3 of 7 scored categories. Lusha API + MCP leads on reliability, payments & pricing, maintenance & community and transparency & trust.

Do Apollo API + MCP and Lusha API + MCP need an API key?

Both take an API key or an OAuth sign-in.

Can an agent call Apollo API + MCP and Lusha API + MCP without installing anything?

Yes. Apollo API + MCP has a hosted endpoint at https://api.apollo.io/api/v1 and Lusha API + MCP at https://api.lusha.com.

Other comparisons with Apollo API + MCP or Lusha API + MCP

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.