Enrichments vs Dropcontact
Waterfall enrichment, with an endpoint your agents can call
Cheapest source first, stop when the field is filled — delivered as a REST API, an MCP server, a chat agent and CSV upload, on one key.
| Contact | |
|---|---|
 Liam Foster Queued | |
 Maya Torres Queued | |
 Ethan Brooks Queued | |
 Zoe Martin Queued | |
 Andre Willis Queued | |
 Chloe Bennett Queued | |
 Noah Klein Queued | |
 Priya Shah Queued | |
 Kenji Tanaka Queued | |
Ava Boone Queued |
Enrichments vs Dropcontact
The differences that decide it, including the ones that go the other way.
| Feature | Enrichments | Dropcontact |
|---|---|---|
| Approach | Waterfall across several sources, cheapest first. | Computes and verifies rather than reselling a stored contact database. |
| European data posture | Standard processing terms; no EU-specific residency guarantee is published. | A European provider that makes GDPR posture central to the product. |
| Billing model | Credits, charged only when a field comes back. Free plan: 100 credits, then $69/mo. | Published subscription plans. |
| Use from an AI agent | Native MCP endpoint. Connect it to Claude or ChatGPT and enrich in the chat. | No first-party MCP endpoint. |
| Phone numbers | Mobile numbers from a LinkedIn profile URL, 10 credits per number found. Unverified — no deliverability equivalent exists for a phone, so none is implied. | Email and company data focused. |
| Access surfaces | REST API, MCP server, in-product chat agent, and CSV upload — one key for all four. | API plus CRM and sequencer integrations. |
| Start free |
Waterfall across several sources, cheapest first.
Computes and verifies rather than reselling a stored contact database.
Standard processing terms; no EU-specific residency guarantee is published.
A European provider that makes GDPR posture central to the product.
Credits, charged only when a field comes back. Free plan: 100 credits, then $69/mo.
Published subscription plans.
Native MCP endpoint. Connect it to Claude or ChatGPT and enrich in the chat.
No first-party MCP endpoint.
Mobile numbers from a LinkedIn profile URL, 10 credits per number found. Unverified — no deliverability equivalent exists for a phone, so none is implied.
Email and company data focused.
REST API, MCP server, in-product chat agent, and CSV upload — one key for all four.
API plus CRM and sequencer integrations.
Only pay for the match that lands
Just ask. The agent plans the run, resolves each row, and checks every address before it reaches you — and a row that comes back empty is never charged.
Built for the whole GTM stack
Enrich a form fill in real time, backfill a million-row list overnight, and keep your CRM current — all from the same key.
A row that comes back empty costs nothing.
Credits are charged per delivered field, and every charge is written to a ledger you can read line by line.
People, companies and firmographics resolve behind a single endpoint — and the same key and the same credit balance work from the REST API, the MCP server, the in-product chat agent, and CSV upload. Ask in any of them and the answer comes back in the same shape.
Work email, title, seniority, department, location, LinkedIn URL, company domain and firmographics. No phone numbers.
Enrich a single record inline on a form fill, or hand a list to an async job and poll it. Same key, same ledger, same field catalogue.
POST /v1/people/enrich
One REST endpoint per operation, an OpenAPI document you can generate a client from, idempotency keys on every write, and typed errors.
GET /v1/openapi
Every record carries the time it was last verified, so you can re-run only what has gone stale — and a re-run that returns nothing new is not charged.
result.lastVerifiedAt
Lands wherever your team already works
A run finishes as a file, a signed webhook or a JSON response your stack already speaks — no connector to install on the other end.
Enrichments and Dropcontact — common questions
- Which should I choose on GDPR grounds?
- If EU data posture is the deciding factor, Dropcontact makes that its central claim and you should evaluate it on those terms directly. This page does not try to win that row.
- What is different here?
- A native MCP server so AI agents can enrich directly, mobile numbers alongside email, and a credit model that charges only when a field actually comes back.
- Do you have native CRM integrations?
- Not first-party today. The REST API and MCP server are the integration path, and the free plan is there to test whether that fits your stack before you pay.
Start enriching in a single call
Free to try, no card required. Ship your first enriched record before your coffee gets cold.
The free plan includes 100 credits, and only rows that return data are charged.