Clearout

Get remaining credits via GET /v2/account/credits. Return the account's `total_remaining_credits` and the breakdown by source (`pay_as_you_go`, `subscription`, bonus) plus the low-balance threshold. Free. This is also the credential check run when a token is pasted: MEASURED 2026-09-20 with the owner's token -> 200 `total_remaining_credits: 100`; a bogus token -> 401 code 1000. It shares the `/account/*` rate-limit bucket, which on the free plan is ONE request per ten seconds. Clearout rate-limits per plan and per service: every authenticated reply carries `x-ratelimit-limit`, `x-ratelimit-remaining` and `x-ratelimit-reset`, and an exhausted budget answers HTTP 429 with Clearout error code 1030 and a `Retry-After` -- a THROTTLE, never a bad token; wait and retry. Measured on the free plan 2026-09-20: the `/account/*` endpoints allow one request per ten seconds, instant verification and the email finder 3 per minute each, name validation 5, reverse lookup 200.

Get service limits via GET /v2/account/limits. Return the account's active service limits: the API requests-per-minute limit and how much of it remains, the reset time, and the number of bulk jobs that may run in parallel. Free; shares the `/account/*` rate-limit bucket. Clearout rate-limits per plan and per service: every authenticated reply carries `x-ratelimit-limit`, `x-ratelimit-remaining` and `x-ratelimit-reset`, and an exhausted budget answers HTTP 429 with Clearout error code 1030 and a `Retry-After` -- a THROTTLE, never a bad token; wait and retry. Measured on the free plan 2026-09-20: the `/account/*` endpoints allow one request per ten seconds, instant verification and the email finder 3 per minute each, name validation 5, reverse lookup 200.

Get plans and add-ons via GET /v2/account/myplans. Return the account's current subscription or pay-as-you-go plan and its add-ons: name, status, type, charge and renewal dates. Free; shares the `/account/*` rate-limit bucket. Clearout rate-limits per plan and per service: every authenticated reply carries `x-ratelimit-limit`, `x-ratelimit-remaining` and `x-ratelimit-reset`, and an exhausted budget answers HTTP 429 with Clearout error code 1030 and a `Retry-After` -- a THROTTLE, never a bad token; wait and retry. Measured on the free plan 2026-09-20: the `/account/*` endpoints allow one request per ten seconds, instant verification and the email finder 3 per minute each, name validation 5, reverse lookup 200.

Get bulk finder progress via GET /v2/email_finder/bulk/progress_status. Report the progress of a bulk email finder list by `list_id`: `progress_status` and the percentage done. Poll until completed, then fetch results with Get a bulk finder result download link. Clearout answers an unknown or expired `list_id` with HTTP 200 and `status: failed`, code 1029 `List is not available` (measured 2026-09-20), so read `status` in the reply rather than trusting the 200. Clearout rate-limits per plan and per service: every authenticated reply carries `x-ratelimit-limit`, `x-ratelimit-remaining` and `x-ratelimit-reset`, and an exhausted budget answers HTTP 429 with Clearout error code 1030 and a `Retry-After` -- a THROTTLE, never a bad token; wait and retry. Measured on the free plan 2026-09-20: the `/account/*` endpoints allow one request per ten seconds, instant verification and the email finder 3 per minute each, name validation 5, reverse lookup 200.

Get a queued email finder result via GET /v2/email_finder/instant/queue_status. Fetch the result of an email finder request that was queued because it outlasted its timeout, by the `qid` from Find a person's email address. The reply has the same shape as an instant result once the search has finished; until then it reports the queue status. AN UNKNOWN OR EXPIRED `qid` ANSWERS HTTP 401 with Clearout code 1104 `Invalid queue ID` (measured 2026-09-20) -- that 401 is about the qid, not the token; only code 1000 is a credential problem. Clearout rate-limits per plan and per service: every authenticated reply carries `x-ratelimit-limit`, `x-ratelimit-remaining` and `x-ratelimit-reset`, and an exhausted budget answers HTTP 429 with Clearout error code 1030 and a `Retry-After` -- a THROTTLE, never a bad token; wait and retry. Measured on the free plan 2026-09-20: the `/account/*` endpoints allow one request per ten seconds, instant verification and the email finder 3 per minute each, name validation 5, reverse lookup 200.

Get bulk verify progress via GET /v2/email_verify/bulk/progress_status. Report the progress of a bulk verification list by `list_id`: `progress_status` (`running`, `completed`, ...) and the percentage done. Poll this after a list is started until it reports completed, then fetch the results with Get a bulk verify result download link. Clearout answers an unknown or expired `list_id` with HTTP 200 and `status: failed`, code 1029 `List is not available` (measured 2026-09-20), so read `status` in the reply rather than trusting the 200. Clearout rate-limits per plan and per service: every authenticated reply carries `x-ratelimit-limit`, `x-ratelimit-remaining` and `x-ratelimit-reset`, and an exhausted budget answers HTTP 429 with Clearout error code 1030 and a `Retry-After` -- a THROTTLE, never a bad token; wait and retry. Measured on the free plan 2026-09-20: the `/account/*` endpoints allow one request per ten seconds, instant verification and the email finder 3 per minute each, name validation 5, reverse lookup 200.

Get available credits (legacy endpoint) via GET /v2/email_verify/getcredits. Return the account's available credits from the older `/email_verify/getcredits` endpoint: `available_credits`, the daily verify limit and its reset date, and the low-balance threshold. Free, and MEASURED 2026-09-20 to be exempt from the per-plan rate limit that throttles the `/account/*` endpoints (three back-to-back calls all answered 200 with no rate-limit headers), so it is the cheap way to poll a balance. Get remaining credits is the current endpoint and breaks the balance down by plan. Clearout rate-limits per plan and per service: every authenticated reply carries `x-ratelimit-limit`, `x-ratelimit-remaining` and `x-ratelimit-reset`, and an exhausted budget answers HTTP 429 with Clearout error code 1030 and a `Retry-After` -- a THROTTLE, never a bad token; wait and retry. Measured on the free plan 2026-09-20: the `/account/*` endpoints allow one request per ten seconds, instant verification and the email finder 3 per minute each, name validation 5, reverse lookup 200.

Find domains for a company name via GET /public/companies/autocomplete. Suggest the website domains for a company name, domain fragment or URL (`query`), each with a `confidence_score` and a logo URL -- the way to turn 'Marvel' into `marvel.com` before Find a person's email address. FREE and PUBLIC: this is the one Clearout endpoint that needs no credential and costs no credit (it lives on https://api.clearout.io/public, outside the `/v2` API), so it is never the credential check for this connection. The connector sends it WITHOUT the account token on purpose: measured 2026-09-20, the route answers 404 `Endpoint Not found` (code 1138) to any request carrying an Authorization header and 200 to one without. Clearout rate-limits per plan and per service: every authenticated reply carries `x-ratelimit-limit`, `x-ratelimit-remaining` and `x-ratelimit-reset`, and an exhausted budget answers HTTP 429 with Clearout error code 1030 and a `Retry-After` -- a THROTTLE, never a bad token; wait and retry. Measured on the free plan 2026-09-20: the `/account/*` endpoints allow one request per ten seconds, instant verification and the email finder 3 per minute each, name validation 5, reverse lookup 200.

Look up a company by domain via GET /v2/reverse_lookup/domain. Retrieve a company profile from a domain `name`: company name, LinkedIn page, logo and address in `data.lead`. METERED against credits. HTTP 402 (Clearout codes 1002/1031) means the account is out of credits: the token is fine, the balance is not -- check Get remaining credits. Clearout rate-limits per plan and per service: every authenticated reply carries `x-ratelimit-limit`, `x-ratelimit-remaining` and `x-ratelimit-reset`, and an exhausted budget answers HTTP 429 with Clearout error code 1030 and a `Retry-After` -- a THROTTLE, never a bad token; wait and retry. Measured on the free plan 2026-09-20: the `/account/*` endpoints allow one request per ten seconds, instant verification and the email finder 3 per minute each, name validation 5, reverse lookup 200.

Look up a lead by email address via GET /v2/reverse_lookup/email. Retrieve the lead behind an `email_address`: name, title, LinkedIn URL, company name and domain, and location in `data.lead`. METERED against credits. HTTP 402 (Clearout codes 1002/1031) means the account is out of credits: the token is fine, the balance is not -- check Get remaining credits. Clearout rate-limits per plan and per service: every authenticated reply carries `x-ratelimit-limit`, `x-ratelimit-remaining` and `x-ratelimit-reset`, and an exhausted budget answers HTTP 429 with Clearout error code 1030 and a `Retry-After` -- a THROTTLE, never a bad token; wait and retry. Measured on the free plan 2026-09-20: the `/account/*` endpoints allow one request per ten seconds, instant verification and the email finder 3 per minute each, name validation 5, reverse lookup 200.

Look up a lead by LinkedIn URL via GET /v2/reverse_lookup/linkedin. Retrieve a lead's profile from a LinkedIn profile `url`: name, title, company name and domain, location and experience in `data.lead`. METERED against credits. HTTP 402 (Clearout codes 1002/1031) means the account is out of credits: the token is fine, the balance is not -- check Get remaining credits. Clearout rate-limits per plan and per service: every authenticated reply carries `x-ratelimit-limit`, `x-ratelimit-remaining` and `x-ratelimit-reset`, and an exhausted budget answers HTTP 429 with Clearout error code 1030 and a `Retry-After` -- a THROTTLE, never a bad token; wait and retry. Measured on the free plan 2026-09-20: the `/account/*` endpoints allow one request per ten seconds, instant verification and the email finder 3 per minute each, name validation 5, reverse lookup 200.

Resolve a domain's MX records via POST /v2/domain/resolve/mx. Resolve a domain's MX records in priority order, so you can see where its mail is hosted before verifying addresses on it. Reply: `mx_records[]` with `exchange` and `priority`. Clearout documents a 402 on this route, so treat it as metered. HTTP 402 (Clearout codes 1002/1031) means the account is out of credits: the token is fine, the balance is not -- check Get remaining credits. `timeout` (milliseconds) is capped at 25000 by this connector and filled in at that value when omitted, because Agentic Fabriq waits at most 30 seconds for a reply; Clearout's own default is longer and a call that honoured it would time out on our side while Clearout kept working. Clearout rate-limits per plan and per service: every authenticated reply carries `x-ratelimit-limit`, `x-ratelimit-remaining` and `x-ratelimit-reset`, and an exhausted budget answers HTTP 429 with Clearout error code 1030 and a `Retry-After` -- a THROTTLE, never a bad token; wait and retry. Measured on the free plan 2026-09-20: the `/account/*` endpoints allow one request per ten seconds, instant verification and the email finder 3 per minute each, name validation 5, reverse lookup 200.

Look up a domain's WHOIS record via POST /v2/domain/resolve/whois. Return a domain's WHOIS record as JSON: registrar, registrant, admin and technical contacts, status flags, creation and expiry dates. Clearout documents a 402 on this route, so treat it as metered. HTTP 402 (Clearout codes 1002/1031) means the account is out of credits: the token is fine, the balance is not -- check Get remaining credits. `timeout` (milliseconds) is capped at 25000 by this connector and filled in at that value when omitted, because Agentic Fabriq waits at most 30 seconds for a reply; Clearout's own default is longer and a call that honoured it would time out on our side while Clearout kept working. Clearout rate-limits per plan and per service: every authenticated reply carries `x-ratelimit-limit`, `x-ratelimit-remaining` and `x-ratelimit-reset`, and an exhausted budget answers HTTP 429 with Clearout error code 1030 and a `Retry-After` -- a THROTTLE, never a bad token; wait and retry. Measured on the free plan 2026-09-20: the `/account/*` endpoints allow one request per ten seconds, instant verification and the email finder 3 per minute each, name validation 5, reverse lookup 200.

Get a bulk verify result download link via POST /v2/download/result. Get a time-limited download URL for the results CSV of a completed bulk verification list. The reply carries `data.url`, a presigned Amazon S3 link to the results file -- this tool returns the LINK, not the file. THE LINK IS SHORT-LIVED: measured 2026-09-20, `X-Amz-Expires=300`, so fetch it within five minutes and call again for a fresh one; the results themselves stay available until the list's `result_expires_on` (about 30 days), after which this answers the ResultFileExpired shape rather than a URL. Clearout answers an unknown or expired `list_id` with HTTP 200 and `status: failed`, code 1029 `List is not available` (measured 2026-09-20), so read `status` in the reply rather than trusting the 200. Clearout rate-limits per plan and per service: every authenticated reply carries `x-ratelimit-limit`, `x-ratelimit-remaining` and `x-ratelimit-reset`, and an exhausted budget answers HTTP 429 with Clearout error code 1030 and a `Retry-After` -- a THROTTLE, never a bad token; wait and retry. Measured on the free plan 2026-09-20: the `/account/*` endpoints allow one request per ten seconds, instant verification and the email finder 3 per minute each, name validation 5, reverse lookup 200.

Get a bulk finder result download link via POST /v2/email_finder/download/result. Get a time-limited download URL for the results CSV of a completed bulk email finder list. The reply carries `data.url`, a presigned Amazon S3 link -- this tool returns the LINK, not the file, and the link is short-lived (the verifier's equivalent was measured at `X-Amz-Expires=300`, five minutes), so fetch it promptly; an expired list answers the ResultFileExpired shape rather than a URL. Clearout answers an unknown or expired `list_id` with HTTP 200 and `status: failed`, code 1029 `List is not available` (measured 2026-09-20), so read `status` in the reply rather than trusting the 200. Clearout rate-limits per plan and per service: every authenticated reply carries `x-ratelimit-limit`, `x-ratelimit-remaining` and `x-ratelimit-reset`, and an exhausted budget answers HTTP 429 with Clearout error code 1030 and a `Retry-After` -- a THROTTLE, never a bad token; wait and retry. Measured on the free plan 2026-09-20: the `/account/*` endpoints allow one request per ten seconds, instant verification and the email finder 3 per minute each, name validation 5, reverse lookup 200.

Find a person's email address via POST /v2/email_finder/instant. Find a person's business email address from their `name` and their company's `domain` (or company name). The reply carries `emails[]` with a `confidence_score`, the normalised first/last name and the company. Discovery can outlast the `timeout`: with `queue` true (the default) Clearout keeps searching in the background and the reply carries a `qid` -- poll Get a queued email finder result with it; with `queue` false the search stops at the timeout. METERED: a credit is charged when an address is found. HTTP 402 (Clearout codes 1002/1031) means the account is out of credits: the token is fine, the balance is not -- check Get remaining credits. `timeout` (milliseconds) is capped at 25000 by this connector and filled in at that value when omitted, because Agentic Fabriq waits at most 30 seconds for a reply; Clearout's own default is longer and a call that honoured it would time out on our side while Clearout kept working. Clearout rate-limits per plan and per service: every authenticated reply carries `x-ratelimit-limit`, `x-ratelimit-remaining` and `x-ratelimit-reset`, and an exhausted budget answers HTTP 429 with Clearout error code 1030 and a `Retry-After` -- a THROTTLE, never a bad token; wait and retry. Measured on the free plan 2026-09-20: the `/account/*` endpoints allow one request per ten seconds, instant verification and the email finder 3 per minute each, name validation 5, reverse lookup 200.

List bulk finder lists via POST /v2/email_finder/list. List the account's bulk email finder lists with cursor pagination: up to `limit` records (max 100), each with its `list_id`, name, type, in-progress action, processing timestamps and an `email_finder_result` summary (found, billable, business, role, confidence). Pass `page_info.last_cursor` from one reply as `start_after` for the next page while `page_info.has_more` is true; omit it for the first page. `filter` narrows by `date_range` and `processed`. This is where a `list_id` comes from for every other bulk finder tool. Lists are created in the Clearout app or by a customer's own bulk upload; this integration cannot create one because the upload is a file transfer. Clearout rate-limits per plan and per service: every authenticated reply carries `x-ratelimit-limit`, `x-ratelimit-remaining` and `x-ratelimit-reset`, and an exhausted budget answers HTTP 429 with Clearout error code 1030 and a `Retry-After` -- a THROTTLE, never a bad token; wait and retry. Measured on the free plan 2026-09-20: the `/account/*` endpoints allow one request per ten seconds, instant verification and the email finder 3 per minute each, name validation 5, reverse lookup 200.

Cancel a running bulk finder list via POST /v2/email_finder/list/cancel. Cancel a bulk email finder list that is currently running. Contacts already processed keep their result; the rest are not searched. A list that has already finished answers HTTP 200 with `status: failed` (the verifier's equivalent was measured as code 1116 `List is not in the cancellable stage`). The list itself is kept -- Remove a bulk finder list deletes it. Clearout answers an unknown or expired `list_id` with HTTP 200 and `status: failed`, code 1029 `List is not available` (measured 2026-09-20), so read `status` in the reply rather than trusting the 200. Clearout rate-limits per plan and per service: every authenticated reply carries `x-ratelimit-limit`, `x-ratelimit-remaining` and `x-ratelimit-reset`, and an exhausted budget answers HTTP 429 with Clearout error code 1030 and a `Retry-After` -- a THROTTLE, never a bad token; wait and retry. Measured on the free plan 2026-09-20: the `/account/*` endpoints allow one request per ten seconds, instant verification and the email finder 3 per minute each, name validation 5, reverse lookup 200.

Remove a bulk finder list via POST /v2/email_finder/list/remove. PERMANENTLY REMOVE a bulk email finder list and its results from the account. There is no undo. Removal is refused while a download of that list's results is in progress unless `ignore_result` is true. Use Cancel a running bulk finder list to stop a job you want to keep. Clearout answers an unknown or expired `list_id` with HTTP 200 and `status: failed`, code 1029 `List is not available` (measured 2026-09-20), so read `status` in the reply rather than trusting the 200. Clearout rate-limits per plan and per service: every authenticated reply carries `x-ratelimit-limit`, `x-ratelimit-remaining` and `x-ratelimit-reset`, and an exhausted budget answers HTTP 429 with Clearout error code 1030 and a `Retry-After` -- a THROTTLE, never a bad token; wait and retry. Measured on the free plan 2026-09-20: the `/account/*` endpoints allow one request per ten seconds, instant verification and the email finder 3 per minute each, name validation 5, reverse lookup 200.

Check whether an email address is a business account via POST /v2/email/verify/business. Check whether an email address is a business (work) account rather than a personal one. Reply: `business_account` yes/no. METERED against credits. HTTP 402 (Clearout codes 1002/1031) means the account is out of credits: the token is fine, the balance is not -- check Get remaining credits. `timeout` (milliseconds) is capped at 25000 by this connector and filled in at that value when omitted, because Agentic Fabriq waits at most 30 seconds for a reply; Clearout's own default is longer and a call that honoured it would time out on our side while Clearout kept working. Clearout rate-limits per plan and per service: every authenticated reply carries `x-ratelimit-limit`, `x-ratelimit-remaining` and `x-ratelimit-reset`, and an exhausted budget answers HTTP 429 with Clearout error code 1030 and a `Retry-After` -- a THROTTLE, never a bad token; wait and retry. Measured on the free plan 2026-09-20: the `/account/*` endpoints allow one request per ten seconds, instant verification and the email finder 3 per minute each, name validation 5, reverse lookup 200.

Check whether an email domain is catch-all via POST /v2/email/verify/catchall. Check whether an email address belongs to a catch-all (accept-all) domain -- a mail server that accepts every address and never bounces, so deliverability cannot be confirmed. Reply: `catchall` yes/no. METERED against credits. HTTP 402 (Clearout codes 1002/1031) means the account is out of credits: the token is fine, the balance is not -- check Get remaining credits. `timeout` (milliseconds) is capped at 25000 by this connector and filled in at that value when omitted, because Agentic Fabriq waits at most 30 seconds for a reply; Clearout's own default is longer and a call that honoured it would time out on our side while Clearout kept working. Clearout rate-limits per plan and per service: every authenticated reply carries `x-ratelimit-limit`, `x-ratelimit-remaining` and `x-ratelimit-reset`, and an exhausted budget answers HTTP 429 with Clearout error code 1030 and a `Retry-After` -- a THROTTLE, never a bad token; wait and retry. Measured on the free plan 2026-09-20: the `/account/*` endpoints allow one request per ten seconds, instant verification and the email finder 3 per minute each, name validation 5, reverse lookup 200.

Check whether an email address is disposable via POST /v2/email/verify/disposable. Check whether an email address is on a disposable (temporary) mail service, the kind used for one-off sign-ups. Reply: `disposable` yes/no. METERED against credits. HTTP 402 (Clearout codes 1002/1031) means the account is out of credits: the token is fine, the balance is not -- check Get remaining credits. `timeout` (milliseconds) is capped at 25000 by this connector and filled in at that value when omitted, because Agentic Fabriq waits at most 30 seconds for a reply; Clearout's own default is longer and a call that honoured it would time out on our side while Clearout kept working. Clearout rate-limits per plan and per service: every authenticated reply carries `x-ratelimit-limit`, `x-ratelimit-remaining` and `x-ratelimit-reset`, and an exhausted budget answers HTTP 429 with Clearout error code 1030 and a `Retry-After` -- a THROTTLE, never a bad token; wait and retry. Measured on the free plan 2026-09-20: the `/account/*` endpoints allow one request per ten seconds, instant verification and the email finder 3 per minute each, name validation 5, reverse lookup 200.

Check whether an email address is on a free provider via POST /v2/email/verify/free. Check whether an email address is on a free mail provider such as Gmail, Yahoo, AOL or Mail.ru. Reply: `free_account` yes/no. METERED against credits. HTTP 402 (Clearout codes 1002/1031) means the account is out of credits: the token is fine, the balance is not -- check Get remaining credits. `timeout` (milliseconds) is capped at 25000 by this connector and filled in at that value when omitted, because Agentic Fabriq waits at most 30 seconds for a reply; Clearout's own default is longer and a call that honoured it would time out on our side while Clearout kept working. Clearout rate-limits per plan and per service: every authenticated reply carries `x-ratelimit-limit`, `x-ratelimit-remaining` and `x-ratelimit-reset`, and an exhausted budget answers HTTP 429 with Clearout error code 1030 and a `Retry-After` -- a THROTTLE, never a bad token; wait and retry. Measured on the free plan 2026-09-20: the `/account/*` endpoints allow one request per ten seconds, instant verification and the email finder 3 per minute each, name validation 5, reverse lookup 200.

Check whether an email address is gibberish via POST /v2/email/verify/gibberish. Check whether an email address's local part looks like gibberish (`asdfg@`, keyboard mashing) rather than a name a real person would use. Reply: `gibberish` yes/no. METERED against credits. HTTP 402 (Clearout codes 1002/1031) means the account is out of credits: the token is fine, the balance is not -- check Get remaining credits. `timeout` (milliseconds) is capped at 25000 by this connector and filled in at that value when omitted, because Agentic Fabriq waits at most 30 seconds for a reply; Clearout's own default is longer and a call that honoured it would time out on our side while Clearout kept working. Clearout rate-limits per plan and per service: every authenticated reply carries `x-ratelimit-limit`, `x-ratelimit-remaining` and `x-ratelimit-reset`, and an exhausted budget answers HTTP 429 with Clearout error code 1030 and a `Retry-After` -- a THROTTLE, never a bad token; wait and retry. Measured on the free plan 2026-09-20: the `/account/*` endpoints allow one request per ten seconds, instant verification and the email finder 3 per minute each, name validation 5, reverse lookup 200.

Verify an email address via POST /v2/email_verify/instant. Verify one email address in real time and get its deliverability verdict: `status` (`valid`, `invalid`, `catch_all`, `unknown`), `safe_to_send` (`yes`/`no`/`risky`), a `sub_status` code and reason, and the `disposable`, `free`, `role` and `gibberish` flags, plus the MX host and SMTP provider in `detail_info` and a `suggested_email_address` when a typo was detected. METERED: one credit per address; an `unknown` result is not charged. Clearout reserves test addresses that return a fixed result and cost no credit: `valid@example.com`, `invalid@example.com`, `catch_all@example.com`, `unknown@example.com`, `disposable@example.com`, `role@example.com`, `free@example.com`, `gibberish@example.com`, `safe_to_send_yes@example.com` and the other `<outcome>@example.com` spellings from the API overview. HTTP 402 (Clearout codes 1002/1031) means the account is out of credits: the token is fine, the balance is not -- check Get remaining credits. `timeout` (milliseconds) is capped at 25000 by this connector and filled in at that value when omitted, because Agentic Fabriq waits at most 30 seconds for a reply; Clearout's own default is longer and a call that honoured it would time out on our side while Clearout kept working. Clearout rate-limits per plan and per service: every authenticated reply carries `x-ratelimit-limit`, `x-ratelimit-remaining` and `x-ratelimit-reset`, and an exhausted budget answers HTTP 429 with Clearout error code 1030 and a `Retry-After` -- a THROTTLE, never a bad token; wait and retry. Measured on the free plan 2026-09-20: the `/account/*` endpoints allow one request per ten seconds, instant verification and the email finder 3 per minute each, name validation 5, reverse lookup 200.

List bulk verify lists via POST /v2/email_verify/list. List the account's bulk verification lists with cursor pagination: up to `limit` records (max 100, default 10), newest first, each with its `list_id`, name, type, in-progress action and the verified/cancelled/exported/expiry timestamps. Pass `page_info.last_cursor` from one reply as `start_after` to fetch the next page while `page_info.has_more` is true; omit it (or send null) for the first page. `filter` narrows by `date_range` (e.g. `ps_this_month`), `verified` and `type` (`upload`, ...). This is where a `list_id` comes from for every other bulk verify tool. Lists are created in the Clearout app or by a customer's own bulk upload; this integration cannot create one because the upload is a file transfer. Clearout rate-limits per plan and per service: every authenticated reply carries `x-ratelimit-limit`, `x-ratelimit-remaining` and `x-ratelimit-reset`, and an exhausted budget answers HTTP 429 with Clearout error code 1030 and a `Retry-After` -- a THROTTLE, never a bad token; wait and retry. Measured on the free plan 2026-09-20: the `/account/*` endpoints allow one request per ten seconds, instant verification and the email finder 3 per minute each, name validation 5, reverse lookup 200.

Cancel a running bulk verify list via POST /v2/email_verify/list/cancel. Cancel a bulk verification list that is currently running. Emails already verified stay verified and charged; the rest are not processed. A list that has already finished answers HTTP 200 with `status: failed`, code 1116 `List is not in the cancellable stage` (measured 2026-09-20 on a completed list). The list itself is kept -- Remove a bulk verify list deletes it. Clearout answers an unknown or expired `list_id` with HTTP 200 and `status: failed`, code 1029 `List is not available` (measured 2026-09-20), so read `status` in the reply rather than trusting the 200. Clearout rate-limits per plan and per service: every authenticated reply carries `x-ratelimit-limit`, `x-ratelimit-remaining` and `x-ratelimit-reset`, and an exhausted budget answers HTTP 429 with Clearout error code 1030 and a `Retry-After` -- a THROTTLE, never a bad token; wait and retry. Measured on the free plan 2026-09-20: the `/account/*` endpoints allow one request per ten seconds, instant verification and the email finder 3 per minute each, name validation 5, reverse lookup 200.

Remove a bulk verify list via POST /v2/email_verify/list/remove. PERMANENTLY REMOVE a bulk verification list and its results from the account. There is no undo. Removal is refused while a download of that list's results is in progress unless `ignore_result` is true. Use Cancel a running bulk verify list to stop a job you want to keep. Clearout answers an unknown or expired `list_id` with HTTP 200 and `status: failed`, code 1029 `List is not available` (measured 2026-09-20), so read `status` in the reply rather than trusting the 200. Clearout rate-limits per plan and per service: every authenticated reply carries `x-ratelimit-limit`, `x-ratelimit-remaining` and `x-ratelimit-reset`, and an exhausted budget answers HTTP 429 with Clearout error code 1030 and a `Retry-After` -- a THROTTLE, never a bad token; wait and retry. Measured on the free plan 2026-09-20: the `/account/*` endpoints allow one request per ten seconds, instant verification and the email finder 3 per minute each, name validation 5, reverse lookup 200.

Check whether an email address is a role account via POST /v2/email/verify/role. Check whether an email address is a role or group account (`postmaster@`, `support@`, `sales@`, `hr@`) rather than a person's. Reply: `role_account` yes/no. METERED against credits. HTTP 402 (Clearout codes 1002/1031) means the account is out of credits: the token is fine, the balance is not -- check Get remaining credits. `timeout` (milliseconds) is capped at 25000 by this connector and filled in at that value when omitted, because Agentic Fabriq waits at most 30 seconds for a reply; Clearout's own default is longer and a call that honoured it would time out on our side while Clearout kept working. Clearout rate-limits per plan and per service: every authenticated reply carries `x-ratelimit-limit`, `x-ratelimit-remaining` and `x-ratelimit-reset`, and an exhausted budget answers HTTP 429 with Clearout error code 1030 and a `Retry-After` -- a THROTTLE, never a bad token; wait and retry. Measured on the free plan 2026-09-20: the `/account/*` endpoints allow one request per ten seconds, instant verification and the email finder 3 per minute each, name validation 5, reverse lookup 200.

Validate a person's name via POST /v2/name/validate. Judge whether a string is a legitimate person's name using Clearout's trained model: the reply says `status` (`valid`/`invalid`) and flags `profanity` and `gibberish`. `settings.gibberish_threshold` (`high`, ...) tunes the strictness. `timeout` is capped by Clearout itself at 10000 ms (default 8000). Clearout rate-limits per plan and per service: every authenticated reply carries `x-ratelimit-limit`, `x-ratelimit-remaining` and `x-ratelimit-reset`, and an exhausted budget answers HTTP 429 with Clearout error code 1030 and a `Retry-After` -- a THROTTLE, never a bad token; wait and retry. Measured on the free plan 2026-09-20: the `/account/*` endpoints allow one request per ten seconds, instant verification and the email finder 3 per minute each, name validation 5, reverse lookup 200.