Head to head · Lead search · October 2026 research run

Coresignal API + MCP vs FullEnrich API + MCP

FullEnrich API + MCP scores 64.7 (B) on agent readiness against Coresignal API + MCP's 62.1 (B), and leads in 2 of 7 scored categories. Coresignal API + MCP leads on schema & documentation, 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

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 76
  • Agent ergonomics, 73 against 66
  • Maintenance & community, 82 against 48

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

FullEnrich API + MCP B

Best for Maximising find rate on known contacts, especially mobiles, without a long-term contract.

Ahead on

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

Also in its favour

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

Watch for

Enrichment sources are data providers the vendor doesn't name

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

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.

FullEnrich API + MCP 48

Every dated source of the vendor's own was looked for, in the MCP and skills repository (tags and CHANGELOG), the product changelog (answered 400 on 4 November; newest entry 30 November 2024 per the 1 October check), the docs (no changelog page; the OpenAPI file's Last-Modified date records no listed change). 1.0.4 on 27 August 2026 only links the repository from server.json and corrects the README, a packaging release that counts half and can't set recency. 1.0.2 (10 August) rewrote the full-crm skill's description and steps as well as adding the portable package, and 1.0.3 on 11 August changed skill behaviour (opt-out signals, a confirmation before sequencer changes), so both count in full. The newest of them, 1.0.3, is 85 days back (20). From 6 August, 1.0.2 and 1.0.3 in full and 1.0.4 at half make 2.5, under three (0; was 20). Support by email and help centre (6 of 15). Listed in the official MCP registry as io.github.FullEnrich/fullenrich, a GitHub-verified namespace (15). The skills repo has tests and a version-locked publish workflow (7 of 10). 20+0+6+15+7 = 48.

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

FullEnrich API + MCP 60

No x402, MPP or L402 (0). Per-unit credit costs and plan prices are public, on the pricing page and its Markdown twin, 1 credit a work email, 3 a personal email, 10 a mobile, 0.25 a search result, Pro from $29 a month for 500 credits ($55 for 1,000) (20). 50 trial credits with no card, API and MCP included (20). A person signs up in a browser (0). 0+20+20+0 = 40. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.

Reliability FullEnrich API + MCP +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.

FullEnrich API + MCP 70

Better Stack status page, but with one component (app.fullenrich.com/app) and none for the API or MCP (15 of 20). Its incident history, read on 4 November month by month from December 2025 to November 2026, says "No incidents reported" for every month, so the page has never posted an incident in the history we read (20, this run's value for a never-posted page; was 15 with the history unread). The monitor bar shows uptime figures of 100 and 99.983 per cent across its 30 to 90 day views, with no incident posted. 60 calls a minute on every endpoint, 100 contacts a bulk and 100 concurrent enrichments per workspace (15). The v2 OpenAPI documents a 429 on six operations with code error.rate.limit and the message "Too many requests. Try again in 1m", and identical re-submissions within 3 months aren't charged again, but there is no safe-retry guidance for writes (10 of 15; was 5). No SLA found (0). Generally available, no beta label on the API or MCP (10). 15+20+15+10+0+10 = 70.

Schema & documentation Coresignal API + MCP +10

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

FullEnrich API + MCP 76

OpenAPI file for v2 at docs.fullenrich.com/api/v2/reference/openapi.yaml (version 2.0.0, eight paths, Last-Modified 3 November 2026), with a v1 file alongside (25). llms.txt with 34 links and Markdown twins (10). The MCP keeps tool descriptions short on purpose and moves workflow guidance into separate skills, so a client without skills gets less of it (12 of 20). Typed inputs, with helper tools that list valid industry, seniority and function codes (12 of 15). Test contacts that cost 0 credits and signed webhook examples. The OpenAPI file gives 400, 401, 402, 404 and 429 responses with a code and message schema and named examples such as error.enrichment.first_name.empty and error.rate.limit, though the docs have no separate error page (12 of 15; was 8, the 1 October check found no error reference). v1 and v2 paths. The public product changelog stopped at 30 November 2024 per the 1 October check and answered 400 "Invalid page" on 4 November, and only the MCP package has a current CHANGELOG (5 of 15). 25+10+12+12+12+5 = 76.

Agent ergonomics Coresignal API + MCP +7

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

FullEnrich API + MCP 66

13 MCP tools with short descriptions. Search returns a free preview of 10 results plus a count, and bulk output goes to CSV or JSON exports rather than the chat (17 of 25). Structured filters for people and companies, single-record lookups and export endpoints (16 of 20). The OpenAPI file documents error codes per operation, 20 named codes in all, for missing fields, an enrichment still in progress, unknown keys and the rate limit, which an agent can act on (14 of 20; was 8). Asynchronous enrichment with polling or a signed webhook, identical inputs within 3 months return without a new charge, and the MCP guide asks for a balance check and confirmation before paid steps. No tool annotations confirmed (12 of 20). No official SDKs found (7 of 15). 17+16+14+12+7 = 66.

Score by category

CategoryWeightCoresignal API + MCPFullEnrich API + MCPEdge
Reliability16%6070FullEnrich API + MCP +10
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8676Coresignal API + MCP +10
Agent ergonomics13%7366Coresignal API + MCP +7
Security & auth14%5857Coresignal API + MCP +1
Payments & pricing10%3060FullEnrich API + MCP +30
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8248Coresignal API + MCP +34
Transparency & trust7%7168Coresignal API + MCP +3
Negative events≤15-30
TotalB 62.1/100B 64.7/100

Facts side by side

FactCoresignal API + MCPFullEnrich API + MCP
KindHTTP APIHTTP API
VendorCoresignalFullEnrich
Hosted endpointhttps://api.coresignal.com/cdapihttps://app.fullenrich.com/api/v2
TransportsHTTP, Streamable HTTPHTTP, Streamable HTTP
AuthOAuth or keyOAuth or key
PricingPaidFreemium
x402nono
Tools exposed513
Read-only variant documentednono
llms.txtyesyes
MCP registrycom.coresignal/mcpio.github.FullEnrich/fullenrich
Last release2026-11-012026-08-27
Terms last updated2022-02-212026-08-20
Privacy policy last updated2026-08-252026-08-20
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 textyes
Terms or service can change without noticenot found in the textnot found in the text
Arbitration or class-action waivernot found in the textyes
Popularity2 starsnone
Agent reviews3.5/5 (2)3.5/5 (2)

The panel on both

The 2 reviewers who reviewed both rate them the same.

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.

FullEnrich API + MCP

Credits are spent only on found data, identical re-runs within 3 months are free, and the v2 OpenAPI documents error codes per operation. The status page covers only the web app, no MCP release since 27 August changed more than packaging, and the enrichment data providers aren't named.

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

FullEnrich API + MCP

  1. Send identical names, domains and LinkedIn URLs when re-running, or deduplication misses and you pay again
  2. Expect 30 to 90 seconds a contact. Use the webhook or poll get_enrichment_results
  3. Ask for mobiles only when needed. They cost 10 credits against 1 for a work email
  4. Call list_industries and list_seniorities before filtering search
  5. Use the 0-credit test contacts in the docs to check an integration
  6. On a 429 with error.rate.limit, wait a minute before retrying. The limit is 60 calls a minute on every endpoint

Questions

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

FullEnrich API + MCP scores 64.7 (B) on agent readiness against Coresignal API + MCP's 62.1 (B), and leads in 2 of 7 scored categories. Coresignal API + MCP leads on schema & documentation, agent ergonomics and maintenance & community.

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

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

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

Yes. Coresignal API + MCP has a hosted endpoint at https://api.coresignal.com/cdapi and FullEnrich API + MCP at https://app.fullenrich.com/api/v2.

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