# Dievio vs Leadsets (slim)

> Leadsets scores 62.9 (B) to Dievio's 28.5 (F) for lead search. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/dievio-vs-leadsets.md (~6,550 tokens) · this version ~1,130 tokens · JSON https://www.anchorterminal.com/compare/dievio-vs-leadsets.json · canonical https://www.anchorterminal.com/compare/dievio-vs-leadsets
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-22
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Leadsets scores 62.9 (B) on agent readiness against Dievio's 28.5 (F), and leads in 6 of 7 scored categories. Both do lead search.

- Dievio: F 28.5, rank #1479 of 1571 · https://www.anchorterminal.com/tools/dievio.min.md
- Leadsets: B 62.9, rank #661 of 1571 · https://www.anchorterminal.com/tools/leadsets.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.
- Leadsets, good for Prospect search, contact enrichment with verified work emails and company-site scraping for an agent on a flat monthly plan rather than credits. Ahead on Reliability, 40 against 28; Schema & documentation, 58 against 50; Agent ergonomics, 90 against 63; Security & auth, 67 against 56; Maintenance & community, 80 against 8; Transparency & trust, 67 against 27. Also No incidents deducted, where Dievio loses 15 points for them.

| Category | Dievio | Leadsets |
| --- | --- | --- |
| Reliability (16%) | 28 | 40 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 50 | 58 |
| Agent ergonomics (13%) | 63 | 90 |
| Security & auth (14%) | 56 | 67 |
| Payments & pricing (10%) | 53 | 50 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 8 | 80 |
| Transparency & trust (7%) | 27 | 67 |

| Fact (where they differ) | Dievio | Leadsets |
| --- | --- | --- |
| Vendor | Dievio | Leadsets |
| Hosted endpoint | `https://dievio.com/api/public` | `https://mcp.leadsets.ai` |
| Transports | HTTP, Streamable HTTP | Streamable HTTP |
| 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 | 8 |
| MCP registry | not listed | `io.github.leadsets/leadsets` |
| Last release | none | 2026-11-22 |
| Terms last updated | not read yet | 2026-11-15 |
| Privacy policy last updated | not read yet | 2026-11-19 |
| 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 |

Why the edge:
- Maintenance & community, Leadsets +72: Dievio 8 (Closed service with no changelog, release notes or version numbers.); Leadsets 80 (The product is about two weeks old.)
- Transparency & trust, Leadsets +40: Dievio 27 (Closed service.); Leadsets 67 (Closed service with terms naming Mobylogix LLC under Texas law.)
- Agent ergonomics, Leadsets +27: Dievio 63 (API reading.); Leadsets 90 (Eight MCP tools per the docs, with sizes unread, and REST responses sized by `limit` and a `count_only` mode that returns only a count, but no field selection f…)
- Reliability, Leadsets +12: Dievio 28 (Hosted reading, for the REST API with the MCP server it shares a database with.); Leadsets 40 (No status page found, and the support page answers "Where can I check if Leadsets is down?" by pointing to the 503 error and support email (0).)
- Security & auth, Leadsets +11: Dievio 56 (MCP uses OAuth with the authorisation code flow, PKCE S256, dynamic registration of public clients, refresh tokens of 30 days, a revocation endpoint and six sco…); Leadsets 67 (Bearer keys with a full, data or read access level, an expiry of never, 30, 90 or 365 days, hashed storage, revocation within a minute and a documented rotation…)
- Schema & documentation, Leadsets +8: Dievio 50 (API reading, with the MCP server described.); Leadsets 58 (No OpenAPI file or other machine-readable contract found in the docs or llms.txt, and the MCP server answers `initialize` with 401 without a key, so its tool sc…)
