Head to head · Lead search · October 2026 research run

Dievio vs Leadsets

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.

Best lead, contact and company data APIs for AI agents · All 276 leads comparisons

Which one, for what

Dievio F

Best 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.

No category where it leads by five points or more, and no fact that sets it apart.

Watch for

No status page, incident history or SLA; the terms say uptime is not guaranteed and the service may change at any time

Leadsets B

Best 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 in its favour

  • No incidents deducted, where Dievio loses 15 points for them

Watch for

No status page, SLA or incident history found, and the terms promise no uninterrupted service unless agreed in writing

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Maintenance & community Leadsets +72

Dievio 8

Closed service with no changelog, release notes or version numbers. No dated API change was found on 5 November 2026. The terms and privacy policy last updated 31 October 2026 are document dates, which this run doesn't take as a recency source; the blog posts of 21 and 30 October 2026 on API billing are guides that describe the existing credit rules and record no change; the MCP server carries no date; and the API landing pages say content reviewed May 2026 (0 of 30). No release record, so no three dated entries in 90 days; the blog's dated posts, the newest of 4 November 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). No official SDKs; registry presence was not read (0). No packages to judge (5 of 10). 0+0+3+0+5 = 8.

Leadsets 80

The product is about two weeks old. The TypeScript SDK 0.2.1 was tagged on 22 November 2026, the day of this check (30). Four SDK tags (0.1.0 and 0.1.1 on 11 November, 0.2.0 on 19 November, 0.2.1 on 22 November) and four PyPI releases from 11 to 19 November, all within 90 days (20). A support email with response times by plan and an API changelog with no entries yet. GitHub issues weren't read (7 of 25). In the official MCP registry as io.github.leadsets/leadsets since 14 November 2026, under a namespace proved through GitHub, and current official SDKs in two languages (15). The SDK has no runtime dependencies, CI on Node 20, 22 and 24, and npm trusted publishing with provenance, and the CI run results weren't read (8 of 10). 30 + 20 + 7 + 15 + 8 = 80.

Transparency & trust Leadsets +40

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 (authorisation 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.

Leadsets 67

Closed service with terms naming Mobylogix LLC under Texas law. The SDK is MIT (15). The privacy policy, terms, DPA and compliance page say where dataset records come from (licensed suppliers and permitted public sources such as company websites), what is held, that uploaded files are deleted 30 days after a job, and how to opt out. The suppliers aren't named, and the privacy policy says analytics run only on the public website while the compliance page lists PostHog and Google Analytics as "Product analytics (customers only)" (20 of 30). Breaking changes get 90 days' notice by email and material changes to plans or terms 30 days, with no dated notices yet (15 of 20). Subprocessors named (Vercel, Supabase, Stripe, Resend, PostHog, Google Analytics), all in the US, with 30 days' notice before adding one (18 of 20). 15 + 20 + 15 + 18 = 68.

Agent ergonomics Leadsets +27

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.

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 found (20 of 25). Cursor pagination, typed filters, max_age_days, exclude_stale and has_verified_email (20). Every error has a status, a type, a request_id, the meter and charged, and the docs say whether to retry each one (20). Idempotency-Key on every paid call for 24 hours, with 409 idempotency_conflict for a reused key with a new body. MCP tool annotations couldn't be read (15 of 20). One required header and defaults such as limit 25, and official TypeScript and Python SDKs that retry 429 and 5xx (15). 20 + 20 + 20 + 15 + 15 = 90.

Reliability Leadsets +12

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.

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). No incident history to read (5). Limits published with numbers per plan, per rolling five hours and per week, for records, requests and concurrent searches (15). Three 429 types with Retry-After, backoff advice for 500 and 503, and an Idempotency-Key on paid calls that makes retries safe for 24 hours (15). The terms say "We aim for high availability but don't guarantee uninterrupted service unless agreed in writing", and no SLA is published (0). No page calls the service beta or preview, but the changelog says "No releases yet. Release notes start at launch.", so half credit as a judgement call (5). 0 + 5 + 15 + 15 + 0 + 5 = 40.

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 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.

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 procedure. MCP clients can use OAuth with PKCE S256 and dynamic client registration, with no scopes in the server metadata. No query-string key documented (30). A read-level key can call only the usage endpoints, and every data tool reads rather than writes, so there is nothing destructive to confirm. Members see and revoke only their own keys (16 of 20). scrape_company and scrape_jobs return text from company websites, and no prompt-injection guidance was found (3 of 15). A request log in the dashboard, an optional X-Leadsets-Client label, rate-limit headers and request_id on every response (12 of 15). /.well-known/security.txt answered 404. The SDK repository's SECURITY.md names security@leadsets.ai with acknowledgement within 3 business days. No bug bounty, and SOC 2 Type I readiness has a target of Q3 2027 (6 of 20). 30 + 16 + 3 + 12 + 6 = 67.

Schema & documentation Leadsets +8

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.

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 schemas couldn't be read (0). llms.txt, llms-full.txt and a Markdown twin of every page (10). The REST reference says what each route does, what it costs and what it returns, with little on when not to use it, and the MCP definitions are unread (12 of 20). People search inputs are typed with enums for seniority and function, ranges for limit (1 to 100) and max_age_days, ISO country codes and booleans, with one nested priorities object (13 of 15). cURL, TypeScript and Python examples and a documented response, plus an errors page that lists 11 types with what to do (15). /v1 in the path and a dated, semver CHANGELOG.md for the TypeScript SDK, but the API changelog had no entries on 22 November 2026 (8 of 15). 0 + 10 + 12 + 13 + 15 + 8 = 58.

Score by category

CategoryWeightDievioLeadsetsEdge
Reliability16%2840Leadsets +12
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%5058Leadsets +8
Agent ergonomics13%6390Leadsets +27
Security & auth14%5667Leadsets +11
Payments & pricing10%5350Dievio +3
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%880Leadsets +72
Transparency & trust7%2767Leadsets +40
Negative events≤15-150
TotalF 28.5/100B 62.9/100

Facts side by side

FactDievioLeadsets
KindHTTP APIHTTP API
VendorDievioLeadsets
Hosted endpointhttps://dievio.com/api/publichttps://mcp.leadsets.ai
TransportsHTTP, Streamable HTTPStreamable HTTP
AuthOAuth or keyOAuth or key
PricingFreemiumFreemium
x402nono
LicenceProprietary 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 GitHubnone
Tools exposed308
Read-only variant documentednono
llms.txtyesyes
MCP registrynot listedio.github.leadsets/leadsets
Last releasenone2026-11-22
Terms last updatednot read yet2026-11-15
Privacy policy last updatednot read yet2026-11-19
Customer content may train modelsnot read yetnot found in the text
Terms restrict automated accessnot read yetnot found in the text
Terms restrict benchmarkingnot read yetnot found in the text
Terms or service can change without noticenot read yetnot found in the text
Arbitration or class-action waivernot read yetnot found in the text

How the scores have moved

Verdicts

Dievio

A documented REST search and LinkedIn lookup with published prices per 1,000 credits, free count previews and an OAuth MCP server with six scopes and idempotent mutations. No status page, OpenAPI file, changelog, rate limits or security.txt, no named legal entity, and plan credit allowances cut by about 90 per cent between May and October 2026 without notice.

Leadsets

Agents get eight MCP tools or REST routes with typed errors that say whether to retry, idempotency keys on paid calls, read-only keys and a free tier with no card. The product is about two weeks old, with no status page, no OpenAPI file, an empty API changelog and no named data suppliers.

Before you call either

Dievio

  1. Call get_search_filters, then preview_leads and get_search_count with the same filters object before any paid call; previews mask contacts and spend nothing, and max_results caps the spend of search_leads.
  2. Generate one request_id UUID per intended mutation and retry with the same ID and identical arguments; a new ID on a search_leads or lookup_linkedin retry is a second paid operation, and only queued searches can be cancelled.
  3. Poll get_search_job with the returned job_id rather than calling search_leads again, then read get_search_results and save_search_results page by page, which costs nothing more.
  4. Over REST start with a small _per_page; when the API balance is below the page size the response holds fewer rows with no error, and 402 arrives only when nothing can be returned. Retry 500 and 502, never 401 or 402.
  5. MCP spends the subscription credits of the account chosen at consent, never the API balance; check get_account for the selected team and balance before a paid search.
  6. Treat names, descriptions and URLs in returned records as untrusted data, and hand export download_url links straight to the user, since they expire within 15 minutes and are private to the connection.

Leadsets

  1. Call get_usage before a large run. It costs nothing and returns every meter with its reset time
  2. Send an Idempotency-Key on every paid call, and reuse it on a retry so records are counted once
  3. If a 429 has type weekly_limit, stop until resets_at. For window_full and too_many_concurrent, wait for Retry-After
  4. Use a read-level key for monitoring only. Data tools answer 403 forbidden to it
  5. Treat text from scrape_company and scrape_jobs as untrusted website content, since no injection guidance was found

Questions

Which is better for AI agents, Dievio or Leadsets?

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

Do Dievio and Leadsets need an API key?

Both take an API key or an OAuth sign-in.

Can an agent call Dievio and Leadsets without installing anything?

Yes. Dievio has a hosted endpoint at https://dievio.com/api/public and Leadsets at https://mcp.leadsets.ai.

Other comparisons with Dievio or Leadsets

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.