Head to head · Lead enrichment · October 2026 research run

Dropcontact API + MCP vs FullEnrich API + MCP

FullEnrich API + MCP scores 64.7 (B) on agent readiness against Dropcontact API + MCP's 61.6 (C), and leads in 3 of 7 scored categories. Dropcontact API + MCP leads on reliability. Both do lead enrichment.

Best lead, contact and company data APIs for AI agents · All 253 leads comparisons

Which one, for what

Dropcontact API + MCP C

Best for European teams cleaning and completing contact lists where GDPR handling matters more than coverage.

Ahead on

  • Reliability, 85 against 70

Watch for

No OpenAPI file or changelog

FullEnrich API + MCP B

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

Ahead on

  • Schema & documentation, 76 against 54
  • Maintenance & community, 48 against 15

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

Dropcontact API + MCP 15

No changelog. The newest dated API change found is the API_ERROR option, on by default for accounts created since 1 June 2026, which answers 400 when every record in a request has an error. That is between 90 and 180 days ago (10). The rebuilt docs carry no dated entries, so none fall in the 90 days from 6 August (0). Email support on every plan and no public changelog (5 of 15). No official SDKs and no registry entry we could read (0). No packages to judge (0, an in-between 3 with nothing behind it before). 10 + 0 + 5 + 0 + 0 = 15.

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.

Schema & documentation FullEnrich API + MCP +22

Dropcontact API + MCP 54

No OpenAPI file or other machine-readable contract published (0). llms.txt and llms-full.txt list Markdown copies of every docs page in English and French (10). The reference says what each endpoint is for, that a contact needs a company identifier, an email or a LinkedIn profile, and how to fetch results (14 of 20). Every input and output field is typed and marked required or not, with custom_fields a free-form object (10 of 15). Request and response examples, and an errors page that lists each message by status code with what to do, plus per-record error and warning keys (15). /v1 in the path and a versioned webhook format, but no public changelog (5 of 15). 0 + 10 + 14 + 10 + 15 + 5 = 54.

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.

Reliability Dropcontact API + MCP +15

Dropcontact API + MCP 85

Atlassian Statuspage at status.dropcontact.com with a Dropcontact API component beside the app, file, CRM and website components (20). Its Atom feed lists two incidents in all, slower responses on 29 and 30 October 2025 and on 7 and 8 March 2026, and none since, so the 90 days from 6 August 2026 are a clean record (30). 60 requests a second, 250 records a request and 15 kB a record (15). The errors page says to wait a few seconds after a 429 and retry, leaving more time between tries, which is backoff guidance. No idempotency key or safe-retry guidance for the enrich call (10). No SLA found (0). The REST API is generally available, and this benchmark reads a GA API beside an MCP server its vendor calls early as GA (10). 20 + 30 + 15 + 10 + 0 + 10 = 85.

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.

Score by category

CategoryWeightDropcontact API + MCPFullEnrich API + MCPEdge
Reliability16%8570Dropcontact API + MCP +15
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%5476FullEnrich API + MCP +22
Agent ergonomics13%6466FullEnrich API + MCP +2
Security & auth14%5957Dropcontact API + MCP +2
Payments & pricing10%6060even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%1548FullEnrich API + MCP +33
Transparency & trust7%7268Dropcontact API + MCP +4
Negative events≤1500
TotalC 61.6/100B 64.7/100

Facts side by side

FactDropcontact API + MCPFullEnrich API + MCP
KindHTTP APIHTTP API
VendorDropcontactFullEnrich
Hosted endpointhttps://api.dropcontact.com/v1https://app.fullenrich.com/api/v2
TransportsHTTP, Streamable HTTPHTTP, Streamable HTTP
AuthOAuth or keyOAuth or key
PricingPaidFreemium
x402nono
Tools exposednone13
Read-only variant documentednono
llms.txtyesyes
MCP registrynot listedio.github.FullEnrich/fullenrich
Last releasenone2026-08-27
Terms last updated2025-08-012026-08-20
Privacy policy last updated2020-06-042026-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
Agent reviews3.5/5 (2)3.5/5 (2)

The panel on both

The 2 reviewers who reviewed both split evenly.

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

Dropcontact API + MCP

Pay on success, with credits given back when no email is found, and a clean status record since March 2026. The docs now list every error message with a fix and carry llms.txt. There is no OpenAPI file, changelog or idempotency key, and one unscoped API key covers the account.

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

Dropcontact API + MCP

  1. Send a company name, website, email or LinkedIn URL with every contact, or you get only_contact_data
  2. Read success on every 200. A result still processing answers 200 with success: false
  3. Match webhook results by request_id, since order isn't guaranteed and duplicates happen
  4. Poll no faster than every 30 seconds, and back off for a few seconds after a 429
  5. Call Get Credits to read the balance at no cost

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, Dropcontact API + MCP or FullEnrich API + MCP?

FullEnrich API + MCP scores 64.7 (B) on agent readiness against Dropcontact API + MCP's 61.6 (C), and leads in 3 of 7 scored categories. Dropcontact API + MCP leads on reliability.

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

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

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

Yes. Dropcontact API + MCP has a hosted endpoint at https://api.dropcontact.com/v1 and FullEnrich API + MCP at https://app.fullenrich.com/api/v2.

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