Clearout API

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.