> For the complete documentation index, see [llms.txt](https://copilot-docs.bugbase.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://copilot-docs.bugbase.ai/enterprise/settings/credits-and-usage.md).

# Credits and Usage

Understand pentesting credits and estimate usage from your application features and user roles.

Open **Settings -> Usage** to review your credits and usage. **Settings -> Billing** also includes the credit guide alongside your billing information.

## What Is a Credit?

**1 credit = 1 pentesting hour.** For a web application, credits add up across **Discovery + Assessment** running time.

* **Discovery:** explore application features and how users interact with them.
* **Assessment:** test for vulnerabilities.

Credits add up across discovery and assessment runs. For example, 2 hours of discovery plus 8 hours of assessment uses 10 credits. Paused time is excluded.

Separate runs each use credits for their own running time, even when they overlap. Total pentesting hours can therefore differ from the time until your results are ready.

Credits reflect testing time, not a fixed charge per application feature, API endpoint, or trajectory.

## How Many Credits Will Your Application Use?

Use these approximate ranges to plan **Discovery + Assessment** for one web application. Each range includes both phases.

Use your application features and user roles to choose a starting estimate. Features can include sign-in, purchases, approvals, and reporting.

| Application size         | Approximate credits | Application features                                                                                                                        |
| ------------------------ | ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------- |
| **Small application**    | **\~8-10 credits**  | A focused application with a few features, such as sign-in, user profiles, and simple forms.                                                |
| **Mid-size application** | **\~15-20 credits** | An application with several connected features, such as customer onboarding, search, purchases, and account management.                     |
| **Large application**    | **\~25-30 credits** | An extensive application with many features, such as order management, approvals, reporting, and administration across multiple user roles. |

{% hint style="info" %}
Estimates only. Actual usage may be lower or higher. Adding user roles or expanding the testing scope can take usage beyond these ranges.
{% endhint %}

These are approximate planning ranges for a single web application. They are not a fixed quote, a credit limit, or a guarantee of complete coverage. The application features, user roles, and testing settings you include determine the work required. These web application estimates do not describe network, cloud, or code assessment usage.

## What Can Increase Credit Usage?

### More user roles and permissions

Testing as an admin, employee, customer, or guest can involve separate runs, each with different features and permissions to check.

### More application features

Additional application features, such as payments, order management, and approvals, give discovery more to explore and assessment more to test.

### Deeper testing

More thorough checks and additional attack scenarios can require more testing time, especially for complex application features such as payments or approvals.

### Slower responses or request limits

Slow application responses or limits on how many requests a scan can send per minute can extend its running time.

## How Your Balance Works

* **Shared trials:** Discovery and Assessment have separate balances that cannot be exchanged. The ranges above describe the combined usage across both phases.
* **Dedicated plans:** Discovery and Assessment draw from one credit balance.

## Vetting and AI Configure

[AI configure](https://copilot-docs.bugbase.ai/enterprise/how-to-trigger-a-web-assessment/ai-configure-and-vetting.md) vets a domain before its scan. The **Review** step notes that vetting is billed like a rate calibration run. The Discovery and Assessment scans it starts then use credits like any other run.

Before vetting starts, Pentest Copilot applies the same usage checks as any scan start:

* **Every plan:** the workspace must have credits available. If not, starting vetting shows **Not enough credits**: "This workspace does not have enough credits to start vetting. Add credits, then start again." Select **Go to Usage** to open this page.
* **Shared trials:** the trial must be active, and credits must be left for each phase the run will scan. **Discovery + Assessment** needs both Discovery and Assessment credits. If the trial refuses the start, you see **Your trial can't start scans yet** with the reason, or **No Discovery time left** / **No Assessment time left** when a phase's time is used up. Both offer **Go to Usage**, or **Verify domain** when the reason is domain verification.
* The domain's root must also be verified on a shared trial, unless BugBase has waived verification. See [Domain Verification](https://copilot-docs.bugbase.ai/enterprise/settings/domain-verification.md#ai-configure-on-a-shared-trial).

**Use existing configuration** skips vetting and starts the scan straight away, so only the scan uses credits.

## On a Shared Trial

A shared trial shows where it stands before you start a scan:

* **Header:** when your trial is not activated, the top bar shows **Trial not active · Activate**. When it has ended, it shows **Trial ended · View plans**. Both open **Settings -> Usage**.
* **Run Assessment banner:** when the trial can't start a scan yet, a banner at the top of **Run Assessment** names the next step, such as **Activate your trial to run scans** or **Your trial credits are used up**. See [Shared-Trial Banner](https://copilot-docs.bugbase.ai/enterprise/run-assessment-wizard.md#shared-trial-banner).
* **Intent cards:** each intent shows the credits left for the phases it runs, for example **Discovery: 4.0 credits left · Assessment: 10.0 credits left**. An intent whose phases have no credits left reads, for example, **No Assessment credits left. Upgrade your plan in Settings › Usage.**, and you can't continue with it.

## Before You Start

Review the estimate in scan setup for the application, user roles, and scope you plan to test. Check your available balance in **Settings -> Usage** before launching.

See [Your First Web Run](https://copilot-docs.bugbase.ai/enterprise/how-to-trigger-a-web-assessment.md#your-first-web-run) for setup, and [Common Web Settings](https://copilot-docs.bugbase.ai/enterprise/how-to-trigger-a-web-assessment/configure-scan-settings-for-web-assessment.md) for authentication coverage, scope, and request limits.
