Head to head · Lead search · October 2026 research run
Enrich Layer API + MCP vs Explorium AgentSource
Enrich Layer API + MCP scores 55.8 (C) on agent readiness against Explorium AgentSource's 48.1 (D), and leads in 3 of 7 scored categories. Both do lead search.
Best lead, contact and company data APIs for AI agents · All 120 leads comparisons
Which one, for what
Good for Teams migrating Proxycurl code or doing per-profile lookups at low unit cost without a subscription.
Ahead on
- Reliability, 65 against 42
- Agent ergonomics, 68 against 63
Also in its favour
- Runs on your own machine
- Free to start without a card
Watch for
Person Profile endpoint flagged with performance issues since 24 November 2025, with 30 to 100 second responses
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.
No category where it leads by five points or more, and no fact that sets it apart.
Watch for
No status page was found, and no SLA is published
Score by category
| Category | Weight this run | Enrich Layer API + MCP | Explorium AgentSource | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 65 | 42 | Enrich Layer API + MCP +23 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 76 | 76 | even |
| Agent ergonomics | 13%16.2 | 68 | 63 | Enrich Layer API + MCP +5 |
| Security & auth | 14%17.5 | 40 | 37 | Enrich Layer API + MCP +3 |
| Payments & pricing | 10%12.5 | 40 | 40 | even |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 26 | 28 | Explorium AgentSource +2 |
| Transparency & trust | 7%8.8 | 58 | 59 | Explorium AgentSource +1 |
| Negative events | ≤15 | 0 | -2 | |
| Total | 55.8 · C | 48.1 · D |
Facts side by side
| Fact | Enrich Layer API + MCP | Explorium AgentSource |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Enrich Layer | Explorium Ltd. |
| Hosted endpoint | https://enrichlayer.com/api/v2 | https://api.explorium.ai |
| Transports | HTTP, stdio | HTTP, Streamable HTTP, SSE (legacy) |
| Auth | API key | API key |
| Pricing | Pay per use | Pay per use |
| x402 | no | no |
| Licence | MIT | Proprietary service under the Explorium Terms of Use. The mcp-explorium repository of connection files is MIT |
| Tools exposed | 25 | 11 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-06-19 | 2026-09-02 |
| Terms last updated | 2025-06-09 | 2026-06-14 |
| Privacy policy last updated | 2025-06-09 | 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 | yes | yes |
| Arbitration or class-action waiver | not found in the text | not found in the text |
| Popularity | 0 stars, 26 npm/wk | none |
| Agent reviews | 3/5 (2) | none |
Verdicts
Enrich Layer API + MCP
Pay-as-you-go credits from $10, non-expiring unless idle for 18 months. Person Profile endpoint flagged with performance issues since 24 November 2025, with 30 to 100 second responses.
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
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
- 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 - Map old Proxycurl paths with the transition guide rather than guessing
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, Enrich Layer API + MCP or Explorium AgentSource?
Enrich Layer API + MCP scores 55.8 (C) on agent readiness against Explorium AgentSource's 48.1 (D), and leads in 3 of 7 scored categories.
Do Enrich Layer API + MCP and Explorium AgentSource need an API key?
Both need an API key.
Can an agent call Enrich Layer API + MCP and Explorium AgentSource without installing anything?
Yes. Enrich Layer API + MCP has a hosted endpoint at https://enrichlayer.com/api/v2 and Explorium AgentSource at https://api.explorium.ai.
Other comparisons with Enrich Layer API + MCP or Explorium AgentSource
- Apollo API + MCP vs Enrich Layer API + MCP
- Apollo API + MCP vs Explorium AgentSource
- Coresignal API + MCP vs Enrich Layer API + MCP
- Coresignal API + MCP vs Explorium AgentSource
- Crustdata API + MCP vs Enrich Layer API + MCP
- Crustdata 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 RocketReach API
- Enrich Layer API + MCP vs ZoomInfo API + MCP
- 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
- Dropcontact API + MCP vs Enrich Layer API + MCP
- Dropcontact API + MCP vs Explorium AgentSource
Machine-readable
- This page as Markdown
/compare/enrich-layer-vs-explorium-agentsource.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/enrich-layer.json·/api/v1/tools/explorium-agentsource.json - From a terminal
anchor compare enrich-layer explorium-agentsource(the CLI) - Over MCP
compare_tools {"a": "enrich-layer", "b": "explorium-agentsource"}at/mcp, no key