# Usage

Usage information helps you understand how much activity the current account or project has consumed and whether any limits may affect new generation or test work.

## Where usage appears

You may see usage information in several places:

| Place                      | What it shows                                                                              |
| -------------------------- | ------------------------------------------------------------------------------------------ |
| Settings > Account         | Account summary, usage information, plan, credit, limits, and GitHub quota when available. |
| Settings > Usage & Billing | Plan cards, billing options, purchased credit, and plan usage when available.              |
| Dashboard usage section    | Repository-level usage summaries when the dashboard is enabled for your workspace.         |
| Activity and Runs          | Workflow activity and run history that explain where usage came from.                      |

## Usage types

| Usage type        | What it means                                                  |
| ----------------- | -------------------------------------------------------------- |
| Generation usage  | AI-assisted feature and Playwright generation activity.        |
| Run usage         | Browser test execution activity and scheduled runs.            |
| Suggestions usage | Test suggestion generation and inventory maintenance.          |
| GitHub API quota  | GitHub request quota for the active session or installation.   |
| Plan limits       | Product limits or credits tied to the current account or plan. |

GitHub API quota is separate from TestVibe plan usage. Low GitHub quota can affect how quickly TestVibe reads repository, workflow, runner, or artifact data.

## Check usage before large work

Review usage before:

| Situation                     | Why it helps                                         |
| ----------------------------- | ---------------------------------------------------- |
| Running a full suite          | Confirms the project is ready for broader execution. |
| Starting multiple generations | Helps avoid surprise limits during AI generation.    |
| Enabling schedules            | Scheduled runs can create recurring activity.        |
| Troubleshooting slow updates  | GitHub quota or workflow limits may explain delays.  |

## Plan information

Open **Settings > Usage & Billing** to review available plan information. If plan actions are managed outside TestVibe, the app may direct you to your billing or account portal instead of changing the plan directly.

For current plan details, included minutes, multipliers, and add-on minute packs, see [Pricing](/pricing.md).

For scheduled activity, see [Schedule runs](/run-tests/schedule-runs.md).


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.testvibe.com/account-settings/usage.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.