---
title: "Manage billing and usage"
description: "Read your organization's allowances and usage, configure workload limits and alerts, and inspect invoices."
sidebar:
  label: "Billing & Usage"
seo:
  title: "Manage Billing and Usage | Judgment How-to"
  description: "Understand included and prepaid JUs, PAYGO, trace allowances, workload caps, usage alerts, and invoice history in Judgment."
---

Open **Settings > Billing & Usage** in the intended organization to understand
what consumed its allowance and which limits apply. Usage spans the
organization's projects; the project breakdown helps identify its sources.

Plan, contract, allowance, price, and period values vary by organization. Use
the values displayed in your account. Admin or owner access is required to
edit customer billing controls; some controls depend on the plan or contract.

## Read the current period

1. Check the dates beside **Usage this cycle** or **Usage this period**. A
   contract may use a different period from a standard subscription.
2. Read the billing summary and **Total Allowance** or **Total Allowance and
   PAYGO** section.
3. Under **Raw usage per workload**, select **Evaluations/platform agent** or
   **Traces** to inspect usage and its project breakdown.
4. Use **View Detailed Usage and Cost Breakdown** when you need to reconcile
   usage, credits, and cost. Use the usage-over-time chart to find when usage
   changed.

| Displayed term | What it tells you |
| --- | --- |
| JUs | Usage units shared by supported workloads; a JU is not a count of API requests. |
| Included JUs / Prepaid JUs | The allowance supplied by your plan or contract. Adjustment JUs may appear separately. |
| PAYGO | Billable usage beyond applicable allowances when enabled for your account. |
| Free trace allowance | Trace ingestion covered before trace usage draws from the JU pool. Use the displayed byte allowance. |
| Raw workload usage | Usage measured for a workload, distinct from the final amount billed after applicable credits. |

The trace JU limit applies after the free trace allowance. The evaluation
workload includes platform-agent usage as well as evaluations. Inspect both
the workload and overall limits when investigating blocked usage.

## Set a workload limit

Workload limits constrain raw JUs within the organization's overall capacity;
they do not create extra allowance or reserve capacity for a project.

1. Under **Raw usage per workload**, select the workload tab.
2. Edit its **JU limit**. Use a nonnegative value; `0` leaves no JU capacity for
   that workload beyond any applicable free trace allowance.
3. Press Enter or leave the field to save. Check the success message and the
   displayed limit after it refreshes.

Clear the field to remove the explicit workload cap and use the displayed
overall default. A blank field is different from `0`.

Work can be blocked by either the workload limit or the overall capacity.
Raising one limit does not bypass the other. These are usage limits for the
period, separate from [request rate limits](/documentation/reference/rate-limits).

## Understand PAYGO and prepaid caps

Where available, the **PAYGO JU cap** supports **Fixed** and **Unlimited** modes.
A fixed cap accepts a positive integer; an empty value uses the displayed
default. Changing the mode saves it immediately; numeric edits save on Enter
or when leaving the field. **Unlimited** removes that PAYGO cap, while explicit
workload limits still apply.

Some contracts also expose a **Prepaid JU cap**. It stops usage after the
configured prepaid amount instead of continuing into PAYGO. A blank prepaid
cap permits continuation into PAYGO where the account supports it. The
available prepaid balance still matters: setting a cap above that balance does
not create more prepaid JUs.

Review the displayed limits and rates before changing a cap. A usage cap is
not a replacement for understanding the contract or invoice.

## Configure usage alerts

1. Select **Usage Alerts** where available and enable **Alerts enabled**.
2. Set **Alert thresholds (%)** for the resources you want to monitor.
   Enter comma- or space-separated integers from `1` to `100`, or leave a
   field empty to use its displayed defaults.
3. Choose **Notify roles**, then select **Save**.
4. Reopen **Usage Alerts** to verify the saved switch, thresholds, and roles.

These alerts email organization members in the selected roles. They are
separate from Slack automation notifications. Workload-limit thresholds apply
when that workload has an explicit limit; PAYGO thresholds are available when
PAYGO is enabled. An alert reports usage—it does not raise a limit or add
allowance. Saving the alert settings verifies configuration, not email delivery.

## Inspect invoices and payment details

In **Invoice History**, inspect the invoice date, amount, and status. Select
**View** when an invoice link is available. **Period Usage Breakdown** appears
when that invoice has a billing period and a valid pricing snapshot; older
invoices may not expose it.

Use the invoice's period breakdown to understand that invoice rather than
assuming the current cycle's settings describe a past charge. **Manage Payment**
is available to organization administrators for supported payment accounts.

## Troubleshooting

- If a control is disabled, confirm your organization role and whether the
  plan or contract exposes that control.
- If evaluation or trace usage is blocked, inspect the workload limit, overall
  capacity, and any prepaid cap before changing settings.
- If requests are throttled despite remaining JUs, check the applicable
  [rate-limit scope](/documentation/reference/rate-limits).
- If an alert does not arrive, check the enabled switch, recipient roles,
  applicable threshold, and whether the resource has an explicit limit.

## Next step

Use [production monitoring](/documentation/monitoring) to investigate the
project or workload responsible for a usage change.