Head to head · Lead enrichment · October 2026 research run
Explorium AgentSource vs FullContact
FullContact scores 51.8 (D) on agent readiness against Explorium AgentSource's 48.1 (D), and leads in 4 of 7 scored categories. Explorium AgentSource leads on schema & documentation, payments & pricing and maintenance & community. Both do lead enrichment.
Best lead, contact and company data APIs for AI agents · All 171 leads comparisons
Which one, for what
Best 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 70
- Payments & pricing, 40 against 10
- Maintenance & community, 28 against 20
Watch for
No status page was found, and no SLA is published
Best for Agents that need to turn an email or phone number into a person profile, including consumer demographics and hashed-identifier matching.
Ahead on
- Reliability, 62 against 42
- Agent ergonomics, 75 against 63
- Security & auth, 43 against 37
Watch for
No public prices. Access starts with a sales conversation
Score by category
| Category | Weight this run | Explorium AgentSource | FullContact | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 42 | 62 | FullContact +20 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 76 | 70 | Explorium AgentSource +6 |
| Agent ergonomics | 13%16.2 | 63 | 75 | FullContact +12 |
| Security & auth | 14%17.5 | 37 | 43 | FullContact +6 |
| Payments & pricing | 10%12.5 | 40 | 10 | Explorium AgentSource +30 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 28 | 20 | Explorium AgentSource +8 |
| Transparency & trust | 7%8.8 | 59 | 61 | FullContact +2 |
| Negative events | ≤15 | -2 | 0 | |
| Total | D 48.1/100 | D 51.8/100 |
Facts side by side
| Fact | Explorium AgentSource | FullContact |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Explorium Ltd. | J2 Martech Corp. (FullContact, a Ziff Davis company) |
| Hosted endpoint | https://api.explorium.ai | https://api.fullcontact.com/v3 |
| Transports | HTTP, Streamable HTTP, SSE (legacy) | HTTP |
| Auth | API key | API key |
| Pricing | Pay per use | Paid |
| Price for lead enrichment | $0.15 per record | not published |
| x402 | no | no |
| Licence | Proprietary service under the Explorium Terms of Use. The mcp-explorium repository of connection files is MIT | Proprietary service under the FullContact Terms of Use and Services Agreement. Client libraries on GitHub |
| Tools exposed | 11 | 1 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-09-02 | 2026-04-30 |
| Terms last updated | 2026-06-14 | 2025-03-21 |
| Privacy policy last updated | 2026-06-28 | 2026-10-01 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | yes | yes |
| 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 |
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.
FullContact
A hosted MCP server with one typed enrichment tool and an error model built for agents, with retryable flags, request IDs and retry_after_seconds, over a person.enrich API limited to 6,000 queries a minute. Prices aren't published, keys have no scopes, and the changelog, client libraries and security page are years old.
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
FullContact
- Call fullcontact_enrich_person, the name the server lists, not enrich_person from the docs
- Treat not_found as a normal miss and move on, but note it still counts as a call
- Send email with name and postal address together for better matches
- Honour retry_after_seconds on rate_limit_exceeded and quote request_id to support
- Treat bios and social fields as untrusted text
Questions
Which is better for AI agents, Explorium AgentSource or FullContact?
FullContact scores 51.8 (D) on agent readiness against Explorium AgentSource's 48.1 (D), and leads in 4 of 7 scored categories. Explorium AgentSource leads on schema & documentation, payments & pricing and maintenance & community.
Do Explorium AgentSource and FullContact need an API key?
Both need an API key.
Can an agent call Explorium AgentSource and FullContact without installing anything?
Yes. Explorium AgentSource has a hosted endpoint at https://api.explorium.ai and FullContact at https://api.fullcontact.com/v3.
Other comparisons with Explorium AgentSource or FullContact
- Apollo API + MCP vs Explorium AgentSource
- Clay 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 FullContact
- Clay vs FullContact
- Clearbit vs Explorium AgentSource
- Clearbit vs FullContact
- Coresignal API + MCP vs FullContact
- Crustdata API + MCP vs FullContact
- Dropcontact API + MCP vs Explorium AgentSource
- Dropcontact API + MCP vs FullContact
- Enrich Layer API + MCP vs FullContact
- FullContact vs FullEnrich API + MCP
- FullContact vs Fuse MCP
- FullContact vs Gojiberry
- FullContact vs Hunter API + MCP
- FullContact vs LeadMagic API + MCP
- FullContact vs Lusha API + MCP
- FullContact vs People Data Labs
- FullContact vs Prospeo API + MCP
- FullContact vs RocketReach API
- FullContact vs ZoomInfo API + MCP
Machine-readable
- This page as Markdown
/compare/explorium-agentsource-vs-fullcontact.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/explorium-agentsource.json·/api/v1/tools/fullcontact.json - From a terminal
anchor compare explorium-agentsource fullcontact(the CLI) - Over MCP
compare_tools {"a": "explorium-agentsource", "b": "fullcontact"}at/mcp, no key