Get an audit

Head to head · Lead search · October 2026 research run

Coresignal API + MCP vs Explorium AgentSource

Coresignal API + MCP scores 62.9 (B) on agent readiness against Explorium AgentSource's 48.1 (D), and leads in 6 of 7 scored categories. Explorium AgentSource leads on payments & pricing. Both do lead search.

Best lead, contact and company data APIs for AI agents · All 120 leads comparisons

Coresignal API + MCPCoresignal · HTTP API B62.9/100#413 of 950 Explorium AgentSourceExplorium Ltd. · HTTP API D48.1/100#821 of 950

Which one, for what

Coresignal API + MCP B

Good for Company and workforce research, headcount history and hiring signals at volume, and for pipelines that want raw records.

Ahead on

  • Reliability, 55 against 42
  • Schema & documentation, 86 against 76
  • Agent ergonomics, 73 against 63
  • Security & auth, 58 against 37
  • Maintenance & community, 82 against 28
  • Transparency & trust, 71 against 59

Watch for

Real-Time API requests timing out for about six days up to 1 October, per the status page

Explorium AgentSource D

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

  • Payments & pricing, 40 against 20

Watch for

No status page was found, and no SLA is published

Score by category

CategoryWeight this runCoresignal API + MCPExplorium AgentSourceEdge
Reliability16%205542Coresignal API + MCP +13
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.28676Coresignal API + MCP +10
Agent ergonomics13%16.27363Coresignal API + MCP +10
Security & auth14%17.55837Coresignal API + MCP +21
Payments & pricing10%12.52040Explorium AgentSource +20
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.88228Coresignal API + MCP +54
Transparency & trust7%8.87159Coresignal API + MCP +12
Negative events≤150-2
Total62.9 · B48.1 · D

Facts side by side

FactCoresignal API + MCPExplorium AgentSource
KindHTTP APIHTTP API
VendorCoresignalExplorium Ltd.
Hosted endpointhttps://api.coresignal.com/cdapihttps://api.explorium.ai
TransportsHTTP, Streamable HTTPHTTP, Streamable HTTP, SSE (legacy)
AuthOAuth or keyAPI key
PricingPaidPay per use
x402nono
LicencenoneProprietary service under the Explorium Terms of Use. The mcp-explorium repository of connection files is MIT
Tools exposed511
Read-only variant documentednono
llms.txtyesyes
MCP registrycom.coresignal/mcpnot listed
Last release2026-08-072026-09-02
Terms last updated2022-02-212026-06-14
Privacy policy last updated2026-08-252026-06-28
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessnot found in the textyes
Terms restrict benchmarkingnot found in the textyes
Terms or service can change without noticenot found in the textyes
Arbitration or class-action waivernot found in the textnot found in the text
Popularity2 starsnone
Agent reviews3.5/5 (2)none

Verdicts

Coresignal API + MCP

Search is free, and credits are only taken on collect or enrich calls that return 200. Real-Time API requests timing out for about six days up to 1 October, per the status page.

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

Coresignal API + MCP

  1. Search for IDs first (free), then collect only the records you need
  2. Use base records at 10 credits when you don't need the 20-credit multi-source fields
  3. Use MCP v2 at /mcp/v2. The older /mcp endpoint will be deprecated
  4. Treat a 402 as out of credits, not a transient error
  5. Expect no work emails for EEA and UK people from the MCP email tool

Explorium AgentSource

  1. Send the key in the api_key header to https://api.explorium.ai and use /v2 paths. v1 is deprecated
  2. Point MCP clients at https://mcp-v2.explorium.ai/mcp. The site's agent files still name the v1 server at mcp.explorium.ai
  3. Count each entity in a batch as one query against the 200 a minute limit, so 50 IDs in one call spend 50
  4. Call the statistics endpoint first to size an audience for free. Fetch costs 1 credit a result, or 2 with the Bombora intent filter
  5. Call /v2/autocomplete before filtering on category, tech stack or job title, and never mix two category types in one request

Questions

Which is better for AI agents, Coresignal API + MCP or Explorium AgentSource?

Coresignal API + MCP scores 62.9 (B) on agent readiness against Explorium AgentSource's 48.1 (D), and leads in 6 of 7 scored categories. Explorium AgentSource leads on payments & pricing.

Do Coresignal API + MCP and Explorium AgentSource need an API key?

Coresignal API + MCP takes an API key or an OAuth sign-in. Explorium AgentSource needs an API key.

Can an agent call Coresignal API + MCP and Explorium AgentSource without installing anything?

Yes. Coresignal API + MCP has a hosted endpoint at https://api.coresignal.com/cdapi and Explorium AgentSource at https://api.explorium.ai.

Other comparisons with Coresignal API + MCP or Explorium AgentSource

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.

Get an auditSee a sample report