Head to head · Lead search · October 2026 research run
LeadMagic API + MCP vs Lusha API + MCP
Lusha API + MCP and LeadMagic API + MCP score within a point of each other on agent readiness, 64.8 (B) and 64.5 (B). LeadMagic 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 Verification and email or mobile finding in automated pipelines, especially at volume on the plans with credit-free search.
Ahead on
- Schema & documentation, 93 against 83
- Agent ergonomics, 71 against 51
Also in its favour
- 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
No free credits, and payments are non-refundable; plans from $99 a month
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 52
- Payments & pricing, 60 against 30
- Transparency & trust, 80 against 65
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.
Reliability Lusha API + MCP +33
LeadMagic API + MCP 52
Own status page at leadmagic.io/status listing the REST API, web app, Email Finder, Mobile Finder, Email Validation and integrations, with a live API health check but no incident history, re-read on 4 November (10 of 20). No history to read (5). Per-second and per-minute limits published, 5 or 10 requests a second for credit-free search with a fair-use ceiling of 13,333 searches a day, and 300 or 600 Email Finder and Validation lookups a minute by plan (15). 429 carries Retry-After with advice to back off, a rejected 429 consumes no credits, and 400s aren't charged. Bulk job submissions and the MCP's Tables tools write data, and no idempotency key or safe-retry guidance for writes was found, so safe-retry guidance without keys, as runway and fal-video read retries of billed jobs (12). The Service Level and Availability Policy states there's no guaranteed uptime and service credits are discretionary, per the 1 October check (0). Generally available (10). 10 + 5 + 15 + 12 + 0 + 10 = 52.
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.
Payments & pricing Lusha API + MCP +30
LeadMagic API + MCP 30
No x402, MPP or L402 (0). Plan prices, annual prices and per-endpoint credit costs are public, re-read on 4 November (20). There are no free credits, the pricing FAQ now calls payments non-refundable except where law or a signed agreement says otherwise, and a 14-day Search trial 'with no automatic charge' covers search only, with no word on whether a card is needed (0). A person signs up and pays in a browser (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 20 is 30.
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 LeadMagic API + MCP +20
LeadMagic API + MCP 71
The full hosted MCP connection carries every tool, which the docs now split into four focused connections (Tables 22, Tables setup 22, Data enrichment 27, Bulk and signals 48 tools) so a client loads only one group. More than 30 tools on the full connection (5), plus 10 back for the focused connections, plus a free preview_cost tool and browse pages of up to 25 rows (3), so 18 of 25. Search filters and pages (16 of 20). Problem-details errors with request_id, 402 for credits and Retry-After on 429 (20). Unknown validation results and 400s are free, and preview_cost estimates before spending. No idempotency keys or tool annotations found (10 of 20). No official SDKs found. A terminal client, LeadMagic CLI (lm), shares the credits (7 of 15). 18 + 16 + 20 + 10 + 7 = 71.
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 +15
LeadMagic API + MCP 65
Closed service with terms naming Lead Magic Corporation, Massachusetts (15). The privacy policy covers people returned by the API and links a request form, a do-not-sell page and privacy@leadmagic.io. We found no stated legal basis, data sources or retention periods in it. The DPA uses SCCs and the UK IDTA (14 of 30). Changelog entries are dated, but no deprecation policy or notices found (6 of 20). The DPA points to a subprocessor list with 15 days' notice of changes and says data is processed in the US and elsewhere (12 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).
Schema & documentation LeadMagic API + MCP +10
LeadMagic API + MCP 93
OpenAPI file at leadmagic.io/openapi.json, per the 30 September check (25). llms.txt (10). MCP tools state their purpose and credit cost, and the server tells the model to report only data the tools returned (16 of 20). Typed request bodies (12 of 15). RFC 9457 problem details with a request_id on every error, and documented 400, 401, 402 and 429 cases (15). A dated changelog versioned per component, api 3.3.1 on 2026-09-17 (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 | LeadMagic API + MCP | Lusha API + MCP | Edge |
|---|---|---|---|---|
| Reliability | 16% | 52 | 85 | Lusha API + MCP +33 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 93 | 83 | LeadMagic API + MCP +10 |
| Agent ergonomics | 13% | 71 | 51 | LeadMagic API + MCP +20 |
| Security & auth | 14% | 63 | 59 | LeadMagic API + MCP +4 |
| Payments & pricing | 10% | 30 | 60 | Lusha API + MCP +30 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 80 | 82 | Lusha API + MCP +2 |
| Transparency & trust | 7% | 65 | 80 | Lusha API + MCP +15 |
| Negative events | ≤15 | 0 | -6 | |
| Total | B 64.5/100 | B 64.8/100 |
Facts side by side
| Fact | LeadMagic API + MCP | Lusha API + MCP |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | LeadMagic | Lusha |
| Hosted endpoint | https://api.leadmagic.io | https://api.lusha.com |
| Transports | HTTP, Streamable HTTP | HTTP, Streamable HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Paid | Freemium |
| x402 | no | no |
| Tools exposed | 48 | 50 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | io.leadmagic/server | com.lusha.mcp/mcp |
| Last release | 2026-10-15 | 2026-10-29 |
| Terms last updated | 2026-08-31 | no date given |
| Privacy policy last updated | 2026-09-20 | 2026-09-01 |
| Customer content may train models | not found in the text | yes, with an opt-out |
| Terms restrict automated access | yes | yes |
| Terms restrict benchmarking | yes | yes |
| Terms or service can change without notice | yes | 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 LeadMagic API + MCP higher, the other way from the total score.
| Reviewer | LeadMagic API + MCP | Lusha API + MCP |
|---|---|---|
| LedgerCost analyst | 4/5 $99 to start, then every response shows its cost | 3/5 Seven credits for one contact, and a miss still costs one |
| WardenSecurity auditor | 3/5 No deletes, no read-only mode either | 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
LeadMagic API + MCP
RFC 9457 problem-details errors with request_id, Retry-After on 429 and credit headers on every response. The hosted MCP server is in the official registry and can load one focused tool group. No free credits, payments are non-refundable, and plans start at $99 a month.
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
LeadMagic API + MCP
- Connect only the focused MCP group the task needs, such as https://mcp.leadmagic.io/mcp/enrichment-core for lookups
- Call
preview_costbefore bulk work. It's free - Read
X-Credits-Remainingafter each call instead of polling the balance - Treat 402 as out of credits and wait out Retry-After on 429
- Follow each table tool's returned approval step before deletions, cell edits or runs over 5 credits
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, LeadMagic API + MCP or Lusha API + MCP?
Lusha API + MCP and LeadMagic API + MCP score within a point of each other on agent readiness, 64.8 (B) and 64.5 (B). LeadMagic API + MCP leads on schema & documentation and agent ergonomics.
Do LeadMagic API + MCP and Lusha API + MCP need an API key?
Both take an API key or an OAuth sign-in.
Can an agent call LeadMagic API + MCP and Lusha API + MCP without installing anything?
Yes. LeadMagic API + MCP has a hosted endpoint at https://api.leadmagic.io and Lusha API + MCP at https://api.lusha.com.
Other comparisons with LeadMagic API + MCP or Lusha API + MCP
- Apollo API + MCP vs LeadMagic API + MCP
- Apollo API + MCP vs Lusha API + MCP
- Clay vs LeadMagic API + MCP
- Clay vs Lusha API + MCP
- Coresignal API + MCP vs LeadMagic API + MCP
- Coresignal API + MCP vs Lusha API + MCP
- Crustdata API + MCP vs LeadMagic API + MCP
- Crustdata API + MCP vs Lusha API + MCP
- Dievio vs LeadMagic API + MCP
- Dievio vs Lusha API + MCP
- Enrich Layer API + MCP vs LeadMagic API + MCP
- Enrich Layer API + MCP vs Lusha API + MCP
- Explorium AgentSource vs LeadMagic API + MCP
- Explorium AgentSource vs Lusha API + MCP
- FullEnrich API + MCP vs LeadMagic API + MCP
- FullEnrich API + MCP vs Lusha API + MCP
- Fuse MCP vs LeadMagic API + MCP
- Fuse MCP vs Lusha API + MCP
- Gojiberry vs LeadMagic API + MCP
- Gojiberry vs Lusha API + MCP
- LeadMagic API + MCP vs People Data Labs
- LeadMagic API + MCP vs Prospeo API + MCP
- LeadMagic API + MCP vs Retriever
- LeadMagic API + MCP vs RocketReach API
- LeadMagic API + MCP vs ZoomInfo 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 LeadMagic API + MCP
- Clearbit vs Lusha API + MCP
- Databar vs LeadMagic API + MCP
- Databar vs Lusha API + MCP
- Dropcontact API + MCP vs LeadMagic API + MCP
- Dropcontact API + MCP vs Lusha API + MCP
- FullContact vs LeadMagic API + MCP
- FullContact vs Lusha API + MCP
- Lusha API + MCP vs ZeroBounce
- Hunter API + MCP vs LeadMagic API + MCP
- Hunter API + MCP vs Lusha API + MCP
- LeadMagic API + MCP vs ZeroBounce
Machine-readable
- This page as Markdown
/compare/leadmagic-vs-lusha.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/leadmagic.json·/api/v1/tools/lusha.json - From a terminal
anchor compare leadmagic lusha(the CLI) - Over MCP
compare_tools {"a": "leadmagic", "b": "lusha"}at/mcp, no key