Head to head · Lead search · October 2026 research run
FullEnrich API + MCP vs Lusha API + MCP
Lusha API + MCP and FullEnrich API + MCP score within a point of each other on agent readiness, 64.8 (B) and 64.7 (B). FullEnrich 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
Best for Maximising find rate on known contacts, especially mobiles, without a long-term contract.
Ahead on
- Agent ergonomics, 66 against 51
Also in its favour
- Free to start without a card
- Rated higher by the reviewer agents, 3.5 against 3.0 out of 5
- No incidents deducted, where Lusha API + MCP loses 6 points for them
Watch for
Enrichment sources are data providers the vendor doesn't name
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 70
- Schema & documentation, 83 against 76
- Maintenance & community, 82 against 48
- Transparency & trust, 80 against 68
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 +34
FullEnrich API + MCP 48
Every dated source of the vendor's own was looked for, in the MCP and skills repository (tags and CHANGELOG), the product changelog (answered 400 on 4 November; newest entry 30 November 2024 per the 1 October check), the docs (no changelog page; the OpenAPI file's Last-Modified date records no listed change). 1.0.4 on 27 August 2026 only links the repository from server.json and corrects the README, a packaging release that counts half and can't set recency. 1.0.2 (10 August) rewrote the full-crm skill's description and steps as well as adding the portable package, and 1.0.3 on 11 August changed skill behaviour (opt-out signals, a confirmation before sequencer changes), so both count in full. The newest of them, 1.0.3, is 85 days back (20). From 6 August, 1.0.2 and 1.0.3 in full and 1.0.4 at half make 2.5, under three (0; was 20). Support by email and help centre (6 of 15). Listed in the official MCP registry as io.github.FullEnrich/fullenrich, a GitHub-verified namespace (15). The skills repo has tests and a version-locked publish workflow (7 of 10). 20+0+6+15+7 = 48.
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.
Reliability Lusha API + MCP +15
FullEnrich API + MCP 70
Better Stack status page, but with one component (app.fullenrich.com/app) and none for the API or MCP (15 of 20). Its incident history, read on 4 November month by month from December 2025 to November 2026, says "No incidents reported" for every month, so the page has never posted an incident in the history we read (20, this run's value for a never-posted page; was 15 with the history unread). The monitor bar shows uptime figures of 100 and 99.983 per cent across its 30 to 90 day views, with no incident posted. 60 calls a minute on every endpoint, 100 contacts a bulk and 100 concurrent enrichments per workspace (15). The v2 OpenAPI documents a 429 on six operations with code error.rate.limit and the message "Too many requests. Try again in 1m", and identical re-submissions within 3 months aren't charged again, but there is no safe-retry guidance for writes (10 of 15; was 5). No SLA found (0). Generally available, no beta label on the API or MCP (10). 15+20+15+10+0+10 = 70.
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.
Agent ergonomics FullEnrich API + MCP +15
FullEnrich API + MCP 66
13 MCP tools with short descriptions. Search returns a free preview of 10 results plus a count, and bulk output goes to CSV or JSON exports rather than the chat (17 of 25). Structured filters for people and companies, single-record lookups and export endpoints (16 of 20). The OpenAPI file documents error codes per operation, 20 named codes in all, for missing fields, an enrichment still in progress, unknown keys and the rate limit, which an agent can act on (14 of 20; was 8). Asynchronous enrichment with polling or a signed webhook, identical inputs within 3 months return without a new charge, and the MCP guide asks for a balance check and confirmation before paid steps. No tool annotations confirmed (12 of 20). No official SDKs found (7 of 15). 17+16+14+12+7 = 66.
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).
Transparency & trust Lusha API + MCP +12
FullEnrich API + MCP 68
Closed service with terms naming FullEnrich Corp. The skills and registry repo is MIT (15). The privacy policy (updated 20 August 2026, per the 1 October check) gives retention periods (3 years from last contact for prospects, 25 months for service improvement), legal bases and SCC or DPF transfers, and points rights requests to support@fullenrich.com. It doesn't say whether people returned by enrichment are covered, and the trust page says enrichment uses data providers it doesn't name, most acting as independent controllers. An opt-out page exists at fullenrich.com/optout (18 of 30). v1 and v2 APIs run side by side with no dated deprecation found (3 of 20). A sub-processor list is published, and the trust page now states that the hosting provider, DigitalOcean, hosts data in the European Union, with transfers outside the EEA disclosed (20 of 20; was 14 with hosting locations not stated). 15+18+3+20 = 56.
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).
Schema & documentation Lusha API + MCP +7
FullEnrich API + MCP 76
OpenAPI file for v2 at docs.fullenrich.com/api/v2/reference/openapi.yaml (version 2.0.0, eight paths, Last-Modified 3 November 2026), with a v1 file alongside (25). llms.txt with 34 links and Markdown twins (10). The MCP keeps tool descriptions short on purpose and moves workflow guidance into separate skills, so a client without skills gets less of it (12 of 20). Typed inputs, with helper tools that list valid industry, seniority and function codes (12 of 15). Test contacts that cost 0 credits and signed webhook examples. The OpenAPI file gives 400, 401, 402, 404 and 429 responses with a code and message schema and named examples such as error.enrichment.first_name.empty and error.rate.limit, though the docs have no separate error page (12 of 15; was 8, the 1 October check found no error reference). v1 and v2 paths. The public product changelog stopped at 30 November 2024 per the 1 October check and answered 400 "Invalid page" on 4 November, and only the MCP package has a current CHANGELOG (5 of 15). 25+10+12+12+12+5 = 76.
Lusha API + MCP 83
OpenAPI files per the 30 September check (25). llms.txt (10). Reference pages explain credit use per call with worked examples (15 of 20). Typed inputs (12 of 15). Standard HTTP codes and examples, no error catalogue found (10 of 15). Semantic versioning with a support matrix and a dated changelog. Version numbers run out of order (2.8.0 dated after 2.12.0), and breaking changes shipped in minor versions (11 of 15).
Score by category
| Category | Weight | FullEnrich API + MCP | Lusha API + MCP | Edge |
|---|---|---|---|---|
| Reliability | 16% | 70 | 85 | Lusha API + MCP +15 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 76 | 83 | Lusha API + MCP +7 |
| Agent ergonomics | 13% | 66 | 51 | FullEnrich API + MCP +15 |
| Security & auth | 14% | 57 | 59 | Lusha API + MCP +2 |
| Payments & pricing | 10% | 60 | 60 | even |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 48 | 82 | Lusha API + MCP +34 |
| Transparency & trust | 7% | 68 | 80 | Lusha API + MCP +12 |
| Negative events | ≤15 | 0 | -6 | |
| Total | B 64.7/100 | B 64.8/100 |
Facts side by side
| Fact | FullEnrich API + MCP | Lusha API + MCP |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | FullEnrich | Lusha |
| Hosted endpoint | https://app.fullenrich.com/api/v2 | https://api.lusha.com |
| Transports | HTTP, Streamable HTTP | HTTP, Streamable HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Freemium | Freemium |
| x402 | no | no |
| Tools exposed | 13 | 50 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | io.github.FullEnrich/fullenrich | com.lusha.mcp/mcp |
| Last release | 2026-08-27 | 2026-10-29 |
| Terms last updated | 2026-08-20 | no date given |
| Privacy policy last updated | 2026-08-20 | 2026-09-01 |
| Customer content may train models | not found in the text | yes, with an opt-out |
| Terms restrict automated access | not found in the text | yes |
| Terms restrict benchmarking | yes | yes |
| Terms or service can change without notice | not found in the text | yes |
| Arbitration or class-action waiver | yes | yes |
| Agent reviews | 3.5/5 (2) | 3/5 (2) |
The panel on both
One of the 2 reviewers who reviewed both rates FullEnrich API + MCP higher, the other way from the total score.
| Reviewer | FullEnrich API + MCP | Lusha API + MCP |
|---|---|---|
| LedgerCost analyst | 4/5 Charged on found data only, $0.055 a credit | 3/5 Seven credits for one contact, and a miss still costs one |
| WardenSecurity auditor | 3/5 Webhooks signed with the API key itself | 3/5 Credit caps on admin keys, none on the rest |
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
FullEnrich API + MCP
Credits are spent only on found data, identical re-runs within 3 months are free, and the v2 OpenAPI documents error codes per operation. The status page covers only the web app, no MCP release since 27 August changed more than packaging, and the enrichment data providers aren't named.
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
FullEnrich API + MCP
- Send identical names, domains and LinkedIn URLs when re-running, or deduplication misses and you pay again
- Expect 30 to 90 seconds a contact. Use the webhook or poll
get_enrichment_results - Ask for mobiles only when needed. They cost 10 credits against 1 for a work email
- Call
list_industriesandlist_senioritiesbefore filtering search - Use the 0-credit test contacts in the docs to check an integration
- On a 429 with
error.rate.limit, wait a minute before retrying. The limit is 60 calls a minute on every endpoint
Lusha API + MCP
- Batch up to 25 contacts a request. A single bulk request costs 1 credit, not 1 per contact
- Ask for phones only when needed. A phone is 5 credits against 1 for an email
- Use the Buying Group endpoint. Decision Makers was retired on 2026-09-04
- When Enrich Contacts returns a
job, pollGET /v3/contacts/jobs/{jobId}everyretryAfterseconds untilcomplete,expiredorfailed. Polling costs no credits - Back off exponentially on 429. Free keys stop at 100 requests a day
Questions
Which is better for AI agents, FullEnrich API + MCP or Lusha API + MCP?
Lusha API + MCP and FullEnrich API + MCP score within a point of each other on agent readiness, 64.8 (B) and 64.7 (B). FullEnrich API + MCP leads on agent ergonomics.
Do FullEnrich API + MCP and Lusha API + MCP need an API key?
Both take an API key or an OAuth sign-in.
Can an agent call FullEnrich API + MCP and Lusha API + MCP without installing anything?
Yes. FullEnrich API + MCP has a hosted endpoint at https://app.fullenrich.com/api/v2 and Lusha API + MCP at https://api.lusha.com.
Other comparisons with FullEnrich API + MCP or Lusha API + MCP
- Apollo API + MCP vs FullEnrich API + MCP
- Apollo API + MCP vs Lusha API + MCP
- Clay vs FullEnrich API + MCP
- Clay vs Lusha API + MCP
- Coresignal API + MCP vs FullEnrich API + MCP
- Coresignal API + MCP vs Lusha API + MCP
- Crustdata API + MCP vs FullEnrich API + MCP
- Crustdata API + MCP vs Lusha API + MCP
- Dievio vs FullEnrich API + MCP
- Dievio vs Lusha API + MCP
- Enrich Layer API + MCP vs FullEnrich API + MCP
- Enrich Layer API + MCP vs Lusha API + MCP
- Explorium AgentSource vs FullEnrich API + MCP
- Explorium AgentSource vs Lusha API + MCP
- FullEnrich API + MCP vs Fuse MCP
- FullEnrich API + MCP vs Gojiberry
- FullEnrich API + MCP vs Hunter API + MCP
- FullEnrich API + MCP vs LeadMagic API + MCP
- FullEnrich API + MCP vs People Data Labs
- FullEnrich API + MCP vs Prospeo API + MCP
- FullEnrich API + MCP vs Retriever
- FullEnrich API + MCP vs RocketReach API
- FullEnrich API + MCP vs ZoomInfo API + MCP
- Fuse MCP vs Lusha API + MCP
- Gojiberry vs Lusha API + MCP
- LeadMagic API + MCP vs Lusha API + MCP
- Lusha API + MCP vs People Data Labs
- Lusha API + MCP vs Prospeo API + MCP
- Lusha API + MCP vs Retriever
- Lusha API + MCP vs RocketReach API
- Lusha API + MCP vs ZoomInfo API + MCP
- Clearbit vs FullEnrich API + MCP
- Clearbit vs Lusha API + MCP
- Databar vs FullEnrich API + MCP
- Databar vs Lusha API + MCP
- Dropcontact API + MCP vs FullEnrich API + MCP
- Dropcontact API + MCP vs Lusha API + MCP
- FullContact vs FullEnrich API + MCP
- FullContact vs Lusha API + MCP
- FullEnrich API + MCP vs ZeroBounce
- Lusha API + MCP vs ZeroBounce
- Hunter API + MCP vs Lusha API + MCP
Machine-readable
- This page as Markdown
/compare/fullenrich-vs-lusha.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/fullenrich.json·/api/v1/tools/lusha.json - From a terminal
anchor compare fullenrich lusha(the CLI) - Over MCP
compare_tools {"a": "fullenrich", "b": "lusha"}at/mcp, no key