# Leadsets vs ZeroBounce

> ZeroBounce scores 64.6 (B) to Leadsets's 62.9 (B) for email verification. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/leadsets-vs-zerobounce
- Markdown: https://www.anchorterminal.com/compare/leadsets-vs-zerobounce.md (~3,900 tokens)
- Slim: https://www.anchorterminal.com/compare/leadsets-vs-zerobounce.min.md (~780 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/leadsets-vs-zerobounce.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-22

ZeroBounce scores 64.6 (B) on agent readiness against Leadsets's 62.9 (B), and leads in 2 of 7 scored categories. Leadsets leads on agent ergonomics and maintenance & community. Both do email verification.

- Leadsets: grade B, 62.9/100, rank #661 of 1571. Markdown https://www.anchorterminal.com/tools/leadsets.md · JSON https://www.anchorterminal.com/api/v1/tools/leadsets.json
- ZeroBounce: grade B, 64.6/100, rank #585 of 1571. Markdown https://www.anchorterminal.com/tools/zerobounce.md · JSON https://www.anchorterminal.com/api/v1/tools/zerobounce.json
- Best lead, contact and company data APIs for AI agents: https://www.anchorterminal.com/best/lead-data/index.md
- All 276 leads comparisons: https://www.anchorterminal.com/compare/lead-data/index.md

## Which one, for what

### Leadsets (B)

Good 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 69
- Maintenance & community, 80 against 70

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

### ZeroBounce (B)

Good for: Email verification before outreach, the verification-first listing in lead-data.

Ahead on:
- Reliability, 75 against 40

Also in its favour:
- Runs on your own machine

Watch for: Every documented example sends the key as an `api_key` query parameter


## Why the edge

### Reliability: ZeroBounce +35

- 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.
- ZeroBounce (75): Hosted lines. Statuspage at status.zerobounce.net with API, API-US, API-EU, Bulk API, website and Cloudflare components (20). The incident feed for 8 August to 6 November shows a 6-minute members platform disruption on 9 September, about 3 minutes of reduced EU API availability on 1 October, and a file upload issue on 26 October resolved within 6 minutes, all minor (20). Limits published per endpoint group with numbers and block lengths (15). 429 is documented with advice to throttle, but no Retry-After, and a block can last an hour or a day (10 of 15). No SLA found (0). Generally available (10). 20+20+15+10+0+10 = 75.

### Agent ergonomics: Leadsets +21

- 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.
- ZeroBounce (69): A compact JSON result per address, batch validation and a file API for lists (18 of 25). Little to paginate; file status and results by file id (10 of 20). Status and sub-status codes say why an address failed, and the error page explains 400, 404 and 429 (14 of 20). Unknown results are free and safe to retry; repeated validations are charged again (12 of 20). Many official SDK wrappers and an MCP server, with few required parameters (15). 18+10+14+12+15 = 69.

### Maintenance & community: Leadsets +10

- 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.
- ZeroBounce (70): Closed service. The JavaScript SDK 3.0.0 was published on 25 October 2026 (30). No API changelog; the dated changes found in 90 days are that release and status-page notices, fewer than three releases (10 of 20). Support by email and 24/7 chat per the docs, a public status page; replies not tested (10 of 15). Official SDKs in many languages and an MCP server (15). Package health not checked (5 of 10). 30+10+10+15+5 = 70.

## Score by category

| Category | Weight | Leadsets | ZeroBounce | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% | 40 | 75 | ZeroBounce +35 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 58 | 54 | Leadsets +4 |
| Agent ergonomics | 13% | 90 | 69 | Leadsets +21 |
| Security & auth | 14% | 67 | 65 | Leadsets +2 |
| Payments & pricing | 10% | 50 | 53 | ZeroBounce +3 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 80 | 70 | Leadsets +10 |
| Transparency & trust | 7% | 67 | 63 | Leadsets +4 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **62.9 · B** | **64.6 · B** | |

## Facts side by side

| Fact | Leadsets | ZeroBounce |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | Leadsets | Hertza L.L.C. (ZeroBounce) |
| Hosted endpoint | `https://mcp.leadsets.ai` | `https://api.zerobounce.net/v2` |
| Transports | Streamable HTTP | HTTP, stdio |
| Auth | OAuth or key | API key |
| Pricing | Freemium | Pay per use |
| x402 | no | no |
| Licence | none | Proprietary service under ZeroBounce's terms of use; SDKs and the MCP server are open source |
| Tools exposed | 8 | 0 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | `io.github.leadsets/leadsets` | not listed |
| Last release | 2026-11-22 | 2026-10-25 |
| Terms last updated | 2026-11-15 | 2026-05-05 |
| Privacy policy last updated | 2026-11-19 | 2026-06-30 |
| Customer content may train models | not found in the text | 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 | yes |
| Arbitration or class-action waiver | not found in the text | yes |

## How the scores have moved

### Leadsets

No score change since it was listed.

### ZeroBounce

- +2.2 on 13 November 2026: checklist

## 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.

**ZeroBounce.** ZeroBounce's v2 API verifies emails with detailed status and sub-status codes, publishes per-endpoint limits, a Statuspage with short incidents only in the last 90 days, SOC 2 Type 2 and ISO 27001, and $0.0195 per email at the smallest pack. The documented key travels in the query string, and there is no OpenAPI contract.

## Before you call either

### Leadsets

1. Call get_usage before a large run. It costs nothing and returns every meter with its reset time
2. Send an `Idempotency-Key` on every paid call, and reuse it on a retry so records are counted once
3. If a 429 has type `weekly_limit`, stop until `resets_at`. For `window_full` and `too_many_concurrent`, wait for Retry-After
4. Use a read-level key for monitoring only. Data tools answer 403 `forbidden` to it
5. Treat text from scrape_company and scrape_jobs as untrusted website content, since no injection guidance was found

### ZeroBounce

1. Use the regional host (api-us or api-eu) that matches the data, and test with the sandbox addresses, which spend no credits
2. Set `timeout` (3 to 60 seconds); slow mail servers return unknown, which is free to retry later
3. Stay under 80,000 validations per 10 seconds and avoid repeated bad requests, which block the key for an hour
4. Use the bulk file API for large lists instead of looping on /v2/validate
5. Keep the key out of logs; the API takes it only as `api_key` in the URL

## Questions

### Which is better for AI agents, Leadsets or ZeroBounce?

ZeroBounce scores 64.6 (B) on agent readiness against Leadsets's 62.9 (B), and leads in 2 of 7 scored categories. Leadsets leads on agent ergonomics and maintenance & community.

### Do Leadsets and ZeroBounce need an API key?

Leadsets takes an API key or an OAuth sign-in. ZeroBounce needs an API key.

### Can an agent call Leadsets and ZeroBounce without installing anything?

Yes. Leadsets has a hosted endpoint at https://mcp.leadsets.ai and ZeroBounce at https://api.zerobounce.net/v2.


## For agents

- This comparison as JSON: https://www.anchorterminal.com/compare/leadsets-vs-zerobounce.json, and with the fewest tokens: https://www.anchorterminal.com/compare/leadsets-vs-zerobounce.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "leadsets", "b": "zerobounce"}`. From a terminal: `anchor compare leadsets zerobounce`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/leadsets.json and https://www.anchorterminal.com/api/v1/tools/zerobounce.json

## Other comparisons with Leadsets or ZeroBounce

- [Apollo API + MCP vs Leadsets](https://www.anchorterminal.com/compare/apollo-vs-leadsets.md)
- [Clay vs Leadsets](https://www.anchorterminal.com/compare/clay-vs-leadsets.md)
- [Coresignal API + MCP vs Leadsets](https://www.anchorterminal.com/compare/coresignal-vs-leadsets.md)
- [Crustdata API + MCP vs Leadsets](https://www.anchorterminal.com/compare/crustdata-vs-leadsets.md)
- [Dievio vs Leadsets](https://www.anchorterminal.com/compare/dievio-vs-leadsets.md)
- [Enrich Layer API + MCP vs Leadsets](https://www.anchorterminal.com/compare/enrich-layer-vs-leadsets.md)
- [Explorium AgentSource vs Leadsets](https://www.anchorterminal.com/compare/explorium-agentsource-vs-leadsets.md)
- [FullEnrich API + MCP vs Leadsets](https://www.anchorterminal.com/compare/fullenrich-vs-leadsets.md)
- [Fuse MCP vs Leadsets](https://www.anchorterminal.com/compare/fuse-mcp-vs-leadsets.md)
- [Gojiberry vs Leadsets](https://www.anchorterminal.com/compare/gojiberry-vs-leadsets.md)
- [LeadMagic API + MCP vs Leadsets](https://www.anchorterminal.com/compare/leadmagic-vs-leadsets.md)
- [Leadsets vs Lusha API + MCP](https://www.anchorterminal.com/compare/leadsets-vs-lusha.md)
- [Leadsets vs People Data Labs](https://www.anchorterminal.com/compare/leadsets-vs-people-data-labs.md)
- [Leadsets vs Prospeo API + MCP](https://www.anchorterminal.com/compare/leadsets-vs-prospeo.md)
- [Leadsets vs Retriever](https://www.anchorterminal.com/compare/leadsets-vs-retriever.md)
- [Leadsets vs RocketReach API](https://www.anchorterminal.com/compare/leadsets-vs-rocketreach.md)
- [Leadsets vs ZoomInfo API + MCP](https://www.anchorterminal.com/compare/leadsets-vs-zoominfo.md)
- [Apollo API + MCP vs ZeroBounce](https://www.anchorterminal.com/compare/apollo-vs-zerobounce.md)
- [Clay vs ZeroBounce](https://www.anchorterminal.com/compare/clay-vs-zerobounce.md)
- [Clearbit vs Leadsets](https://www.anchorterminal.com/compare/clearbit-vs-leadsets.md)
- [Clearbit vs ZeroBounce](https://www.anchorterminal.com/compare/clearbit-vs-zerobounce.md)
- [Coresignal API + MCP vs ZeroBounce](https://www.anchorterminal.com/compare/coresignal-vs-zerobounce.md)
- [Crustdata API + MCP vs ZeroBounce](https://www.anchorterminal.com/compare/crustdata-vs-zerobounce.md)
- [Databar vs Leadsets](https://www.anchorterminal.com/compare/databar-vs-leadsets.md)
- [Databar vs ZeroBounce](https://www.anchorterminal.com/compare/databar-vs-zerobounce.md)
- [Dievio vs ZeroBounce](https://www.anchorterminal.com/compare/dievio-vs-zerobounce.md)
- [Dropcontact API + MCP vs Leadsets](https://www.anchorterminal.com/compare/dropcontact-vs-leadsets.md)
- [Dropcontact API + MCP vs ZeroBounce](https://www.anchorterminal.com/compare/dropcontact-vs-zerobounce.md)
- [Enrich Layer API + MCP vs ZeroBounce](https://www.anchorterminal.com/compare/enrich-layer-vs-zerobounce.md)
- [Explorium AgentSource vs ZeroBounce](https://www.anchorterminal.com/compare/explorium-agentsource-vs-zerobounce.md)
- [FullContact vs Leadsets](https://www.anchorterminal.com/compare/fullcontact-vs-leadsets.md)
- [FullContact vs ZeroBounce](https://www.anchorterminal.com/compare/fullcontact-vs-zerobounce.md)
- [FullEnrich API + MCP vs ZeroBounce](https://www.anchorterminal.com/compare/fullenrich-vs-zerobounce.md)
- [Gojiberry vs ZeroBounce](https://www.anchorterminal.com/compare/gojiberry-vs-zerobounce.md)
- [Lusha API + MCP vs ZeroBounce](https://www.anchorterminal.com/compare/lusha-vs-zerobounce.md)
- [People Data Labs vs ZeroBounce](https://www.anchorterminal.com/compare/people-data-labs-vs-zerobounce.md)
- [Prospeo API + MCP vs ZeroBounce](https://www.anchorterminal.com/compare/prospeo-vs-zerobounce.md)
- [Retriever vs ZeroBounce](https://www.anchorterminal.com/compare/retriever-vs-zerobounce.md)
- [ZeroBounce vs ZoomInfo API + MCP](https://www.anchorterminal.com/compare/zerobounce-vs-zoominfo.md)
- [Hunter API + MCP vs Leadsets](https://www.anchorterminal.com/compare/hunter-vs-leadsets.md)
- [Hunter API + MCP vs ZeroBounce](https://www.anchorterminal.com/compare/hunter-vs-zerobounce.md)
- [Fuse MCP vs ZeroBounce](https://www.anchorterminal.com/compare/fuse-mcp-vs-zerobounce.md)
- [LeadMagic API + MCP vs ZeroBounce](https://www.anchorterminal.com/compare/leadmagic-vs-zerobounce.md)
- [RocketReach API vs ZeroBounce](https://www.anchorterminal.com/compare/rocketreach-vs-zerobounce.md)

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
