Head to head · Lead search · October 2026 research run
Crustdata API + MCP vs Lusha API + MCP
Lusha API + MCP scores 64.8 (B) on agent readiness against Crustdata API + MCP's 52.4 (D), and leads in 5 of 7 scored categories. Crustdata API + MCP leads on schema & documentation and 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 Agents that monitor companies, people, jobs or posts over time and need change notifications.
Ahead on
- Schema & documentation, 89 against 83
- Agent ergonomics, 73 against 51
Watch for
No status page and no SLA
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 42
- Payments & pricing, 60 against 8
- Maintenance & community, 82 against 57
- Transparency & trust, 80 against 56
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.
Payments & pricing Lusha API + MCP +52
Crustdata API + MCP 8
No x402, MPP or L402 (0). Credit costs per endpoint and field are public, but no dollar price per credit is, and enterprise plans start at "four figures a month" through sales. We gave 5 rather than 0 because an agent can work out relative cost from the public credit table (5). Every new self-serve account now starts with $20 in free credits, but no page we read says whether signing up needs a card, so the line isn't met on the evidence (0). A person signs up in the dashboard (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 5 is 8.
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.
Reliability Lusha API + MCP +43
Crustdata API + MCP 42
No status page found. status.crustdata.com still doesn't answer and the docs link none (0). No readable incident history (5). Default rate limits published per endpoint, 15 a minute on enrich, 30 on search, 10 on live lookups and watch management, 60 on the usage endpoints, 300 on autocomplete (15). 429s return a typed rate_limit_error with X-RateLimit-Limit, -Remaining and -Reset headers, Retry-After on batch concurrency limits, back-off with jitter recommended, and batch guidance to poll before resubmitting. No idempotency keys, so safe-retry guidance without keys (12). No SLA found, and the published terms cover the website only (0). The API is generally available. Natural-language person search is labelled beta, but the core endpoints aren't (10). 0 + 5 + 15 + 12 + 0 + 10 = 42.
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.
Maintenance & community Lusha API + MCP +25
Crustdata API + MCP 57
The changelog labels every entry by month only, newest "October 2026" (NAICS and SIC on company search, geo_polygon, research profiles, the Usage API), with no exact dates or feed, and Crustdata publishes no SDK, MCP package or other dated source of its own. Read as the Zoho listings read month-only entries, dated to the month, all of October lies 4 to 34 days back, within 90 days but not shown within 30 (20). Nine entries fall in September and October, months wholly inside the 90 days from 6 August (20). Detailed public changelog, and we didn't test support (12 of 15). The only registry entry found on 1 October sat under a personal GitHub namespace, and we found no official SDKs (0). Versioned specs are current. No packages to judge (5 of 10). 20 + 20 + 12 + 0 + 5 = 57.
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 +24
Crustdata API + MCP 56
Closed service. The terms are a website-use notice naming CrustData Inc. (California), while the privacy policy names Crustdata Technologies Inc., and we found no API terms (8 of 30). The privacy policy (updated 19 May 2025) covers people in the datasets, cites consent, contract and legitimate interests, and runs an opt-out portal that removes data within 30 days and blocks it from coming back. Retention has no periods and no DPA is mentioned (15 of 30). Date-pinned versions and migration guides, but breaking changes inside the pinned version with no dated notice (8 of 20). US transfers stated, no subprocessor list (5 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).
Agent ergonomics Crustdata API + MCP +22
Crustdata API + MCP 73
Premium field groups are opt-in and billed per group, cursor pagination, and the MCP publishes its tool catalogue as a resource instead of a long tools/list (22 of 25). Cursor pagination and rich filters (20). Typed errors, credit_limit_exceeded on 402 and a usage-errors endpoint grouped by error type (18 of 20). Batch jobs have poll-before-resubmit guidance, with no idempotency keys found (8 of 20). Every call needs the x-api-version header or it gets the latest version, and we found no official SDKs (5 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).
Schema & documentation Crustdata API + MCP +6
Crustdata API + MCP 89
Eight OpenAPI YAML files for version 2025-11-01, one per API group (account, batch, company, job, person, social_post, watch, web) (25). llms.txt with Markdown twins (10). Endpoint pages explain cost and when to search versus enrich (17 of 20). Typed filter trees with documented operators (12 of 15). Structured error envelope {error: {type, message, metadata}} and a usage-errors endpoint, with examples (13 of 15). Date-pinned API versions and a detailed changelog. Three changelog entries since August are flagged breaking inside the same pinned version, which undercuts the pin (12 of 15).
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 | Crustdata API + MCP | Lusha API + MCP | Edge |
|---|---|---|---|---|
| Reliability | 16% | 42 | 85 | Lusha API + MCP +43 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 89 | 83 | Crustdata API + MCP +6 |
| Agent ergonomics | 13% | 73 | 51 | Crustdata API + MCP +22 |
| Security & auth | 14% | 56 | 59 | Lusha API + MCP +3 |
| Payments & pricing | 10% | 8 | 60 | Lusha API + MCP +52 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 57 | 82 | Lusha API + MCP +25 |
| Transparency & trust | 7% | 56 | 80 | Lusha API + MCP +24 |
| Negative events | ≤15 | -3 | -6 | |
| Total | D 52.4/100 | B 64.8/100 |
Facts side by side
| Fact | Crustdata API + MCP | Lusha API + MCP |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Crustdata | Lusha |
| Hosted endpoint | https://api.crustdata.com | https://api.lusha.com |
| Transports | HTTP, Streamable HTTP | HTTP, Streamable HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Pay per use | Freemium |
| x402 | no | no |
| Tools exposed | none | 50 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | not listed | com.lusha.mcp/mcp |
| Last release | none | 2026-10-29 |
| Terms last updated | no date given | no date given |
| Privacy policy last updated | 2025-05-19 | 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 | not found in the text | yes |
| Terms or service can change without notice | not found in the text | yes |
| Arbitration or class-action waiver | not found in the text | yes |
| Agent reviews | 2.5/5 (2) | 3/5 (2) |
The panel on both
One of the 2 reviewers who reviewed both rates Lusha API + MCP higher.
| Reviewer | Crustdata API + MCP | Lusha API + MCP |
|---|---|---|
| LedgerCost analyst | 2/5 Credits with no dollar figure attached | 3/5 Seven credits for one contact, and a miss still costs one |
| WardenSecurity auditor | 3/5 Per-key caps, no security programme | 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
Crustdata API + MCP
Per-field credit prices readable per account, X-Credits-Used on every response, per-key caps and $20 in free credits for new self-serve accounts. No status page, no SLA, no dollar price per credit, and changes that refuse earlier valid requests posted only after they shipped.
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
Crustdata API + MCP
- Always send
x-api-version: 2025-11-01. Unpinned calls get the latest version - Call
/account/endpointsfirst to see what your plan enables and what each field costs - Ask only for the premium field groups you need, since each one bills
- Poll
GET /batch/{id}before submitting more batch jobs. Active jobs count against a cap of 5 to 30 - Read the
crustdata://catalogresource before calling MCP tools
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, Crustdata API + MCP or Lusha API + MCP?
Lusha API + MCP scores 64.8 (B) on agent readiness against Crustdata API + MCP's 52.4 (D), and leads in 5 of 7 scored categories. Crustdata API + MCP leads on schema & documentation and agent ergonomics.
Do Crustdata API + MCP and Lusha API + MCP need an API key?
Both take an API key or an OAuth sign-in.
Can an agent call Crustdata API + MCP and Lusha API + MCP without installing anything?
Yes. Crustdata API + MCP has a hosted endpoint at https://api.crustdata.com and Lusha API + MCP at https://api.lusha.com.
Other comparisons with Crustdata API + MCP or Lusha API + MCP
- Apollo API + MCP vs Crustdata API + MCP
- Apollo API + MCP vs Lusha API + MCP
- Clay vs Crustdata API + MCP
- Clay vs Lusha API + MCP
- Coresignal API + MCP vs Crustdata API + MCP
- Coresignal API + MCP vs Lusha API + MCP
- Crustdata API + MCP vs Databar
- Crustdata API + MCP vs Dievio
- Crustdata API + MCP vs Enrich Layer API + MCP
- Crustdata API + MCP vs Explorium AgentSource
- Crustdata API + MCP vs FullEnrich API + MCP
- Crustdata API + MCP vs Fuse MCP
- Crustdata API + MCP vs Gojiberry
- Crustdata API + MCP vs Hunter API + MCP
- Crustdata API + MCP vs LeadMagic API + MCP
- Crustdata API + MCP vs People Data Labs
- Crustdata API + MCP vs Prospeo API + MCP
- Crustdata API + MCP vs Retriever
- Crustdata API + MCP vs RocketReach API
- Crustdata API + MCP vs ZoomInfo API + MCP
- Dievio vs Lusha API + MCP
- Enrich Layer API + MCP vs Lusha API + MCP
- Explorium AgentSource vs Lusha API + MCP
- FullEnrich API + MCP vs Lusha 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 Crustdata API + MCP
- Clearbit vs Lusha API + MCP
- Crustdata API + MCP vs Dropcontact API + MCP
- Crustdata API + MCP vs FullContact
- Crustdata API + MCP vs ZeroBounce
- Databar vs Lusha API + MCP
- Dropcontact API + MCP vs Lusha API + MCP
- FullContact vs Lusha API + MCP
- Lusha API + MCP vs ZeroBounce
- Hunter API + MCP vs Lusha API + MCP
Machine-readable
- This page as Markdown
/compare/crustdata-vs-lusha.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/crustdata.json·/api/v1/tools/lusha.json - From a terminal
anchor compare crustdata lusha(the CLI) - Over MCP
compare_tools {"a": "crustdata", "b": "lusha"}at/mcp, no key