> For the complete documentation index, see [llms.txt](https://docs.clearout.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.clearout.io/help-and-support/featured-answered/credits-and-limits.md).

# Credits & Limits

Common questions on Clearout credits, limits, and billing usage

Clearout follows a transparent credit-based system across Email Verification, Email Finding, Form Guard, Sales Prospecting, Prospect Enrichment, and Reverse Lookup tool.

<details>

<summary>How are email verification credits charged?</summary>

* **1 credit per** [billable email](https://clearout.io/pricing-guide/#:~:text=and%20charged%20accordingly.-,What%20Is%20a%20Billable%20Service%20Action%3F,-A%20billable%20service)
* Not charged for unknown results
* Not charged for unprocessed emails in the cancelled files.

Deep Verify is charged based on outcome of Safe to Send property.

Safe To Send: Yes - 5 credits\
Safe To Send: No - 5 credits\
Safe To Send: Risky - 1 credit

</details>

<details>

<summary>Do free credits expire?</summary>

No. Free credits do not expire and have lifetime validity.

</details>

<details>

<summary>What happens to unused credits?</summary>

For Pay-as-you-go plans, Unused credits remain in your account. Credits never expire.\
For the subscription plan, unused credits roll over to the next month and have lifetime validity.\
However, discounted credits may come with an expiry date, subject to the terms of the specific deal.

</details>

<details>

<summary>What happens if my credits run out?</summary>

You can purchase additional credits from the [pricing page](https://app.clearout.io/pricing) by selecting the suitable plans as per your needs. For auto top-up, you can enable [Auto-credit Replenishment](https://app.clearout.io/account/manage-plans)(ACR) as per your need.

</details>

<details>

<summary>How do I view my credit balance?</summary>

Your credit balance is displayed in the top-left panel of your dashboard.\
Detailed history is available under **Dashboard** → **My Account** → [Plans](https://app.clearout.io/account/manage-plans).

</details>

<details>

<summary>How do I enable auto credit replenishment?</summary>

Go to **Dashboard** → **My Account** → **Plans** → [**Auto Credit Replenishment**](https://app.clearout.io/account/manage-plans)**(ACR)**, set a minimum threshold, and configure automatic top-up.

</details>

<details>

<summary>Are there limits on the size of bulk file uploads?</summary>

No strict limit. However, for best performance and faster completion cycles, upload files in batches of up to 500,000 records.

</details>

<details>

<summary>What API rate limits apply?</summary>

Rate limits depend on [your plan](https://docs.clearout.io/developers/api/overview#plan-specific-limits). Contact support via email at **<us@clearout.io>** for enterprise-level increases.

</details>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.clearout.io/help-and-support/featured-answered/credits-and-limits.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.