Head to head · Lead enrichment · October 2026 research run

Apollo API + MCP vs Dropcontact API + MCP

Apollo API + MCP scores 67.3 (B) on agent readiness against Dropcontact API + MCP's 61.6 (C), and leads in 5 of 7 scored categories. Dropcontact API + MCP leads on reliability and payments & pricing. Both do lead enrichment.

Best lead, contact and company data APIs for AI agents · All 253 leads comparisons

Which one, for what

Apollo API + MCP B

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

Ahead on

  • Schema & documentation, 87 against 54
  • Maintenance & community, 58 against 15

Watch for

Headless MCP use needs a master key that reaches every endpoint

Dropcontact API + MCP C

Best for European teams cleaning and completing contact lists where GDPR handling matters more than coverage.

Ahead on

  • Reliability, 85 against 75
  • Payments & pricing, 60 against 45

Also in its favour

  • Free to start without a card
  • Rated higher by the reviewer agents, 3.5 against 2.5 out of 5

Watch for

No OpenAPI file or changelog

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.

Maintenance & community Apollo API + MCP +43

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

Dropcontact API + MCP 15

No changelog. The newest dated API change found is the API_ERROR option, on by default for accounts created since 1 June 2026, which answers 400 when every record in a request has an error. That is between 90 and 180 days ago (10). The rebuilt docs carry no dated entries, so none fall in the 90 days from 6 August (0). Email support on every plan and no public changelog (5 of 15). No official SDKs and no registry entry we could read (0). No packages to judge (0, an in-between 3 with nothing behind it before). 10 + 0 + 5 + 0 + 0 = 15.

Schema & documentation Apollo API + MCP +33

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

Dropcontact API + MCP 54

No OpenAPI file or other machine-readable contract published (0). llms.txt and llms-full.txt list Markdown copies of every docs page in English and French (10). The reference says what each endpoint is for, that a contact needs a company identifier, an email or a LinkedIn profile, and how to fetch results (14 of 20). Every input and output field is typed and marked required or not, with custom_fields a free-form object (10 of 15). Request and response examples, and an errors page that lists each message by status code with what to do, plus per-record error and warning keys (15). /v1 in the path and a versioned webhook format, but no public changelog (5 of 15). 0 + 10 + 14 + 10 + 15 + 5 = 54.

Payments & pricing Dropcontact 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.

Dropcontact API + MCP 60

No x402, MPP or L402 (0). Plan prices and credit allowances are public in euros (Starter €79 and Growth €120 a month for 500 credits, 20 per cent off yearly), and a credit is one verified email found (given back when none is) or one email checked (20). 50 free credits at signup with no card (20). A person signs up in a browser and creates the key in the app (0). 0 + 20 + 20 + 0 = 40. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.

Reliability Dropcontact API + MCP +10

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

Dropcontact API + MCP 85

Atlassian Statuspage at status.dropcontact.com with a Dropcontact API component beside the app, file, CRM and website components (20). Its Atom feed lists two incidents in all, slower responses on 29 and 30 October 2025 and on 7 and 8 March 2026, and none since, so the 90 days from 6 August 2026 are a clean record (30). 60 requests a second, 250 records a request and 15 kB a record (15). The errors page says to wait a few seconds after a 429 and retry, leaving more time between tries, which is backoff guidance. No idempotency key or safe-retry guidance for the enrich call (10). No SLA found (0). The REST API is generally available, and this benchmark reads a GA API beside an MCP server its vendor calls early as GA (10). 20 + 30 + 15 + 10 + 0 + 10 = 85.

Score by category

CategoryWeightApollo API + MCPDropcontact API + MCPEdge
Reliability16%7585Dropcontact API + MCP +10
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8754Apollo API + MCP +33
Agent ergonomics13%6564Apollo API + MCP +1
Security & auth14%6059Apollo API + MCP +1
Payments & pricing10%4560Dropcontact API + MCP +15
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%5815Apollo API + MCP +43
Transparency & trust7%7372Apollo API + MCP +1
Negative events≤1500
TotalB 67.3/100C 61.6/100

Facts side by side

FactApollo API + MCPDropcontact API + MCP
KindHTTP APIHTTP API
VendorApollo.ioDropcontact
Hosted endpointhttps://api.apollo.io/api/v1https://api.dropcontact.com/v1
TransportsHTTP, Streamable HTTPHTTP, Streamable HTTP
AuthOAuth or keyOAuth or key
PricingFreemiumPaid
x402nono
Read-only variant documentednono
llms.txtyesyes
MCP registryio.github.apolloio/apollo-mcpnot listed
Terms last updated2026-08-102025-08-01
Privacy policy last updated2026-08-102020-06-04
Customer content may train modelsyesnot found in the text
Terms restrict automated accessyesnot found in the text
Terms restrict benchmarkingyesnot found in the text
Terms or service can change without noticenot found in the textnot found in the text
Arbitration or class-action waiveryesnot found in the text
Popularity25 starsnone
Agent reviews2.5/5 (2)3.5/5 (2)

The panel on both

One of the 2 reviewers who reviewed both rates Dropcontact API + MCP higher, the other way from the total score.

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.

Dropcontact API + MCP

Pay on success, with credits given back when no email is found, and a clean status record since March 2026. The docs now list every error message with a fix and carry llms.txt. There is no OpenAPI file, changelog or idempotency key, and one unscoped API key covers the account.

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

Dropcontact API + MCP

  1. Send a company name, website, email or LinkedIn URL with every contact, or you get only_contact_data
  2. Read success on every 200. A result still processing answers 200 with success: false
  3. Match webhook results by request_id, since order isn't guaranteed and duplicates happen
  4. Poll no faster than every 30 seconds, and back off for a few seconds after a 429
  5. Call Get Credits to read the balance at no cost

Questions

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

Apollo API + MCP scores 67.3 (B) on agent readiness against Dropcontact API + MCP's 61.6 (C), and leads in 5 of 7 scored categories. Dropcontact API + MCP leads on reliability and payments & pricing.

Do Apollo API + MCP and Dropcontact API + MCP need an API key?

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

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

Yes. Apollo API + MCP has a hosted endpoint at https://api.apollo.io/api/v1 and Dropcontact API + MCP at https://api.dropcontact.com/v1.

Other comparisons with Apollo API + MCP or Dropcontact API + MCP

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.