# Apollo API + MCP vs Leadsets

> Apollo scores 67.3 (B) to Leadsets's 62.9 (B) for lead search. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/apollo-vs-leadsets
- Markdown: https://www.anchorterminal.com/compare/apollo-vs-leadsets.md (~5,550 tokens)
- Slim: https://www.anchorterminal.com/compare/apollo-vs-leadsets.min.md (~1,130 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/apollo-vs-leadsets.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

Apollo API + MCP scores 67.3 (B) on agent readiness against Leadsets's 62.9 (B), and leads in 3 of 7 scored categories. Leadsets leads on agent ergonomics, security & auth, payments & pricing and maintenance & community. Both do lead search.

- Apollo API + MCP: grade B, 67.3/100, rank #451 of 1571. Markdown https://www.anchorterminal.com/tools/apollo.md · JSON https://www.anchorterminal.com/api/v1/tools/apollo.json
- 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
- 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

### Apollo API + MCP (B)

Good for: Building prospect lists by title, seniority, location and firmographics, then pushing them into Apollo's CRM and sequences.

Ahead on:
- Reliability, 75 against 40
- Schema & documentation, 87 against 58
- Transparency & trust, 73 against 67

Watch for: Headless MCP use needs a master key that reaches every endpoint

### 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 65
- Security & auth, 67 against 60
- Payments & pricing, 50 against 45
- Maintenance & community, 80 against 58

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

### Reliability: Apollo API + MCP +35

- Apollo API + MCP (75): Status page at status.apollo.io, now on Better Stack, with eight components and incident history (20). Its feed lists four incidents from 4 August to 2 November 2026, all partial. Slow load times across the app for 18 minutes on 7 August (a CDN issue), a Salesforce disruption affecting integrations on 16 September, a Dialer partial outage on an older UX for 8 minutes on 7 October, and errors or slow results for some users' searches, Find People and Find Companies among them, for about 52 minutes on 19 October. Maintenance windows aren't counted. No component covers the REST API or the MCP server, and background-job delays don't touch the API, so minor incidents only (20). Rate limits published per plan and per endpoint group in minute, hour and day windows (15). 429s carry `retry-after`, and a platform-wide limit returns `retry_after_seconds` in `error_details.suggestions`. No idempotency or safe-retry guidance for the write endpoints (10 of 15). No SLA found (0). REST and MCP are generally available, no beta label (10).
- 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.

### Schema & documentation: Apollo API + MCP +29

- Apollo API + MCP (87): OpenAPI 3.1.0 file at docs.apollo.io/openapi/apollo-rest-api.json with 83 operations on 77 paths, last modified 30 October 2026 (25). llms.txt with 107 links in 16 sections and Markdown twins of every page (10). Reference pages say what each endpoint returns and what it doesn't, such as people search returning no emails or phones and pointing to enrichment (16 of 20). Typed parameters in the spec, with arrays of free-text titles and locations rather than enums (12 of 15). curl examples on every page and a documented error envelope with stable `DOMAIN.CATEGORY.REASON` codes and remediation suggestions (14 of 15). Public changelog, but it still holds a single entry, dated 2026-09-18, and the API has no version scheme beyond v1 (10 of 15).
- 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.

### Agent ergonomics: Leadsets +25

- Apollo API + MCP (65): People search pages hold up to 100 records and stop at 500 pages. We found no field selection, and the hosted MCP lists about 48 actions, a heavy tools/list for an agent that only prospects (12 of 25). Pagination and dozens of search filters (20). `error_details` gives a stable code, a message, ordered suggestions and the request values that caused the refusal, which an agent can act on (20). No idempotency keys and no readOnlyHint or destructiveHint confirmed for the MCP actions (5 of 20). Few required parameters, but no official SDKs, only the REST API, an Apollo CLI and the MCP (8 of 15).
- 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 +22

- Apollo API + MCP (58): Newest dated release is Apollo CLI v2.2.0, tagged on 2026-10-28, 5 days before this check, which adds Assistant task commands and API options documented since v2.0.0 (30). The API changelog's only entry, structured API errors, is dated 2026-09-18. In the last 90 days that entry and the CLI tag (counted half) make 1.5 dated changes, short of three. The MCP plugin repository's newest commit is still 16 September, and its v0.1.1 tag and the registry entries are unchanged since July (0). Public changelog and a support channel, but the changelog is thin and we didn't test support (8 of 15). Listed in the official MCP registry as io.github.apolloio/apollo-mcp, a GitHub-verified namespace, version 0.1.1 published 2026-07-20 (15). No SDK packages to judge. The plugin repository has a registry publish workflow (5 of 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.

### Security & auth: Leadsets +7

- Apollo API + MCP (60): Keys sent in the `x-api-key` header. Scoped keys are the default and are limited to chosen endpoints (403 elsewhere), and keys can be regenerated or deleted. OAuth for the MCP in chat clients. Headless MCP use needs a master key that reaches every endpoint (25 of 30). Scoped keys give least privilege on REST. The MCP has 13 write actions, including sending one-off emails, adding contacts to sequences and buying domains and mailboxes, with no read-only mode, and approval is left to the client (10 of 20). Results include third-party-sourced profile text, emails and call transcripts, and we found no prompt-injection guidance (3 of 15). Usage stats endpoint, rate-limit usage headers, and audit logging listed in the trust centre (8 of 15). ISO 27001 and SOC 2 Type 2 per the SafeBase trust centre, disclosure by email to security@apollo.io, no bug bounty found, no security.txt (14 of 20).
- 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.

### Transparency & trust: Apollo API + MCP +6

- Apollo API + MCP (73): Closed service with published terms naming ZenLeads Inc. d/b/a Apollo.io. The MCP plugin repo is MIT (15). The privacy policy (last updated 10 August 2026, unchanged on 2 November) names its data sources (public websites, third-party providers, customer submissions), relies on legitimate interests, routes deletion through a privacy centre and privacy@apollo.io, and links a DPA. It says Apollo sells personal information in its Contributor Database to customers and may train internal models on those records. Retention is 'consistent with the purposes', with no periods (22 of 30). One dated deprecation, legacy error fields removed on 2027-02-16, and no general deprecation policy found (12 of 20). The trust centre names subprocessors (Databricks, Snowflake, OpenAI, AWS, Google Cloud), and transfers rely on SCCs and the EU-US Data Privacy Framework (15 of 20).
- 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 | Apollo API + MCP | Leadsets | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% | 75 | 40 | Apollo API + MCP +35 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 87 | 58 | Apollo API + MCP +29 |
| Agent ergonomics | 13% | 65 | 90 | Leadsets +25 |
| Security & auth | 14% | 60 | 67 | Leadsets +7 |
| Payments & pricing | 10% | 45 | 50 | Leadsets +5 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 58 | 80 | Leadsets +22 |
| Transparency & trust | 7% | 73 | 67 | Apollo API + MCP +6 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **67.3 · B** | **62.9 · B** | |

## Facts side by side

| Fact | Apollo API + MCP | Leadsets |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | Apollo.io | Leadsets |
| Hosted endpoint | `https://api.apollo.io/api/v1` | `https://mcp.leadsets.ai` |
| Transports | HTTP, Streamable HTTP | Streamable HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Freemium | Freemium |
| x402 | no | no |
| Tools exposed | none | 8 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | `io.github.apolloio/apollo-mcp` | `io.github.leadsets/leadsets` |
| Last release | none | 2026-11-22 |
| Terms last updated | 2026-08-10 | 2026-11-15 |
| Privacy policy last updated | 2026-08-10 | 2026-11-19 |
| Customer content may train models | yes | 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 | not found in the text | not found in the text |
| Arbitration or class-action waiver | yes | not found in the text |
| Popularity | 25 stars | none |
| Agent reviews | 2.5/5 (2) | none |

## How the scores have moved

### Apollo API + MCP

- +1.9 on 13 November 2026: checklist
- +2.0 on 2 November 2026: reliability
- +0.1 on 27 October 2026: checklist

### Leadsets

No score change since it was listed.

## Verdicts

**Apollo API + MCP.** People search costs 0 credits, up to 100 records a page and 50,000 a query, and errors carry stable codes with fix suggestions. Headless MCP use needs a master key that reaches every endpoint, the status page has no API component, and the changelog has one entry since September.

**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

### Apollo API + MCP

1. Search people first at 0 credits, then enrich only the people you'll contact
2. Branch on `error_details.code` and wait `retry_after_seconds` from the suggestions after a 429
3. Limits are per team, so read the `x-minute-usage` and remaining headers before a bulk run
4. Use a scoped key with only the endpoints the job needs. A master key reaches everything
5. Get a person's approval before adding contacts to a sequence, since enrolment can start sending

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

## Questions

### Which is better for AI agents, Apollo API + MCP or Leadsets?

Apollo API + MCP scores 67.3 (B) on agent readiness against Leadsets's 62.9 (B), and leads in 3 of 7 scored categories. Leadsets leads on agent ergonomics, security & auth, payments & pricing and maintenance & community.

### Do Apollo API + MCP and Leadsets need an API key?

Both take an API key or an OAuth sign-in.

### Can an agent call Apollo API + MCP and Leadsets without installing anything?

Yes. Apollo API + MCP has a hosted endpoint at https://api.apollo.io/api/v1 and Leadsets at https://mcp.leadsets.ai.


## For agents

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

## Other comparisons with Apollo API + MCP or Leadsets

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