> ## Documentation Index > Fetch the complete documentation index at: https://docs.bead.run/llms.txt > Use this file to discover all available pages before exploring further. # bead usage alerts > Configure bead usage alerts and read account usage, machine cost, and low-credit notifications. Configure bead usage alerts and read usage alongside credit to understand your spending. Observed usage can arrive before all charges and reservations settle. ## Check your balance ```bash theme={null} bead balance ``` Balance reports funds, reservations, and available credit. See [Prepaid credit](https://docs.bead.run/platform/prepaid-credit.md) for those distinctions. ## Read account and machine usage With admin scope, read the organization's usage projection: ```bash theme={null} bead api GET /billing/usage ``` The result includes `spend_today_units`, `usage`, and whether the organization has a billing customer. Use the unit metadata returned by `GET /v1/pricing` to interpret ledger amounts. Read a machine's observed cost separately: ```bash theme={null} bead api GET /sandboxes/MACHINE_ID/cost ``` A running machine's observed cost is not a final invoice. Late confirmed usage and reserved exposure can change the reconciled balance. ## Configure a low-credit alert The admin-scoped billing alert operation uses ledger units. Set `ALERT_THRESHOLD_UNITS` to your chosen threshold in ledger units, then write a request file: ```bash theme={null} cat > credit-alert.json <