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

# Credits and billing

> Understand estimates, purchases, billing history, and common balance-related questions.

## How credits work

Before a job starts, BrezelScraper calculates an estimate based on your configuration.

That estimate changes with settings such as:

* Number of keywords
* Search depth
* Max results
* Review scraping
* Image collection
* Contact enrichment

If your available balance is too low, BrezelScraper blocks the job before launch and asks you to add credits first.

## Estimate vs actual cost

The estimate is a pre-run projection. The final charge depends on what the scraper actually collects.

In practice:

* Broader jobs usually cost more
* Optional enrichments increase cost
* Actual cost can be lower than the estimate if fewer records are found

You can review the final cost on the job detail page after the run finishes.

## Where to manage billing

Open **Credits** in the dashboard to:

* Check your current balance
* Buy more credits
* Review transaction history
* Inspect the current pricing reference

## Buying credits

The purchase flow is simple:

1. Open **Credits**
2. Choose the amount you want to buy
3. Continue to Stripe checkout
4. Return to the dashboard after payment

After a successful purchase, your balance refreshes automatically.

## Transaction history

Your billing history can include:

* Purchases
* Usage or consumption
* Bonus credits
* Refunds
* Adjustments

Use this page to understand where your balance changed and which jobs consumed credits.

## Common billing questions

### Do I need a subscription?

No. BrezelScraper is designed for pay-as-you-go usage.

### What happens if I run out of credits?

New jobs will not start until you add balance or reduce the job scope.

### Why did the dashboard send me to Credits?

Your current setup needs more balance than you have available. Add credits or lower the depth, caps, or enrichments and retry.

### Where can I see current pricing?

Open **Credits** and expand the pricing reference card. That is the best place to check the current in-product pricing breakdown before launch.

## Ways to keep spend predictable

* Use a max results cap for early tests
* Keep enrichments off until you confirm data quality
* Estimate first, then scale the same setup gradually
* Split large research projects into smaller named jobs

## Next step

If you want to automate runs after you understand the pricing model, continue with [API access](/docs/api-reference/introduction).