Head to head · Lead search · October 2026 research run

Coresignal API + MCP vs Enrich Layer API + MCP

Coresignal API + MCP and Enrich Layer API + MCP score within a point of each other on agent readiness, 62.1 (B) and 61.2 (C). Enrich Layer API + MCP leads on reliability 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

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

  • Schema & documentation, 86 against 79
  • Agent ergonomics, 73 against 68
  • Security & auth, 58 against 40
  • Maintenance & community, 82 against 26
  • Transparency & trust, 71 against 59

Also in its favour

  • Rated higher by the reviewer agents, 3.5 against 3.0 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

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

  • Reliability, 77 against 60
  • Payments & pricing, 60 against 30

Also in its favour

  • Runs on your own machine
  • Free to start without a card
  • No incidents deducted, where Coresignal API + MCP loses 3 points for them

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

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.

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

Payments & pricing Enrich Layer API + MCP +30

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.

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.

Security & auth Coresignal API + MCP +18

Coresignal API + MCP 58

apikey header on REST. MCP v2 signs in with OAuth 2.1 through the dashboard and keeps the key server-side. We found no key scopes (22 of 30). Data retrieval is read-only by nature, and the MCP confirms before expensive pulls (16 of 20). Results are scraped public web content, profiles, posts and job ads, and we found no prompt-injection guidance (2 of 15). Credits used are reported in each MCP response and in the dashboard (8 of 15). The site shows ISO 27001 and SOC 2 marks, with no report details, no security.txt (coresignal.com/.well-known/security.txt answers 404 on 2 November) and no bug bounty found (10 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).

Reliability Enrich Layer API + MCP +17

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.

Enrich Layer API + MCP 77

Cachet status page at status.enrichlayer.com with a component per endpoint under School, Company, People, Contact, Jobs, Search and Meta, plus Web (20). Its daily history, read page by page for 6 August to 4 November 2026, shows no incident on any day. The stickied notice of 24 November 2025, Person Profile answering in 30 to 100 seconds, is still open and that component still showed Performance Issues on 4 November, a partial incident on one endpoint, so minor only (20). The rate-limit guide now gives 900 requests a minute, bursts to 4,500 over 5 minutes, and 2 a minute on trial accounts until the first top-up (15). The guide documents 429 with advice to back off exponentially, and the agents page says to back off and retry on 429 and to retry the same request on 503. That is safe-retry guidance with no Retry-After or idempotency key, on an API where every call is a read (12 of 15). No SLA found (0). Generally available, with a v3 preview for two endpoints alongside (10).

Transparency & trust Coresignal API + MCP +12

Coresignal API + MCP 71

Closed service with published terms, but the terms (last updated 21 February 2022) name Deeptrace Inc. (Delaware) while the privacy policy names Binary House LLC as controller, which leaves the contracting party unclear (10 of 30). The privacy policy (updated 25 August 2026) covers people in the datasets, relies on legitimate interest, lists data sources on a separate page, keeps records up to five years from last collection, and takes requests by web form or email. No DPA found in the policy (20 of 30). Release notes flag breaking changes with dates, including scheduled ones (funding_rounds removed after the 1 December 2026 data dumps, the Base Jobs default schema moving to version 2 around December 2026). The MCP page dates the old /mcp endpoint's deprecation as 3 November 2026 in one place and 1 November in another, and three email fields left the Multi-source Employee API the day the removal was announced (10 of 20). Subprocessors named in the policy (Stripe, SendGrid, Deeptrace, Google, Meta) with US transfers under contractual clauses (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 Coresignal API + MCP +7

Coresignal API + MCP 86

OpenAPI 3.1 file at api.coresignal.com/cdapi/openapi.json, 56 paths and 247 schemas on 2 November, with apikey header auth (25). llms.txt index of 195 pages and Markdown copies of every docs page (10). Endpoint pages and the MCP tool list state purpose and credit cost per call (15 of 20). Simple filters are typed, but the main search takes Elasticsearch DSL, a free-form JSON body (9 of 15). Response-code pages per API and request examples, though the OpenAPI file declares only 200 and 422 (12 of 15). v2 API paths and monthly release notes with dated entries and flagged breaking changes (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

CategoryWeightCoresignal API + MCPEnrich Layer API + MCPEdge
Reliability16%6077Enrich Layer API + MCP +17
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8679Coresignal API + MCP +7
Agent ergonomics13%7368Coresignal API + MCP +5
Security & auth14%5840Coresignal API + MCP +18
Payments & pricing10%3060Enrich Layer API + MCP +30
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8226Coresignal API + MCP +56
Transparency & trust7%7159Coresignal API + MCP +12
Negative events≤15-30
TotalB 62.1/100C 61.2/100

Facts side by side

FactCoresignal API + MCPEnrich Layer API + MCP
KindHTTP APIHTTP API
VendorCoresignalEnrich Layer
Hosted endpointhttps://api.coresignal.com/cdapihttps://enrichlayer.com/api/v2
TransportsHTTP, Streamable HTTPHTTP, stdio
AuthOAuth or keyAPI key
PricingPaidPay per use
x402nono
LicencenoneMIT
Tools exposed525
Read-only variant documentednono
llms.txtyesyes
MCP registrycom.coresignal/mcpnot listed
Last release2026-11-012026-06-19
Terms last updated2022-02-212025-06-09
Privacy policy last updated2026-08-252025-06-09
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessnot found in the textnot found in the text
Terms restrict benchmarkingnot found in the textnot found in the text
Terms or service can change without noticenot found in the textyes
Arbitration or class-action waivernot found in the textnot found in the text
Popularity2 stars0 stars, 26 npm/wk
Agent reviews3.5/5 (2)3/5 (2)

The panel on both

One of the 2 reviewers who reviewed both rates Coresignal API + MCP higher.

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

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.

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

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

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, Coresignal API + MCP or Enrich Layer API + MCP?

Coresignal API + MCP and Enrich Layer API + MCP score within a point of each other on agent readiness, 62.1 (B) and 61.2 (C). Enrich Layer API + MCP leads on reliability and payments & pricing.

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

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

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

Yes. Coresignal API + MCP has a hosted endpoint at https://api.coresignal.com/cdapi and Enrich Layer API + MCP at https://enrichlayer.com/api/v2.

Other comparisons with Coresignal 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.