Clearout for AI agents
Clearout verifies email addresses and finds contact emails, helping sales and marketing teams keep lists clean and reach the right inbox. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.
What agents do in Clearout.
Verify a single email address
Verify a single email address instantly before adding it to an outreach sequence.
Find a person's email by LinkedIn
Find a person's email address from their LinkedIn profile URL before reaching out.
Check remaining verification credits
Check remaining email verification credits before kicking off a large bulk verify job.
21 Clearout actions, graded by risk.
Every Clearout action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
0Look things up. Allowed by default.
- No read actions.
write
19Create and change things. Allow, or ask the user first.
- clearout.domain_find_mxFind Domain MX Records
- clearout.catch_all_verifyCatch-All Verify
- clearout.disposable_verifyVerify Disposable Email
- clearout.domain_find_whoisFetch Domain WHOIS Information
- clearout.email_finder_bulkBulk Email Finder
- clearout.email_verify_bulkBulk Email Verify
- clearout.free_account_verifyVerify Free Email Account
- clearout.role_account_verifyRole Account Verifier
- clearout.email_verify_instantInstant Email Verifier
- clearout.business_account_verifyBusiness Account Verify
- clearout.email_verify_get_creditsEmail Verify Get Credits
- clearout.gibberish_account_verifyVerify Gibberish Email
- clearout.autocomplete_company_to_domainAutocomplete Company to Domain
- clearout.email_finder_bulk_result_downloadBulk Email Finder Result Download
- clearout.email_verify_bulk_progress_statusBulk Email Verify Progress Status
- clearout.email_verify_bulk_result_downloadBulk Email Verify Result Download
destructive
2Delete, cancel or archive. Ask first, or deny outright.
- clearout.email_finder_bulk_cancelCancel Bulk Email Finder Job
- clearout.email_verify_bulk_cancelCancel Bulk Email Verification Job
Clearout in three steps.
- 01Your users connect ClearoutThey add their Clearout api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, writes like “find Domain MX Records” can wait for the user, and “cancel Bulk Email Finder Job” can be denied outright.
- 03Any agent can actYour agent calls Clearout through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('clearout', { read: 'allow', write: 'ask', // domain_find_mx destructive: 'deny', // email_finder_bulk_cancel }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Clearout connects.
Users add their Clearout api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
The same Clearout connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →
- AUTH
- API key
- CREDENTIALS
- Per-tenant encrypted vault
- MODEL SEES
- Results only, never credentials
- AUDIT LOG
- Every call, on every plan
Use Clearout from any agent.
Clearout and Arc0, answered.
Can I use Clearout with Claude, ChatGPT or Cursor?
Yes. Connect Clearout to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the Clearout actions you allow.
How do users connect Clearout?
Users add their Clearout api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
Which Clearout actions can my agent take?
21 in total: 0 read, 19 write and 2 destructive, such as “find Domain MX Records”. Your policies decide which of them each agent may call.
Can I stop my agent from deleting things in Clearout?
Yes. Actions like “cancel Bulk Email Finder Job” are graded destructive. Set destructive actions to deny, or to ask so the user approves each one, and blocked calls still show up on the audit log.
Can my own backend call Clearout too?
Yes. The same Clearout connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Clearout into your agent.
Your users connect Clearout once, under your brand. Your agent gets 21 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan