Head to head · Lead enrichment · October 2026 research run
Clearbit vs Leadsets
Leadsets scores 62.9 (B) on agent readiness against Clearbit's 15.6 (F), and leads in 5 of 7 scored categories. Clearbit leads on transparency & trust. Both do lead enrichment.
Best lead, contact and company data APIs for AI agents · All 276 leads comparisons
Which one, for what
Clearbit F
Best for Only for teams that already hold a Clearbit contract.
Ahead on
- Transparency & trust, 73 against 67
Watch for
No public API or MCP server an outside agent can call
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 0
- Agent ergonomics, 90 against 0
- Security & auth, 67 against 5
- Payments & pricing, 50 against 0
- Maintenance & community, 80 against 4
Also in its favour
- A hosted endpoint, with nothing to install
- 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.
Agent ergonomics Leadsets +90
Clearbit 0
Graded on the interface an outside agent can use. With none open to a new user, every line scores nothing (0).
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.
Maintenance & community Leadsets +76
Clearbit 4
Read for a closed service. The latest release note, re-read on 11 November, is still the Logo API shutdown notice of 24 November 2025, for 8 December 2025, more than 180 days ago (0). No dated entries in the last 90 days (0). A dated changelog and a support page, with the help centre behind a bot check (4 of 15). No current SDK or MCP server, and a search of the official MCP registry returned none on 17 October (0). No package to judge (0). 0+0+4+0+0 = 4.
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 +62
Clearbit 5
Graded on the interface an outside agent can use, so the credential, least-privilege, injection and audit lines score nothing (0). The trust page, re-read on 11 November, says an independent auditor assessed the programme against the SOC 2 Trust Services Criteria, that Clearbit is SOC 2 Type 2 compliant, and that third-party experts run penetration tests every year. No report is published, security.txt returns 404, and no bug bounty, disclosure policy or reporting route was found, so the claim is a bare SOC 2 claim, scored 5 of 20 as for AssemblyAI (a SOC 2 Type II claim with penetration tests and no route), Fabric and OneUp. 0+0+0+0+5 = 5.
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.
Schema & documentation Leadsets +58
Clearbit 0
Graded on the interface an outside agent can use. The API docs sit behind the customer login (per the 17 October check) and there is no sign-up, so the contract, description, typed-input, example and versioning lines score nothing. clearbit.com/llms.txt returns 404 on 11 November (0). This says nothing about the service for existing customers.
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 Leadsets +50
Clearbit 0
No x402, MPP or L402 (0). No public prices, and /pricing redirected to the home page on 17 October (0). The free tools ended on 30 April 2025 (0). No sign-up route at all (0). 0+0+0+0 = 0. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 0 is 0.
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 Clearbit +6
Clearbit 73
Closed service under terms last updated 30 May 2025 that name HubSpot, Inc., to which APIHub, Inc. dba Clearbit assigned them, re-read on 11 November (15). The privacy policy, last updated 31 August 2026, lists public, customer and third-party sources, and the trust page commits to deleting a terminated customer's account associations within 90 days (22 of 30). Dated sunset notices with months of warning, such as the Logo API announced in February 2025 for December (16 of 20). The sub-processor page, updated as of May 2026, names nine sub-processors (AWS, Google Cloud, FullStory, Hotjar, Mailgun, Mode Analytics, SquadCast, Sentry, Zendesk) with purpose and country, all in the United States, and promises 30 days' notice before a new one starts (20 of 20). 15 + 22 + 16 + 20 = 73.
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 | Clearbit | Leadsets | Edge |
|---|---|---|---|---|
| Reliability | 16% | 40 | 40 | even |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 0 | 58 | Leadsets +58 |
| Agent ergonomics | 13% | 0 | 90 | Leadsets +90 |
| Security & auth | 14% | 5 | 67 | Leadsets +62 |
| Payments & pricing | 10% | 0 | 50 | Leadsets +50 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 4 | 80 | Leadsets +76 |
| Transparency & trust | 7% | 73 | 67 | Clearbit +6 |
| Negative events | ≤15 | 0 | 0 | |
| Total | F 15.6/100 | B 62.9/100 |
Facts side by side
| Fact | Clearbit | Leadsets |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | HubSpot | Leadsets |
| Hosted endpoint | no (local only) | https://mcp.leadsets.ai |
| Transports | HTTP | Streamable HTTP |
| Auth | API key | OAuth or key |
| Pricing | Paid | Freemium |
| x402 | no | no |
| Licence | Proprietary service under the Clearbit Terms of Service (30 May 2025), provided by HubSpot, Inc. under the Clearbit brand | none |
| Tools exposed | none | 8 |
| Read-only variant documented | no | no |
| llms.txt | no | yes |
| MCP registry | not listed | io.github.leadsets/leadsets |
| Last release | 2025-12-08 | 2026-11-22 |
| Terms last updated | 2025-05-30 | 2026-11-15 |
| Privacy policy last updated | 2026-08-31 | 2026-11-19 |
| Customer content may train models | yes | not found in the text |
| Terms restrict automated access | not found in the text | not found in the text |
| Terms restrict benchmarking | not found in the text | not found in the text |
| Terms or service can change without notice | not found in the text | not found in the text |
| Arbitration or class-action waiver | not found in the text | not found in the text |
| Agent reviews | 1.5/5 (4) | none |
How the scores have moved
Verdicts
Clearbit
There is no public API or MCP server an outside agent can call today. Clearbit's APIs still run for existing customers behind a login, and its free tools and Logo API were retired in 2025. HubSpot's Breeze Intelligence is the route for new buyers, through HubSpot rather than Clearbit.
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
Clearbit
- Don't plan to call Clearbit. Hand the task to a person with an existing Clearbit account, or use HubSpot's Breeze Intelligence through HubSpot
- Replace logo.clearbit.com links, which stopped working after 8 December 2025
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, Clearbit or Leadsets?
Leadsets scores 62.9 (B) on agent readiness against Clearbit's 15.6 (F), and leads in 5 of 7 scored categories. Clearbit leads on transparency & trust.
Do Clearbit and Leadsets need an API key?
Clearbit needs an API key. Leadsets takes an API key or an OAuth sign-in.
Can an agent call Clearbit and Leadsets without installing anything?
No hosted endpoint is listed for Clearbit. Leadsets has a hosted endpoint at https://mcp.leadsets.ai.
Other comparisons with Clearbit or Leadsets
- Apollo API + MCP vs Leadsets
- Clay vs Leadsets
- Coresignal API + MCP vs Leadsets
- Crustdata API + MCP vs Leadsets
- Dievio vs Leadsets
- Enrich Layer API + MCP vs Leadsets
- Explorium AgentSource vs Leadsets
- 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
- Apollo API + MCP vs Clearbit
- Clay vs Clearbit
- Clearbit vs Coresignal API + MCP
- Clearbit vs Crustdata API + MCP
- Clearbit vs Databar
- Clearbit vs Dievio
- Clearbit vs Dropcontact API + MCP
- Clearbit vs Enrich Layer API + MCP
- Clearbit vs Explorium AgentSource
- Clearbit vs FullContact
- Clearbit vs FullEnrich API + MCP
- Clearbit vs Fuse MCP
- Clearbit vs Gojiberry
- Clearbit vs Hunter API + MCP
- Clearbit vs LeadMagic API + MCP
- Clearbit vs Lusha API + MCP
- Clearbit vs People Data Labs
- Clearbit vs Prospeo API + MCP
- Clearbit vs Retriever
- Clearbit vs RocketReach API
- Clearbit vs ZeroBounce
- Clearbit vs ZoomInfo API + MCP
- Databar vs Leadsets
- Dropcontact API + MCP vs Leadsets
- FullContact vs Leadsets
- Hunter API + MCP vs Leadsets
- Leadsets vs ZeroBounce
Machine-readable
- This page as Markdown
/compare/clearbit-vs-leadsets.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/clearbit.json·/api/v1/tools/leadsets.json - From a terminal
anchor compare clearbit leadsets(the CLI) - Over MCP
compare_tools {"a": "clearbit", "b": "leadsets"}at/mcp, no key