Head to head · Lead search · October 2026 research run

Apollo API + MCP vs Retriever

Apollo API + MCP scores 67.3 (B) on agent readiness against Retriever's 32 (F), and leads in 6 of 7 scored categories. Retriever leads on agent ergonomics. 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

  • Reliability, 75 against 45
  • Schema & documentation, 87 against 82
  • Security & auth, 60 against 23
  • Payments & pricing, 45 against 30
  • Maintenance & community, 58 against 5
  • Transparency & trust, 73 against 49

Also in its favour

  • No incidents deducted, where Retriever loses 15 points for them

Watch for

Headless MCP use needs a master key that reaches every endpoint

Retriever F

Best for A sales team that wants an agent to build qualified lead tables and run outreach from Claude, Cursor or Codex.

Ahead on

  • Agent ergonomics, 75 against 65

Watch for

Its sequences send LinkedIn invitations, messages, visits and likes from connected accounts automatically, which LinkedIn forbids, so customers' accounts can be restricted

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

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

Retriever 5

No changelog, release notes or dated API change found, and the docs carry no dates; the blog's posts are marketing articles, not release notes (0 and 0). Support is an email address and a demo booking, with no public changelog or community channel that answers (5 of 25). Not in the official MCP registry and no official SDK (0). No package to check (0). The domain dates from 7 April 2026.

Security & auth Apollo API + MCP +37

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

Retriever 23

The MCP server's OAuth 2.1 issues an ordinary API key, and keys have no scopes or expiry and work as their creator in that organisation: plain revocable keys (20), less 10 because the MCP docs offer the key in the URL as ?api_key= (10 of 30). No read-only mode; destructive hints and explicit-request instructions on cancels and deletes, and the outreach toolset can be switched off (8 of 20). The tools return scraped pages, social posts and inbox replies, with no prompt-injection guidance found (0). Credit charges per run and a credits ledger by source, but no audit log documented (5 of 15). No security.txt (404), disclosure policy, bug bounty or certification found (0).

Reliability Apollo API + MCP +30

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

Retriever 45

No status page found, linked from neither the site nor the docs (0), so no incident history to read (5). Rate limits published per key and class, 30 a minute for runs and Go, 120 for services, 600 for reads and MCP messages, 5 runs at once per organisation (15). 429 carries Retry-After, and a recipe on reliable integrations covers retries, polling and idempotency keys (15). The pricing page lists "Dedicated support & SLA" on Enterprise only, with no SLA terms published (0). The API and MCP server aren't labelled beta (10).

Transparency & trust Apollo API + MCP +24

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

Retriever 49

Closed source with clear terms, last updated 30 August 2026 (15). The privacy policy states retention (deletion within 30 days of closing an account) and names some subprocessors, but says nothing about the LinkedIn and email accounts customers connect, the people in lead tables or the data providers named on the pricing page (12 of 30). The terms say the service may be changed or removed "with reasonable notice" and material changes to the terms get 15 days' notice; no deprecation dates found (8 of 20). Subprocessors are given as examples (Vercel, Railway, Supabase, Anthropic, OpenAI) with no data locations, beyond Standard Contractual Clauses for transfers (8 of 20).

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.

Retriever 30

No x402, MPP or L402 (0). Credits per action and the dollar price per credit ($0.0134 on Starter) are public without a login (30). No free tier or trial without a card found; the terms say only that free tiers may be offered (0). Access needs a browser signup and a subscription, so an agent can't onboard itself (0).

Agent ergonomics Retriever +10

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

Retriever 75

67 tools in the catalogue (5), with 5 back because the outreach tools are a toolset shown only when the organisation has a sender and switchable in settings (10 of 25). Limit, offset and cursor pagination, up to 1,000 rows a call, and the first 20 rows returned with a finished run (18 of 20). Stable error codes with the action to take (20). Idempotency-Key on run creation, and readOnlyHint, destructiveHint and idempotentHint on the tools (20). Few required parameters (a run needs only a prompt), but no official SDK, only a Node client in a recipe (7 of 15).

Score by category

CategoryWeightApollo API + MCPRetrieverEdge
Reliability16%7545Apollo API + MCP +30
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8782Apollo API + MCP +5
Agent ergonomics13%6575Retriever +10
Security & auth14%6023Apollo API + MCP +37
Payments & pricing10%4530Apollo API + MCP +15
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%585Apollo API + MCP +53
Transparency & trust7%7349Apollo API + MCP +24
Negative events≤150-15
TotalB 67.3/100F 32/100

Facts side by side

FactApollo API + MCPRetriever
KindHTTP APIHTTP API
VendorApollo.ioRetriever
Hosted endpointhttps://api.apollo.io/api/v1https://api.retriever.run/mcp
TransportsHTTP, Streamable HTTPStreamable HTTP
AuthOAuth or keyOAuth or key
PricingFreemiumPaid
x402nono
Tools exposednone67
Read-only variant documentednoyes
llms.txtyesyes
MCP registryio.github.apolloio/apollo-mcpnot listed
Terms last updated2026-08-102026-08-30
Privacy policy last updated2026-08-102026-08-30
Customer content may train modelsyesnot found in the text
Terms restrict automated accessyesyes
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)none

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.

Retriever

Retriever automates outreach from customers' LinkedIn accounts, which LinkedIn's rules forbid. For agents it has an OAuth MCP server, an OpenAPI file, idempotency keys, stable error codes and published credit prices, but no status page, changelog, security contact, free tier or named company behind it.

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

Retriever

  1. Don't enrol leads in a sequence with LinkedIn steps without the user knowing LinkedIn forbids automated activity and can restrict their account
  2. Send an Idempotency-Key with each run and replay with the same key after a timeout, so a retry doesn't start a second billed run
  3. Run getEmail, getPhoneNumber and webResearch through service_batch_execute, even for one person; service_execute refuses them
  4. Check credits before a paid run, and call service_inspect for a service's thingsToKnow and credit cost before executing it
  5. On 429 wait for Retry-After; at most 5 runs execute per organisation, so a queued run starts on its own and shouldn't be created again

Questions

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

Apollo API + MCP scores 67.3 (B) on agent readiness against Retriever's 32 (F), and leads in 6 of 7 scored categories. Retriever leads on agent ergonomics.

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

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

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

Yes. Apollo API + MCP has a hosted endpoint at https://api.apollo.io/api/v1 and Retriever at https://api.retriever.run/mcp.

Other comparisons with Apollo API + MCP or Retriever

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.