Dievio vs People Data Labs

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.

People Data Labs 79

The latest release notes are dated 15 September 2026 and the JavaScript SDK 14.6.0 followed on 16 September (30). Release notes on 21 July, 18 August and 15 September, plus three JavaScript SDK releases in the same 90 days (20). Public release notes, a Canny board for bugs and feature requests and a support address. We did not test support (11 of 15). Five official SDKs. JavaScript is current, while the Python package on PyPI is 6.4.13 from 12 January 2026 and the repository's April job posting commit is not published (11 of 15). Both SDK repositories have test and publish workflows and dependency updates (7 of 10).

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.

People Data Labs 78

Statuspage at status.peopledatalabs.com with a component for each API and the sandbox, and history back to 2021 (20). Two incidents in the 90 days to 8 October 2026, both minor. Requests carrying a location failed for about 10 minutes during the 15 September release, and IP enrichment was slow or timing out on 9 August, duration not given (25 of 30). Rate limits are published with numbers, 100 a minute free and 1,000 paid on person enrichment, 10 a minute on person search, five on the sandbox (15). A 429 body and the x-ratelimit-reset header are documented with a fixed-window explanation, and no back-off or retry guidance was found (8 of 15). No SLA was found in the agreement or on the pricing page (0). The v5 endpoints are generally available (10).

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.

People Data Labs 68

Closed service under a published Services Subscription Agreement and Acceptable Data Use Policy that name People Data Labs, Inc. (15 of 30). The privacy policy, a GDPR Article 14 notice and a DPA are published. The DPA commits to deleting customer personal data within 90 days of termination and to breach notice within 72 hours, and describes blind logging of API inputs. Retention in the privacy policy is described by criteria with no periods, and the text we read carried no effective date (20 of 30). The agreement says data and services may be modified without prior notice. Release notes flag parameters that will lose support, such as from on search, with no dates or policy (6 of 20). The DPA names Amazon Web Services and points to the trust centre for other sub-processors, which our reader could not load. The security page places hosting in Oregon and Northern California (12 of 20).

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.

People Data Labs 70

No OpenAPI file was found at the docs root or in the docs index. A public Postman collection and Elasticsearch mappings for each dataset stand in (8 of 25). llms.txt on the docs site and a Markdown twin of every page (10). Each API has overview, reference, input, output, examples and FAQ pages that state purpose and billing (15 of 20). Enrichment inputs are typed with canonical value lists, while search takes an Elasticsearch 7.7 query or an SQL string, both free-form (9 of 15). Examples in five languages and a six-row error table with sample bodies (13 of 15). A v5 path, numbered dataset versions and monthly release notes back to 2019 (15).

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.

People Data Labs 77

data_include selects or excludes fields, size caps records at 1 to 100, gzip is supported and a 1 MB response limit is documented (20 of 25). Search pages with scroll_token and filters on any mapped field, with dataset to narrow the source (18 of 20). Errors carry a status, a type and a short message across six documented codes, with 404 meaning no match (13 of 20). The API is read-only and charges only on a 200, so a repeat is safe, though no retry guidance or idempotency key was found (12 of 20). Enrichment needs one identifier, defaults are sensible, and SDKs exist for Python, JavaScript, Ruby, Go and Rust (14 of 15).

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.

People Data Labs 43

One revocable API key type with no scopes, with 1, 3 or 5 active keys by plan (20), less 10 because the docs show the key as api_key in the URL query string (10 of 30). The data endpoints only read, and there is no restricted or per-endpoint key (12 of 20). Records come from public and third-party sources and include free-text fields, and no prompt-injection guidance was found (2 of 15). The dashboard Usage tab and per-call credit headers give the operator visibility, with no audit log found (7 of 15). The security page states SOC 2 Type 2 and ISO 27001 compliance and quarterly external penetration tests. No security.txt, bug bounty or disclosure policy was found (12 of 20).