The agent calls Listclean's Verify Email API endpoint with the email address provided during conversation. Listclean runs multi-layer checks including syntax validation, MX record lookup, SMTP verification, and disposable domain detection. The result returns in real time, and the agent acts accordingly, accepting valid addresses or requesting correction for invalid ones.

Listclean identifies invalid mailboxes, disposable and temporary email addresses, role-based addresses like info@ or admin@, domains with no MX records, and known spam trap addresses. The AI agent receives a detailed classification for each verified email, not just a pass/fail result.

A Listclean API key is all that is required. Generate it in your Listclean account dashboard, enter it in the Tars Tools configuration, and the integration goes live. No OAuth, no webhooks, no additional infrastructure needed.

Tars sends the email address to Listclean's API in real time and receives the verification result. The email is used within the active conversation context. Tars does not maintain a separate database of verified or unverified email addresses from Listclean interactions.

Each email verification through Listclean consumes one credit, regardless of whether the result is valid, invalid, or unknown. The agent can check your remaining credit balance before processing large batches, so you always know your verification capacity.

Both. For real-time conversation use, the agent verifies one email at a time through the Verify Email endpoint. For batch processing, the agent creates a CSV file of email addresses through the Bulk Verification List endpoint, which you can then upload through Listclean for batch validation.

Listclean's dashboard requires manual upload and review. With Tars, verification happens inside the conversation the moment an email is provided. There is no separate step, no CSV export, and no dashboard login. The validation is invisible to the customer and instant for your data quality.

You configure the agent's behavior for edge cases. For emails marked as risky or catch-all, the agent can accept them with a flag, ask the customer to confirm, or request an alternative address. Strict or lenient handling is your choice based on your risk tolerance for email deliverability.