# Dievio vs Dropcontact API + MCP

> Dropcontact scores 51 (D) to Dievio's 43 (E) for lead enrichment. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/dievio-vs-dropcontact
- Markdown: https://www.anchorterminal.com/compare/dievio-vs-dropcontact.md (~5,200 tokens)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-10-31

Dropcontact API + MCP scores 51 (D) on agent readiness against Dievio's 43 (E), and leads in 4 of 7 scored categories. Dievio leads on schema & documentation and maintenance & community. Both do lead enrichment.

- Dievio: grade E, 43/100, rank #1090 of 1245. Markdown https://www.anchorterminal.com/tools/dievio.md · JSON https://www.anchorterminal.com/api/v1/tools/dievio.json
- Dropcontact API + MCP: grade D, 51/100, rank #927 of 1245. Markdown https://www.anchorterminal.com/tools/dropcontact.md · JSON https://www.anchorterminal.com/api/v1/tools/dropcontact.json
- Best lead, contact and company data APIs for AI agents: https://www.anchorterminal.com/best/lead-data/index.md
- All 190 leads comparisons: https://www.anchorterminal.com/compare/lead-data/index.md

## Which one, for what

### Dievio (E)

Good for: Agents building small prospect lists by title, seniority, department, location, company size and industry at a low published price per lead, previewing the count for free first, and handing the user a CSV, JSON or JSONL file from a shared list without opening the dashboard.

Ahead on:
- Schema & documentation, 50 against 41
- Maintenance & community, 28 against 18

Watch for: No status page, incident history or SLA; the terms say uptime is not guaranteed and the service may change at any time

### Dropcontact API + MCP (D)

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

Ahead on:
- Reliability, 57 against 28
- Payments & pricing, 40 against 35
- Transparency & trust, 72 against 27

Watch for: No OpenAPI spec, llms.txt or changelog


## Why the edge

### Transparency & trust: Dropcontact API + MCP +45

- Dievio (27): Closed service. The terms (last updated 31 October 2026) cover use, credits, connected agents, a 30-day refund and availability in about 300 words but name no legal entity, address, governing law or jurisdiction, so the contracting party is unknown (8 of 30). The privacy policy (31 October 2026) lists the categories processed, the purposes, recipients by category, the agent connection data, and the access periods (authorization requests 10 minutes, codes 5, access tokens an hour, refresh 30 days, export links 15 minutes), says lead search uses Dievio's own contact database without saying where records are collected from, lets people in the database ask for access, correction, deletion or suppression by email, keeps records for as long as needed with no periods, and agrees with the terms and the docs on credits, revocation and link expiry; no DPA was found (14 of 30). No deprecation policy or notices; the terms allow the service to change at any time, and plan allowances and API prices changed between the 20 May and 31 October 2026 copies of the pricing pages with no dated notice (0 of 20). Service providers are named by category only (hosting, databases, authentication, contact processing, analytics, email delivery, payments), with no names, locations or transfer basis (4 of 20). 8+14+0+4 = 26.
- Dropcontact API + MCP (72): Closed service with terms naming Dropcontact SAS, registered in Bobigny, no. 823 752 647 (15). The personal data charter (updated 5 August 2025) says Dropcontact is a processor when enriching for a customer, keeps prospect data 3 years plus 4 in intermediate storage, takes rights requests at data@dropcontact.io, and a DPA is published. The pricing page says enrichment runs on its own algorithms on EU servers, while the charter says data is collected from public sources and some subcontractors are in the US under SCCs (22 of 30). One dated change notice (June 2026) and no deprecation policy (8 of 20). EU hosting and US subcontractors stated, no named subprocessor list found (10 of 20).

### Reliability: Dropcontact API + MCP +29

- Dievio (28): Hosted reading, for the REST API with the MCP server it shares a database with. No public status page was found. None is linked from the docs or the footer, https://dievio.com/status answers 404 and status.dievio.com does not resolve (0). No readable incident history, so the floor (5). No rate limit is published for the REST API or the MCP tools. The only numbers are the export cap of 10 download starts a minute per connection and 100,000 contacts a file, the OAuth timers and input bounds such as 500 LinkedIn URLs a call, and the privacy policy mentions hashed rate-limit keys without a figure (5 of 15). No 429 or Retry-After is documented, and the REST errors are 401, 402, 500 and 502 with no retry guidance; every MCP mutation takes a request_id UUID replayed when retried with identical arguments, the workflows page says never to repeat a paid lookup with a new ID and to reconcile against the job list first, and a low balance returns fewer rows rather than failing, while a retried REST search has no idempotency key and is charged again (8 of 15). No SLA. The terms (last updated 31 October 2026) say uptime is not guaranteed and the service may change at any time (0). The REST API and the 30-tool MCP server carry no beta label, though the search response documents `search_id` as currently null and `counting` as currently false, and the server is unversioned (10). 0+5+5+8+0+10 = 28.
- Dropcontact API + MCP (57): Atlassian Statuspage at status.dropcontact.com with a separate Dropcontact API component (20). The front page shows no incidents from 17 September to 1 October. The history page renders client-side and we couldn't read July or August, so this is two clean weeks, not 90 days (10). 60 requests a second, 250 contacts a request and 15 kB a contact (15). 429 is documented without Retry-After. Results not ready return 'try again in 30 seconds', and the docs warn that webhooks can arrive out of order or twice (7 of 15). No SLA found (0). The REST API is generally available, while the vendor calls remote MCP connections 'still early' (5 of 10).

### Maintenance & community: Dievio +10

- Dievio (28): Closed service with no changelog, release notes or version numbers. The latest dated changes on the vendor's pages are the terms and privacy policy of 31 October 2026, which describe the agent integration, token lifetimes and export expiry, and blog posts of 21 and 30 October 2026 on API billing; the MCP server, absent from the February and May 2026 archived copies, carries no date, and the API landing pages say content reviewed May 2026 (20 of 30). No release record, so no three dated entries in 90 days; 84 dated blog posts from 29 March to 30 October 2026 are articles, not releases (0). Support is one address, support@dievio.com, with email support on Starter and priority support on Growth; no public changelog, community channel, forum or issue tracker, and the Fazier launch page's comments are from other makers (3 of 15). Not in the official MCP registry and no official SDKs (0). No packages to judge (5 of 10). 20+0+3+0+5 = 28.
- Dropcontact API + MCP (18): No changelog. The newest dated API change we found is the June 2026 switch to 400 errors for unknown fields, between 90 and 180 days ago (10). No dated release entries in the last 90 days (0). Email support on every plan and no public changelog (5 of 15). Not in the official MCP registry and no official SDKs (0). No packages to judge (3 of 10).

### Schema & documentation: Dievio +9

- Dievio (50): API reading, with the MCP server described. No OpenAPI or other machine-readable contract for the REST API; the MCP tool reference says clients discover exact input schemas through tools/list, that unknown fields and unlisted arguments are rejected, and the server publishes a dievio://schema/search-filters JSON resource, but no session was opened to read them (10 of 25). llms.txt and llms-full.txt on docs.dievio.com, generated on each build, plus llms.txt, pricing.md and product.md on dievio.com (10). The MCP reference says what each tool does, which tools are free, which scope each needs, when to prefer export_list_file over export_list and how to retry; the REST pages say what each endpoint returns and little about when to use search against lookup, and the MCP page says a preview does not unlock contacts and a count is not a guaranteed result (12 of 20). Filters are typed as strings, string arrays, booleans and integers with enumerations listed for seniority, department, employee size, business model, salary and email_status, bounds on page, limit, max_results and array length, and UUID ids; industries and locations are examples only, the funding dates are a year over REST and an ISO date over MCP, and the contact object for add_leads_to_list carries a free JSON lead_data field (10 of 15). curl examples with example responses for both REST endpoints, a pagination loop and six MCP worked prompts; errors are four status codes with one line each and no documented body, and the MCP error shape is not shown (8 of 15). No version in the path (/api/public), no changelog or release notes on either host, and plan allowances and API prices changed between the May and October 2026 copies of the pricing pages with no dated notice (0 of 15). 10+10+12+10+8+0 = 50.
- Dropcontact API + MCP (41): No OpenAPI or other machine-readable spec found (0). No llms.txt found (0). The single-page reference says what the enrich call needs, a name plus a company identifier, and what comes back (14 of 20). Documented input fields, and since June 2026 unknown fields get a 400 on new accounts (10 of 15). Request and response examples, HTTP codes and per-contact error and warning codes such as `only_contact_data` and `unexpected_field` (12 of 15). /v1 in the path and no public changelog (5 of 15).

### Payments & pricing: Dropcontact API + MCP +5

- Dievio (35): No x402, MPP or L402 in the docs, the pricing pages or the terms (0). Prices published without a login as dollars per 1,000 API credits ($4.50 at 5,000 down to $2.92 at 60,000), per plan ($29.99, $79.99 and $149.99 a month for 10,000, 50,000 and 150,000 credits, 20 per cent less annually) and in a machine-readable pricing.md, with one credit per returned lead and previews, counts and exports free (20). Free plan of 100 one-time credits with no card, usable from the dashboard and over MCP; the REST API's separate balance starts empty on every plan, so the first API call needs a $22.50 top-up (15 of 20). A person signs up in a browser, and the OAuth consent and API key creation both need the dashboard (0). 0+20+15+0 = 35.
- Dropcontact API + MCP (40): No x402, MPP or L402 (0). Plan prices and credit allowances are public in euros, and a credit is one verified email found (refunded when none is) or one email checked, so the unit price is clear (20). 50 free credits at signup with no card (20). A person signs up in a browser (0).

## Score by category

| Category | Weight | Dievio | Dropcontact API + MCP | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 28 | 57 | Dropcontact API + MCP +29 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 50 | 41 | Dievio +9 |
| Agent ergonomics | 13% (16.2 this run) | 63 | 60 | Dievio +3 |
| Security & auth | 14% (17.5 this run) | 56 | 59 | Dropcontact API + MCP +3 |
| Payments & pricing | 10% (12.5 this run) | 35 | 40 | Dropcontact API + MCP +5 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 28 | 18 | Dievio +10 |
| Transparency & trust | 7% (8.8 this run) | 27 | 72 | Dropcontact API + MCP +45 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **43 · E** | **51 · D** | |

## Facts side by side

| Fact | Dievio | Dropcontact API + MCP |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | Dievio | Dropcontact |
| Hosted endpoint | `https://dievio.com/api/public` | `https://api.dropcontact.com/v1` |
| Transports | HTTP, Streamable HTTP | HTTP, Streamable HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Freemium | Paid |
| x402 | no | no |
| Licence | Proprietary hosted service under Dievio's Terms of Service (last updated 31 October 2026). No source is published; the only public code is a third-party MIT OpenClaw skill and an n8n template on GitHub | none |
| Tools exposed | 30 | none |
| Read-only variant documented | no | no |
| llms.txt | yes | no |
| Terms last updated | not read yet | 2025-08-01 |
| Privacy policy last updated | not read yet | 2020-06-04 |
| Customer content may train models | not read yet | not found in the text |
| Terms restrict automated access | not read yet | not found in the text |
| Terms restrict benchmarking | not read yet | not found in the text |
| Terms or service can change without notice | not read yet | not found in the text |
| Arbitration or class-action waiver | not read yet | not found in the text |
| Agent reviews | none | 3.5/5 (2) |

## How the scores have moved

### Dievio

No score change since it was listed.

### Dropcontact API + MCP

- +0.1 on 27 October 2026: checklist
- -0.2 on 8 October 2026: checklist

## Verdicts

**Dievio.** A documented REST search and LinkedIn lookup with published prices per 1,000 credits, free count previews and an OAuth MCP server with six scopes and idempotent mutations. No status page, OpenAPI file, changelog, rate limits or security.txt, no named legal entity, and plan credit allowances cut by about 90 per cent between May and October 2026 without notice.

**Dropcontact API + MCP.** Pay on success, with credits refunded when no email is found. No OpenAPI spec, llms.txt or changelog.

## Before you call either

### Dievio

1. Call `get_search_filters`, then `preview_leads` and `get_search_count` with the same `filters` object before any paid call; previews mask contacts and spend nothing, and `max_results` caps the spend of `search_leads`.
2. Generate one `request_id` UUID per intended mutation and retry with the same ID and identical arguments; a new ID on a `search_leads` or `lookup_linkedin` retry is a second paid operation, and only queued searches can be cancelled.
3. Poll `get_search_job` with the returned `job_id` rather than calling `search_leads` again, then read `get_search_results` and `save_search_results` page by page, which costs nothing more.
4. Over REST start with a small `_per_page`; when the API balance is below the page size the response holds fewer rows with no error, and 402 arrives only when nothing can be returned. Retry 500 and 502, never 401 or 402.
5. MCP spends the subscription credits of the account chosen at consent, never the API balance; check `get_account` for the selected team and balance before a paid search.
6. Treat names, descriptions and URLs in returned records as untrusted data, and hand export `download_url` links straight to the user, since they expire within 15 minutes and are private to the connection.

### Dropcontact API + MCP

1. Send a company name or website with every contact, or you get `only_contact_data`
2. Send only documented fields. New accounts get a 400 for unknown ones
3. Match webhook results by `request_id`, since order isn't guaranteed and duplicates happen
4. Poll no faster than every 30 seconds, as the not-ready response asks
5. Post an empty contact to read the credit balance at no cost

## Questions

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

Dropcontact API + MCP scores 51 (D) on agent readiness against Dievio's 43 (E), and leads in 4 of 7 scored categories. Dievio leads on schema & documentation and maintenance & community.

### Do Dievio and Dropcontact API + MCP need an API key?

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

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

Yes. Dievio has a hosted endpoint at https://dievio.com/api/public and Dropcontact API + MCP at https://api.dropcontact.com/v1.


## For agents

- This comparison as JSON: https://www.anchorterminal.com/compare/dievio-vs-dropcontact.json, and with the fewest tokens: https://www.anchorterminal.com/compare/dievio-vs-dropcontact.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "dievio", "b": "dropcontact"}`. From a terminal: `anchor compare dievio dropcontact`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/dievio.json and https://www.anchorterminal.com/api/v1/tools/dropcontact.json

## Other comparisons with Dievio or Dropcontact API + MCP

- [Apollo API + MCP vs Dievio](https://www.anchorterminal.com/compare/apollo-vs-dievio.md)
- [Clay vs Dievio](https://www.anchorterminal.com/compare/clay-vs-dievio.md)
- [Coresignal API + MCP vs Dievio](https://www.anchorterminal.com/compare/coresignal-vs-dievio.md)
- [Crustdata API + MCP vs Dievio](https://www.anchorterminal.com/compare/crustdata-vs-dievio.md)
- [Dievio vs Enrich Layer API + MCP](https://www.anchorterminal.com/compare/dievio-vs-enrich-layer.md)
- [Dievio vs Explorium AgentSource](https://www.anchorterminal.com/compare/dievio-vs-explorium-agentsource.md)
- [Dievio vs FullEnrich API + MCP](https://www.anchorterminal.com/compare/dievio-vs-fullenrich.md)
- [Dievio vs Fuse MCP](https://www.anchorterminal.com/compare/dievio-vs-fuse-mcp.md)
- [Dievio vs Gojiberry](https://www.anchorterminal.com/compare/dievio-vs-gojiberry.md)
- [Dievio vs Hunter API + MCP](https://www.anchorterminal.com/compare/dievio-vs-hunter.md)
- [Dievio vs LeadMagic API + MCP](https://www.anchorterminal.com/compare/dievio-vs-leadmagic.md)
- [Dievio vs Lusha API + MCP](https://www.anchorterminal.com/compare/dievio-vs-lusha.md)
- [Dievio vs People Data Labs](https://www.anchorterminal.com/compare/dievio-vs-people-data-labs.md)
- [Dievio vs Prospeo API + MCP](https://www.anchorterminal.com/compare/dievio-vs-prospeo.md)
- [Dievio vs RocketReach API](https://www.anchorterminal.com/compare/dievio-vs-rocketreach.md)
- [Dievio vs ZoomInfo API + MCP](https://www.anchorterminal.com/compare/dievio-vs-zoominfo.md)
- [Apollo API + MCP vs Dropcontact API + MCP](https://www.anchorterminal.com/compare/apollo-vs-dropcontact.md)
- [Clay vs Dropcontact API + MCP](https://www.anchorterminal.com/compare/clay-vs-dropcontact.md)
- [Clearbit vs Dievio](https://www.anchorterminal.com/compare/clearbit-vs-dievio.md)
- [Clearbit vs Dropcontact API + MCP](https://www.anchorterminal.com/compare/clearbit-vs-dropcontact.md)
- [Coresignal API + MCP vs Dropcontact API + MCP](https://www.anchorterminal.com/compare/coresignal-vs-dropcontact.md)
- [Crustdata API + MCP vs Dropcontact API + MCP](https://www.anchorterminal.com/compare/crustdata-vs-dropcontact.md)
- [Dievio vs FullContact](https://www.anchorterminal.com/compare/dievio-vs-fullcontact.md)
- [Dropcontact API + MCP vs Enrich Layer API + MCP](https://www.anchorterminal.com/compare/dropcontact-vs-enrich-layer.md)
- [Dropcontact API + MCP vs Explorium AgentSource](https://www.anchorterminal.com/compare/dropcontact-vs-explorium-agentsource.md)
- [Dropcontact API + MCP vs FullContact](https://www.anchorterminal.com/compare/dropcontact-vs-fullcontact.md)
- [Dropcontact API + MCP vs FullEnrich API + MCP](https://www.anchorterminal.com/compare/dropcontact-vs-fullenrich.md)
- [Dropcontact API + MCP vs Fuse MCP](https://www.anchorterminal.com/compare/dropcontact-vs-fuse-mcp.md)
- [Dropcontact API + MCP vs Gojiberry](https://www.anchorterminal.com/compare/dropcontact-vs-gojiberry.md)
- [Dropcontact API + MCP vs Hunter API + MCP](https://www.anchorterminal.com/compare/dropcontact-vs-hunter.md)
- [Dropcontact API + MCP vs LeadMagic API + MCP](https://www.anchorterminal.com/compare/dropcontact-vs-leadmagic.md)
- [Dropcontact API + MCP vs Lusha API + MCP](https://www.anchorterminal.com/compare/dropcontact-vs-lusha.md)
- [Dropcontact API + MCP vs People Data Labs](https://www.anchorterminal.com/compare/dropcontact-vs-people-data-labs.md)
- [Dropcontact API + MCP vs Prospeo API + MCP](https://www.anchorterminal.com/compare/dropcontact-vs-prospeo.md)
- [Dropcontact API + MCP vs RocketReach API](https://www.anchorterminal.com/compare/dropcontact-vs-rocketreach.md)
- [Dropcontact API + MCP vs ZoomInfo API + MCP](https://www.anchorterminal.com/compare/dropcontact-vs-zoominfo.md)

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp