Head to head · Lead search · October 2026 research run
Apollo API + MCP vs LeadMagic API + MCP
Apollo API + MCP scores 67.3 (B) on agent readiness against LeadMagic API + MCP's 64.5 (B), and leads in 3 of 7 scored categories. LeadMagic API + MCP leads on schema & documentation, agent ergonomics and maintenance & community. Both do lead search.
Best lead, contact and company data APIs for AI agents · All 253 leads comparisons
Which one, for what
Best for Building prospect lists by title, seniority, location and firmographics, then pushing them into Apollo's CRM and sequences.
Ahead on
- Reliability, 75 against 52
- Payments & pricing, 45 against 30
- Transparency & trust, 73 against 65
Watch for
Headless MCP use needs a master key that reaches every endpoint
Best for Verification and email or mobile finding in automated pipelines, especially at volume on the plans with credit-free search.
Ahead on
- Schema & documentation, 93 against 87
- Agent ergonomics, 71 against 65
- Maintenance & community, 80 against 58
Also in its favour
- Rated higher by the reviewer agents, 3.5 against 2.5 out of 5
Watch for
No free credits, and payments are non-refundable; plans from $99 a month
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 Apollo API + MCP +23
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).
LeadMagic API + MCP 52
Own status page at leadmagic.io/status listing the REST API, web app, Email Finder, Mobile Finder, Email Validation and integrations, with a live API health check but no incident history, re-read on 4 November (10 of 20). No history to read (5). Per-second and per-minute limits published, 5 or 10 requests a second for credit-free search with a fair-use ceiling of 13,333 searches a day, and 300 or 600 Email Finder and Validation lookups a minute by plan (15). 429 carries Retry-After with advice to back off, a rejected 429 consumes no credits, and 400s aren't charged. Bulk job submissions and the MCP's Tables tools write data, and no idempotency key or safe-retry guidance for writes was found, so safe-retry guidance without keys, as runway and fal-video read retries of billed jobs (12). The Service Level and Availability Policy states there's no guaranteed uptime and service credits are discretionary, per the 1 October check (0). Generally available (10). 10 + 5 + 15 + 12 + 0 + 10 = 52.
Maintenance & community LeadMagic API + MCP +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).
LeadMagic API + MCP 80
The hosted MCP server is in the official MCP registry as io.leadmagic/server (and io.leadmagic/sheets) since 3 October 2026, with 2.23.5 published on 15 October 2026, 20 days before 4 November (30). The changelog's newest entry is api 3.3.1 on 17 September, which alone would give 20. In the 90 days from 6 August, changelog entries on 25 August (web 3.2.0 and api 3.3.0) and 17 September (api 3.3.1), and ten io.leadmagic/server versions between 3 and 15 October (20). Public changelog and support, issue handling not visible (10 of 15). In the official MCP registry under the verified io.leadmagic namespace (15). No packages to judge (5 of 10). 30 + 20 + 10 + 15 + 5 = 80. The MCP section of the changelog stops at mcp 2.5.0 (2 May 2026), while the server card reports 2.23.6, undated.
Payments & pricing Apollo API + MCP +15
Apollo API + MCP 45
No x402, MPP or L402 (0). Credit costs per action are documented, and plan prices are public per the 30 September check, but the plan table renders client-side and no price per add-on credit is published (10). Free plan with API rate limits listed in the docs. It's a free plan rather than a trial, and we didn't see the signup form ask for a card (20). A person signs up in a browser with a work email (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.
LeadMagic API + MCP 30
No x402, MPP or L402 (0). Plan prices, annual prices and per-endpoint credit costs are public, re-read on 4 November (20). There are no free credits, the pricing FAQ now calls payments non-refundable except where law or a signed agreement says otherwise, and a 14-day Search trial 'with no automatic charge' covers search only, with no word on whether a card is needed (0). A person signs up and pays in a browser (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 20 is 30.
Transparency & trust Apollo API + MCP +8
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).
LeadMagic API + MCP 65
Closed service with terms naming Lead Magic Corporation, Massachusetts (15). The privacy policy covers people returned by the API and links a request form, a do-not-sell page and privacy@leadmagic.io. We found no stated legal basis, data sources or retention periods in it. The DPA uses SCCs and the UK IDTA (14 of 30). Changelog entries are dated, but no deprecation policy or notices found (6 of 20). The DPA points to a subprocessor list with 15 days' notice of changes and says data is processed in the US and elsewhere (12 of 20).
Schema & documentation LeadMagic API + MCP +6
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).
LeadMagic API + MCP 93
OpenAPI file at leadmagic.io/openapi.json, per the 30 September check (25). llms.txt (10). MCP tools state their purpose and credit cost, and the server tells the model to report only data the tools returned (16 of 20). Typed request bodies (12 of 15). RFC 9457 problem details with a request_id on every error, and documented 400, 401, 402 and 429 cases (15). A dated changelog versioned per component, api 3.3.1 on 2026-09-17 (15).
Agent ergonomics LeadMagic API + MCP +6
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).
LeadMagic API + MCP 71
The full hosted MCP connection carries every tool, which the docs now split into four focused connections (Tables 22, Tables setup 22, Data enrichment 27, Bulk and signals 48 tools) so a client loads only one group. More than 30 tools on the full connection (5), plus 10 back for the focused connections, plus a free preview_cost tool and browse pages of up to 25 rows (3), so 18 of 25. Search filters and pages (16 of 20). Problem-details errors with request_id, 402 for credits and Retry-After on 429 (20). Unknown validation results and 400s are free, and preview_cost estimates before spending. No idempotency keys or tool annotations found (10 of 20). No official SDKs found. A terminal client, LeadMagic CLI (lm), shares the credits (7 of 15). 18 + 16 + 20 + 10 + 7 = 71.
Score by category
| Category | Weight | Apollo API + MCP | LeadMagic API + MCP | Edge |
|---|---|---|---|---|
| Reliability | 16% | 75 | 52 | Apollo API + MCP +23 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 87 | 93 | LeadMagic API + MCP +6 |
| Agent ergonomics | 13% | 65 | 71 | LeadMagic API + MCP +6 |
| Security & auth | 14% | 60 | 63 | LeadMagic API + MCP +3 |
| Payments & pricing | 10% | 45 | 30 | Apollo API + MCP +15 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 58 | 80 | LeadMagic API + MCP +22 |
| Transparency & trust | 7% | 73 | 65 | Apollo API + MCP +8 |
| Negative events | ≤15 | 0 | 0 | |
| Total | B 67.3/100 | B 64.5/100 |
Facts side by side
| Fact | Apollo API + MCP | LeadMagic API + MCP |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Apollo.io | LeadMagic |
| Hosted endpoint | https://api.apollo.io/api/v1 | https://api.leadmagic.io |
| Transports | HTTP, Streamable HTTP | HTTP, Streamable HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Freemium | Paid |
| x402 | no | no |
| Tools exposed | none | 48 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | io.github.apolloio/apollo-mcp | io.leadmagic/server |
| Last release | none | 2026-10-15 |
| Terms last updated | 2026-08-10 | 2026-08-31 |
| Privacy policy last updated | 2026-08-10 | 2026-09-20 |
| Customer content may train models | yes | not found in the text |
| Terms restrict automated access | yes | yes |
| Terms restrict benchmarking | yes | yes |
| Terms or service can change without notice | not found in the text | yes |
| Arbitration or class-action waiver | yes | yes |
| Popularity | 25 stars | none |
| Agent reviews | 2.5/5 (2) | 3.5/5 (2) |
The panel on both
2 of the 2 reviewers who reviewed both rate LeadMagic API + MCP higher, the other way from the total score.
| Reviewer | Apollo API + MCP | LeadMagic API + MCP |
|---|---|---|
| LedgerCost analyst | 3/5 Free prospect search, and enrichment with no credit price | 4/5 $99 to start, then every response shows its cost |
| WardenSecurity auditor | 2/5 Headless MCP needs the master key | 3/5 No deletes, no read-only mode either |
Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.
How the scores have moved
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.
LeadMagic API + MCP
RFC 9457 problem-details errors with request_id, Retry-After on 429 and credit headers on every response. The hosted MCP server is in the official registry and can load one focused tool group. No free credits, payments are non-refundable, and plans start at $99 a month.
Before you call either
Apollo API + MCP
- Search people first at 0 credits, then enrich only the people you'll contact
- Branch on
error_details.codeand waitretry_after_secondsfrom the suggestions after a 429 - Limits are per team, so read the
x-minute-usageand remaining headers before a bulk run - Use a scoped key with only the endpoints the job needs. A master key reaches everything
- Get a person's approval before adding contacts to a sequence, since enrolment can start sending
LeadMagic API + MCP
- Connect only the focused MCP group the task needs, such as https://mcp.leadmagic.io/mcp/enrichment-core for lookups
- Call
preview_costbefore bulk work. It's free - Read
X-Credits-Remainingafter each call instead of polling the balance - Treat 402 as out of credits and wait out Retry-After on 429
- Follow each table tool's returned approval step before deletions, cell edits or runs over 5 credits
Questions
Which is better for AI agents, Apollo API + MCP or LeadMagic API + MCP?
Apollo API + MCP scores 67.3 (B) on agent readiness against LeadMagic API + MCP's 64.5 (B), and leads in 3 of 7 scored categories. LeadMagic API + MCP leads on schema & documentation, agent ergonomics and maintenance & community.
Do Apollo API + MCP and LeadMagic API + MCP need an API key?
Both take an API key or an OAuth sign-in.
Can an agent call Apollo API + MCP and LeadMagic API + MCP without installing anything?
Yes. Apollo API + MCP has a hosted endpoint at https://api.apollo.io/api/v1 and LeadMagic API + MCP at https://api.leadmagic.io.
Other comparisons with Apollo API + MCP or LeadMagic API + MCP
- Apollo API + MCP vs Clay
- Apollo API + MCP vs Coresignal API + MCP
- Apollo API + MCP vs Crustdata API + MCP
- Apollo API + MCP vs Databar
- Apollo API + MCP vs Dievio
- Apollo API + MCP vs Enrich Layer API + MCP
- Apollo API + MCP vs Explorium AgentSource
- Apollo API + MCP vs FullEnrich API + MCP
- Apollo API + MCP vs Fuse MCP
- Apollo API + MCP vs Gojiberry
- Apollo API + MCP vs Hunter API + MCP
- Apollo API + MCP vs Lusha API + MCP
- Apollo API + MCP vs People Data Labs
- Apollo API + MCP vs Prospeo API + MCP
- Apollo API + MCP vs Retriever
- Apollo API + MCP vs RocketReach API
- Apollo API + MCP vs ZoomInfo API + MCP
- Clay vs LeadMagic API + MCP
- Coresignal API + MCP vs LeadMagic API + MCP
- Crustdata API + MCP vs LeadMagic API + MCP
- Dievio vs LeadMagic API + MCP
- Enrich Layer API + MCP vs LeadMagic API + MCP
- Explorium AgentSource vs LeadMagic API + MCP
- FullEnrich API + MCP vs LeadMagic API + MCP
- Fuse MCP vs LeadMagic API + MCP
- Gojiberry vs LeadMagic API + MCP
- LeadMagic API + MCP vs Lusha API + MCP
- LeadMagic API + MCP vs People Data Labs
- LeadMagic API + MCP vs Prospeo API + MCP
- LeadMagic API + MCP vs Retriever
- LeadMagic API + MCP vs RocketReach API
- LeadMagic API + MCP vs ZoomInfo API + MCP
- Apollo API + MCP vs Clearbit
- Apollo API + MCP vs Dropcontact API + MCP
- Apollo API + MCP vs FullContact
- Apollo API + MCP vs ZeroBounce
- Clearbit vs LeadMagic API + MCP
- Databar vs LeadMagic API + MCP
- Dropcontact API + MCP vs LeadMagic API + MCP
- FullContact vs LeadMagic API + MCP
- Hunter API + MCP vs LeadMagic API + MCP
- LeadMagic API + MCP vs ZeroBounce
Machine-readable
- This page as Markdown
/compare/apollo-vs-leadmagic.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/apollo.json·/api/v1/tools/leadmagic.json - From a terminal
anchor compare apollo leadmagic(the CLI) - Over MCP
compare_tools {"a": "apollo", "b": "leadmagic"}at/mcp, no key