Head to head · Lead search · October 2026 research run
Explorium AgentSource vs Prospeo API + MCP
Prospeo 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 reliability, schema & documentation and transparency & trust. 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
- Reliability, 42 against 35
- Schema & documentation, 76 against 61
- Transparency & trust, 59 against 42
Watch for
No status page was found, and no SLA is published
Good for An agent that searches for prospects and then enriches them with verified emails and mobiles in one cheap loop.
Ahead on
- Agent ergonomics, 79 against 63
- Security & auth, 54 against 37
- Maintenance & community, 34 against 28
Also in its favour
- Runs on your own machine
Watch for
No status page, SLA or changelog
Score by category
| Category | Weight this run | Explorium AgentSource | Prospeo API + MCP | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 42 | 35 | Explorium AgentSource +7 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 76 | 61 | Explorium AgentSource +15 |
| Agent ergonomics | 13%16.2 | 63 | 79 | Prospeo API + MCP +16 |
| Security & auth | 14%17.5 | 37 | 54 | Prospeo API + MCP +17 |
| 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 | 34 | Prospeo API + MCP +6 |
| Transparency & trust | 7%8.8 | 59 | 42 | Explorium AgentSource +17 |
| Negative events | ≤15 | -2 | 0 | |
| Total | 48.1 · D | 50.9 · D |
Facts side by side
| Fact | Explorium AgentSource | Prospeo API + MCP |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Explorium Ltd. | Prospeo |
| Hosted endpoint | https://api.explorium.ai | https://api.prospeo.io |
| Transports | HTTP, Streamable HTTP, SSE (legacy) | HTTP, Streamable HTTP, stdio |
| 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 | MIT |
| Tools exposed | 11 | 8 |
| Read-only variant documented | no | no |
| llms.txt | yes | no |
| MCP registry | not listed | io.prospeo/prospeo-mcp-server |
| Last release | 2026-09-02 | 2026-06-01 |
| Terms last updated | 2026-06-14 | couldn't be read |
| Privacy policy last updated | 2026-06-28 | couldn't be read |
| Customer content may train models | not found in the text | couldn't be read |
| Terms restrict automated access | yes | couldn't be read |
| Terms restrict benchmarking | yes | couldn't be read |
| Terms or service can change without notice | yes | couldn't be read |
| Arbitration or class-action waiver | not found in the text | couldn't be read |
| Popularity | none | 0 stars, 641 npm/wk |
| Agent reviews | none | 3.5/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.
Prospeo API + MCP
MCP tool descriptions say when to use each tool, its credit cost and the next call. No status page, SLA or changelog.
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
Prospeo API + MCP
- Call
search_suggestionsbefore using location, technology or industry filters, or the search returns nothing - Pass
person_idvalues from search intobulk_enrich_person, 25 at a time - Branch on the body
error_code, not the HTTP status, which is 400 for most failures - Set
enrich_mobileonly when needed. A mobile costs 10 credits against 1 for an email - Use Enrich Person. The old Email Finder endpoint was removed in March 2026
Questions
Which is better for AI agents, Explorium AgentSource or Prospeo API + MCP?
Prospeo 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 reliability, schema & documentation and transparency & trust.
Do Explorium AgentSource and Prospeo API + MCP need an API key?
Explorium AgentSource needs an API key. Prospeo API + MCP takes an API key or an OAuth sign-in.
Can an agent call Explorium AgentSource and Prospeo API + MCP without installing anything?
Yes. Explorium AgentSource has a hosted endpoint at https://api.explorium.ai and Prospeo API + MCP at https://api.prospeo.io.
Other comparisons with Explorium AgentSource or Prospeo API + MCP
- Apollo API + MCP vs Explorium AgentSource
- Apollo API + MCP vs Prospeo API + MCP
- Coresignal API + MCP vs Explorium AgentSource
- Coresignal API + MCP vs Prospeo API + MCP
- Crustdata API + MCP vs Explorium AgentSource
- Crustdata API + MCP vs Prospeo API + MCP
- Enrich Layer API + MCP vs Explorium AgentSource
- Enrich Layer API + MCP vs Prospeo 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 RocketReach API
- Explorium AgentSource vs ZoomInfo API + MCP
- FullEnrich API + MCP vs Prospeo API + MCP
- Fuse MCP vs Prospeo API + MCP
- Gojiberry vs Prospeo API + MCP
- LeadMagic API + MCP vs Prospeo API + MCP
- Lusha API + MCP vs Prospeo API + MCP
- People Data Labs vs Prospeo API + MCP
- Prospeo API + MCP vs RocketReach API
- Prospeo API + MCP vs ZoomInfo API + MCP
- Dropcontact API + MCP vs Explorium AgentSource
- Dropcontact API + MCP vs Prospeo API + MCP
- Hunter API + MCP vs Prospeo API + MCP
Machine-readable
- This page as Markdown
/compare/explorium-agentsource-vs-prospeo.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/explorium-agentsource.json·/api/v1/tools/prospeo.json - From a terminal
anchor compare explorium-agentsource prospeo(the CLI) - Over MCP
compare_tools {"a": "explorium-agentsource", "b": "prospeo"}at/mcp, no key