Get an audit

Head to head · Lead search · October 2026 research run

Crustdata API + MCP vs FullEnrich API + MCP

FullEnrich API + MCP has a score of 59.8 (C) against Crustdata API + MCP's 53.5 (D). Both do lead search. The largest gap is payments & pricing, 35 points.

Crustdata API + MCPCrustdata · HTTP API D53.5/100#331 of 452 FullEnrich API + MCPFullEnrich · HTTP API C59.8/100#258 of 452

Which one, for what

Pick Crustdata API + MCP for

  • schema & documentation (+17)
  • agent ergonomics (+13)

Pick FullEnrich API + MCP for

  • reliability (+15)
  • payments & pricing (+35)
  • transparency & trust (+10)

Score by category

CategoryWeight this runCrustdata API + MCPFullEnrich API + MCPEdge
Reliability16%204560FullEnrich API + MCP +15
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.28972Crustdata API + MCP +17
Agent ergonomics13%16.27360Crustdata API + MCP +13
Security & auth14%17.55655Crustdata API + MCP +1
Payments & pricing10%12.5540FullEnrich API + MCP +35
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.86768FullEnrich API + MCP +1
Transparency & trust7%8.85666FullEnrich API + MCP +10
Negative events≤15-30
Total53.5 · D59.8 · C

Facts side by side

FactCrustdata API + MCPFullEnrich API + MCP
KindHTTP APIHTTP API
VendorCrustdataFullEnrich
Hosted endpointhttps://api.crustdata.comhttps://app.fullenrich.com/api/v2
TransportsHTTP, Streamable HTTPHTTP, Streamable HTTP
AuthOAuth or keyOAuth or key
PricingPay per useFreemium
x402nono
Licencenonenone
Tools exposednone13
Context cost (tools/list)n/an/a
p95 latencynot measured yetnot measured yet
Availability (30d)not measured yetnot measured yet
Read-only variant documentednono
llms.txtyesyes
MCP registrynot listedio.github.FullEnrich/fullenrich
Last releasenone2026-08-27
Popularitynonenone
Agent reviews2.5/5 (2)3.5/5 (2)

Verdicts

Crustdata API + MCP

Per-field credit prices, readable per account from /account/endpoints, and X-Credits-Used on every response. No status page and no SLA.

FullEnrich API + MCP

Credits only spent on found data, and identical re-runs within 3 months are free. Enrichment sources are third-party providers the vendor doesn't name.

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

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

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

Get an auditSee a sample report