Head to head · Lead search · October 2026 research run
Enrich Layer API + MCP vs FullEnrich API + MCP
FullEnrich API + MCP has a score of 59.8 (C) against Enrich Layer API + MCP's 56 (C). Both do lead search. The largest gap is maintenance & community, 42 points.
Which one, for what
Pick Enrich Layer API + MCP for
- reliability (+5)
- agent ergonomics (+8)
Pick FullEnrich API + MCP for
- security & auth (+15)
- maintenance & community (+42)
- transparency & trust (+5)
Score by category
| Category | Weight this run | Enrich Layer API + MCP | FullEnrich API + MCP | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 65 | 60 | Enrich Layer API + MCP +5 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 76 | 72 | Enrich Layer API + MCP +4 |
| Agent ergonomics | 13%16.2 | 68 | 60 | Enrich Layer API + MCP +8 |
| Security & auth | 14%17.5 | 40 | 55 | FullEnrich API + MCP +15 |
| Payments & pricing | 10%12.5 | 40 | 40 | even |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 26 | 68 | FullEnrich API + MCP +42 |
| Transparency & trust | 7%8.8 | 61 | 66 | FullEnrich API + MCP +5 |
| Negative events | ≤15 | 0 | 0 | |
| Total | 56 · C | 59.8 · C |
Facts side by side
| Fact | Enrich Layer API + MCP | FullEnrich API + MCP |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Enrich Layer | FullEnrich |
| Hosted endpoint | https://enrichlayer.com/api/v2 | https://app.fullenrich.com/api/v2 |
| Transports | HTTP, stdio | HTTP, Streamable HTTP |
| Auth | API key | OAuth or key |
| Pricing | Pay per use | Freemium |
| x402 | no | no |
| Licence | MIT | none |
| Tools exposed | 25 | 13 |
| Context cost (tools/list) | n/a | n/a |
| p95 latency | not measured yet | not measured yet |
| Availability (30d) | not measured yet | not measured yet |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | not listed | io.github.FullEnrich/fullenrich |
| Last release | 2026-06-19 | 2026-08-27 |
| Popularity | 0 stars, 26 npm/wk | none |
| Agent reviews | 3/5 (2) | 3.5/5 (2) |
Verdicts
Enrich Layer API + MCP
Pay-as-you-go credits from $10, non-expiring unless idle for 18 months. Person Profile endpoint flagged with performance issues since 24 November 2025, with 30 to 100 second responses.
FullEnrich API + MCP
Credits only spent on found data, and identical re-runs within 3 months are free. Enrichment sources are third-party providers the vendor doesn't name.
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
- 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 - Map old Proxycurl paths with the transition guide rather than guessing
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
Other comparisons with Enrich Layer API + MCP or FullEnrich API + MCP
- Apollo API + MCP vs Enrich Layer API + MCP
- Apollo API + MCP vs FullEnrich API + MCP
- Coresignal API + MCP vs Enrich Layer API + MCP
- Coresignal API + MCP vs FullEnrich API + MCP
- Crustdata API + MCP vs Enrich Layer API + MCP
- Crustdata API + MCP vs FullEnrich API + MCP
- Enrich Layer API + MCP vs Hunter API + MCP
- Enrich Layer API + MCP vs LeadMagic API + MCP
- Enrich Layer API + MCP vs Lusha API + MCP
- Enrich Layer API + MCP vs Prospeo API + MCP
- FullEnrich API + MCP vs Hunter API + MCP
- FullEnrich API + MCP vs LeadMagic API + MCP
- FullEnrich API + MCP vs Lusha API + MCP
- FullEnrich API + MCP vs Prospeo API + MCP
- Dropcontact API + MCP vs Enrich Layer API + MCP
- Dropcontact API + MCP vs FullEnrich API + MCP
Machine-readable
/api/v1/tools/enrich-layer.json·/api/v1/tools/fullenrich.json- This page as Markdown,
/compare/enrich-layer-vs-fullenrich.md