> For the complete documentation index, see [llms.txt](https://docs.distro.so/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.distro.so/integrations/icypeas.md). # Icypeas email verification Use Icypeas to check whether an email exists before deciding how to route or follow up. ## Connect An admin opens **Settings → Integrations → Icypeas** and enters the **API key** and **Icypeas account email**. Saving reads the subscription to verify the credentials without using verification credits. Each live email check uses one Icypeas credit. ## Add a check Use the standalone Icypeas email-check workflow action and map the prospect email. Add conditions for the returned status, including an unknown or failed-check path. A connection does not automatically block submissions. Specify what your business does with a valid, invalid or uncertain address. ## Chains and Records Records can consume the supported email-check setting when it runs enrichment. Workflow Enrich Lead does not automatically execute chain-level email validation flags; use the standalone action for a workflow decision. See [Provider support by surface](/data-and-integrations/provider-support.md). ## Troubleshoot Check both the key and account email, then inspect quota and provider errors. Use a controlled test address before applying a new condition to all inbound leads. A failed API check is different from an invalid prospect email. Route provider failures deliberately so a transient outage does not silently discard real prospects. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.distro.so/integrations/icypeas.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.