# How can my AI agent verify email addresses before a handoff? Verify email addresses with supported Agentik tools. By [Agentik](/about.md). Updated: 2026-10-19. Email verification checks a supplied address using a supported provider operation. It is separate from discovering an address or identifying a person. Agentik can expose both through one connection, but the agent should preserve the actual verification outcome and time rather than label every returned address as deliverable. - [Connect your agent](/docs/clients.md) ## Verify an address, not a guessed contact Start with an authorized list and stable row identifiers. Normalize obvious formatting issues without silently changing the person or domain. If the task is missing an email, use a separate finding operation or return the gap. The catalog includes icypeas/verify-email and icypeas/verify-email-sync. Inspect which operation fits the client’s execution flow, including pending result handling. An asynchronous submission and a completed verification are different states. ## Preserve provider outcomes without overstatement Return the original address, provider outcome, retrieval time and any relevant uncertainty. The provider’s billing status and deliverability verdict may be different fields; a debit marker is not by itself a valid-address verdict. A result can be uncertain or limited by server behavior. Preserve that state and avoid converting it into a positive verification. Verification does not guarantee a future delivery, a response or permission to send a message. ## Review units and completion for a batch Inspect whether pricing follows submitted addresses, charged credits or another returned unit. Keep missing or uncharged outcomes separate according to the tool contract. Do not derive a final receipt from the size of the uploaded list alone. Retain the run and provider search identifiers where returned. If the client times out, retrieve the existing result before starting the same batch again. Produce a reviewable handoff file without initiating outreach as an implied next step. ## What you pay for Supported paid tools use Agentik's prepaid workspace balance. Inspect the selected tool's pricing units and maximum before approving a run; a reservation can differ from its settled charge. Funding fees, taxes and your model's usage are separate. Current terms are on the Pricing and Billing pages linked below. ## Keep verification and billing fields separate For an address supplied by the user, the handoff should contain the original value and the provider’s real outcomes. This table is a schema proposal, not a verification result. Keep verification and billing fields separate | Column | Meaning | | --- | --- | | Row ID and address | Join back to the authorized input. | | Verification outcome | Exact provider verdict or explicit uncertainty. | | Checked at | When the observation was retrieved. | | Execution and cost | Run state, receipt and returned billing units. | ## A prompt to try [Connect your agent](/docs/clients.md), then use this prompt with your connected assistant. Keep credentials in the authorized connection. ```text Verify the authorized email list [file or records] using Agentik. Inspect_tool for synchronous or asynchronous verification, required fields, result states and pricing. Keep finding missing addresses out of scope unless I approve it. Propose a sample and maximum first. After approval, preserve row IDs, exact provider verdicts, uncertainty, check times and run references. Keep billing status separate from deliverability. Return a handoff file and do not send messages. ``` ## A related workflow [B2B lead list](/b2b-lead-list.md). People who match your buyer, emails found by two providers and verified, and a recent news hook for each company. Example tool-call maximum: at most $2.21. 50 people in software companies of 20 to 200 employees in France and Germany, emails looked up for all, a second source for 10, every address verified, 25 companies checked in the news. This catalog-based reservation maximum belongs to the playbook’s inputs, separately from this guide’s worked example. It is not an executed charge. Optional calls, funding fees, taxes and model usage are excluded. - [leadsforge/count-people](/providers/leadsforge/count-people.md) - [leadsforge/search-people](/providers/leadsforge/search-people.md) - [leadsforge/find-emails-batch](/providers/leadsforge/find-emails-batch.md) [View every step, input and tool in the playbook](/b2b-lead-list.md). ## Questions ### Is a found email automatically verified? No. Discovery and verification are separate operations. Preserve the source and verification state independently. ### Does a verification result guarantee delivery? No. Keep the actual provider verdict and time, including uncertainty. Conditions can change after the check. ## Sources and next steps Agentik publishes this guide. The editorial update date is 2026-10-19; provider terms and availability can change. - [Icypeas email verification](https://api-doc.icypeas.com/find-emails/email-verification) - [Agentik billing units](/docs/billing.md) ### Continue with Agentik - [B2B tools](/tools/b2b-data.md) - [Async execution](/docs/async.md) ## Related guides - [B2B enrichment for agents](/ai-agent-b2b-data-enrichment.md) - [Long-running tool workflows](/ai-agent-async-tool-workflows.md) - [Compare tool pricing units](/ai-agent-tool-pricing-models.md) [Browse all agent tool guides](/agent-tool-guides.md) --- [HTML page](/ai-agent-email-verification) · [Agent index](/llms.txt)