Head to head · Lead enrichment · October 2026 research run
Dropcontact API + MCP vs Explorium AgentSource
Dropcontact API + MCP scores 50.9 (D) on agent readiness against Explorium AgentSource's 48.1 (D), and leads in 3 of 7 scored categories. Explorium AgentSource leads on schema & documentation and maintenance & community. Both do lead enrichment.
Best lead, contact and company data APIs for AI agents · All 120 leads comparisons
Which one, for what
Good for European teams cleaning and completing contact lists where GDPR handling matters more than coverage.
Ahead on
- Reliability, 57 against 42
- Security & auth, 59 against 37
- Transparency & trust, 71 against 59
Also in its favour
- Free to start without a card
Watch for
No OpenAPI spec, llms.txt or changelog
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
- Schema & documentation, 76 against 41
- Maintenance & community, 28 against 18
Watch for
No status page was found, and no SLA is published
Score by category
| Category | Weight this run | Dropcontact API + MCP | Explorium AgentSource | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 57 | 42 | Dropcontact API + MCP +15 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 41 | 76 | Explorium AgentSource +35 |
| Agent ergonomics | 13%16.2 | 60 | 63 | Explorium AgentSource +3 |
| Security & auth | 14%17.5 | 59 | 37 | Dropcontact API + MCP +22 |
| Payments & pricing | 10%12.5 | 40 | 40 | even |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 18 | 28 | Explorium AgentSource +10 |
| Transparency & trust | 7%8.8 | 71 | 59 | Dropcontact API + MCP +12 |
| Negative events | ≤15 | 0 | -2 | |
| Total | 50.9 · D | 48.1 · D |
Facts side by side
| Fact | Dropcontact API + MCP | Explorium AgentSource |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Dropcontact | Explorium Ltd. |
| Hosted endpoint | https://api.dropcontact.com/v1 | https://api.explorium.ai |
| Transports | HTTP, Streamable HTTP | HTTP, Streamable HTTP, SSE (legacy) |
| Auth | OAuth or key | API key |
| Pricing | Paid | Pay per use |
| Price for lead enrichment | not published | $0.15 per record |
| x402 | no | no |
| Licence | none | Proprietary service under the Explorium Terms of Use. The mcp-explorium repository of connection files is MIT |
| Tools exposed | none | 11 |
| Read-only variant documented | no | no |
| llms.txt | no | yes |
| Last release | none | 2026-09-02 |
| Terms last updated | 2025-08-01 | 2026-06-14 |
| Privacy policy last updated | 2020-06-04 | 2026-06-28 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | not found in the text | yes |
| Terms restrict benchmarking | not found in the text | yes |
| 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 |
| Agent reviews | 3.5/5 (2) | none |
Verdicts
Dropcontact API + MCP
Pay on success, with credits refunded when no email is found. No OpenAPI spec, llms.txt or changelog.
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.
Before you call either
Dropcontact API + MCP
- Send a company name or website with every contact, or you get
only_contact_data - Send only documented fields. New accounts get a 400 for unknown ones
- Match webhook results by
request_id, since order isn't guaranteed and duplicates happen - Poll no faster than every 30 seconds, as the not-ready response asks
- Post an empty contact to read the credit balance at no cost
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
Questions
Which is better for AI agents, Dropcontact API + MCP or Explorium AgentSource?
Dropcontact API + MCP scores 50.9 (D) on agent readiness against Explorium AgentSource's 48.1 (D), and leads in 3 of 7 scored categories. Explorium AgentSource leads on schema & documentation and maintenance & community.
Do Dropcontact API + MCP and Explorium AgentSource need an API key?
Dropcontact API + MCP takes an API key or an OAuth sign-in. Explorium AgentSource needs an API key.
Can an agent call Dropcontact API + MCP and Explorium AgentSource without installing anything?
Yes. Dropcontact API + MCP has a hosted endpoint at https://api.dropcontact.com/v1 and Explorium AgentSource at https://api.explorium.ai.
Other comparisons with Dropcontact API + MCP or Explorium AgentSource
- Apollo API + MCP vs Explorium AgentSource
- Coresignal API + MCP vs Explorium AgentSource
- Crustdata API + MCP vs Explorium AgentSource
- Enrich Layer API + MCP vs Explorium AgentSource
- Explorium AgentSource vs FullEnrich API + MCP
- Explorium AgentSource vs Fuse MCP
- Explorium AgentSource vs Gojiberry
- Explorium AgentSource vs Hunter API + MCP
- 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
- Apollo API + MCP vs Dropcontact API + MCP
- Coresignal API + MCP vs Dropcontact API + MCP
- Crustdata API + MCP vs Dropcontact API + MCP
- Dropcontact API + MCP vs Enrich Layer API + MCP
- 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 RocketReach API
- Dropcontact API + MCP vs ZoomInfo API + MCP
Machine-readable
- This page as Markdown
/compare/dropcontact-vs-explorium-agentsource.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/dropcontact.json·/api/v1/tools/explorium-agentsource.json - From a terminal
anchor compare dropcontact explorium-agentsource(the CLI) - Over MCP
compare_tools {"a": "dropcontact", "b": "explorium-agentsource"}at/mcp, no key