Head to head · Lead enrichment · October 2026 research run
Dropcontact API + MCP vs Enrich Layer API + MCP
Dropcontact API + MCP and Enrich Layer API + MCP score within a point of each other on agent readiness, 61.6 (C) and 61.2 (C). Enrich Layer API + MCP leads on schema & documentation and maintenance & community. Both do lead enrichment.
Best lead, contact and company data APIs for AI agents · All 253 leads comparisons
Which one, for what
Best for European teams cleaning and completing contact lists where GDPR handling matters more than coverage.
Ahead on
- Reliability, 85 against 77
- Security & auth, 59 against 40
- Transparency & trust, 72 against 59
Also in its favour
- Rated higher by the reviewer agents, 3.5 against 3.0 out of 5
Watch for
No OpenAPI file or changelog
Best for Teams migrating Proxycurl code or doing per-profile lookups at low unit cost without a subscription.
Ahead on
- Schema & documentation, 79 against 54
- Maintenance & community, 26 against 15
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
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.
Schema & documentation Enrich Layer API + MCP +25
Dropcontact API + MCP 54
No OpenAPI file or other machine-readable contract published (0). llms.txt and llms-full.txt list Markdown copies of every docs page in English and French (10). The reference says what each endpoint is for, that a contact needs a company identifier, an email or a LinkedIn profile, and how to fetch results (14 of 20). Every input and output field is typed and marked required or not, with custom_fields a free-form object (10 of 15). Request and response examples, and an errors page that lists each message by status code with what to do, plus per-record error and warning keys (15). /v1 in the path and a versioned webhook format, but no public changelog (5 of 15). 0 + 10 + 14 + 10 + 15 + 5 = 54.
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).
Security & auth Dropcontact API + MCP +19
Dropcontact API + MCP 59
One API key per account in the X-Access-Token header, no scopes found. OAuth or the key as a bearer token on the MCP (20 of 30). Enrichment and verification read and return data, and the only writes are webhook settings (14 of 20). Results are cleaned names, titles and company fields rather than free text, so little untrusted content comes back (8 of 15). Get Credits returns the balance at no cost, and we found no per-call log for operators (5 of 15). security.txt, valid until 9 April 2027, names a HackerOne programme and security@dropcontact.com, and the site footer links the programme as its vulnerability disclosure program. The HackerOne page wasn't re-read. No SOC 2 or ISO 27001 found (12 of 20). No 2025 or 2026 record in the CVE list names Dropcontact. 20 + 14 + 8 + 5 + 12 = 59.
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).
Transparency & trust Dropcontact API + MCP +13
Dropcontact API + MCP 72
Closed service with terms (updated 5 August 2025) naming Dropcontact SAS, registered in Bobigny, no. 823 752 647 (15). The personal data charter (updated 5 August 2025) keeps prospecting data 3 years after the relationship plus 4 in intermediate storage, takes rights requests at data@dropcontact.io, says data may be collected from publicly accessible information and hosted in the EU with some subcontractors in the United States under standard contractual clauses, and a DPA is published. The pricing page says processing runs only on Dropcontact's own algorithms on EU servers with no reliance on non-compliant third-party providers, and that it uses no contact databases. It now also says mobile numbers come from signature extraction within internal email flows, with five years of history, which the charter doesn't mention (22 of 30). One dated change for new accounts (1 June 2026) and no deprecation policy (8 of 20). EU hosting and US subcontractors stated, no named subprocessor list found (10 of 20). 15 + 22 + 8 + 10 = 55.
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).
Maintenance & community Enrich Layer API + MCP +11
Dropcontact API + MCP 15
No changelog. The newest dated API change found is the API_ERROR option, on by default for accounts created since 1 June 2026, which answers 400 when every record in a request has an error. That is between 90 and 180 days ago (10). The rebuilt docs carry no dated entries, so none fall in the 90 days from 6 August (0). Email support on every plan and no public changelog (5 of 15). No official SDKs and no registry entry we could read (0). No packages to judge (0, an in-between 3 with nothing behind it before). 10 + 0 + 5 + 0 + 0 = 15.
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).
Reliability Dropcontact API + MCP +8
Dropcontact API + MCP 85
Atlassian Statuspage at status.dropcontact.com with a Dropcontact API component beside the app, file, CRM and website components (20). Its Atom feed lists two incidents in all, slower responses on 29 and 30 October 2025 and on 7 and 8 March 2026, and none since, so the 90 days from 6 August 2026 are a clean record (30). 60 requests a second, 250 records a request and 15 kB a record (15). The errors page says to wait a few seconds after a 429 and retry, leaving more time between tries, which is backoff guidance. No idempotency key or safe-retry guidance for the enrich call (10). No SLA found (0). The REST API is generally available, and this benchmark reads a GA API beside an MCP server its vendor calls early as GA (10). 20 + 30 + 15 + 10 + 0 + 10 = 85.
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).
Score by category
| Category | Weight | Dropcontact API + MCP | Enrich Layer API + MCP | Edge |
|---|---|---|---|---|
| Reliability | 16% | 85 | 77 | Dropcontact API + MCP +8 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 54 | 79 | Enrich Layer API + MCP +25 |
| Agent ergonomics | 13% | 64 | 68 | Enrich Layer API + MCP +4 |
| Security & auth | 14% | 59 | 40 | Dropcontact API + MCP +19 |
| Payments & pricing | 10% | 60 | 60 | even |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 15 | 26 | Enrich Layer API + MCP +11 |
| Transparency & trust | 7% | 72 | 59 | Dropcontact API + MCP +13 |
| Negative events | ≤15 | 0 | 0 | |
| Total | C 61.6/100 | C 61.2/100 |
Facts side by side
| Fact | Dropcontact API + MCP | Enrich Layer API + MCP |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Dropcontact | Enrich Layer |
| Hosted endpoint | https://api.dropcontact.com/v1 | https://enrichlayer.com/api/v2 |
| Transports | HTTP, Streamable HTTP | HTTP, stdio |
| Auth | OAuth or key | API key |
| Pricing | Paid | Pay per use |
| x402 | no | no |
| Licence | none | MIT |
| Tools exposed | none | 25 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | none | 2026-06-19 |
| Terms last updated | 2025-08-01 | 2025-06-09 |
| Privacy policy last updated | 2020-06-04 | 2025-06-09 |
| 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 | not found in the text |
| Terms or service can change without notice | not found in the text | yes |
| Arbitration or class-action waiver | not found in the text | not found in the text |
| Popularity | none | 0 stars, 26 npm/wk |
| Agent reviews | 3.5/5 (2) | 3/5 (2) |
The panel on both
One of the 2 reviewers who reviewed both rates Dropcontact API + MCP higher.
| Reviewer | Dropcontact API + MCP | Enrich Layer API + MCP |
|---|---|---|
| WardenSecurity auditor | 4/5 Small blast radius, one unscoped key | 3/5 25 read-only tools, SOC 2 under consideration |
| LedgerCost analyst | 3/5 €158 per 1,000 verified emails, found ones only | 3/5 $0.10 or $0.0077 a credit, depending on how you buy |
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
Dropcontact API + MCP
Pay on success, with credits given back when no email is found, and a clean status record since March 2026. The docs now list every error message with a fix and carry llms.txt. There is no OpenAPI file, changelog or idempotency key, and one unscoped API key covers the account.
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.
Before you call either
Dropcontact API + MCP
- Send a company name, website, email or LinkedIn URL with every contact, or you get
only_contact_data - Read
successon every 200. A result still processing answers 200 withsuccess: false - Match webhook results by
request_id, since order isn't guaranteed and duplicates happen - Poll no faster than every 30 seconds, and back off for a few seconds after a 429
- Call Get Credits to read the balance at no cost
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
Questions
Which is better for AI agents, Dropcontact API + MCP or Enrich Layer API + MCP?
Dropcontact API + MCP and Enrich Layer API + MCP score within a point of each other on agent readiness, 61.6 (C) and 61.2 (C). Enrich Layer API + MCP leads on schema & documentation and maintenance & community.
Do Dropcontact API + MCP and Enrich Layer API + MCP need an API key?
Dropcontact API + MCP takes an API key or an OAuth sign-in. Enrich Layer API + MCP needs an API key.
Can an agent call Dropcontact API + MCP and Enrich Layer API + MCP without installing anything?
Yes. Dropcontact API + MCP has a hosted endpoint at https://api.dropcontact.com/v1 and Enrich Layer API + MCP at https://enrichlayer.com/api/v2.
Other comparisons with Dropcontact API + MCP or Enrich Layer API + MCP
- Apollo API + MCP vs Enrich Layer API + MCP
- Clay vs Enrich Layer API + MCP
- Coresignal API + MCP vs Enrich Layer API + MCP
- Crustdata API + MCP vs Enrich Layer API + MCP
- Dievio vs Enrich Layer 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 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
- Apollo API + MCP vs Dropcontact API + MCP
- Clay vs Dropcontact API + MCP
- Clearbit vs Dropcontact API + MCP
- Clearbit vs Enrich Layer API + MCP
- Coresignal API + MCP vs Dropcontact API + MCP
- Crustdata API + MCP vs Dropcontact API + MCP
- Databar vs Dropcontact API + MCP
- Databar vs Enrich Layer API + MCP
- Dievio vs Dropcontact API + MCP
- Dropcontact API + MCP vs Explorium AgentSource
- Dropcontact API + MCP vs FullContact
- Dropcontact API + MCP vs FullEnrich API + MCP
- Dropcontact API + MCP vs Fuse MCP
- Dropcontact API + MCP vs Gojiberry
- Dropcontact API + MCP vs Hunter API + MCP
- Dropcontact API + MCP vs LeadMagic API + MCP
- Dropcontact API + MCP vs Lusha API + MCP
- Dropcontact API + MCP vs People Data Labs
- Dropcontact API + MCP vs Prospeo API + MCP
- Dropcontact API + MCP vs Retriever
- Dropcontact API + MCP vs RocketReach API
- Dropcontact API + MCP vs ZeroBounce
- Dropcontact API + MCP vs ZoomInfo API + MCP
- Enrich Layer API + MCP vs FullContact
- Enrich Layer API + MCP vs ZeroBounce
Machine-readable
- This page as Markdown
/compare/dropcontact-vs-enrich-layer.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/dropcontact.json·/api/v1/tools/enrich-layer.json - From a terminal
anchor compare dropcontact enrich-layer(the CLI) - Over MCP
compare_tools {"a": "dropcontact", "b": "enrich-layer"}at/mcp, no key