---
title: Usage
description: Inspect Sume usage ledger entries and balance.
---

Open the [Usage dashboard](https://www.sume.com/dashboard/usage) for a human
summary of metered Developer API activity. Programmatic usage reads are
available from:

```text
GET /v1/balance
GET /v1/usage
```

Exact schemas: live [OpenAPI](https://api.sume.com/reference/json).

## Balance

```bash
curl https://api.sume.com/v1/balance \
  -H "Authorization: Bearer $SUME_API_KEY"
```

Balance is USD-denominated. Compatibility fields can expose rounded cent values
as credits.

## Usage ledger

```bash
curl https://api.sume.com/v1/usage \
  -H "Authorization: Bearer $SUME_API_KEY"
```

Usage entries can include reservations, captures, refunds, top-ups, and grants,
depending on the workspace and environment.

| Status | Meaning |
|---|---|
| `reserved` | Estimated usage was reserved before provider execution. |
| `captured` | Billable usage was captured after successful completion. |
| `refunded` | Reserved usage was released after failure or cancellation before capture. |

Use job ids and request ids to correlate usage rows with generation workflows.

Per-capability metered rates live on the
[API pricing page](https://www.sume.com/pricing/api). They are not duplicated
here — that page is generated from the same pricing constants the API bills on.

For plan changes and top-ups, use
[Billing & subscription](https://www.sume.com/dashboard/subscription).