Head to head · Lead search · October 2026 research run

Enrich Layer API + MCP vs Lusha API + MCP

Lusha API + MCP scores 64.8 (B) on agent readiness against Enrich Layer API + MCP's 61.2 (C), and leads in 5 of 7 scored categories. Enrich Layer API + MCP leads on agent ergonomics. Both do lead search.

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

Which one, for what

Enrich Layer API + MCP C

Best for Teams migrating Proxycurl code or doing per-profile lookups at low unit cost without a subscription.

Ahead on

  • Agent ergonomics, 68 against 51

Also in its favour

  • Runs on your own machine
  • Free to start without a card
  • No incidents deducted, where Lusha API + MCP loses 6 points for them

Watch for

Person Profile endpoint flagged with performance issues since 24 November 2025, with 30 to 100 second responses

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 77
  • Security & auth, 59 against 40
  • Maintenance & community, 82 against 26
  • Transparency & trust, 80 against 59

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 +56

Enrich Layer API + MCP 26

Newest MCP release 0.3.0, tagged on 12 June and published to npm on 19 June 2026 per the 1 October check, 138 days before this check (10). The last commits, on 10 and 11 August 2026, haven't been released. No release or dated changelog entry found from 6 August to 4 November (0). Release dates of the enrichlayer-cli npm package couldn't be read. Four merged pull requests since March 2026 and no public changelog. We couldn't see issue replies from git (8 of 25). Not in the official MCP registry and no official SDKs found (0). CI runs build, tests and an OpenAPI conformance check, and dependencies are recent (8 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.

Transparency & trust Lusha API + MCP +21

Enrich Layer API + MCP 59

The MCP server is MIT, the API is closed with terms (9 June 2025) naming Vertical Int, Inc. (Wyoming) (18 of 30). The privacy policy (9 June 2025) covers people in its databases, relies on legitimate interests, names sources including professional networking platforms and data brokers, and gives retention criteria without periods. The trust centre adds a 45-day deletion process, but its sub-processor list (Stripe, Cloudflare, Sentry, Intercom, OVH, Novu, Google Analytics, Anthropic) doesn't match the policy's (Google, PostHog, Intercom). A DPA is available on request (15 of 30). A Proxycurl transition guide maps old paths to new, and no deprecation policy found (5 of 20). Sub-processors listed with US data locations. The MCP's Sentry error reporting is off unless SENTRY_DSN is set and the README says so (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).

Security & auth Lusha API + MCP +19

Enrich Layer API + MCP 40

One secret key per user, sent as a bearer token. We found no scopes or key rotation docs. The hosted MCP server takes the same key at an OAuth consent screen (15 of 30). The API only reads, and the MCP marks all 25 tools read-only (18 of 20). Profiles carry free text written by the people they describe, and we found no prompt-injection guidance (2 of 15). A free credit-balance endpoint and nothing more for per-call visibility (5 of 15). No security.txt, disclosure policy, bug bounty or certification. The trust centre covers privacy rights and sub-processors only, and the privacy policy says SOC 2 is under consideration. OSV lists no advisory (0 of 20).

Lusha API + MCP 59

REST takes an api_key header. Every user gets a key, admins can mint more and cap each one's monthly credits, and a key a user makes for themselves has no cap of its own. OAuth for the MCP in Claude, ChatGPT and Codex, x-api-key elsewhere. No endpoint scopes found (22 of 30). Credit caps limit damage, but the MCP isn't read-only and writes to workspace tables and CRM exports (8 of 20). Signals and conversation data carry some free text, no injection guidance found (5 of 15). Usage endpoint, no per-call log found (8 of 15). SOC 2 Type II and five ISO certifications claimed in the trust centre, ISO 27701 named in the privacy notice, security.txt valid (Expires 1 May 2027, read on 2 November), no bug bounty found (16 of 20).

Agent ergonomics Enrich Layer API + MCP +17

Enrich Layer API + MCP 68

25 MCP tools, all compact, no toolsets. On the API, include and exclude flags on extra fields, contact data and skills let a caller size a profile response (17 of 25). next_token pagination on person and company search and filters (17 of 20). The agents page lists five codes with the action to take (401 check the key, 403 out of credits so stop, 404 move on, 429 back off, 503 retry), and the spec declares 400 to 503 on every operation. Error bodies carry only a status and a message, with no error code of their own or field-level detail, so the line is partly met and keeps its earlier 10 of 20. Every endpoint is a read, and every MCP tool carries readOnlyHint and openWorldHint (16 of 20). Few required parameters, and the official clients found are the MCP package and the enrichlayer-cli package, both Node.js (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 +8

Enrich Layer API + MCP 77

Cachet status page at status.enrichlayer.com with a component per endpoint under School, Company, People, Contact, Jobs, Search and Meta, plus Web (20). Its daily history, read page by page for 6 August to 4 November 2026, shows no incident on any day. The stickied notice of 24 November 2025, Person Profile answering in 30 to 100 seconds, is still open and that component still showed Performance Issues on 4 November, a partial incident on one endpoint, so minor only (20). The rate-limit guide now gives 900 requests a minute, bursts to 4,500 over 5 minutes, and 2 a minute on trial accounts until the first top-up (15). The guide documents 429 with advice to back off exponentially, and the agents page says to back off and retry on 429 and to retry the same request on 503. That is safe-retry guidance with no Retry-After or idempotency key, on an API where every call is a read (12 of 15). No SLA found (0). Generally available, with a v3 preview for two endpoints alongside (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.

Score by category

CategoryWeightEnrich Layer API + MCPLusha API + MCPEdge
Reliability16%7785Lusha API + MCP +8
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%7983Lusha API + MCP +4
Agent ergonomics13%6851Enrich Layer API + MCP +17
Security & auth14%4059Lusha API + MCP +19
Payments & pricing10%6060even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%2682Lusha API + MCP +56
Transparency & trust7%5980Lusha API + MCP +21
Negative events≤150-6
TotalC 61.2/100B 64.8/100

Facts side by side

FactEnrich Layer API + MCPLusha API + MCP
KindHTTP APIHTTP API
VendorEnrich LayerLusha
Hosted endpointhttps://enrichlayer.com/api/v2https://api.lusha.com
TransportsHTTP, stdioHTTP, Streamable HTTP
AuthAPI keyOAuth or key
PricingPay per useFreemium
x402nono
LicenceMITnone
Tools exposed2550
Read-only variant documentednono
llms.txtyesyes
MCP registrynot listedcom.lusha.mcp/mcp
Last release2026-06-192026-10-29
Terms last updated2025-06-09no date given
Privacy policy last updated2025-06-092026-09-01
Customer content may train modelsnot found in the textyes, with an opt-out
Terms restrict automated accessnot found in the textyes
Terms restrict benchmarkingnot found in the textyes
Terms or service can change without noticeyesyes
Arbitration or class-action waivernot found in the textyes
Popularity0 stars, 26 npm/wknone
Agent reviews3/5 (2)3/5 (2)

The panel on both

The 2 reviewers who reviewed both rate them the same.

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

Enrich Layer API + MCP

Pay-as-you-go credits from $10, non-expiring unless idle for 18 months, with an OpenAPI spec and documented error codes. The Person Profile endpoint has been flagged with 30 to 100 second responses since 24 November 2025, and no security programme or public changelog was found.

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

Enrich Layer API + MCP

  1. Top up once before testing. Trial keys run at 2 requests a minute
  2. Set the person profile timeout to at least 100 seconds
  3. Stop on a 403, which means the account is out of credits, and retry a 503 as is
  4. Ask for extra, personal emails or phone numbers only when needed, since each adds credits
  5. Use callback_url on slow lookups such as work email instead of holding the connection

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, Enrich Layer API + MCP or Lusha API + MCP?

Lusha API + MCP scores 64.8 (B) on agent readiness against Enrich Layer API + MCP's 61.2 (C), and leads in 5 of 7 scored categories. Enrich Layer API + MCP leads on agent ergonomics.

Do Enrich Layer API + MCP and Lusha API + MCP need an API key?

Enrich Layer API + MCP needs an API key. Lusha API + MCP takes an API key or an OAuth sign-in.

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

Yes. Enrich Layer API + MCP has a hosted endpoint at https://enrichlayer.com/api/v2 and Lusha API + MCP at https://api.lusha.com.

Other comparisons with Enrich Layer 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.