> For the complete documentation index, see [llms.txt](https://docs.konvu.com/konvu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.konvu.com/konvu/administration/assessment-credits.md).

# Assessment Credits

How Konvu assessment credits work, what consumes them, and how to monitor your usage.

Konvu uses a credit system to meter AI-powered assessments. Each credit corresponds to one finding assessed -- meaning Konvu ran its AI agents to determine whether that finding is exploitable or a false positive, and produced an evidence report.

## How credits work

Credits are tracked per organization as a running balance. Your balance increases when credits are added (initial allocation, top-ups) and decreases when assessments consume them.

### What counts as one credit

One credit = one open integration finding assessed. If the same vulnerability appears in multiple scanner findings (e.g., reported by both Snyk and Semgrep), each finding consumes its own credit when assessed.

Credits are consumed at assessment completion, not at the start. If an assessment fails or is retried, you are not double-charged -- the system uses idempotent tracking per finding to prevent duplicate consumption.

### Container credits

Container assessments draw on a **separate credit pool** from your SCA and SAST balance. Each container assessment that completes successfully consumes one credit from the container pool; failed jobs are not charged. Because the pools are independent, container assessments can't drain the balance that gates your code findings, and vice versa.

Your monthly credit allowance applies to the SCA pool only -- there is no monthly container allowance. To add container credits, open **Edit Company Settings**, set **Credit pool** to *Container* on the top-up row, and add the amount. Both pool balances are shown above the row.

### Secrets credits

Secrets assessments use a separate Secrets credit pool. When metering is enabled, a completed secret assessment consumes one credit from this pool; receiving the same assessment result again does not charge it twice. Do not assume that one grouped row always corresponds to one lifetime credit: a credential can have assessment records for different repository and commit contexts.

Secrets has no monthly allowance. Check the Secrets balance and transaction history when investigating paused assessments, and contact the Konvu team if you need additional credits. See [Triage Secrets](/konvu/triage-and-remediation/finding-types/secrets.md) for the review workflow.

## Monitoring your usage

### Credit balance

Your current credit balance is displayed in the top navigation bar of the Konvu dashboard. The balance shows the remaining credits available to your organization. A balance of zero or below means assessments will pause until credits are added.

### Credit history

The **Credit History** page provides a full transaction log. Each entry shows:

* **Date** -- when the transaction occurred
* **Type** -- the transaction type (AI qualification, stack analysis, admin top-up, or initial balance)
* **Amount** -- credits consumed (-1) or added (+N)
* **Finding** -- link to the assessed finding (for consumption transactions)
* **Description** -- additional context (for top-ups)
* **By** -- who triggered the transaction (system or admin email)

Navigate to Credit History from the credit balance indicator in the navigation bar.

## Pricing

New organizations start with **a defined number of trial credits** at no cost. For pricing on additional credits, contact the Konvu team at [support@konvu.com](mailto:support@konvu.com?subject=Assessment%20Credits) or talk to your account representative.

{% hint style="info" %}
During onboarding, Konvu suggests limiting initial assessments to 3 repositories. This helps you evaluate results before committing credits across your full portfolio. You can adjust which repositories have assessments enabled at any time from **Configuration > AI Triage**.
{% endhint %}


---

# 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.konvu.com/konvu/administration/assessment-credits.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.