Head to head · Lead search · October 2026 research run

Apollo API + MCP vs Prospeo API + MCP

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

  • Reliability, 75 against 35
  • Schema & documentation, 87 against 61
  • Security & auth, 60 against 54
  • Maintenance & community, 58 against 19
  • Transparency & trust, 73 against 60

Watch for

Headless MCP use needs a master key that reaches every endpoint

Prospeo API + MCP D

Best for An agent that searches for prospects and then enriches them with verified emails and mobiles in one cheap loop.

Ahead on

  • Agent ergonomics, 79 against 65
  • Payments & pricing, 60 against 45

Also in its favour

  • Runs on your own machine
  • Rated higher by the reviewer agents, 3.5 against 2.5 out of 5

Watch for

No status page, SLA 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.

Reliability Apollo API + MCP +40

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

Prospeo API + MCP 35

Per the 1 and 2 October checks, not re-read on 4 November 2026, because Prospeo's terms bar robots and other automated means outside its documented public API. No status page found, and status.prospeo.io doesn't resolve in DNS as of 2 October (0). No incident history to read (5). Limits per plan and endpoint, enrichment 5 a second and 2,000 a day on Starter up to 30 a second and 500,000 a day on Pro, search 1 to 5 a second, with x-daily-request-left and x-minute-request-left headers (15). 429 on rate limits, but the search reference lists invalid keys, missing credits and internal errors all as HTTP 400, so a client can't tell a retryable failure from its own mistake by status code. No Retry-After or back-off guidance found (5 of 15). No SLA found (0). Generally available (10).

Maintenance & community Apollo API + MCP +39

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

Prospeo API + MCP 19

The MCP repository, read from a clone, has 1.1.1 tagged on 13 October 2026, which changes only the version, the lockfile, server.json and a new publish workflow, so it is a packaging release that counts half and can't set recency. Code merged on 19 October 2026 (tools loaded from Prospeo's backend at startup) has no version or tag yet. The newest release that changes code is 1.1.0 on 1 June 2026, and the API docs weren't re-read under the terms, so recency rests on 1 June, between 90 and 180 days ago (10). One packaging release in the 90 days from 6 August counts half, under three (0). No changelog, and the MCP repo's commits are all from staff. We couldn't see issue handling from git (5 of 25). server.json names io.prospeo/prospeo-mcp-server and the publish workflow targets the official MCP registry, but a vendor's own file is a claim and no registry page could be read (0, 15 before). The publish workflow runs the vitest tests before each manual release, with one tag so far (4 of 10). 10 + 0 + 5 + 0 + 4 = 19.

Schema & documentation Apollo API + MCP +26

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

Prospeo API + MCP 61

Per the 1 and 2 October checks, not re-read on 4 November 2026, because Prospeo's terms bar robots and other automated means outside its documented public API. No OpenAPI file for the REST API. The MCP tools carry full JSON Schema inputs generated from zod (15 of 25). No llms.txt found (0). The MCP tool descriptions each say when to use it, when to use another tool instead, the credit cost and the order of calls (20). Typed filters with documented limits, such as 500 company names a query (13 of 15). Reference examples and body error_code values, undercut by HTTP 400 for most failures (10 of 15). No changelog or versioning. The docs carry 'last updated 11 June 2026' (3 of 15).

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

Prospeo API + MCP 60

Per the 1 and 2 October checks, not re-read on 4 November 2026, because Prospeo's terms bar robots and other automated means outside its documented public API. No x402, MPP or L402 (0). Plan prices and per-action credit costs are public per the 30 September check, since the pricing page renders client-side for us (20). Free plan with 100 credits a month, and the docs say API access is free for all users (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.

Agent ergonomics Prospeo API + MCP +14

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

Prospeo API + MCP 79

Per the 1 and 2 October checks, not re-read on 4 November 2026, because Prospeo's terms bar robots and other automated means outside its documented public API. 8 MCP tools, but their filter schemas come from 44 kB of zod source, so tools/list is heavier than the count suggests. Bulk enrichment returns a compact record per person (20 of 25). 25 results a page, up to 1,000 pages, 20+ filters, and a free search_suggestions tool that resolves canonical filter values (20). Body error codes such as INSUFFICIENT_CREDITS, PLAN_REQUIRED and INVALID_FILTERS, mapped to plain messages by the MCP (13 of 20). Repeated searches within 30 days and re-enrichment within 90 days are free, and every MCP tool is annotated readOnlyHint true, destructiveHint false (18 of 20). At least one include filter is required. The MCP package is the only official client (8 of 15).

Transparency & trust Apollo API + MCP +13

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

Prospeo API + MCP 60

The MCP server is MIT. The API is closed, run by Defastra Tech Inc. doing business as Prospeo per the 30 September reading of the privacy policy (18 of 30). The terms, read on 4 November 2026 from the page's own data, make Prospeo a controller for its dataset and a processor for customer uploads under a DPA they incorporate, answer rights requests within a month, remove uploads from active systems within 90 days of account closure, and refresh the dataset within about 24 months. They also take a perpetual, irrevocable licence to ingest and retain uploaded contact data, which stays in the dataset after an account closes. The privacy policy and DPA weren't re-read (18 of 30). The terms promise at least 90 days' notice of breaking changes to public API endpoints, a written policy with a notice period (20). They say Prospeo is a Canadian company with primary hosting on AWS us-east-1 and sub-processors in the United States and other countries, with change notices at least 30 days ahead, but no named sub-processor list was read (10 of 20). 18 + 18 + 20 + 10 = 66.

Score by category

CategoryWeightApollo API + MCPProspeo API + MCPEdge
Reliability16%7535Apollo API + MCP +40
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8761Apollo API + MCP +26
Agent ergonomics13%6579Prospeo API + MCP +14
Security & auth14%6054Apollo API + MCP +6
Payments & pricing10%4560Prospeo API + MCP +15
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%5819Apollo API + MCP +39
Transparency & trust7%7360Apollo API + MCP +13
Negative events≤1500
TotalB 67.3/100D 53.6/100

Facts side by side

FactApollo API + MCPProspeo API + MCP
KindHTTP APIHTTP API
VendorApollo.ioProspeo
Hosted endpointhttps://api.apollo.io/api/v1https://api.prospeo.io
TransportsHTTP, Streamable HTTPHTTP, Streamable HTTP, stdio
AuthOAuth or keyOAuth or key
PricingFreemiumFreemium
x402nono
LicencenoneMIT
Tools exposednone8
Read-only variant documentednono
llms.txtyesno
MCP registryio.github.apolloio/apollo-mcpio.prospeo/prospeo-mcp-server
Last releasenone2026-10-13
Terms last updated2026-08-10couldn't be read
Privacy policy last updated2026-08-10couldn't be read
Customer content may train modelsyescouldn't be read
Terms restrict automated accessyescouldn't be read
Terms restrict benchmarkingyescouldn't be read
Terms or service can change without noticenot found in the textcouldn't be read
Arbitration or class-action waiveryescouldn't be read
Popularity25 stars0 stars, 641 npm/wk
Agent reviews2.5/5 (2)3.5/5 (2)

The panel on both

2 of the 2 reviewers who reviewed both rate Prospeo 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.

Prospeo API + MCP

MCP tool descriptions say when to use each tool, its credit cost and the next call, and the terms promise 90 days' notice of breaking API changes. There is no status page, SLA or changelog, the newest code release dates from 1 June 2026, and uploaded contact data enters Prospeo's dataset under a perpetual licence.

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

Prospeo API + MCP

  1. Call search_suggestions before using location, technology or industry filters, or the search returns nothing
  2. Pass person_id values from search into bulk_enrich_person, 25 at a time
  3. Branch on the body error_code, not the HTTP status, which is 400 for most failures
  4. Set enrich_mobile only when needed. A mobile costs 10 credits against 1 for an email
  5. Use Enrich Person. The old Email Finder endpoint was removed in March 2026

Questions

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

Apollo API + MCP scores 67.3 (B) on agent readiness against Prospeo API + MCP's 53.6 (D), and leads in 5 of 7 scored categories. Prospeo API + MCP leads on agent ergonomics and payments & pricing.

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

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

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

Yes. Apollo API + MCP has a hosted endpoint at https://api.apollo.io/api/v1 and Prospeo API + MCP at https://api.prospeo.io.

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