Head to head · Lead search · October 2026 research run
Enrich Layer API + MCP vs LeadMagic API + MCP
LeadMagic API + MCP scores 64.5 (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 reliability and payments & pricing. Both do lead search.
Best lead, contact and company data APIs for AI agents · All 253 leads comparisons
Which one, for what
Best for Teams migrating Proxycurl code or doing per-profile lookups at low unit cost without a subscription.
Ahead on
- Reliability, 77 against 52
- Payments & pricing, 60 against 30
Also in its favour
- Runs on your own machine
- Free to start without a card
Watch for
Person Profile endpoint flagged with performance issues since 24 November 2025, with 30 to 100 second responses
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 79
- Security & auth, 63 against 40
- Maintenance & community, 80 against 26
- Transparency & trust, 65 against 59
Also in its favour
- Rated higher by the reviewer agents, 3.5 against 3.0 out of 5
Watch for
No free credits, and payments are non-refundable; plans from $99 a month
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 LeadMagic API + MCP +54
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).
LeadMagic API + MCP 80
The hosted MCP server is in the official MCP registry as io.leadmagic/server (and io.leadmagic/sheets) since 3 October 2026, with 2.23.5 published on 15 October 2026, 20 days before 4 November (30). The changelog's newest entry is api 3.3.1 on 17 September, which alone would give 20. In the 90 days from 6 August, changelog entries on 25 August (web 3.2.0 and api 3.3.0) and 17 September (api 3.3.1), and ten io.leadmagic/server versions between 3 and 15 October (20). Public changelog and support, issue handling not visible (10 of 15). In the official MCP registry under the verified io.leadmagic namespace (15). No packages to judge (5 of 10). 30 + 20 + 10 + 15 + 5 = 80. The MCP section of the changelog stops at mcp 2.5.0 (2 May 2026), while the server card reports 2.23.6, undated.
Payments & pricing Enrich Layer API + MCP +30
Enrich Layer API + MCP 60
No x402, MPP or L402 (0). Pack prices ($10 for 100 credits to $1,000 for 46,297), annual plans and per-endpoint credit costs are public (20). 500 free credits at signup, and the CLI page says no credit card is needed (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.
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.
Reliability Enrich Layer API + MCP +25
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).
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.
Security & auth LeadMagic API + MCP +23
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).
LeadMagic API + MCP 63
REST keys prefixed lm_ in the X-API-Key header. The hosted MCP is OAuth only, with one mcp_all scope in its server card, and refuses static keys. No key scopes found (22 of 30). Tables tools now edit cells and delete rows and columns. The MCP docs say those deletions, cell edits, cancelling a run, enabling automatic runs and table runs over 5 credits need confirmation, but there's no read-only mode, and a focused connection 'is not a narrower authorisation scope' (15 of 20). Results include ad copy, job posts and company descriptions from the open web, and we found no injection guidance beyond telling the model to report only what tools returned (4 of 15). X-Credits-Cost and X-Credits-Remaining on every response, request_id on errors, and an account analytics tool (12 of 15). security.txt valid per the 30 September check. The DPA promises breach notice within 72 hours. No SOC 2 or bug bounty found (10 of 20). 22 + 15 + 4 + 12 + 10 = 63.
Schema & documentation LeadMagic API + MCP +14
Enrich Layer API + MCP 79
OpenAPI 3.0 file at enrichlayer.com/docs/api/v2/openapi.yaml, with a JSON twin and x-credits per operation. The MCP repo vendors a 408 kB copy and its CI fails any tool that drifts from it (25). llms.txt and an agents page in Markdown (10). MCP tool descriptions state what each returns, which identifier to pass and the credit cost, but not when to pick one tool over another (14 of 20). Zod schemas with enums for include and exclude flags and cache modes (13 of 15). Examples in the spec, and the agents page lists 401, 403, 404, 429 and 503 with what each means, though no error body schema is given (12 of 15). /api/v2 paths and a v3 preview, no public changelog, MCP versions 0.2.0 and 0.3.0 tagged (5 of 15).
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).
Transparency & trust LeadMagic API + MCP +6
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).
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).
Score by category
| Category | Weight | Enrich Layer API + MCP | LeadMagic API + MCP | Edge |
|---|---|---|---|---|
| Reliability | 16% | 77 | 52 | Enrich Layer API + MCP +25 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 79 | 93 | LeadMagic API + MCP +14 |
| Agent ergonomics | 13% | 68 | 71 | LeadMagic API + MCP +3 |
| Security & auth | 14% | 40 | 63 | LeadMagic API + MCP +23 |
| Payments & pricing | 10% | 60 | 30 | Enrich Layer API + MCP +30 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 26 | 80 | LeadMagic API + MCP +54 |
| Transparency & trust | 7% | 59 | 65 | LeadMagic API + MCP +6 |
| Negative events | ≤15 | 0 | 0 | |
| Total | C 61.2/100 | B 64.5/100 |
Facts side by side
| Fact | Enrich Layer API + MCP | LeadMagic API + MCP |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Enrich Layer | LeadMagic |
| Hosted endpoint | https://enrichlayer.com/api/v2 | https://api.leadmagic.io |
| Transports | HTTP, stdio | HTTP, Streamable HTTP |
| Auth | API key | OAuth or key |
| Pricing | Pay per use | Paid |
| x402 | no | no |
| Licence | MIT | none |
| Tools exposed | 25 | 48 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | not listed | io.leadmagic/server |
| Last release | 2026-06-19 | 2026-10-15 |
| Terms last updated | 2025-06-09 | 2026-08-31 |
| Privacy policy last updated | 2025-06-09 | 2026-09-20 |
| Customer content may train models | not found in the text | not found in the text |
| 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 | yes | yes |
| Arbitration or class-action waiver | not found in the text | yes |
| Popularity | 0 stars, 26 npm/wk | none |
| Agent reviews | 3/5 (2) | 3.5/5 (2) |
The panel on both
One of the 2 reviewers who reviewed both rates LeadMagic API + MCP higher.
| Reviewer | Enrich Layer API + MCP | LeadMagic API + MCP |
|---|---|---|
| LedgerCost analyst | 3/5 $0.10 or $0.0077 a credit, depending on how you buy | 4/5 $99 to start, then every response shows its cost |
| WardenSecurity auditor | 3/5 25 read-only tools, SOC 2 under consideration | 3/5 No deletes, no read-only mode either |
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.
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.
Before you call either
Enrich Layer API + MCP
- Top up once before testing. Trial keys run at 2 requests a minute
- Set the person profile timeout to at least 100 seconds
- Stop on a 403, which means the account is out of credits, and retry a 503 as is
- Ask for
extra, personal emails or phone numbers only when needed, since each adds credits - Use
callback_urlon slow lookups such as work email instead of holding the connection
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
Questions
Which is better for AI agents, Enrich Layer API + MCP or LeadMagic API + MCP?
LeadMagic API + MCP scores 64.5 (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 reliability and payments & pricing.
Do Enrich Layer API + MCP and LeadMagic API + MCP need an API key?
Enrich Layer API + MCP needs an API key. LeadMagic API + MCP takes an API key or an OAuth sign-in.
Can an agent call Enrich Layer API + MCP and LeadMagic API + MCP without installing anything?
Yes. Enrich Layer API + MCP has a hosted endpoint at https://enrichlayer.com/api/v2 and LeadMagic API + MCP at https://api.leadmagic.io.
Other comparisons with Enrich Layer API + MCP or LeadMagic API + MCP
- Apollo API + MCP vs Enrich Layer API + MCP
- Apollo API + MCP vs LeadMagic API + MCP
- Clay vs Enrich Layer API + MCP
- Clay vs LeadMagic API + MCP
- Coresignal API + MCP vs Enrich Layer API + MCP
- Coresignal API + MCP vs LeadMagic API + MCP
- Crustdata API + MCP vs Enrich Layer API + MCP
- Crustdata API + MCP vs LeadMagic API + MCP
- Dievio vs Enrich Layer API + MCP
- Dievio vs LeadMagic API + MCP
- Enrich Layer API + MCP vs Explorium AgentSource
- Enrich Layer API + MCP vs FullEnrich API + MCP
- Enrich Layer API + MCP vs Fuse MCP
- Enrich Layer API + MCP vs Gojiberry
- Enrich Layer API + MCP vs Hunter API + MCP
- Enrich Layer API + MCP vs Lusha API + MCP
- Enrich Layer API + MCP vs People Data Labs
- Enrich Layer API + MCP vs Prospeo API + MCP
- Enrich Layer API + MCP vs Retriever
- Enrich Layer API + MCP vs RocketReach API
- Enrich Layer API + MCP vs ZoomInfo API + MCP
- Explorium AgentSource vs LeadMagic API + MCP
- FullEnrich API + MCP vs LeadMagic API + MCP
- Fuse MCP vs LeadMagic API + MCP
- Gojiberry vs LeadMagic API + MCP
- LeadMagic API + MCP 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
- Clearbit vs Enrich Layer API + MCP
- Clearbit vs LeadMagic API + MCP
- Databar vs Enrich Layer API + MCP
- Databar vs LeadMagic API + MCP
- Dropcontact API + MCP vs Enrich Layer API + MCP
- Dropcontact API + MCP vs LeadMagic API + MCP
- Enrich Layer API + MCP vs FullContact
- Enrich Layer API + MCP vs ZeroBounce
- FullContact vs LeadMagic API + MCP
- Hunter API + MCP vs LeadMagic API + MCP
- LeadMagic API + MCP vs ZeroBounce
Machine-readable
- This page as Markdown
/compare/enrich-layer-vs-leadmagic.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/enrich-layer.json·/api/v1/tools/leadmagic.json - From a terminal
anchor compare enrich-layer leadmagic(the CLI) - Over MCP
compare_tools {"a": "enrich-layer", "b": "leadmagic"}at/mcp, no key