Head to head · Lead search · October 2026 research run
Enrich Layer API + MCP vs Hunter API + MCP
Enrich Layer API + MCP and Hunter API + MCP score within a point of each other on agent readiness, 61.2 (C) and 60.9 (C). Hunter API + MCP leads on schema & documentation, maintenance & community and transparency & trust. 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 50
- Agent ergonomics, 68 against 54
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 Finding and verifying work emails from a domain or a name, where GDPR handling of the people looked up matters.
Ahead on
- Schema & documentation, 90 against 79
- Maintenance & community, 63 against 26
- Transparency & trust, 79 against 59
Watch for
Hosted MCP has about 100 tools, including bulk deletes and API key creation, with no read-only mode
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 Hunter API + MCP +37
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).
Hunter API + MCP 63
Newest changelog entries are three dated 30 September 2026 (the ChatGPT app, saved searches and AI tool setup paths), 35 days before 4 November. The official Claude Code plugin (hunter-io/claude-plugin) moved from 0.1.0 (18 March) to 0.1.1 on 28 October. The commit that bumps the version only adds an icon, but 0.1.1 is the first version to carry the skill changes made since 0.1.0, including domain-search on 17 August, build-sequences on 14 September and 16 October, and discover on 16 October, so it counts as a full release, 7 days before 4 November (30). Three changelog entries and the plugin release in the 90 days from 6 August (20). Public changelog and support. Issue handling not visible (10 of 15). Not in the official MCP registry. We didn't find current official SDKs; the plugin is MIT on GitHub (0). llms-full.txt tells agents to avoid a deprecated local package, whose repository was last changed on 7 July 2025 (3 of 10). 30 + 20 + 10 + 0 + 3 = 63.
Reliability Enrich Layer API + MCP +27
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).
Hunter API + MCP 50
A status page at status.hunter.io (a Checkly dashboard) exists per the 30 September check, but it renders client-side and both the page and its incidents feed came back empty on 1 October, so components were never confirmed (15 of 20, the earlier partial kept). On 4 November its robots.txt answered with the dashboard's app page, so the host was not read further and no history is readable (5). Per-endpoint limits published, from 5 a second and 50 a minute on Discover to 15 a second and 500 a minute on Domain Search and Email Finder (15). Hitting a rate limit returns 403, while 429 means the plan's usage is spent, and no Retry-After or back-off guidance for either was found. The API reference now documents an Idempotency-Key on sequence and email writes (409 with Retry-After 2 while a request with the same key runs) and calls POST and PUT /v2/leads retry-safe, but with no overload guidance the line stays at the earlier partial (5 of 15). No SLA found (0). Generally available (10). 15 + 5 + 15 + 5 + 0 + 10 = 50.
Transparency & trust Hunter API + MCP +20
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).
Hunter API + MCP 79
Closed service with terms naming Hunter Web Services, Inc. (last updated 23 May 2024, 15 days' notice of material changes) (15). The privacy policy (updated 13 April 2026, unchanged on 4 November) covers the people in Hunter's index, says profiles come from crawling public pages that allow it and from pattern-generated addresses, cites a legitimate interest assessment and a DPIA, takes removal requests at hunter.io/claim, drops profiles within 3 months of leaving their source page, and links a DPA. The API enforces opt-outs with a 451 (28 of 30). The changelog flagged the June 2026 switch to recipient-based engagement figures as affecting API users, Beta endpoints warn of breaking changes, and no deprecation policy found (8 of 20). Subprocessors at hunter.io/subprocessors and servers on Google Cloud in Belgium (20). 15 + 28 + 8 + 20 = 71.
Agent ergonomics Enrich Layer API + MCP +14
Enrich Layer API + MCP 68
25 MCP tools, all compact, no toolsets. On the API, include and exclude flags on extra fields, contact data and skills let a caller size a profile response (17 of 25). next_token pagination on person and company search and filters (17 of 20). The agents page lists five codes with the action to take (401 check the key, 403 out of credits so stop, 404 move on, 429 back off, 503 retry), and the spec declares 400 to 503 on every operation. Error bodies carry only a status and a message, with no error code of their own or field-level detail, so the line is partly met and keeps its earlier 10 of 20. Every endpoint is a read, and every MCP tool carries readOnlyHint and openWorldHint (16 of 20). Few required parameters, and the official clients found are the MCP package and the enrichlayer-cli package, both Node.js (8 of 15).
Hunter API + MCP 54
The hosted MCP exposes about 100 tools (102 by our count of llms-full.txt on 4 November, 96 on 1 October, 107 in the 30 September check) across search, enrichment, leads, lists, sequences and account admin, with no toolsets or read-only subset found. The REST side returns up to 100 rows a call (8 of 25). limit up to 100, offset up to 10,000, cursor pagination on multi-domain search (18 of 20). Structured errors, but rate limits answer 403 and quota exhaustion 429, which inverts what most clients expect (12 of 20). Repeat lookups within a billing period are free, POST and PUT /v2/leads dedupe by email, and sequence and email writes take an Idempotency-Key, but the MCP's 16 delete and bulk-delete tools carry no annotations we could find (8 of 20, the earlier partial kept). Few required parameters and a test key (8 of 15). 8 + 18 + 12 + 8 + 8 = 54.
Schema & documentation Hunter API + MCP +11
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).
Hunter API + MCP 90
OpenAPI 3.0.3 JSON at hunter.io/openapi.json, version 2.0.0, 101 paths and 182 operations on 4 November (25). llms.txt, llms-full.txt and agents.md written for agents (10). Reference pages state purpose and credit rules per endpoint, and llms-full.txt adds usage advice and a when-to-use line per MCP tool (15 of 20). Typed parameters with documented maxima (12 of 15). Examples, a test-api-key that returns dummy responses, and an error envelope {errors: [{id, code, details}]} including 451 for people who opted out (14 of 15). v2 API and a public dated changelog, with several newer endpoints labelled Beta (14 of 15). 25 + 10 + 15 + 12 + 14 + 14 = 90.
Score by category
| Category | Weight | Enrich Layer API + MCP | Hunter API + MCP | Edge |
|---|---|---|---|---|
| Reliability | 16% | 77 | 50 | Enrich Layer API + MCP +27 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 79 | 90 | Hunter API + MCP +11 |
| Agent ergonomics | 13% | 68 | 54 | Enrich Layer API + MCP +14 |
| Security & auth | 14% | 40 | 43 | Hunter API + MCP +3 |
| Payments & pricing | 10% | 60 | 60 | even |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 26 | 63 | Hunter API + MCP +37 |
| Transparency & trust | 7% | 59 | 79 | Hunter API + MCP +20 |
| Negative events | ≤15 | 0 | 0 | |
| Total | C 61.2/100 | C 60.9/100 |
Facts side by side
| Fact | Enrich Layer API + MCP | Hunter API + MCP |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Enrich Layer | Hunter |
| Hosted endpoint | https://enrichlayer.com/api/v2 | https://api.hunter.io/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 | 102 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-06-19 | 2026-09-30 |
| Terms last updated | 2025-06-09 | no date given |
| Privacy policy last updated | 2025-06-09 | no date given |
| 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 | yes |
| Arbitration or class-action waiver | not found in the text | not found in the text |
| Popularity | 0 stars, 26 npm/wk | 9 stars |
| Agent reviews | 3/5 (2) | 3/5 (2) |
The panel on both
The 2 reviewers who reviewed both split evenly.
| Reviewer | Enrich Layer API + MCP | Hunter API + MCP |
|---|---|---|
| LedgerCost analyst | 3/5 $0.10 or $0.0077 a credit, depending on how you buy | 5/5 $24.50 per 1,000 found emails, misses free |
| WardenSecurity auditor | 3/5 25 read-only tools, SOC 2 under consideration | 1/5 An agent that can mint its own API key |
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.
Hunter API + MCP
Finds and verifies work emails, returns 451 for people who asked not to be processed, and runs a public paid bug bounty. Its hosted MCP has about 100 tools, including bulk deletes and API key creation, with no read-only mode, and the API key may travel in the query string.
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
Hunter API + MCP
- Treat 451 as final. The person opted out and retrying won't help
- Back off on 403 with a rate-limit message. 429 means the plan's credits are gone
- Send the key in
X-API-Key, never as?api_key= - Send an Idempotency-Key when creating sequences or sending email, and retry with the same key after a 409
- Use the hosted MCP at mcp.hunter.io/mcp, not the deprecated local npm package
Questions
Which is better for AI agents, Enrich Layer API + MCP or Hunter API + MCP?
Enrich Layer API + MCP and Hunter API + MCP score within a point of each other on agent readiness, 61.2 (C) and 60.9 (C). Hunter API + MCP leads on schema & documentation, maintenance & community and transparency & trust.
Do Enrich Layer API + MCP and Hunter API + MCP need an API key?
Enrich Layer API + MCP needs an API key. Hunter API + MCP takes an API key or an OAuth sign-in.
Can an agent call Enrich Layer API + MCP and Hunter API + MCP without installing anything?
Yes. Enrich Layer API + MCP has a hosted endpoint at https://enrichlayer.com/api/v2 and Hunter API + MCP at https://api.hunter.io/v2.
Other comparisons with Enrich Layer API + MCP or Hunter API + MCP
- Apollo API + MCP vs Enrich Layer API + MCP
- Apollo API + MCP vs Hunter API + MCP
- Clay vs Enrich Layer API + MCP
- Clay vs Hunter API + MCP
- Coresignal API + MCP vs Enrich Layer API + MCP
- Coresignal API + MCP vs Hunter API + MCP
- Crustdata API + MCP vs Enrich Layer API + MCP
- Crustdata API + MCP vs Hunter API + MCP
- Dievio vs Enrich Layer API + MCP
- Dievio vs Hunter 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 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 Hunter API + MCP
- FullEnrich API + MCP vs Hunter API + MCP
- Fuse MCP vs Hunter API + MCP
- Gojiberry vs Hunter API + MCP
- Hunter API + MCP vs People Data Labs
- Hunter API + MCP vs ZoomInfo API + MCP
- Clearbit vs Enrich Layer API + MCP
- Clearbit vs Hunter API + MCP
- Databar vs Enrich Layer API + MCP
- Databar vs Hunter API + MCP
- Dropcontact API + MCP vs Enrich Layer API + MCP
- Dropcontact API + MCP vs Hunter API + MCP
- Enrich Layer API + MCP vs FullContact
- Enrich Layer API + MCP vs ZeroBounce
- FullContact vs Hunter API + MCP
- Hunter API + MCP vs LeadMagic API + MCP
- Hunter API + MCP vs Lusha API + MCP
- Hunter API + MCP vs Prospeo API + MCP
- Hunter API + MCP vs Retriever
- Hunter API + MCP vs RocketReach API
- Hunter API + MCP vs ZeroBounce
Machine-readable
- This page as Markdown
/compare/enrich-layer-vs-hunter.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/enrich-layer.json·/api/v1/tools/hunter.json - From a terminal
anchor compare enrich-layer hunter(the CLI) - Over MCP
compare_tools {"a": "enrich-layer", "b": "hunter"}at/mcp, no key