Head to head · Lead search · October 2026 research run

Apollo API + MCP vs Coresignal API + MCP

Apollo API + MCP scores 67.3 (B) on agent readiness against Coresignal API + MCP's 62.1 (B), and leads in 5 of 7 scored categories. Coresignal API + MCP leads on agent ergonomics and maintenance & community. 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 60
  • Payments & pricing, 45 against 30

Also in its favour

  • No incidents deducted, where Coresignal API + MCP loses 3 points for them

Watch for

Headless MCP use needs a master key that reaches every endpoint

Coresignal API + MCP B

Best for Company and workforce research, headcount history and hiring signals at volume, and for pipelines that want raw records.

Ahead on

  • Agent ergonomics, 73 against 65
  • Maintenance & community, 82 against 58

Also in its favour

  • Rated higher by the reviewer agents, 3.5 against 2.5 out of 5

Watch for

Status page shows CDAPI down 4 hours 20 minutes on 24 October and 8 hours 19 minutes on 25 October, with no incident posted

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 Coresignal API + MCP +24

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

Coresignal API + MCP 82

Release notes have dated entries to 1 November 2026 (30). 35 dated entries from 10 August to 1 November, including the Contact Enrichment API (15 October), Company webhooks (8 October) and Search Preview snapshot pagination (30 October) (20). Public, detailed release notes, and we didn't test support (12 of 15). Listed in the official MCP registry as com.coresignal/mcp 2.0.0, a domain-verified namespace, published 7 August 2026 (15). No SDK packages to judge (5 of 10). 30 + 20 + 12 + 15 + 5 = 82.

Reliability Apollo API + MCP +15

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

Coresignal API + MCP 60

Better Stack status page at status.coresignal.com with CDAPI, RTAPI and Self-service components (20). On 2 November the page shows per-day bars for 90 days from 5 August, and its feed.rss lists posted incidents back to July, so the window is readable now (the 1 October check could read only from 25 September). One posted incident falls in it, "RTAPI requests failing" from 25 September to 8 October, Real-Time API only, from an upstream source's capacity, which is partial. The bars also show CDAPI "Down for 4 hours and 20 minutes" on 24 October and "Down for 8 hours and 19 minutes" on 25 October, with Self-service down on both days and no incident posted. That is the core Data API down for more than an hour, read as one major (10). Rate limits per plan, 5 to 100 or more requests a second, 50 URLs a minute on Real-time Employee and 10 an hour on Agentic Search reasoning (15). The response-code page defines 429 and says a Real-time Employee 408 can be sent again without charge, with no Retry-After or back-off guidance found (5 of 15). No SLA found (0). The surfaces agents use are generally available (10). 20 + 10 + 15 + 5 + 0 + 10 = 60.

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.

Coresignal API + MCP 30

No x402, MPP or L402 (0). Every plan price, credit allowance and per-endpoint credit cost is public, and only successful collect or enrich calls are charged (20). 7-day trial with 2,000 credits once per company email domain. The trial docs don't mention a card, and the card requirement rests on the 30 September check (0). 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): 20 is 30.

Agent ergonomics Coresignal API + MCP +8

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

Coresignal API + MCP 73

The hosted MCP has 5 tools, and large results go to a file read back in pages with artifact_read rather than into the context (23 of 25). Search filters and pagination, with search itself free (18 of 20). 402 when credits run out and per-API response codes (14 of 20). The API is read-only apart from webhook subscriptions, credits are only taken on a 200, and MCP v2 pauses to confirm record count and credit cost before large pulls (12 of 20). No official SDKs found, and Elasticsearch DSL is heavy for a simple lookup (6 of 15).

Score by category

CategoryWeightApollo API + MCPCoresignal API + MCPEdge
Reliability16%7560Apollo API + MCP +15
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8786Apollo API + MCP +1
Agent ergonomics13%6573Coresignal API + MCP +8
Security & auth14%6058Apollo API + MCP +2
Payments & pricing10%4530Apollo API + MCP +15
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%5882Coresignal API + MCP +24
Transparency & trust7%7371Apollo API + MCP +2
Negative events≤150-3
TotalB 67.3/100B 62.1/100

Facts side by side

FactApollo API + MCPCoresignal API + MCP
KindHTTP APIHTTP API
VendorApollo.ioCoresignal
Hosted endpointhttps://api.apollo.io/api/v1https://api.coresignal.com/cdapi
TransportsHTTP, Streamable HTTPHTTP, Streamable HTTP
AuthOAuth or keyOAuth or key
PricingFreemiumPaid
x402nono
Tools exposednone5
Read-only variant documentednono
llms.txtyesyes
MCP registryio.github.apolloio/apollo-mcpcom.coresignal/mcp
Last releasenone2026-11-01
Terms last updated2026-08-102022-02-21
Privacy policy last updated2026-08-102026-08-25
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 stars2 stars
Agent reviews2.5/5 (2)3.5/5 (2)

The panel on both

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

Coresignal API + MCP

Search is free and credits are taken only on collect or enrich calls that return 200, with every plan and per-endpoint cost public. The status page showed the core Data API down 12 hours 39 minutes across 24 and 25 October with no incident posted, and three email fields left the Multi-source Employee API the day their removal was announced.

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

Coresignal API + MCP

  1. Search for IDs first (free), then collect only the records you need
  2. Request only the bundles you need. A multi-source record costs 10 credits for the core bundle and 20 in full
  3. Use MCP v2 at /mcp/v2. The older /mcp endpoint is deprecated in November 2026
  4. Treat a 402 as out of credits, not a transient error
  5. Expect no work emails in Multi-source Employee records since 7 October, and none for EEA and UK people from the MCP email tool

Questions

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

Apollo API + MCP scores 67.3 (B) on agent readiness against Coresignal API + MCP's 62.1 (B), and leads in 5 of 7 scored categories. Coresignal API + MCP leads on agent ergonomics and maintenance & community.

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

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

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

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

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