Head to head · Lead enrichment · October 2026 research run

Crustdata API + MCP vs Dropcontact API + MCP

Dropcontact API + MCP scores 61.6 (C) on agent readiness against Crustdata API + MCP's 52.4 (D), and leads in 4 of 7 scored categories. Crustdata API + MCP leads on schema & documentation, agent ergonomics and maintenance & community. Both do lead enrichment.

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

Which one, for what

Crustdata API + MCP D

Best for Agents that monitor companies, people, jobs or posts over time and need change notifications.

Ahead on

  • Schema & documentation, 89 against 54
  • Agent ergonomics, 73 against 64
  • Maintenance & community, 57 against 15

Watch for

No status page and no SLA

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 42
  • Payments & pricing, 60 against 8
  • Transparency & trust, 72 against 56

Also in its favour

  • Free to start without a card
  • Rated higher by the reviewer agents, 3.5 against 2.5 out of 5
  • No incidents deducted, where Crustdata API + MCP loses 3 points for them

Watch for

No OpenAPI file 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.

Payments & pricing Dropcontact API + MCP +52

Crustdata API + MCP 8

No x402, MPP or L402 (0). Credit costs per endpoint and field are public, but no dollar price per credit is, and enterprise plans start at "four figures a month" through sales. We gave 5 rather than 0 because an agent can work out relative cost from the public credit table (5). Every new self-serve account now starts with $20 in free credits, but no page we read says whether signing up needs a card, so the line isn't met on the evidence (0). A person signs up in the dashboard (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 5 is 8.

Dropcontact API + MCP 60

No x402, MPP or L402 (0). Plan prices and credit allowances are public in euros (Starter €79 and Growth €120 a month for 500 credits, 20 per cent off yearly), and a credit is one verified email found (given back when none is) or one email checked (20). 50 free credits at signup with no card (20). A person signs up in a browser and creates the key in the app (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 Dropcontact API + MCP +43

Crustdata API + MCP 42

No status page found. status.crustdata.com still doesn't answer and the docs link none (0). No readable incident history (5). Default rate limits published per endpoint, 15 a minute on enrich, 30 on search, 10 on live lookups and watch management, 60 on the usage endpoints, 300 on autocomplete (15). 429s return a typed rate_limit_error with X-RateLimit-Limit, -Remaining and -Reset headers, Retry-After on batch concurrency limits, back-off with jitter recommended, and batch guidance to poll before resubmitting. No idempotency keys, so safe-retry guidance without keys (12). No SLA found, and the published terms cover the website only (0). The API is generally available. Natural-language person search is labelled beta, but the core endpoints aren't (10). 0 + 5 + 15 + 12 + 0 + 10 = 42.

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.

Maintenance & community Crustdata API + MCP +42

Crustdata API + MCP 57

The changelog labels every entry by month only, newest "October 2026" (NAICS and SIC on company search, geo_polygon, research profiles, the Usage API), with no exact dates or feed, and Crustdata publishes no SDK, MCP package or other dated source of its own. Read as the Zoho listings read month-only entries, dated to the month, all of October lies 4 to 34 days back, within 90 days but not shown within 30 (20). Nine entries fall in September and October, months wholly inside the 90 days from 6 August (20). Detailed public changelog, and we didn't test support (12 of 15). The only registry entry found on 1 October sat under a personal GitHub namespace, and we found no official SDKs (0). Versioned specs are current. No packages to judge (5 of 10). 20 + 20 + 12 + 0 + 5 = 57.

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.

Schema & documentation Crustdata API + MCP +35

Crustdata API + MCP 89

Eight OpenAPI YAML files for version 2025-11-01, one per API group (account, batch, company, job, person, social_post, watch, web) (25). llms.txt with Markdown twins (10). Endpoint pages explain cost and when to search versus enrich (17 of 20). Typed filter trees with documented operators (12 of 15). Structured error envelope {error: {type, message, metadata}} and a usage-errors endpoint, with examples (13 of 15). Date-pinned API versions and a detailed changelog. Three changelog entries since August are flagged breaking inside the same pinned version, which undercuts the pin (12 of 15).

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.

Transparency & trust Dropcontact API + MCP +16

Crustdata API + MCP 56

Closed service. The terms are a website-use notice naming CrustData Inc. (California), while the privacy policy names Crustdata Technologies Inc., and we found no API terms (8 of 30). The privacy policy (updated 19 May 2025) covers people in the datasets, cites consent, contract and legitimate interests, and runs an opt-out portal that removes data within 30 days and blocks it from coming back. Retention has no periods and no DPA is mentioned (15 of 30). Date-pinned versions and migration guides, but breaking changes inside the pinned version with no dated notice (8 of 20). US transfers stated, no subprocessor list (5 of 20).

Dropcontact API + MCP 72

Closed service with terms (updated 5 August 2025) naming Dropcontact SAS, registered in Bobigny, no. 823 752 647 (15). The personal data charter (updated 5 August 2025) keeps prospecting data 3 years after the relationship plus 4 in intermediate storage, takes rights requests at data@dropcontact.io, says data may be collected from publicly accessible information and hosted in the EU with some subcontractors in the United States under standard contractual clauses, and a DPA is published. The pricing page says processing runs only on Dropcontact's own algorithms on EU servers with no reliance on non-compliant third-party providers, and that it uses no contact databases. It now also says mobile numbers come from signature extraction within internal email flows, with five years of history, which the charter doesn't mention (22 of 30). One dated change for new accounts (1 June 2026) and no deprecation policy (8 of 20). EU hosting and US subcontractors stated, no named subprocessor list found (10 of 20). 15 + 22 + 8 + 10 = 55.

Agent ergonomics Crustdata API + MCP +9

Crustdata API + MCP 73

Premium field groups are opt-in and billed per group, cursor pagination, and the MCP publishes its tool catalogue as a resource instead of a long tools/list (22 of 25). Cursor pagination and rich filters (20). Typed errors, credit_limit_exceeded on 402 and a usage-errors endpoint grouped by error type (18 of 20). Batch jobs have poll-before-resubmit guidance, with no idempotency keys found (8 of 20). Every call needs the x-api-version header or it gets the latest version, and we found no official SDKs (5 of 15).

Dropcontact API + MCP 64

The MCP has a handful of tools (enrich from a name and company or a LinkedIn URL, validate an email, check credits, then fetch the result by request ID), and REST takes up to 250 contacts a call. No field selection (20 of 25). No search, so little to page or filter. forceResults=true returns the records already enriched (10 of 20). The errors page gives each message with a fix, and per-record keys such as only_contact_data say what to add (20). Asynchronous jobs keyed by request_id and pay on success, but no idempotency key, and webhooks can arrive out of order or twice (8 of 20). Few required fields and no official SDKs (6 of 15). 20 + 10 + 20 + 8 + 6 = 64.

Score by category

CategoryWeightCrustdata API + MCPDropcontact API + MCPEdge
Reliability16%4285Dropcontact API + MCP +43
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8954Crustdata API + MCP +35
Agent ergonomics13%7364Crustdata API + MCP +9
Security & auth14%5659Dropcontact API + MCP +3
Payments & pricing10%860Dropcontact API + MCP +52
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%5715Crustdata API + MCP +42
Transparency & trust7%5672Dropcontact API + MCP +16
Negative events≤15-30
TotalD 52.4/100C 61.6/100

Facts side by side

FactCrustdata API + MCPDropcontact API + MCP
KindHTTP APIHTTP API
VendorCrustdataDropcontact
Hosted endpointhttps://api.crustdata.comhttps://api.dropcontact.com/v1
TransportsHTTP, Streamable HTTPHTTP, Streamable HTTP
AuthOAuth or keyOAuth or key
PricingPay per usePaid
x402nono
Read-only variant documentednono
llms.txtyesyes
Terms last updatedno date given2025-08-01
Privacy policy last updated2025-05-192020-06-04
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 textnot found in the text
Arbitration or class-action waivernot found in the textnot found in the text
Agent reviews2.5/5 (2)3.5/5 (2)

The panel on both

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

Crustdata API + MCP

Per-field credit prices readable per account, X-Credits-Used on every response, per-key caps and $20 in free credits for new self-serve accounts. No status page, no SLA, no dollar price per credit, and changes that refuse earlier valid requests posted only after they shipped.

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.

Before you call either

Crustdata API + MCP

  1. Always send x-api-version: 2025-11-01. Unpinned calls get the latest version
  2. Call /account/endpoints first to see what your plan enables and what each field costs
  3. Ask only for the premium field groups you need, since each one bills
  4. Poll GET /batch/{id} before submitting more batch jobs. Active jobs count against a cap of 5 to 30
  5. Read the crustdata://catalog resource before calling MCP tools

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

Questions

Which is better for AI agents, Crustdata API + MCP or Dropcontact API + MCP?

Dropcontact API + MCP scores 61.6 (C) on agent readiness against Crustdata API + MCP's 52.4 (D), and leads in 4 of 7 scored categories. Crustdata API + MCP leads on schema & documentation, agent ergonomics and maintenance & community.

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

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

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

Yes. Crustdata API + MCP has a hosted endpoint at https://api.crustdata.com and Dropcontact API + MCP at https://api.dropcontact.com/v1.

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