# Clay vs Dievio (slim)

> Clay scores 57.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/clay-vs-dievio.md (~5,550 tokens) · this version ~3,480 tokens · JSON https://www.anchorterminal.com/compare/clay-vs-dievio.json · canonical https://www.anchorterminal.com/compare/clay-vs-dievio
- 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)

Clay scores 57.7 (C) on agent readiness against Dievio's 43 (E), and leads in 5 of 7 scored categories. Dievio leads on security & auth and payments & pricing. Both do lead search.

- Clay: C 57.7, rank #709 of 1245 · https://www.anchorterminal.com/tools/clay.min.md
- Dievio: E 43, rank #1090 of 1245 · https://www.anchorterminal.com/tools/dievio.min.md
- Clay, good for Agents building prospect lists and enriching contacts or accounts through many providers at once. Ahead on Reliability, 45 against 28; Schema & documentation, 84 against 50; Maintenance & community, 75 against 28; Transparency & trust, 64 against 27.
- 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 48; Payments & pricing, 35 against 30. Also Free to start without a card.

| Category | Clay | Dievio |
| --- | --- | --- |
| Reliability (16%) | 45 | 28 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 84 | 50 |
| Agent ergonomics (13%) | 66 | 63 |
| Security & auth (14%) | 48 | 56 |
| Payments & pricing (10%) | 30 | 35 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 75 | 28 |
| Transparency & trust (7%) | 64 | 27 |

| Fact (where they differ) | Clay | Dievio |
| --- | --- | --- |
| Vendor | Clay Labs Inc. | Dievio |
| Hosted endpoint | `https://api.clay.com/public/v0` | `https://dievio.com/api/public` |
| Transports | HTTP | HTTP, Streamable HTTP |
| Licence | Proprietary service under the Clay Terms of Service. The agent plugin repository carries no licence file | 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 |
| Tools exposed | none | 30 |
| Last release | 2026-10-06 | none |
| Terms last updated | 2024-05-23 | not read yet |
| Privacy policy last updated | 2020-09-11 | not read yet |
| Customer content may train models | not found in the text | not read yet |
| Terms restrict automated access | not found in the text | not read yet |
| Terms restrict benchmarking | not found in the text | not read yet |
| Terms or service can change without notice | not found in the text | not read yet |
| Arbitration or class-action waiver | yes | not read yet |

Why the edge:
- Maintenance & community, Clay +47: Clay 75 (clay plugin 2.32.0 with CLI 1.9.0 on 6 October 2026 (30). Plugin releases on 25 September, 1, 2 (two) and 6 October (20). Weekly dated product roundups and a support address, with the plugin's issue handling not visible (12 of 15). No official SDKs, the CLI is current (8 of 15). CLI binaries ship from GitHub releases, and the repository has no licence file (5 of 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.)
- Transparency & trust, Clay +37: Clay 64 (Closed service under terms dated 23 May 2024, and a plugin repository with no licence (12 of 30). The privacy policy dates from 11 September 2020, gives no retention periods and says nothing on AI training, and doesn't describe an opt-out for people whose data comes from Clay's providers (8 of 30). Deprecated endpoints are marked in the spec without removal dates (8 of 20). No sub-processor list found (0).); 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.)
- Schema & documentation, Clay +34: Clay 84 (A public OpenAPI 3 spec with 16 operations (25). llms.txt and Markdown copies of every page (10). Pages say when to use each primitive, and deprecated filters-mode endpoints name their replacement (16 of 20). Typed request bodies, with a query grammar fetched from a reference endpoint rather than enums (12 of 15). curl examples on every guide, but error bodies carry only a message with no stable codes (9 of 15). v0 in the path and a weekly product changelog that names CLI and MCP changes, without an API-specific log (12 of 15).); 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.)
- Reliability, Clay +17: Clay 45 (Graded with the hosted lines on the Public API. status.clay.com exists but answered with a bot check, so we couldn't confirm components (10 of 20). No readable history (5). A per-workspace request limit with no number, and published search-result caps per plan (8 of 15). 429 with Retry-After and X-RateLimit headers, backoff with jitter, and retry guidance only when a request is safe to retry. No idempotency keys (12 of 15). The terms set a 99.0 per cent monthly uptime target with credits for six-hour outages, a target rather than a guarantee (5 of 10). The API is v0, and Workflows and run search are labelled alpha or beta (5 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.)
- Security & auth, Dievio +8: Clay 48 (A personal API key tied to the user's workspace access, with no scopes documented. The CLI uses OAuth per workspace (15 of 30). Functions need API or MCP access switched on one by one and workspace roles apply, but the Claude Code plugin's hook auto-approves most clay CLI commands, including ones that spend credits (8 of 20). Claygent web research returns untrusted text, and no injection guidance was found (3 of 15). Credit balances and a workflow-run query, with no per-call audit log found (6 of 15). Valid security.txt to July 2027, a trust centre, and SOC 2 Type II, ISO 27001 and ISO 42001 listed. No bug bounty found (16 of 20).); 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.)
- Payments & pricing, Dievio +5: Clay 30 (No x402, MPP or L402 (0). Data credits from $0.05 and plan prices public, though the plan cards and the FAQ disagree on the Launch and Growth prices (15 of 20). A free plan described as "no strings attached", with a card requirement not stated on the page (15 of 20). A person signs up in a browser, and CLI sign-in opens a browser or a device code (0).); 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.)