# Dievio vs FullEnrich API + MCP (slim)

> FullEnrich scores 59.7 (C) to Dievio's 43 (E) for lead search. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/dievio-vs-fullenrich.md (~5,300 tokens) · this version ~3,080 tokens · JSON https://www.anchorterminal.com/compare/dievio-vs-fullenrich.json · canonical https://www.anchorterminal.com/compare/dievio-vs-fullenrich
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-10-31
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

FullEnrich API + MCP scores 59.7 (C) on agent readiness against Dievio's 43 (E), and leads in 5 of 7 scored categories. Both do lead search.

- Dievio: E 43, rank #1090 of 1245 · https://www.anchorterminal.com/tools/dievio.min.md
- FullEnrich API + MCP: C 59.7, rank #633 of 1245 · https://www.anchorterminal.com/tools/fullenrich.min.md
- Dievio, 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.
- FullEnrich API + MCP, good for Maximising find rate on known contacts, especially mobiles, without a long-term contract. Ahead on Reliability, 60 against 28; Schema & documentation, 72 against 50; Payments & pricing, 40 against 35; Maintenance & community, 68 against 28; Transparency & trust, 65 against 27.

| Category | Dievio | FullEnrich API + MCP |
| --- | --- | --- |
| Reliability (16%) | 28 | 60 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 50 | 72 |
| Agent ergonomics (13%) | 63 | 60 |
| Security & auth (14%) | 56 | 55 |
| Payments & pricing (10%) | 35 | 40 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 28 | 68 |
| Transparency & trust (7%) | 27 | 65 |

| Fact (where they differ) | Dievio | FullEnrich API + MCP |
| --- | --- | --- |
| Vendor | Dievio | FullEnrich |
| Hosted endpoint | `https://dievio.com/api/public` | `https://app.fullenrich.com/api/v2` |
| 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 | 13 |
| MCP registry | not listed | `io.github.FullEnrich/fullenrich` |
| Last release | none | 2026-08-27 |
| Terms last updated | not read yet | 2026-08-20 |
| Privacy policy last updated | not read yet | 2026-08-20 |
| 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 | yes |
| Terms or service can change without notice | not read yet | not found in the text |
| Arbitration or class-action waiver | not read yet | yes |
| Agent reviews | none | 3.5/5 (2) |

Why the edge:
- Maintenance & community, FullEnrich API + MCP +40: 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.); FullEnrich API + MCP 68 (The MCP registry package 1.0.4 shipped on 2026-08-27, 35 days ago (20). Three dated releases in the last 90 days, 1.0.2 on 10 August, 1.0.3 on 11 August and 1.0.4 on 27 August, all packaging and registry changes (20). The public product changelog hasn't moved since November 2024. 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).)
- Transparency & trust, FullEnrich API + MCP +38: 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.); FullEnrich API + MCP 65 (Closed service with terms naming FullEnrich Corp. The skills and registry repo is MIT (15). The privacy policy (updated 20 August 2026) gives retention periods (3 years from last contact for prospects, 25 months for service improvement), legal bases and SCC or DPF transfers, and points rights requests to support@fullenrich.com. It doesn't say whether people returned by enrichment are covered, and the trust page says enrichment uses third-party providers it doesn't name. An opt-out page exists at fullenrich.com/optout (18 of 30). v1 and v2 APIs run side by side with no dated deprecation found (3 of 20). A sub-processor list is published. Hosting locations aren't stated on the trust page (14 of 20).)
- Reliability, FullEnrich API + MCP +32: 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.); FullEnrich API + MCP 60 (Better Stack status page, but with one component (app.fullenrich.com/app) and none for the API or MCP (15 of 20). The front page showed no incidents and 99.976 per cent uptime over 30 days. The history page refused us three times because of our own fetch limit, so July and August are unchecked (15 of 30). 60 calls a minute on every endpoint, 100 contacts a bulk and 100 concurrent enrichments per workspace (15). No 429 format, Retry-After or back-off guidance found. Identical re-submissions within 3 months aren't charged again, which makes retries cheap (5 of 15). No SLA found (0). Generally available, no beta label on the API or MCP (10).)
- Schema & documentation, FullEnrich API + MCP +22: 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.); FullEnrich API + MCP 72 (OpenAPI file for v2 at docs.fullenrich.com/api/v2/reference/openapi.yaml, with a v1 file alongside (25). llms.txt with 35 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. We found no error reference in the docs index (8 of 15). v1 and v2 paths. The public product changelog stops at 30 November 2024, and only the MCP package has a current CHANGELOG (5 of 15).)
- Payments & pricing, FullEnrich 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.); FullEnrich API + MCP 40 (No x402, MPP or L402 (0). Per-unit credit costs and plan prices are public, 1 credit a work email, 3 a personal email, 10 a mobile, 0.25 a search result, from $55 for 1,000 credits (20). 50 trial credits with no card, API and MCP included (20). A person signs up in a browser (0).)