Head to head · Lead search · October 2026 research run
Explorium AgentSource vs Hunter API + MCP
Hunter API + MCP scores 56.5 (C) on agent readiness against Explorium AgentSource's 48.1 (D), and leads in 4 of 7 scored categories. Explorium AgentSource leads on agent ergonomics. Both do lead search.
Best lead, contact and company data APIs for AI agents · All 120 leads comparisons
Which one, for what
Good for Agents that build prospect lists by filter and then enrich them, or that watch companies for events such as funding and role changes.
Ahead on
- Agent ergonomics, 63 against 54
Watch for
No status page was found, and no SLA is published
Good for Finding and verifying work emails from a domain or a name, where GDPR handling of the people looked up matters.
Ahead on
- Reliability, 50 against 42
- Schema & documentation, 90 against 76
- Maintenance & community, 63 against 28
- Transparency & trust, 78 against 59
Also in its favour
- Free to start without a card
Watch for
Hosted MCP has about 100 tools, including bulk deletes and API key creation, with no read-only mode
Score by category
| Category | Weight this run | Explorium AgentSource | Hunter API + MCP | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 42 | 50 | Hunter API + MCP +8 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 76 | 90 | Hunter API + MCP +14 |
| Agent ergonomics | 13%16.2 | 63 | 54 | Explorium AgentSource +9 |
| Security & auth | 14%17.5 | 37 | 33 | Explorium AgentSource +4 |
| Payments & pricing | 10%12.5 | 40 | 40 | even |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 28 | 63 | Hunter API + MCP +35 |
| Transparency & trust | 7%8.8 | 59 | 78 | Hunter API + MCP +19 |
| Negative events | ≤15 | -2 | 0 | |
| Total | 48.1 · D | 56.5 · C |
Facts side by side
| Fact | Explorium AgentSource | Hunter API + MCP |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Explorium Ltd. | Hunter |
| Hosted endpoint | https://api.explorium.ai | https://api.hunter.io/v2 |
| Transports | HTTP, Streamable HTTP, SSE (legacy) | HTTP, Streamable HTTP |
| Auth | API key | OAuth or key |
| Pricing | Pay per use | Freemium |
| x402 | no | no |
| Licence | Proprietary service under the Explorium Terms of Use. The mcp-explorium repository of connection files is MIT | none |
| Tools exposed | 11 | 107 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-09-02 | none |
| Terms last updated | 2026-06-14 | no date given |
| Privacy policy last updated | 2026-06-28 | no date given |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | yes | not found in the text |
| Terms restrict benchmarking | yes | 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 | none | 9 stars |
| Agent reviews | none | 3/5 (2) |
Verdicts
Explorium AgentSource
AgentSource v2 has a public OpenAPI 3.1 file, Markdown docs, a 200 queries a minute limit with Retry-After, public credit prices and a 100-credit trial. No status page or published SLA was found, each company shares one API key with no scopes, and the vendor's two published price tables disagree.
Hunter API + MCP
Returns 451 for people who asked not to be processed. Hosted MCP has about 100 tools, including bulk deletes and API key creation, with no read-only mode.
Before you call either
Explorium AgentSource
- Send the key in the
api_keyheader tohttps://api.explorium.aiand use/v2paths. v1 is deprecated - Point MCP clients at
https://mcp-v2.explorium.ai/mcp. The site's agent files still name the v1 server atmcp.explorium.ai - Count each entity in a batch as one query against the 200 a minute limit, so 50 IDs in one call spend 50
- Call the statistics endpoint first to size an audience for free. Fetch costs 1 credit a result, or 2 with the Bombora intent filter
- Call
/v2/autocompletebefore filtering on category, tech stack or job title, and never mix two category types in one request
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= - Use
test-api-keyto check request shapes without spending credits - Use the hosted MCP at mcp.hunter.io/mcp, not the deprecated local npm package
Questions
Which is better for AI agents, Explorium AgentSource or Hunter API + MCP?
Hunter API + MCP scores 56.5 (C) on agent readiness against Explorium AgentSource's 48.1 (D), and leads in 4 of 7 scored categories. Explorium AgentSource leads on agent ergonomics.
Do Explorium AgentSource and Hunter API + MCP need an API key?
Explorium AgentSource needs an API key. Hunter API + MCP takes an API key or an OAuth sign-in.
Can an agent call Explorium AgentSource and Hunter API + MCP without installing anything?
Yes. Explorium AgentSource has a hosted endpoint at https://api.explorium.ai and Hunter API + MCP at https://api.hunter.io/v2.
Other comparisons with Explorium AgentSource or Hunter API + MCP
- Apollo API + MCP vs Explorium AgentSource
- Apollo API + MCP vs Hunter API + MCP
- Coresignal API + MCP vs Explorium AgentSource
- Coresignal API + MCP vs Hunter API + MCP
- Crustdata API + MCP vs Explorium AgentSource
- Crustdata API + MCP vs Hunter API + MCP
- Enrich Layer API + MCP vs Explorium AgentSource
- Enrich Layer API + MCP vs Hunter API + MCP
- Explorium AgentSource vs FullEnrich API + MCP
- Explorium AgentSource vs Fuse MCP
- Explorium AgentSource vs Gojiberry
- Explorium AgentSource vs LeadMagic API + MCP
- Explorium AgentSource vs Lusha API + MCP
- Explorium AgentSource vs People Data Labs
- Explorium AgentSource vs Prospeo API + MCP
- Explorium AgentSource vs RocketReach API
- Explorium AgentSource vs ZoomInfo 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
- Dropcontact API + MCP vs Explorium AgentSource
- Dropcontact API + MCP 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 RocketReach API
Machine-readable
- This page as Markdown
/compare/explorium-agentsource-vs-hunter.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/explorium-agentsource.json·/api/v1/tools/hunter.json - From a terminal
anchor compare explorium-agentsource hunter(the CLI) - Over MCP
compare_tools {"a": "explorium-agentsource", "b": "hunter"}at/mcp, no key