> For the complete documentation index, see [llms.txt](https://docs.baz.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.baz.co/account/billing.md).

# Billing

<figure><img src="/files/dq3AutfJKp36hHpIqIQs" alt=""><figcaption></figcaption></figure>

Account Settings in Baz lets you manage your subscription, subscribed users, payment information, invoices, and usage limits.

Billing is handled through Stripe. Baz does not store or process credit card information directly.

### View or update billing

To view or update billing information:

1. Go to **Settings → Account Settings**
2. Click **Payment & Billing**
3. You will be redirected to the Stripe billing portal

### Subscription

In the billing portal, you can view:

| Field               | Description                                             |
| ------------------- | ------------------------------------------------------- |
| Current plan        | Your active Baz subscription, such as Pro or Enterprise |
| Seats               | The number of subscribed users on the account           |
| Cost                | Subscription total and billing frequency                |
| Next billing date   | The next scheduled billing date                         |
| Update subscription | Manage or update your plan                              |

### Subscribed users

#### Repository owners

Enterprise accounts can assign repository owners.

Repository owners are users who can manage custom reviewers for specific repositories without giving them full organization admin access.

Repo owners can create and edit custom reviewers only for the repositories they own. They cannot create or edit custom reviewers for repositories outside their assigned ownership scope.

Organization admins can assign and update repository owners from Account Settings.

To manage repository owners:

1. Go to **Settings → Account Settings**
2. Select **Repository Owners**
3. Select a repository
4. Add or remove repository owners

#### Repository owner permissions

| Permission                                     | Admin | Repository owner |
| ---------------------------------------------- | ----- | ---------------- |
| Assign repository owners                       | Yes   | No               |
| Create custom reviewers for any repository     | Yes   | No               |
| Edit custom reviewers for any repository       | Yes   | No               |
| Create custom reviewers for owned repositories | Yes   | Yes              |
| Edit custom reviewers for owned repositories   | Yes   | Yes              |
| View repositories available to them            | Yes   | Yes              |

Repository owners only see and manage repositories they are allowed to access.

If a user is removed as a repository owner, they lose the ability to create or edit custom reviewers for that repository. Existing custom reviewers are not deleted.

### Engineering Work Credits

Engineering Work Credits are used for high-model engineering work performed by Baz agents.

Seat-based pricing covers access to Baz and standard AI code review. Engineering Work Credits cover agent work that investigates, validates, fixes, or generates engineering output.

Engineering Work Credits are effective June 1, 2026.

#### What uses Engineering Work Credits

Engineering Work Credits are used for:

| Agent work                 | Description                                                                          |
| -------------------------- | ------------------------------------------------------------------------------------ |
| Fixer session              | Baz analyzes a finding and generates a code fix                                      |
| Advanced Security Reviewer | Baz performs deeper security analysis across the codebase                            |
| Spec Review                | Baz validates implementation against requirements, specs, tickets, or product intent |
| AI SRE                     | Baz investigates issues using runtime context, logs, traces, and code paths          |

Standard AI code review does not use Engineering Work Credits.

#### How credits work

Usage is billed in credits.

**1 credit = $0.01**

Credits are consumed when a credit-eligible agent session runs. The number of credits used depends on the agent, repository size, codebase complexity, and the amount of context required.

Typical session ranges:

| Agent work                 | Typical cost per session |
| -------------------------- | -----------------------: |
| Fixer session              |           $1.00 to $4.30 |
| Advanced Security Reviewer |           $1.75 to $2.20 |
| Spec Review                |           $1.00 to $2.50 |
| AI SRE                     |           $1.50 to $3.00 |

#### Usage limits

You can control Engineering Work Credit usage with limits.

Available limits:

| Limit                    | Description                                               |
| ------------------------ | --------------------------------------------------------- |
| Organization usage limit | A single monthly credit limit for the entire organization |
| Per-user usage limit     | A monthly credit limit per subscribed user                |

When a usage limit is reached, Baz stops running additional credit-eligible agent work until the limit is updated or more credits are available.

Standard AI code review continues according to your active subscription.

### Payment method

You can manage payment methods directly through Stripe.

Supported actions:

| Action                 | Description                                   |
| ---------------------- | --------------------------------------------- |
| Add payment method     | Add a credit or debit card                    |
| Update payment method  | Replace the current card                      |
| Remove payment method  | Remove a saved payment method where supported |
| Update billing details | Edit billing contact and company information  |

Payment details are processed securely by Stripe. Baz does not store credit card information.

### Billing information

Billing information includes:

| Field           | Description                          |
| --------------- | ------------------------------------ |
| Account name    | Organization name                    |
| Billing contact | Email used for billing communication |
| Billing details | Company and payment details          |
| Tax information | Tax details where applicable         |

You can update billing information from the Stripe billing portal.

### Invoice history

The billing portal includes invoice history.

Each invoice includes:

| Field  | Description                                                   |
| ------ | ------------------------------------------------------------- |
| Date   | Invoice issue date                                            |
| Amount | Amount billed                                                 |
| Status | Payment status                                                |
| Type   | Subscription, Engineering Work Credits, or other billing item |

Invoices can be downloaded from the billing portal.

### Cancel or delete account

To delete your account:

1. Go to **Settings → Account**
2. Click **Delete my account**
3. Confirm the action

Deleting an account is irreversible. Team members lose access immediately, and Baz stops reviewing Change Requests.


---

# 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 dynamically by asking a question.

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

```
GET https://docs.baz.co/account/billing.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
