Head to head · Lead search · October 2026 research run
FullEnrich API + MCP vs LeadMagic API + MCP
FullEnrich API + MCP and LeadMagic API + MCP score within a point of each other on agent readiness, 64.7 (B) and 64.5 (B). LeadMagic API + MCP leads on schema & documentation, agent ergonomics, security & auth and maintenance & community. 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
- Reliability, 70 against 52
- Payments & pricing, 60 against 30
Also in its favour
- Free to start without a card
Watch for
Enrichment sources are data providers the vendor doesn't name
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 76
- Agent ergonomics, 71 against 66
- Security & auth, 63 against 57
- Maintenance & community, 80 against 48
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 +32
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.
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 FullEnrich API + MCP +30
FullEnrich API + MCP 60
No x402, MPP or L402 (0). Per-unit credit costs and plan prices are public, on the pricing page and its Markdown twin, 1 credit a work email, 3 a personal email, 10 a mobile, 0.25 a search result, Pro from $29 a month for 500 credits ($55 for 1,000) (20). 50 trial credits with no card, API and MCP included (20). A person signs up in a browser (0). 0+20+20+0 = 40. 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 FullEnrich API + MCP +18
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.
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.
Schema & documentation LeadMagic API + MCP +17
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.
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).
Security & auth LeadMagic API + MCP +6
FullEnrich API + MCP 57
Bearer API key for REST, no scopes found. The MCP signs in with OAuth and holds no static secret in the client. Webhooks are signed with HMAC-SHA1 keyed with the API key itself (20 of 30). The MCP isn't read-only, and confirmation before enrichment is recommended but left to the client. Workspace admins can set monthly credit limits per member, which block further credit-consuming MCP actions, and the skills add a confirmation before any sequencer change and honour opt-out and do-not-contact signals (10 of 20). Results are mostly structured contact fields (8 of 15). A free credits endpoint, and per-member usage views that include MCP activity, no per-call log found (7 of 15; was 5, aligned with people-data-labs' usage view). SOC 2 Type 2 per the trust page, with the report on request, vulnerability reports to support@fullenrich.com per the repository's SECURITY.md, security.txt 404 on 4 November, no bug bounty (12 of 20, as people-data-labs). 20+10+8+7+12 = 57.
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.
Agent ergonomics LeadMagic API + MCP +5
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.
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.
Score by category
| Category | Weight | FullEnrich API + MCP | LeadMagic API + MCP | Edge |
|---|---|---|---|---|
| Reliability | 16% | 70 | 52 | FullEnrich API + MCP +18 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 76 | 93 | LeadMagic API + MCP +17 |
| Agent ergonomics | 13% | 66 | 71 | LeadMagic API + MCP +5 |
| Security & auth | 14% | 57 | 63 | LeadMagic API + MCP +6 |
| Payments & pricing | 10% | 60 | 30 | FullEnrich API + MCP +30 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 48 | 80 | LeadMagic API + MCP +32 |
| Transparency & trust | 7% | 68 | 65 | FullEnrich API + MCP +3 |
| Negative events | ≤15 | 0 | 0 | |
| Total | B 64.7/100 | B 64.5/100 |
Facts side by side
| Fact | FullEnrich API + MCP | LeadMagic API + MCP |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | FullEnrich | LeadMagic |
| Hosted endpoint | https://app.fullenrich.com/api/v2 | https://api.leadmagic.io |
| Transports | HTTP, Streamable HTTP | HTTP, Streamable HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Freemium | Paid |
| x402 | no | no |
| Tools exposed | 13 | 48 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | io.github.FullEnrich/fullenrich | io.leadmagic/server |
| Last release | 2026-08-27 | 2026-10-15 |
| Terms last updated | 2026-08-20 | 2026-08-31 |
| Privacy policy last updated | 2026-08-20 | 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 | 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/5 (2) |
The panel on both
The 2 reviewers who reviewed both rate them the same.
| Reviewer | FullEnrich API + MCP | LeadMagic API + MCP |
|---|---|---|
| LedgerCost analyst | 4/5 Charged on found data only, $0.055 a credit | 4/5 $99 to start, then every response shows its cost |
| WardenSecurity auditor | 3/5 Webhooks signed with the API key itself | 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
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.
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
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
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, FullEnrich API + MCP or LeadMagic API + MCP?
FullEnrich API + MCP and LeadMagic API + MCP score within a point of each other on agent readiness, 64.7 (B) and 64.5 (B). LeadMagic API + MCP leads on schema & documentation, agent ergonomics, security & auth and maintenance & community.
Do FullEnrich API + MCP and LeadMagic API + MCP need an API key?
Both take an API key or an OAuth sign-in.
Can an agent call FullEnrich API + MCP and LeadMagic API + MCP without installing anything?
Yes. FullEnrich API + MCP has a hosted endpoint at https://app.fullenrich.com/api/v2 and LeadMagic API + MCP at https://api.leadmagic.io.
Other comparisons with FullEnrich API + MCP or LeadMagic API + MCP
- Apollo API + MCP vs FullEnrich API + MCP
- Apollo API + MCP vs LeadMagic API + MCP
- Clay vs FullEnrich API + MCP
- Clay vs LeadMagic API + MCP
- Coresignal API + MCP vs FullEnrich API + MCP
- Coresignal API + MCP vs LeadMagic API + MCP
- Crustdata API + MCP vs FullEnrich API + MCP
- Crustdata API + MCP vs LeadMagic API + MCP
- Dievio vs FullEnrich API + MCP
- Dievio vs LeadMagic API + MCP
- Enrich Layer API + MCP vs FullEnrich API + MCP
- Enrich Layer API + MCP vs LeadMagic API + MCP
- Explorium AgentSource vs FullEnrich API + MCP
- Explorium AgentSource vs LeadMagic API + MCP
- FullEnrich API + MCP vs Fuse MCP
- FullEnrich API + MCP vs Gojiberry
- FullEnrich API + MCP vs Hunter API + MCP
- FullEnrich API + MCP vs Lusha 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 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 FullEnrich API + MCP
- Clearbit vs LeadMagic API + MCP
- Databar vs FullEnrich API + MCP
- Databar vs LeadMagic API + MCP
- Dropcontact API + MCP vs FullEnrich API + MCP
- Dropcontact API + MCP vs LeadMagic API + MCP
- FullContact vs FullEnrich API + MCP
- FullContact vs LeadMagic API + MCP
- FullEnrich API + MCP vs ZeroBounce
- Hunter API + MCP vs LeadMagic API + MCP
- LeadMagic API + MCP vs ZeroBounce
Machine-readable
- This page as Markdown
/compare/fullenrich-vs-leadmagic.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/fullenrich.json·/api/v1/tools/leadmagic.json - From a terminal
anchor compare fullenrich leadmagic(the CLI) - Over MCP
compare_tools {"a": "fullenrich", "b": "leadmagic"}at/mcp, no key