# Dievio vs Enrich Layer API + MCP (slim)

> Enrich Layer scores 55.8 (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-enrich-layer.md (~6,000 tokens) · this version ~3,730 tokens · JSON https://www.anchorterminal.com/compare/dievio-vs-enrich-layer.json · canonical https://www.anchorterminal.com/compare/dievio-vs-enrich-layer
- 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)

Enrich Layer API + MCP scores 55.8 (C) on agent readiness against Dievio's 43 (E), and leads in 5 of 7 scored categories. Dievio leads on security & auth. Both do lead search.

- Dievio: E 43, rank #1090 of 1245 · https://www.anchorterminal.com/tools/dievio.min.md
- Enrich Layer API + MCP: C 55.8, rank #775 of 1245 · https://www.anchorterminal.com/tools/enrich-layer.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. Ahead on Security & auth, 56 against 40.
- Enrich Layer API + MCP, good for Teams migrating Proxycurl code or doing per-profile lookups at low unit cost without a subscription. Ahead on Reliability, 65 against 28; Schema & documentation, 76 against 50; Agent ergonomics, 68 against 63; Payments & pricing, 40 against 35; Transparency & trust, 59 against 27. Also Runs on your own machine.

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

| Fact (where they differ) | Dievio | Enrich Layer API + MCP |
| --- | --- | --- |
| Vendor | Dievio | Enrich Layer |
| Hosted endpoint | `https://dievio.com/api/public` | `https://enrichlayer.com/api/v2` |
| Transports | HTTP, Streamable HTTP | HTTP, stdio |
| Auth | OAuth or key | API key |
| Pricing | Freemium | Pay per use |
| 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 | MIT |
| Tools exposed | 30 | 25 |
| Last release | none | 2026-06-19 |
| Terms last updated | not read yet | 2025-06-09 |
| Privacy policy last updated | not read yet | 2025-06-09 |
| 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 | yes |
| Arbitration or class-action waiver | not read yet | not found in the text |
| Popularity | none | 0 stars, 26 npm/wk |
| Agent reviews | none | 3/5 (2) |

Why the edge:
- Reliability, Enrich Layer API + MCP +37: 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.); Enrich Layer API + MCP 65 (Cachet status page at status.enrichlayer.com with a component per API group (School, Company, People, Contact, Jobs, Search, Meta) (20). The only incident shown is a stickied notice from 24 November 2025 that the Person Profile endpoint answers in 30 to 100 seconds, and that component still showed 'Performance Issues' on 1 October 2026. No other history is readable (10). 300 requests a minute with bursts to 1,500 over 5 minutes, 2 a minute on trial accounts until the first top-up (15). 429 documented with advice to back off exponentially, no Retry-After (10 of 15). No SLA found (0). Generally available (10).)
- Transparency & trust, Enrich Layer API + MCP +32: 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.); Enrich Layer API + MCP 59 (The MCP server is MIT, the API is closed with terms naming Vertical Int, Inc. (Wyoming) (18 of 30). The privacy policy (updated 9 June 2025) covers people in its databases, relies on legitimate interests, names sources including professional networking platforms and data brokers, and takes deletion requests by email. Retention has no periods and no DPA is mentioned (15 of 30). A Proxycurl transition guide maps old paths to new, and no deprecation policy found (5 of 20). Subprocessors listed (Google, PostHog, Intercom, all US). The MCP's Sentry error reporting is off unless `SENTRY_DSN` is set and the README says so (15 of 20).)
- Schema & documentation, Enrich Layer API + MCP +26: 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.); Enrich Layer API + MCP 76 (OpenAPI 3.0 file at enrichlayer.com/docs/api/v2/openapi.yaml. The MCP repo vendors a 408 kB copy and its CI fails any tool that drifts from it (25). llms.txt per the 30 September check (10). MCP tool descriptions state what each returns, which identifier to pass and the credit cost, but not when to pick one tool over another (14 of 20). Zod schemas with enums for include and exclude flags and cache modes (13 of 15). Examples in the spec. Errors come back as status and message, and we found no error catalogue (9 of 15). /api/v2 paths, no public changelog, MCP versions 0.2.0 and 0.3.0 tagged (5 of 15).)
- Security & auth, Dievio +16: Dievio 56 (MCP uses OAuth with the authorization code flow, PKCE S256, dynamic registration of public clients, refresh tokens of 30 days, a revocation endpoint and six scopes, revoked per connection on the dashboard; REST uses a plain API key from the dashboard as a bearer or X-API-Key header, with no documented scopes, rotation, expiry or revocation, and nothing documents a secret in a query string (25 of 30). mcp:read is the required baseline and cannot spend credits, leads:search, lists:write, leads:export and team:manage are separate consents, team:manage works for the owner only, the permissions page asks agents to confirm before deleting saved data and to invite or remove people only when asked, and the terms ask users to review filters and the maximum result count before authorising a paid operation; nothing asks for confirmation inside the server and REST keys have no least-privilege mode (16 of 20). Returned records are third-party contact data, and the permissions page says to treat names, descriptions, URLs and other field values as data rather than instructions, with no further mitigation (8 of 15). get_account reports the selected account, permissions and balances, list_search_jobs lists recent jobs, the dashboard lists and revokes each connection, and the privacy policy says operation results are kept to prevent duplicate actions; no audit log or per-call record is exposed to the operator (7 of 15). No security.txt on either host (404), no disclosure policy, bug bounty, SOC 2 or ISO 27001 (0 of 20). 25+16+8+7+0 = 56.); Enrich Layer API + MCP 40 (One secret key per user, sent as a bearer token. We found no scopes or key rotation docs (15 of 30). The API only reads, and the MCP marks all 25 tools read-only (18 of 20). Profiles carry free text written by the people they describe, and we found no prompt-injection guidance (2 of 15). A free credit-balance endpoint and nothing more for per-call visibility (5 of 15). No security.txt, disclosure policy, bug bounty or certification. The privacy policy says SOC 2 is under consideration (0 of 20).)
- Agent ergonomics, Enrich Layer API + MCP +5: Dievio 63 (API reading. REST responses are sized with _per_page (default 25), max_results, include_emails, include_phones, _include_raw to drop the raw object and email_status; the MCP server lists 30 tools with no toolsets or read-only subset, previews mask contact fields and limit runs 1 to 500 (18 of 25). Page-based pagination with has_more and next_page over REST, offset and limit with next_offset over MCP, 20 filters, max_results caps and column selection on exports (20). Errors are 401, 402, 500 and 502 as status codes with one-line meanings and no error body, and a balance below the page size returns fewer rows with success true, which an agent must detect from count; MCP job errors are read from get_search_job (8 of 20). request_id on every MCP mutation with replay semantics, asynchronous searches polled by job id, save_search_results deduplicated by list, job and position, and only queued jobs cancellable; the REST search has no idempotency key and a repeat is charged, and readOnlyHint and destructiveHint are not documented (10 of 20). Every filter is optional with defaults for page size and max_results, and the MCP tools need only filters and a request_id; no official SDK or CLI, only a third-party MIT OpenClaw skill and an n8n template on GitHub (7 of 15). 18+20+8+10+7 = 63.); Enrich Layer API + MCP 68 (25 MCP tools, all compact, no toolsets. On the API, include and exclude flags on extra fields, contact data and skills let a caller size a profile response (17 of 25). `next_token` pagination on person and company search and filters (17 of 20). Errors are passed through as status plus message, with a 30-second timeout message from the MCP (10 of 20). Every endpoint is a read, and every MCP tool carries readOnlyHint and openWorldHint (16 of 20). Few required parameters, and the only official client we found is the MCP package (8 of 15).)
- Payments & pricing, Enrich Layer 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.); Enrich Layer API + MCP 40 (No x402, MPP or L402 (0). Pack prices ($10 for 100 credits to $1,000 for 46,297), annual plans and per-endpoint credit costs are public (20). 500 free credits at signup with no card, per the 30 September check (20). A person signs up in a browser (0).)