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

# AI credits

> What uses AI in TestBrick, and what happens when credits run low

# AI credits

Building a test with Bricklayer uses AI. Running a finished test normally doesn't. AI credits measure the AI you use.

**1 credit = 1 cent of AI.** A typical test build uses about 40 credits. A normal run uses none.

## What uses credits

| | Credits |
| - | - |
| **Building a test** with Bricklayer | about 40 for a typical build; long or tricky flows use more |
| **Help during a run** — when a step needs AI to get through (a moved button, an unexpected pop-up) | a few per step that needed help |
| **Running a test** that needs no help | none |

The brief box shows roughly what a build will use before you start.

## Keeping an eye on them

The bar at the bottom of the sidebar shows what's left this month:

* **purple** — plenty left
* **yellow** — under 40% left
* **red** — under 15% left, or out

**Settings → AI credits** shows where your credits went this month — builds, help during runs, and other AI help — and when they reset.

## When you run out

* **Your tests and monitors keep running.** Nothing stops.
* **New builds and AI help pause** until your credits reset.
* **Monitors keep their AI help for a few more days** after you run out, so an alert doesn't turn into a false failure overnight.

Credits reset each month on the date shown in the sidebar.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.