Head to head · Lead search · October 2026 research run
Enrich Layer API + MCP vs FullEnrich API + MCP
FullEnrich API + MCP scores 64.7 (B) on agent readiness against Enrich Layer API + MCP's 61.2 (C), and leads in 3 of 7 scored categories. Enrich Layer API + MCP leads on reliability. 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 70
Also in its favour
- Runs on your own machine
Watch for
Person Profile endpoint flagged with performance issues since 24 November 2025, with 30 to 100 second responses
Best for Maximising find rate on known contacts, especially mobiles, without a long-term contract.
Ahead on
- Security & auth, 57 against 40
- Maintenance & community, 48 against 26
- Transparency & trust, 68 against 59
Also in its favour
- Rated higher by the reviewer agents, 3.5 against 3.0 out of 5
Watch for
Enrichment sources are data providers the vendor doesn't name
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 FullEnrich API + MCP +22
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).
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.
Security & auth FullEnrich API + MCP +17
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).
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.
Transparency & trust FullEnrich API + MCP +9
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).
FullEnrich API + MCP 68
Closed service with terms naming FullEnrich Corp. The skills and registry repo is MIT (15). The privacy policy (updated 20 August 2026, per the 1 October check) gives retention periods (3 years from last contact for prospects, 25 months for service improvement), legal bases and SCC or DPF transfers, and points rights requests to support@fullenrich.com. It doesn't say whether people returned by enrichment are covered, and the trust page says enrichment uses data providers it doesn't name, most acting as independent controllers. An opt-out page exists at fullenrich.com/optout (18 of 30). v1 and v2 APIs run side by side with no dated deprecation found (3 of 20). A sub-processor list is published, and the trust page now states that the hosting provider, DigitalOcean, hosts data in the European Union, with transfers outside the EEA disclosed (20 of 20; was 14 with hosting locations not stated). 15+18+3+20 = 56.
Reliability Enrich Layer API + MCP +7
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).
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.
Score by category
| Category | Weight | Enrich Layer API + MCP | FullEnrich API + MCP | Edge |
|---|---|---|---|---|
| Reliability | 16% | 77 | 70 | Enrich Layer API + MCP +7 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 79 | 76 | Enrich Layer API + MCP +3 |
| Agent ergonomics | 13% | 68 | 66 | Enrich Layer API + MCP +2 |
| Security & auth | 14% | 40 | 57 | FullEnrich API + MCP +17 |
| Payments & pricing | 10% | 60 | 60 | even |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 26 | 48 | FullEnrich API + MCP +22 |
| Transparency & trust | 7% | 59 | 68 | FullEnrich API + MCP +9 |
| Negative events | ≤15 | 0 | 0 | |
| Total | C 61.2/100 | B 64.7/100 |
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 |
| 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 |
| Terms last updated | 2025-06-09 | 2026-08-20 |
| Privacy policy last updated | 2025-06-09 | 2026-08-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 | not found in the text |
| Terms restrict benchmarking | not found in the text | yes |
| Terms or service can change without notice | yes | not found in the text |
| 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 FullEnrich API + MCP higher.
| Reviewer | Enrich Layer API + MCP | FullEnrich API + MCP |
|---|---|---|
| LedgerCost analyst | 3/5 $0.10 or $0.0077 a credit, depending on how you buy | 4/5 Charged on found data only, $0.055 a credit |
| WardenSecurity auditor | 3/5 25 read-only tools, SOC 2 under consideration | 3/5 Webhooks signed with the API key itself |
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.
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.
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
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
Questions
Which is better for AI agents, Enrich Layer API + MCP or FullEnrich API + MCP?
FullEnrich API + MCP scores 64.7 (B) on agent readiness against Enrich Layer API + MCP's 61.2 (C), and leads in 3 of 7 scored categories. Enrich Layer API + MCP leads on reliability.
Do Enrich Layer API + MCP and FullEnrich API + MCP need an API key?
Enrich Layer API + MCP needs an API key. FullEnrich API + MCP takes an API key or an OAuth sign-in.
Can an agent call Enrich Layer API + MCP and FullEnrich API + MCP without installing anything?
Yes. Enrich Layer API + MCP has a hosted endpoint at https://enrichlayer.com/api/v2 and FullEnrich API + MCP at https://app.fullenrich.com/api/v2.
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
- Clay vs Enrich Layer API + MCP
- Clay 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
- Dievio vs Enrich Layer API + MCP
- Dievio vs FullEnrich API + MCP
- Enrich Layer API + MCP vs Explorium AgentSource
- 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 LeadMagic 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 FullEnrich API + MCP
- FullEnrich API + MCP vs Fuse MCP
- FullEnrich API + MCP vs Gojiberry
- 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 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
- Clearbit vs Enrich Layer API + MCP
- Clearbit vs FullEnrich API + MCP
- Databar vs Enrich Layer API + MCP
- Databar vs FullEnrich API + MCP
- Dropcontact API + MCP vs Enrich Layer API + MCP
- Dropcontact API + MCP vs FullEnrich API + MCP
- Enrich Layer API + MCP vs FullContact
- Enrich Layer API + MCP vs ZeroBounce
- FullContact vs FullEnrich API + MCP
- FullEnrich API + MCP vs ZeroBounce
Machine-readable
- This page as Markdown
/compare/enrich-layer-vs-fullenrich.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/enrich-layer.json·/api/v1/tools/fullenrich.json - From a terminal
anchor compare enrich-layer fullenrich(the CLI) - Over MCP
compare_tools {"a": "enrich-layer", "b": "fullenrich"}at/mcp, no key