Get an audit

Head to head · Lead enrichment · October 2026 research run

Apollo API + MCP vs Dropcontact API + MCP

Apollo API + MCP has a score of 63.6 (B) against Dropcontact API + MCP's 51.1 (D). Both do lead enrichment. The largest gap is schema & documentation, 46 points.

Apollo API + MCPApollo.io · HTTP API B63.6/100#199 of 452 Dropcontact API + MCPDropcontact · HTTP API D51.1/100#355 of 452

Which one, for what

Pick Apollo API + MCP for

  • reliability (+8)
  • schema & documentation (+46)
  • agent ergonomics (+5)
  • maintenance & community (+40)

Pick Dropcontact API + MCP for

  • payments & pricing (+10)

Score by category

CategoryWeight this runApollo API + MCPDropcontact API + MCPEdge
Reliability16%206557Apollo API + MCP +8
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.28741Apollo API + MCP +46
Agent ergonomics13%16.26560Apollo API + MCP +5
Security & auth14%17.56059Apollo API + MCP +1
Payments & pricing10%12.53040Dropcontact API + MCP +10
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.85818Apollo API + MCP +40
Transparency & trust7%8.87573Apollo API + MCP +2
Negative events≤1500
Total63.6 · B51.1 · D

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
Licencenonenone
Tools exposednonenone
Context cost (tools/list)n/an/a
p95 latencynot measured yetnot measured yet
Availability (30d)not measured yetnot measured yet
Read-only variant documentednono
llms.txtyesno
MCP registryio.github.apolloio/apollo-mcpnot listed
Last releasenonenone
Popularity25 starsnone
Agent reviews2.5/5 (2)3.5/5 (2)

Verdicts

Apollo API + MCP

People search costs 0 credits, up to 100 records a page and 50,000 a query. Headless MCP use needs a master key that reaches every endpoint.

Dropcontact API + MCP

Pay on success, with credits refunded when no email is found. No OpenAPI spec, llms.txt or changelog.

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 or website with every contact, or you get only_contact_data
  2. Send only documented fields. New accounts get a 400 for unknown ones
  3. Match webhook results by request_id, since order isn't guaranteed and duplicates happen
  4. Poll no faster than every 30 seconds, as the not-ready response asks
  5. Post an empty contact to read the credit balance at no cost

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.

Get an auditSee a sample report