Reference & Lookup Data · Integration
Clearout
Add Clearout to your product for your customers, and give your AI agents governed access to it.
Clearout verifies email deliverability through api.clearout.io with a bearer token, using /v2/email_verify/instant for single addresses and a separate bulk path where a file is uploaded, progress is polled and results are downloaded once processing completes. The instant response is more than valid or invalid: it carries a status of valid, invalid, catch_all or unknown, a sub_status explaining why, and a safe_to_send verdict that most teams should act on instead of status alone. Catch-all domains accept everything at SMTP time, so they still consume a credit while giving no real assurance, which is the usual surprise in a first bill. A timeout parameter exists because some mail servers respond slowly, and pushing it too low turns genuine addresses into unknowns. There is also an email finder that guesses and verifies an address from a name and domain. fastn stores each customer's token, keeps the connection current and governs how many credits an agent may spend.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a customer connect their own Clearout account so verification runs on their credits and their compliance terms.
Verify an email at signup and block or soft-warn on invalid and risky addresses before an account is created.
Clean an imported list in bulk, poll progress and write the safe_to_send verdict back to each contact.
Use the email finder to fill missing addresses from a name and company domain, then verify the result.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
Let an agent verify a batch of addresses and report how many were catch-all, with credit spend audited per tenant.
Have an agent re-verify contacts that have bounced and mark those no longer safe to send.
Allow an agent to read verification results without permission to launch large bulk jobs unattended.
Example prompt
Verify this list of addresses and tell me which are safe to send to.
Set up Clearout in 4 steps
- 01Enable the Clearout connector from your fastn dashboard.
- 02Have each customer authorise their own Clearout account, so calls run under their credentials rather than a shared key.
- 03Decide which lookups, results and reports your product needs, map those fields, then enable the actions and triggers you want.
- 04Call it from your product and expose it to your agents through the same governed connection.
Why teams use the Clearout integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Clearout integration without building it. Your customers connect their own Clearout account inside your product and work their lookups, results and reports there, with no per-customer code on your side.
- Handle the part that actually costs time: these are metered read sources, so an uncached lookup on every page view burns the customer's allowance. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a Clearout update is not your on-call problem.
- One integration serves your product and your agents. The same governed Clearout connection powers in-product features and gives AI agents scoped, audited access, so you answer questions from an authoritative outside source without holding that data yourself without wiring it twice.
Used by these teams
Compare with
Clearbit
APIVoidOften used alongside
Tools the same teams tend to run next to Clearout, across other categories.
Salesforce
HubSpot
Notion
SnowflakeClearout integration FAQ
How do I add a Clearout integration to my product?
Enable the Clearout connector in your fastn dashboard, then let each customer authenticate their own Clearout account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Clearout client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Clearout account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Clearout account and only ever sees their own lookups, results and reports. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this Clearout integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. Let an agent verify a batch of addresses and report how many were catch-all, with credit spend audited per tenant.
Who maintains the Clearout integration?
fastn does. When Clearout changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Whose credentials does a Clearout lookup run under?
Each customer's own. Quota and cost land on the customer that caused them rather than on a shared key you have to meter and re-bill, and one heavy customer cannot exhaust another's allowance.
How should Clearout results be cached?
Per tenant, with a window that matches how fast the underlying data actually moves. Clearout is a read source rather than a system of record, so the same query returns the same answer until the source changes, and caching is the difference between a sustainable integration and one that exhausts a customer's allowance on a busy page.
What can I build with the Clearout integration?
A common starting point: let a customer connect their own Clearout account so verification runs on their credits and their compliance terms. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the Clearout integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Clearout does not change your per-connector cost. You can start free with 3 connected accounts.
Add Clearout to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.