Clearout
Verify email deliverability and find prospect emails via the Clearout API.
Clearout validates single email addresses in real time (without sending a test email), discovers professional email addresses from a person's name and company domain, and reports your remaining account credits. This tool wraps those endpoints for use inside InTouch jobs and the AI assistant.
What it does
- verify-email — Instant deliverability check for one address. Returns
status (
valid/invalid/catch_all/unknown),safe_to_send, and classification flags (disposable, free, role, gibberish). - find-email — Instant email finder. Given a person's name and a company domain, returns candidate professional emails with a confidence score.
- account-credits — Returns the remaining credit balance on your account.
Operations
| operation | HTTP | Endpoint | Required inputs |
|---|---|---|---|
verify-email |
POST | /v2/email_verify/instant |
email |
find-email |
POST | /v2/email_finder/instant |
name, domain |
account-credits |
GET | /v2/account/credits |
— |
Base URL: https://api.clearout.io
timeout (milliseconds, max 180000) is an optional input for verify-email
and find-email.
API key setup
- Sign in to your Clearout dashboard at https://clearout.io.
- Open the API section and copy your API token (a JWT string).
- Pass it as the
apiKeyinput. The tool sends it asAuthorization: Bearer <apiKey>on every request.
A single token fully authenticates every call — there is no OAuth handshake.
Examples
Verify a single address:
{
"apiKey": "<YOUR_CLEAROUT_TOKEN>",
"operation": "verify-email",
"email": "[email protected]"
}
Find a prospect's email by name + domain:
{
"apiKey": "<YOUR_CLEAROUT_TOKEN>",
"operation": "find-email",
"name": "Tony Stark",
"domain": "marvel.com"
}
Check remaining credits:
{
"apiKey": "<YOUR_CLEAROUT_TOKEN>",
"operation": "account-credits"
}
Output
The tool publishes two values:
result— the Clearout JSON response, as a JSON string.status— the HTTP status code, as a string.
Non-2xx responses (e.g. 401 for a bad token, 402/422 for insufficient
credits or bad parameters) are returned in result/status rather than
raised — the JSON body explains the error. A transport failure or a missing
required input fails the step with an {"error": ...} envelope.