Dievio Lead Search API
ReviewAudited by ClawScan on May 10, 2026.
Overview
This is a transparent Dievio API wrapper, but it needs your Dievio key and can spend credits while retrieving or outputting contact information.
This skill appears coherent and purpose-aligned. Before installing or using it, make sure you are comfortable giving it a Dievio API key, sending search filters or LinkedIn URLs to Dievio, and potentially retrieving contact data. Use explicit result/page limits for larger pulls and avoid raw output unless you need full lead records.
Findings (3)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
Anyone using the skill with your API key can make Dievio API requests against your account and may consume credits.
The skill requires a Dievio API key to authenticate requests. This is expected for the integration and the artifacts warn not to print secrets, but the key enables account activity and credit usage.
Require `DIEVIO_API_KEY` for API-key flows. - Never print raw secrets.
Use a dedicated or rotatable Dievio key if available, keep it in the environment rather than pasting it into chats or logs, and monitor API credit usage.
A broad query or high result limit could retrieve many lead records and spend more Dievio credits than expected.
The CLI can automatically follow pagination and has no page cap by default when auto-pagination is enabled. This is disclosed and purpose-aligned, but large pulls can increase API calls, retrieved data volume, and credit consumption.
search.add_argument("--auto-paginate", action="store_true", help="Follow has_more across pages.") ... search.add_argument("--max-pages", type=int, default=0, help="Cap pages when auto-paginating (0 = no cap).")For large searches, set explicit `max_results` and `--max-pages` values and review the requested filters before running auto-pagination.
Search inputs and enriched contact results may include personal or business contact information that should not be exposed in shared logs or unsecured storage.
The skill sends LinkedIn URLs and search payloads to Dievio and may return full contact rows containing emails or phone numbers. The endpoint and raw-output risk are disclosed, but the data should be handled carefully.
LinkedIn lookup requires `linkedinUrls` and optional output flags. ... Use `--raw-output` only when you explicitly need full rows (which may contain emails/phones).
Only submit LinkedIn URLs or filters you are authorized to process, avoid `--raw-output` unless needed, and store or share returned contact data according to your privacy and compliance requirements.