> ## Documentation Index
> Fetch the complete documentation index at: https://docs.enrow.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Credits & Billing

> Learn how Enrow API credits are consumed per endpoint, check your balance, manage auto-renew and top-up, and handle insufficient credits

Enrow uses a credit-based system, and credits are only consumed when a result is found or a check is performed. This page explains how credits are charged for each endpoint, how to check your balance, how to manage billing settings, and what happens when credits run out.

## How do credits work?

Credits are only consumed when the API returns a result or completes a check — failed lookups that find nothing do not cost credits. Each feature consumes credits at a different rate:

| Endpoint           | Credits                                            |
| ------------------ | -------------------------------------------------- |
| **Email Finder**   | 1 per email found                                  |
| **Phone Finder**   | 40 per phone found (default; 50 with legacy plans) |
| **Email Verifier** | 0.25 per check                                     |

<Note>
  Credits are charged the same way for single and bulk operations — per individual result. Running a [bulk email search](/api-reference/email-finder/find-bulk) of 1,000 names costs the same per found email as 1,000 single searches.
</Note>

Every request that consumes credits returns a `credits_used` field in its response, so you can track consumption per search. See [Find Single Email](/api-reference/email-finder/find-single) for an example response.

## How do I check my credit balance?

Query the account endpoint with your API key in the `x-api-key` header to retrieve your current credit balance. No body payload is needed — the account is identified from the API key.

```bash theme={null}
curl https://api.enrow.io/account/info \
  -H "x-api-key: YOUR_API_KEY"
```

```json Response theme={null}
{
  "credits": 8500,
  "webhooks": ["https://your-app.com/webhooks/enrow"]
}
```

The response contains your balance and registered webhooks:

| Field      | Description                           |
| ---------- | ------------------------------------- |
| `credits`  | Your current credits balance          |
| `webhooks` | Array of your registered webhook URLs |

For the full endpoint reference, see [Account info](/api-reference/account/info). You can also visit your [Dashboard](https://app.enrow.io) to view usage and billing details, or check the [Authentication](/authentication) guide for how the `x-api-key` header works across every endpoint.

## How do I manage billing settings?

From the [Billing page](https://app.enrow.io/billing) in the app, you can configure three options that keep your account topped up and alert you before credits run out:

<AccordionGroup>
  <Accordion title="Auto Renew">
    Automatically renew your plan when it expires. Set the credit amount to renew in the input field next to the toggle.
  </Accordion>

  <Accordion title="Auto Top-Up">
    Automatically purchase additional pay-as-you-go credits when your balance runs low. Set the credit amount to top up in the input field next to the toggle.
  </Accordion>

  <Accordion title="Low Balance Alert">
    Receive an email alert when your credit balance drops below a threshold. Set the credit amount threshold in the input field next to the toggle.
  </Accordion>
</AccordionGroup>

## What happens when credits run out?

When your credit balance reaches zero, API requests return an HTTP `402` status. Single endpoints (email/phone find single, verify single) return:

```json theme={null}
{
  "reason": "Insufficient credits",
  "success": false
}
```

Bulk endpoints return `{ "message": "..." }` instead. For the full list of status codes and response shapes, see [Status codes](/status-codes) and [Error handling](/error-handling).

<Warning>
  To avoid interruptions, enable **Auto Top-Up** or **Low Balance Alert** from the [Billing page](https://app.enrow.io/billing).
</Warning>

## Which plan should I choose?

Visit [enrow.io/pricing](https://enrow.io/pricing) to compare plans and find the right fit for your needs. Pay-as-you-go credits can be added on top of any plan through [Auto Top-Up](#how-do-i-manage-billing-settings).

## FAQ

<AccordionGroup>
  <Accordion title="Do failed searches cost credits?">
    No. Credits are only consumed when an email or phone number is found, or when a verification check is performed. A search that returns no result does not cost credits.
  </Accordion>

  <Accordion title="Are bulk operations cheaper than single operations?">
    No. Credits are charged per individual result, so a bulk operation costs the same per found email, phone, or verification as the equivalent single requests. Bulk endpoints save on requests, not on credits.
  </Accordion>

  <Accordion title="How many credits does an email verification cost?">
    The Email Verifier consumes 0.25 credits per check. The Email Finder consumes 1 credit per email found, and the Phone Finder consumes 40 credits per phone found (50 with legacy plans).
  </Accordion>

  <Accordion title="What error do I get when I have no credits left?">
    Requests return an HTTP `402` status. Single endpoints return `{ "reason": "Insufficient credits", "success": false }`, while bulk endpoints return `{ "message": "..." }`. See [Error handling](/error-handling) for details.
  </Accordion>
</AccordionGroup>

## Next steps

<CardGroup cols={2}>
  <Card title="Authentication" icon="key" href="/authentication">
    How to pass your API key in the x-api-key header.
  </Card>

  <Card title="Account info" icon="circle-user" href="/api-reference/account/info">
    Retrieve your credit balance and registered webhooks.
  </Card>

  <Card title="Rate limits" icon="gauge-high" href="/rate-limits">
    Understand the API request limits before scaling up.
  </Card>

  <Card title="Error handling" icon="triangle-exclamation" href="/error-handling">
    Handle 402 and other error responses gracefully.
  </Card>
</CardGroup>