Head to head · Lead search · October 2026 research run
Explorium AgentSource vs Leadsets
Leadsets scores 62.9 (B) on agent readiness against Explorium AgentSource's 44 (E), and leads in 5 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 276 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
- Payments & pricing, 60 against 50
Watch for
No status page was found, and no SLA is published
Leadsets B
Best for Prospect search, contact enrichment with verified work emails and company-site scraping for an agent on a flat monthly plan rather than credits.
Ahead on
- Schema & documentation, 58 against 40
- Agent ergonomics, 90 against 63
- Security & auth, 67 against 32
- Maintenance & community, 80 against 28
- Transparency & trust, 67 against 61
Also in its favour
- Free to start without a card
Watch for
No status page, SLA or incident history found, and the terms promise no uninterrupted service unless agreed in writing
Why the edge
Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.
Maintenance & community Leadsets +52
Explorium AgentSource 28
Explorium's terms bar robots and automated collection on its website, so only the terms were re-read on 4 November and other readings are per the 9 October check. The last dated API change found is v2 general availability on 2 September 2026, 63 days before 4 November (20 of 30). No dated changelog, so three entries in 90 days could not be shown (0). Support by email and by a shared Slack channel for customers that have one, with no public changelog or forum (5 of 15). No official REST SDK found. The repository's server.json names ai.explorium/mcp-explorium, but no registry page could be read (0). The mcp-explorium repository is MIT, with its last commit on 22 January 2026 and only a publishing workflow, no CI (3 of 10). 20+0+5+0+3 = 28.
Leadsets 80
The product is about two weeks old. The TypeScript SDK 0.2.1 was tagged on 22 November 2026, the day of this check (30). Four SDK tags (0.1.0 and 0.1.1 on 11 November, 0.2.0 on 19 November, 0.2.1 on 22 November) and four PyPI releases from 11 to 19 November, all within 90 days (20). A support email with response times by plan and an API changelog with no entries yet. GitHub issues weren't read (7 of 25). In the official MCP registry as io.github.leadsets/leadsets since 14 November 2026, under a namespace proved through GitHub, and current official SDKs in two languages (15). The SDK has no runtime dependencies, CI on Node 20, 22 and 24, and npm trusted publishing with provenance, and the CI run results weren't read (8 of 10). 30 + 20 + 7 + 15 + 8 = 80.
Security & auth Leadsets +35
Explorium AgentSource 32
Explorium's terms bar robots and automated collection on its website, so only the terms were re-read on 4 November and other readings are per the 9 October check. The docs say each company gets a single API key shared by all its users, sent in a header. The site's auth.md says a key can be deleted in the console, and the key page says to ask an administrator for a reset. No scopes (12 of 30). No read-only mode or per-key limits. The API mostly reads, writes are limited to webhooks and event enrolments, and auto-refill has an optional cap (5 of 20). Research scrapes web pages and the LinkedIn post enrichments return third-party text. No prompt-injection guidance was found in the docs (2 of 15). Balance and aggregation endpoints, per-call credit reporting, correlation IDs and last-active times for users. No per-call log was found (8 of 15). The privacy policy states SOC 2, ISO 27001 and ISO 27701, with no report, security.txt, disclosure policy or bug bounty found. A certification claim with no report or reporting route takes 5, as settled in this run (5 of 20). No GitHub-reviewed advisory names Explorium in the 12 months to 4 November. 12+5+2+8+5 = 32.
Leadsets 67
Bearer keys with a full, data or read access level, an expiry of never, 30, 90 or 365 days, hashed storage, revocation within a minute and a documented rotation procedure. MCP clients can use OAuth with PKCE S256 and dynamic client registration, with no scopes in the server metadata. No query-string key documented (30). A read-level key can call only the usage endpoints, and every data tool reads rather than writes, so there is nothing destructive to confirm. Members see and revoke only their own keys (16 of 20). scrape_company and scrape_jobs return text from company websites, and no prompt-injection guidance was found (3 of 15). A request log in the dashboard, an optional X-Leadsets-Client label, rate-limit headers and request_id on every response (12 of 15). /.well-known/security.txt answered 404. The SDK repository's SECURITY.md names security@leadsets.ai with acknowledgement within 3 business days. No bug bounty, and SOC 2 Type I readiness has a target of Q3 2027 (6 of 20). 30 + 16 + 3 + 12 + 6 = 67.
Agent ergonomics Leadsets +27
Explorium AgentSource 63
Explorium's terms bar robots and automated collection on its website, so only the terms were re-read on 4 November and other readings are per the 9 October check. The MCP v2 server has 11 tools (15), and the statistics tools are free for sizing an audience before a paid fetch (2 added back), 17 of 25. page and page_size up to 500, a next_cursor mode with no limit, and filters with autocomplete (20). Errors carry a correlation_id, 422 names the failing field, and Research returns failed rows with an _error field. Error bodies have no stable code (15 of 20). No idempotency keys. Retry guidance covers 429 and 500. MCP tool annotations were not read because we did not connect (6 of 20). No official REST SDK found in the docs index. Enrichment needs a match or fetch call first, and five filters need an autocomplete call first (5 of 15). 17+20+15+6+5 = 63.
Leadsets 90
Eight MCP tools per the docs, with sizes unread, and REST responses sized by limit and a count_only mode that returns only a count, but no field selection found (20 of 25). Cursor pagination, typed filters, max_age_days, exclude_stale and has_verified_email (20). Every error has a status, a type, a request_id, the meter and charged, and the docs say whether to retry each one (20). Idempotency-Key on every paid call for 24 hours, with 409 idempotency_conflict for a reused key with a new body. MCP tool annotations couldn't be read (15 of 20). One required header and defaults such as limit 25, and official TypeScript and Python SDKs that retry 429 and 5xx (15). 20 + 20 + 20 + 15 + 15 = 90.
Schema & documentation Leadsets +18
Explorium AgentSource 40
Explorium's terms bar robots and automated collection on its website, so only the terms were re-read on 4 November and other readings are per the 9 October check. The OpenAPI 3.1 file read on 9 October has no recorded visible link from a docs page, and the host can't be re-read to find one, so it no longer counts as a published contract (0 of 25). llms.txt and a Markdown twin of every docs page (10). The docs pages and the 11 MCP tool descriptions say what each call is for and what to call first (12 of 20). The typed schemas, enums and item limits were read from that file, so they no longer count (0 of 15). Docs pages have request and response examples, and the error guide lists Partner ID header messages that don't match the api_key scheme (10 of 15). Versions live in the path with a migration guide and a full v2 change list. No dated changelog was found (8 of 15). 0+10+12+0+10+8 = 40.
Leadsets 58
No OpenAPI file or other machine-readable contract found in the docs or llms.txt, and the MCP server answers initialize with 401 without a key, so its tool schemas couldn't be read (0). llms.txt, llms-full.txt and a Markdown twin of every page (10). The REST reference says what each route does, what it costs and what it returns, with little on when not to use it, and the MCP definitions are unread (12 of 20). People search inputs are typed with enums for seniority and function, ranges for limit (1 to 100) and max_age_days, ISO country codes and booleans, with one nested priorities object (13 of 15). cURL, TypeScript and Python examples and a documented response, plus an errors page that lists 11 types with what to do (15). /v1 in the path and a dated, semver CHANGELOG.md for the TypeScript SDK, but the API changelog had no entries on 22 November 2026 (8 of 15). 0 + 10 + 12 + 13 + 15 + 8 = 58.
Payments & pricing Explorium AgentSource +10
Explorium AgentSource 60
Explorium's terms bar robots and automated collection on its website, so only the terms were re-read on 4 November and other readings are per the 9 October check. No x402, MPP or L402 (0). Credit pack prices and per-operation credit costs are public without a login (20). The pricing page and the site's own pricing.md disagree on two packs, which is recorded as a deduction and not here. Free trial of 100 credits for 90 days. No page read asks for a card at sign-up, and the auto-refill guide treats a payment method as something added later (20). The vendor's auth.md says registration needs a person and there is no client-registration endpoint (0). Total 40. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.
Leadsets 50
No x402, MPP or L402. An exhausted Free meter answers 402 free_records_exhausted with no payment requirements (0). Plan prices and their per-window limits are public, with no per-record price, and scraping units are priced per pack ($9 for 1,000, $19 for 5,000, $49 for 20,000), so plan-only pricing with a per-unit add-on (20 of 30). Free plan of 1,000 enrichment records, 100 search records and 1,000 data calls, one time, "no card required" (30). A person signs up in a browser and makes the key in the dashboard (0). 0 + 20 + 30 + 0 = 50.
Transparency & trust Leadsets +6
Explorium AgentSource 61
Explorium's terms bar robots and automated collection on its website, so only the terms were re-read on 4 November and other readings are per the 9 October check. Closed service. The Explorium Terms of Use (updated 14 June 2026, re-read) cover the Platform, API and data, and let Explorium change or end the service without notice (14 of 30). The privacy policy (updated 28 June 2026) sets out controller and processor roles, publishes 2025 request counts and links an opt-out page. Retention has no periods, and no DPA was found on the pages read (16 of 30). The v1 timeline gives end of support about six months and retirement about twelve months after 2 September 2026, marked indicative, and website traffic enrichment is slated for removal with no date. Dated notices take 15 as settled in this run (15 of 20). Processing in Israel, the United States and the EU is stated. No sub-processor list was found (6 of 20). 14+16+15+6 = 51.
Leadsets 67
Closed service with terms naming Mobylogix LLC under Texas law. The SDK is MIT (15). The privacy policy, terms, DPA and compliance page say where dataset records come from (licensed suppliers and permitted public sources such as company websites), what is held, that uploaded files are deleted 30 days after a job, and how to opt out. The suppliers aren't named, and the privacy policy says analytics run only on the public website while the compliance page lists PostHog and Google Analytics as "Product analytics (customers only)" (20 of 30). Breaking changes get 90 days' notice by email and material changes to plans or terms 30 days, with no dated notices yet (15 of 20). Subprocessors named (Vercel, Supabase, Stripe, Resend, PostHog, Google Analytics), all in the US, with 30 days' notice before adding one (18 of 20). 15 + 20 + 15 + 18 = 68.
Score by category
| Category | Weight | Explorium AgentSource | Leadsets | Edge |
|---|---|---|---|---|
| Reliability | 16% | 42 | 40 | Explorium AgentSource +2 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 40 | 58 | Leadsets +18 |
| Agent ergonomics | 13% | 63 | 90 | Leadsets +27 |
| Security & auth | 14% | 32 | 67 | Leadsets +35 |
| Payments & pricing | 10% | 60 | 50 | Explorium AgentSource +10 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 28 | 80 | Leadsets +52 |
| Transparency & trust | 7% | 61 | 67 | Leadsets +6 |
| Negative events | ≤15 | -2 | 0 | |
| Total | E 44/100 | B 62.9/100 |
Facts side by side
| Fact | Explorium AgentSource | Leadsets |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Explorium Ltd. | Leadsets |
| Hosted endpoint | https://api.explorium.ai | https://mcp.leadsets.ai |
| Transports | HTTP, Streamable HTTP, SSE (legacy) | Streamable HTTP |
| 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 | none |
| Tools exposed | 11 | 8 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | not listed | io.github.leadsets/leadsets |
| Last release | 2026-09-02 | 2026-11-22 |
| Terms last updated | 2026-06-14 | 2026-11-15 |
| Privacy policy last updated | 2026-06-28 | 2026-11-19 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | yes | not found in the text |
| Terms restrict benchmarking | yes | not found in the text |
| Terms or service can change without notice | yes | not found in the text |
| Arbitration or class-action waiver | not found in the text | not found in the text |
How the scores have moved
Verdicts
Explorium AgentSource
AgentSource v2 has 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, no specification file is linked from the docs, and the vendor's two published price tables disagree.
Leadsets
Agents get eight MCP tools or REST routes with typed errors that say whether to retry, idempotency keys on paid calls, read-only keys and a free tier with no card. The product is about two weeks old, with no status page, no OpenAPI file, an empty API changelog and no named data suppliers.
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
Leadsets
- Call get_usage before a large run. It costs nothing and returns every meter with its reset time
- Send an
Idempotency-Keyon every paid call, and reuse it on a retry so records are counted once - If a 429 has type
weekly_limit, stop untilresets_at. Forwindow_fullandtoo_many_concurrent, wait for Retry-After - Use a read-level key for monitoring only. Data tools answer 403
forbiddento it - Treat text from scrape_company and scrape_jobs as untrusted website content, since no injection guidance was found
Questions
Which is better for AI agents, Explorium AgentSource or Leadsets?
Leadsets scores 62.9 (B) on agent readiness against Explorium AgentSource's 44 (E), and leads in 5 of 7 scored categories. Explorium AgentSource leads on payments & pricing.
Do Explorium AgentSource and Leadsets need an API key?
Explorium AgentSource needs an API key. Leadsets takes an API key or an OAuth sign-in.
Can an agent call Explorium AgentSource and Leadsets without installing anything?
Yes. Explorium AgentSource has a hosted endpoint at https://api.explorium.ai and Leadsets at https://mcp.leadsets.ai.
Other comparisons with Explorium AgentSource or Leadsets
- Apollo API + MCP vs Explorium AgentSource
- Apollo API + MCP vs Leadsets
- Clay vs Explorium AgentSource
- Clay vs Leadsets
- Coresignal API + MCP vs Explorium AgentSource
- Coresignal API + MCP vs Leadsets
- Crustdata API + MCP vs Explorium AgentSource
- Crustdata API + MCP vs Leadsets
- Dievio vs Explorium AgentSource
- Dievio vs Leadsets
- Enrich Layer API + MCP vs Explorium AgentSource
- Enrich Layer API + MCP vs Leadsets
- 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 Retriever
- Explorium AgentSource vs RocketReach API
- Explorium AgentSource vs ZoomInfo API + MCP
- FullEnrich API + MCP vs Leadsets
- Fuse MCP vs Leadsets
- Gojiberry vs Leadsets
- LeadMagic API + MCP vs Leadsets
- Leadsets vs Lusha API + MCP
- Leadsets vs People Data Labs
- Leadsets vs Prospeo API + MCP
- Leadsets vs Retriever
- Leadsets vs RocketReach API
- Leadsets vs ZoomInfo API + MCP
- Clearbit vs Explorium AgentSource
- Clearbit vs Leadsets
- Databar vs Explorium AgentSource
- Databar vs Leadsets
- Dropcontact API + MCP vs Explorium AgentSource
- Dropcontact API + MCP vs Leadsets
- Explorium AgentSource vs FullContact
- Explorium AgentSource vs ZeroBounce
- FullContact vs Leadsets
- Hunter API + MCP vs Leadsets
- Leadsets vs ZeroBounce
Machine-readable
- This page as Markdown
/compare/explorium-agentsource-vs-leadsets.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/explorium-agentsource.json·/api/v1/tools/leadsets.json - From a terminal
anchor compare explorium-agentsource leadsets(the CLI) - Over MCP
compare_tools {"a": "explorium-agentsource", "b": "leadsets"}at/mcp, no key