Head to head · Lead search · October 2026 research run
Leadsets vs ZoomInfo API + MCP
ZoomInfo API + MCP scores 75.4 (BB) on agent readiness against Leadsets's 62.9 (B), and leads in 5 of 7 scored categories. Leadsets leads on agent ergonomics. Both do lead search.
Best lead, contact and company data APIs for AI agents · All 276 leads comparisons
Which one, for what
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
- Agent ergonomics, 90 against 71
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
Best for Sales and marketing agents that need company, contact, intent and business-event data from one vendor, with free search before paid enrichment.
Ahead on
- Reliability, 87 against 40
- Schema & documentation, 84 against 58
- Payments & pricing, 60 against 50
- Transparency & trust, 76 against 67
Also in its favour
- Agent-ready, a grade of BB or better
Watch for
The Licence Terms and Conditions bar disclosing benchmark results and automated access outside ZoomInfo's own tools without written approval
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.
Reliability ZoomInfo API + MCP +47
Leadsets 40
No status page found, and the support page answers "Where can I check if Leadsets is down?" by pointing to the 503 error and support email (0). No incident history to read (5). Limits published with numbers per plan, per rolling five hours and per week, for records, requests and concurrent searches (15). Three 429 types with Retry-After, backoff advice for 500 and 503, and an Idempotency-Key on paid calls that makes retries safe for 24 hours (15). The terms say "We aim for high availability but don't guarantee uninterrupted service unless agreed in writing", and no SLA is published (0). No page calls the service beta or preview, but the changelog says "No releases yet. Release notes start at launch.", so half credit as a judgement call (5). 0 + 5 + 15 + 15 + 0 + 5 = 40.
ZoomInfo API + MCP 87
Graded with the hosted lines. Atlassian Statuspage at status.zoominfo.com with 16 components, among them ZoomInfo Enterprise API, Enrich and GTM Studio (20). The history page for 3 August to 1 November 2026 shows one major incident on GTM Studio audiences on 4 September lasting 93 minutes, an eight-hour audiences issue on 24 September marked no impact, a list-processing issue on 4 August, a NeverBounce job-processing incident on 28 October marked minor, Chorus incidents, and none naming the API component (20 of 30). Limits published per package on three windows, from 5 a second on Builder to 35 on Scaling (15). 429 carries Retry-After and names the exhausted window, and rejected requests do not consume quota. No idempotency keys found for audience writes (12 of 15). The Licence Terms and Conditions guarantee 99.9 per cent monthly availability (10). API v1, MCP server and CLI carry no beta label (10).
Schema & documentation ZoomInfo API + MCP +26
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.
ZoomInfo API + MCP 84
Eight public OpenAPI 3.0 files, with 18 operations in the Data API file (25). llms.txt and Markdown twins on docs.gtm.ai and gtm.ai (10). Endpoint descriptions state when to search before enriching and how to find valid field names, and MCP tool pages mark superseded tools (16 of 20). The Data API file marks required fields 198 times but has 11 enums, because filter values come from Lookup calls (10 of 15). 150 examples in the Data API file and an error catalogue with codes and a recommended action each (13 of 15). The API is versioned as v1 with breaking changes promised only in a new version. The dated Release Hub covers the whole product with an API filter, newest entries 20 October 2026, and docs.gtm.ai has no changelog of its own (10 of 15). The credit page says rate-limit headers are not returned while the rate-limit page lists them.
Agent ergonomics Leadsets +19
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.
ZoomInfo API + MCP 71
Graded on the REST API, with the MCP server noted. Enrich calls take an outputFields list and the CLI has --select, so responses can be sized. The MCP server lists 27 tools on its tools page with no toolsets found (18 of 25). Search pages with page[number] and page[size] up to 100 records, with many filters and a cap at page 100 (18 of 20). Coded errors with a recommended action, a retryable flag and a table of recovery steps for agents (18 of 20). No idempotency keys found. Rejected 429 requests cost nothing and search is free, but a repeated enrichment is free only under Records Under Management, which the pricing page limits to Enterprise. MCP tool annotations could not be read without an account (10 of 20). No official SDKs, a JSON:API envelope on every request, and one official CLI (7 of 15).
Payments & pricing ZoomInfo API + MCP +10
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.
ZoomInfo API + MCP 60
No x402, MPP or L402 (0). Per-credit prices are public, $0.05 an AI credit and $0.38 a data credit at the $1,000 spend tier, with top-ups from $20 (20). A free account with 1,000 data credits and 1,000 AI credits needs no card (20). A person signs up and completes OAuth in a browser (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.
Transparency & trust ZoomInfo API + MCP +9
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.
ZoomInfo API + MCP 76
Closed service with published terms naming ZoomInfo Technologies LLC, and an MIT CLI (15 of 30). The privacy policy covers people in the database and customers, names sources (web scanning, third parties, a research team, customer contributions and ZoomInfo Lite email access), a Data Protection Officer contact and a removal route. Retention has no fixed period, and the pricing page says both that credits never expire and that they expire after 12 months (22 of 30). Two rate-limit headers carry a removal date of 1 January 2027 and breaking changes are promised only in a new API version, but superseded MCP tools carry no dates and no deprecation policy was found (10 of 20). Sub-processor list updated 17 July 2026 with locations and roles (18 of 20).
Score by category
| Category | Weight | Leadsets | ZoomInfo API + MCP | Edge |
|---|---|---|---|---|
| Reliability | 16% | 40 | 87 | ZoomInfo API + MCP +47 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 58 | 84 | ZoomInfo API + MCP +26 |
| Agent ergonomics | 13% | 90 | 71 | Leadsets +19 |
| Security & auth | 14% | 67 | 65 | Leadsets +2 |
| Payments & pricing | 10% | 50 | 60 | ZoomInfo API + MCP +10 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 80 | 83 | ZoomInfo API + MCP +3 |
| Transparency & trust | 7% | 67 | 76 | ZoomInfo API + MCP +9 |
| Negative events | ≤15 | 0 | 0 | |
| Total | B 62.9/100 | BB 75.4/100 |
Facts side by side
| Fact | Leadsets | ZoomInfo API + MCP |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Leadsets | ZoomInfo Technologies LLC |
| Hosted endpoint | https://mcp.leadsets.ai | https://api.zoominfo.com/gtm |
| Transports | Streamable HTTP | HTTP, Streamable HTTP |
| Auth | OAuth or key | OAuth |
| Pricing | Freemium | Freemium |
| x402 | no | no |
| Licence | none | Proprietary service under ZoomInfo's Licence Terms and Conditions. The GTM CLI on GitHub is MIT |
| Tools exposed | 8 | 27 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | io.github.leadsets/leadsets | io.github.Zoominfo/zoominfo-mcp |
| Last release | 2026-11-22 | 2026-10-28 |
| Terms last updated | 2026-11-15 | no date given |
| Privacy policy last updated | 2026-11-19 | 2025-10-13 |
| Customer content may train models | not found in the text | yes, with an opt-out |
| Terms restrict automated access | not found in the text | yes |
| Terms restrict benchmarking | not found in the text | yes |
| 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 | yes |
| Popularity | none | 534 npm/wk |
| Agent reviews | none | 3/5 (4) |
How the scores have moved
Leadsets
No score change since it was listed.
Verdicts
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.
ZoomInfo API + MCP
Search, lookup and similar-record calls cost no credits, and a free account with 1,000 data and 1,000 AI credits needs no card. OAuth carries 20 scopes and limits are published per package. The Licence Terms and Conditions bar disclosing benchmark results, and the two documentation sites disagree on batch sizes and rate-limit headers.
Before you call either
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
ZoomInfo API + MCP
- Call Lookup first and pass the returned IDs to Search. Unknown industry, metro or topic strings are rejected with a 422
- Search before Enrich. Search is free, and each newly enriched record costs one data credit
- Request only the scopes the task needs in the
scopeparameter of the token call. Omitting it grants every scope configured on the app - On 429 read
X-RateLimit-Rejected-Bucketand wait forRetry-After. An exhausted hourly window can mean a wait of several hundred seconds - Turn off model training in the AI client before connecting the MCP server. ZoomInfo prohibits MCP data being used for training
Questions
Which is better for AI agents, Leadsets or ZoomInfo API + MCP?
ZoomInfo API + MCP scores 75.4 (BB) on agent readiness against Leadsets's 62.9 (B), and leads in 5 of 7 scored categories. Leadsets leads on agent ergonomics.
Do Leadsets and ZoomInfo API + MCP need an API key?
Leadsets takes an API key or an OAuth sign-in. ZoomInfo API + MCP uses an OAuth sign-in.
Can an agent call Leadsets and ZoomInfo API + MCP without installing anything?
Yes. Leadsets has a hosted endpoint at https://mcp.leadsets.ai and ZoomInfo API + MCP at https://api.zoominfo.com/gtm.
Other comparisons with Leadsets or ZoomInfo API + MCP
- Apollo API + MCP vs Leadsets
- Apollo API + MCP vs ZoomInfo API + MCP
- Clay vs Leadsets
- Clay vs ZoomInfo API + MCP
- Coresignal API + MCP vs Leadsets
- Coresignal API + MCP vs ZoomInfo API + MCP
- Crustdata API + MCP vs Leadsets
- Crustdata API + MCP vs ZoomInfo API + MCP
- Dievio vs Leadsets
- Dievio vs ZoomInfo API + MCP
- Enrich Layer API + MCP vs Leadsets
- Enrich Layer API + MCP vs ZoomInfo API + MCP
- Explorium AgentSource vs Leadsets
- Explorium AgentSource vs ZoomInfo API + MCP
- FullEnrich API + MCP vs Leadsets
- FullEnrich API + MCP vs ZoomInfo API + MCP
- Fuse MCP vs Leadsets
- Fuse MCP vs ZoomInfo API + MCP
- Gojiberry vs Leadsets
- Gojiberry vs ZoomInfo API + MCP
- Hunter API + MCP vs ZoomInfo API + MCP
- LeadMagic API + MCP vs Leadsets
- LeadMagic API + MCP vs ZoomInfo API + MCP
- Leadsets vs Lusha API + MCP
- Leadsets vs People Data Labs
- Leadsets vs Prospeo API + MCP
- Leadsets vs Retriever
- Leadsets vs RocketReach API
- Lusha API + MCP vs ZoomInfo API + MCP
- People Data Labs vs ZoomInfo API + MCP
- Prospeo API + MCP vs ZoomInfo API + MCP
- Retriever vs ZoomInfo API + MCP
- RocketReach API vs ZoomInfo API + MCP
- Clearbit vs Leadsets
- Clearbit vs ZoomInfo API + MCP
- Databar vs Leadsets
- Databar vs ZoomInfo API + MCP
- Dropcontact API + MCP vs Leadsets
- Dropcontact API + MCP vs ZoomInfo API + MCP
- FullContact vs Leadsets
- FullContact vs ZoomInfo API + MCP
- ZeroBounce vs ZoomInfo API + MCP
- Hunter API + MCP vs Leadsets
- Leadsets vs ZeroBounce
Machine-readable
- This page as Markdown
/compare/leadsets-vs-zoominfo.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/leadsets.json·/api/v1/tools/zoominfo.json - From a terminal
anchor compare leadsets zoominfo(the CLI) - Over MCP
compare_tools {"a": "leadsets", "b": "zoominfo"}at/mcp, no key