canonical: https://jentic.com/apis/clearout.io/clearout # Clearout API Jentic publishes the only available OpenAPI specification for Clearout API, keeping it validated and agent-ready. Clearout combines email verification, email finder, reverse lookup, and company autocomplete into a single API for cleaning lists and enriching contact records. Synchronous endpoints handle individual lookups while batch endpoints process larger jobs asynchronously and return list IDs to poll. Reverse lookup operations resolve LinkedIn profiles, email addresses, or domains back to associated company and contact data. ## For AI agents Verify emails, find professional emails by name and domain, reverse-lookup LinkedIn profiles or domains, and autocomplete company names through a single bearer-authenticated API. ## Scope Does not handle email sending, CRM record management, or outreach automation - use for email verification, email discovery, and contact enrichment only. ## Capabilities - Verify a single email address with detailed deliverability and risk signals - Run bulk email verification jobs and check completion status by list ID - Find professional email addresses for a person at a specific company domain - Reverse lookup a LinkedIn profile URL to retrieve contact and company data - Reverse lookup an email or domain to surface organisation details - Autocomplete company names to canonical domains for downstream enrichment ## Use cases ### Outbound Sales Email Discovery Find verified work emails for a target list of prospects by combining Clearout's email finder with instant verification. Sales teams provide a list of names and company domains, Clearout returns candidate addresses with confidence scores, and verification flags any risky or undeliverable hits before outreach. Typical workflows enrich a few hundred prospects in minutes via the bulk endpoint. Example prompt: Call POST /email_finder/instant with first name, last name, and domain, then pass the returned email to POST /email_verify/instant and only forward addresses with a positive verification verdict. ### LinkedIn-to-Email Enrichment Convert a LinkedIn profile URL into a professional email and associated company record via Clearout's reverse lookup endpoints. Recruiters and BDRs use this to bridge from LinkedIn searches to outreach without manual research. The lookup returns structured data including current title and company so it can be written straight to a CRM record. Example prompt: Call GET /reverse_lookup/linkedin with the prospect's profile URL and write the returned email, title, and company into a CRM contact record. ### List Hygiene for Marketing Sends Clean a marketing list before a send by uploading it to Clearout's bulk verification endpoint, polling for status, and removing addresses flagged as undeliverable, role-based, or risky. The bulk flow scales to lists that are too large for synchronous verification and returns deliverability plus quality signals per address. Example prompt: Submit the list via POST /email_verify/bulk, poll GET /email_verify/bulk/{list_id} until the job completes, and remove every address whose status is invalid or risky from the marketing platform. ### Company Domain Resolution Resolve a free-text company name typed by a user or extracted from a form into the canonical web domain using Clearout's autocomplete endpoint. This is useful before email finding (which requires a domain) and for deduplicating CRM records that store the same company under different names. Example prompt: Call GET /public/companies/autocomplete with the user-entered company name and select the top match's domain to use in subsequent email finder calls. ### AI Agent Lead Enrichment Pipeline Allow an AI agent to enrich raw leads end-to-end: resolve company domain, find candidate emails, verify deliverability, and reverse-lookup any LinkedIn URLs supplied with the lead. Through Jentic the agent calls each Clearout operation by intent rather than browsing docs, and the bearer token stays in your Jentic One instance. Example prompt: Search Jentic for 'find professional email', then chain autocomplete, email finder, and email verification operations to produce a verified-contact record for each input lead. ## Key endpoints | Method | Path | Description | | --- | --- | --- | | POST | /email_verify/instant | Verify a single email address | | POST | /email_verify/bulk | Submit a bulk email verification job | | GET | /email_verify/bulk/{list_id} | Check the status of a bulk verification job | | POST | /email_finder/instant | Find a professional email by name and domain | | GET | /reverse_lookup/linkedin | Reverse lookup a LinkedIn profile | | GET | /reverse_lookup/email | Reverse lookup an email address | | GET | /public/companies/autocomplete | Autocomplete company names to domains | ## Key resources - **Email Verification** — Instant and bulk email validation - **Email Finder** — Look up professional emails by name and domain - **Reverse Lookup** — Resolve LinkedIn URLs, emails, or domains to contact and company data - **Autocomplete** — Resolve company names to canonical domains ## Why Jentic - **Setup:** Wiring the Clearout API by hand means attaching its bearer token to every call against api.clearout.io/v2 and tracking list ids for bulk verification yourself. Through Jentic you install once, import Clearout from the API Directory, store the token once, and your agent calls it. - **Permission scoping:** Clearout puts the bulk list id in the URL path (/email_verify/bulk/{list_id}), so a rule can pin your agent to reading one verification list. You choose the operations it may call, so instant verify or email finder is not included unless you add it. - **Credential handling:** Your Clearout token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'verify an email instantly' or 'find an email address with Clearout', and Jentic returns the matching operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **Hunter API** — Email finder and verification focused on domain-based discovery and pattern detection. - **Clearbit API** — Firmographic and person enrichment with deeper company datasets. - **ZeroBounce API** — Email verification with detailed scoring and abuse signals. - **NeverBounce API** — Email verification widely integrated into mainstream marketing tools. ## FAQ ### Why is there no official OpenAPI spec for Clearout API? Clearout does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Clearout API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer. ### What authentication does the Clearout API use? Clearout uses HTTP bearer token authentication with a JWT format. The token is sent in the Authorization header. When called through Jentic, the token is stored encrypted in your Jentic One instance and is never exposed to the agent's prompt context. ### Can I find someone's email address with the Clearout API? Yes. Call POST /email_finder/instant with first name, last name, and a company domain to retrieve a candidate professional email along with a confidence indicator. For lists, use POST /email_finder/bulk and poll the resulting list ID for completion. ### Can the Clearout API resolve a LinkedIn profile to an email? Yes. Call GET /reverse_lookup/linkedin with the LinkedIn profile URL and Clearout returns the associated email and company data when available. This is useful for converting LinkedIn search results into outreach records. ### What are the rate limits for the Clearout API? Rate limits are not declared in the public OpenAPI spec and are governed by the credit plan attached to your Clearout account. Bulk endpoints queue server-side, so the practical limit for large jobs is plan credits rather than per-second throughput. ### How do I verify and find emails through Jentic? Search Jentic for 'find professional email' or 'verify email deliverability' and Jentic returns the matching Clearout operation with its input schema. Run pip install jentic, then await client.search, await client.load, await client.execute to chain finder and verification calls. ### Can I limit what my agent is allowed to do with the Clearout API? Yes. Because you run Jentic One yourself, your own rules decide which Clearout operations and credentials the agent may use, so it only ever calls the endpoints you explicitly allow. You can grant just GET /email_verify/bulk/{list_id} to let the agent read a single bulk verification list, while leaving instant verify (POST /email_verify/instant), email finder (POST /email_finder/instant), and the reverse lookup endpoints out unless you add them. Since the bulk list ID sits in the URL path, a rule can pin the agent to one specific verification list rather than the whole account.