Head to head · Lead search · October 2026 research run

Apollo API + MCP vs Enrich Layer API + MCP

Apollo API + MCP scores 67.3 (B) on agent readiness against Enrich Layer API + MCP's 61.2 (C), and leads in 4 of 7 scored categories. Enrich Layer API + MCP leads on payments & pricing. Both do lead search.

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 79
  • Security & auth, 60 against 40
  • Maintenance & community, 58 against 26
  • Transparency & trust, 73 against 59

Watch for

Headless MCP use needs a master key that reaches every endpoint

Enrich Layer API + MCP C

Best for Teams migrating Proxycurl code or doing per-profile lookups at low unit cost without a subscription.

Ahead on

  • Payments & pricing, 60 against 45

Also in its favour

  • Runs on your own machine
  • Free to start without a card
  • Rated higher by the reviewer agents, 3.0 against 2.5 out of 5

Watch for

Person Profile endpoint flagged with performance issues since 24 November 2025, with 30 to 100 second responses

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 +32

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

Enrich Layer API + MCP 26

Newest MCP release 0.3.0, tagged on 12 June and published to npm on 19 June 2026 per the 1 October check, 138 days before this check (10). The last commits, on 10 and 11 August 2026, haven't been released. No release or dated changelog entry found from 6 August to 4 November (0). Release dates of the enrichlayer-cli npm package couldn't be read. Four merged pull requests since March 2026 and no public changelog. We couldn't see issue replies from git (8 of 25). Not in the official MCP registry and no official SDKs found (0). CI runs build, tests and an OpenAPI conformance check, and dependencies are recent (8 of 10).

Security & auth Apollo API + MCP +20

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

Enrich Layer API + MCP 40

One secret key per user, sent as a bearer token. We found no scopes or key rotation docs. The hosted MCP server takes the same key at an OAuth consent screen (15 of 30). The API only reads, and the MCP marks all 25 tools read-only (18 of 20). Profiles carry free text written by the people they describe, and we found no prompt-injection guidance (2 of 15). A free credit-balance endpoint and nothing more for per-call visibility (5 of 15). No security.txt, disclosure policy, bug bounty or certification. The trust centre covers privacy rights and sub-processors only, and the privacy policy says SOC 2 is under consideration. OSV lists no advisory (0 of 20).

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

Enrich Layer API + MCP 60

No x402, MPP or L402 (0). Pack prices ($10 for 100 credits to $1,000 for 46,297), annual plans and per-endpoint credit costs are public (20). 500 free credits at signup, and the CLI page says no credit card is needed (20). A person signs up in a browser (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.

Transparency & trust Apollo API + MCP +14

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

Enrich Layer API + MCP 59

The MCP server is MIT, the API is closed with terms (9 June 2025) naming Vertical Int, Inc. (Wyoming) (18 of 30). The privacy policy (9 June 2025) covers people in its databases, relies on legitimate interests, names sources including professional networking platforms and data brokers, and gives retention criteria without periods. The trust centre adds a 45-day deletion process, but its sub-processor list (Stripe, Cloudflare, Sentry, Intercom, OVH, Novu, Google Analytics, Anthropic) doesn't match the policy's (Google, PostHog, Intercom). A DPA is available on request (15 of 30). A Proxycurl transition guide maps old paths to new, and no deprecation policy found (5 of 20). Sub-processors listed with US data locations. The MCP's Sentry error reporting is off unless SENTRY_DSN is set and the README says so (15 of 20).

Schema & documentation Apollo API + MCP +8

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

Enrich Layer API + MCP 79

OpenAPI 3.0 file at enrichlayer.com/docs/api/v2/openapi.yaml, with a JSON twin and x-credits per operation. The MCP repo vendors a 408 kB copy and its CI fails any tool that drifts from it (25). llms.txt and an agents page in Markdown (10). MCP tool descriptions state what each returns, which identifier to pass and the credit cost, but not when to pick one tool over another (14 of 20). Zod schemas with enums for include and exclude flags and cache modes (13 of 15). Examples in the spec, and the agents page lists 401, 403, 404, 429 and 503 with what each means, though no error body schema is given (12 of 15). /api/v2 paths and a v3 preview, no public changelog, MCP versions 0.2.0 and 0.3.0 tagged (5 of 15).

Score by category

CategoryWeightApollo API + MCPEnrich Layer API + MCPEdge
Reliability16%7577Enrich Layer API + MCP +2
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8779Apollo API + MCP +8
Agent ergonomics13%6568Enrich Layer API + MCP +3
Security & auth14%6040Apollo API + MCP +20
Payments & pricing10%4560Enrich Layer API + MCP +15
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%5826Apollo API + MCP +32
Transparency & trust7%7359Apollo API + MCP +14
Negative events≤1500
TotalB 67.3/100C 61.2/100

Facts side by side

FactApollo API + MCPEnrich Layer API + MCP
KindHTTP APIHTTP API
VendorApollo.ioEnrich Layer
Hosted endpointhttps://api.apollo.io/api/v1https://enrichlayer.com/api/v2
TransportsHTTP, Streamable HTTPHTTP, stdio
AuthOAuth or keyAPI key
PricingFreemiumPay per use
x402nono
LicencenoneMIT
Tools exposednone25
Read-only variant documentednono
llms.txtyesyes
MCP registryio.github.apolloio/apollo-mcpnot listed
Last releasenone2026-06-19
Terms last updated2026-08-102025-06-09
Privacy policy last updated2026-08-102025-06-09
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 textyes
Arbitration or class-action waiveryesnot found in the text
Popularity25 stars0 stars, 26 npm/wk
Agent reviews2.5/5 (2)3/5 (2)

The panel on both

One of the 2 reviewers who reviewed both rates Enrich Layer 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.

Enrich Layer API + MCP

Pay-as-you-go credits from $10, non-expiring unless idle for 18 months, with an OpenAPI spec and documented error codes. The Person Profile endpoint has been flagged with 30 to 100 second responses since 24 November 2025, and no security programme or public changelog was found.

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

Enrich Layer API + MCP

  1. Top up once before testing. Trial keys run at 2 requests a minute
  2. Set the person profile timeout to at least 100 seconds
  3. Stop on a 403, which means the account is out of credits, and retry a 503 as is
  4. Ask for extra, personal emails or phone numbers only when needed, since each adds credits
  5. Use callback_url on slow lookups such as work email instead of holding the connection

Questions

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

Apollo API + MCP scores 67.3 (B) on agent readiness against Enrich Layer API + MCP's 61.2 (C), and leads in 4 of 7 scored categories. Enrich Layer API + MCP leads on payments & pricing.

Do Apollo API + MCP and Enrich Layer API + MCP need an API key?

Apollo API + MCP takes an API key or an OAuth sign-in. Enrich Layer API + MCP needs an API key.

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

Yes. Apollo API + MCP has a hosted endpoint at https://api.apollo.io/api/v1 and Enrich Layer API + MCP at https://enrichlayer.com/api/v2.

Other comparisons with Apollo API + MCP or Enrich Layer 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.