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

# Manage credits

> Check a workspace's credit balance and find out where credits went.

Runs consume credits. Both credit commands are read-only.

## Check the balance

```bash theme={null}
jstm credits balance
jstm credits balance --workspace acme-corp/finance
```

Without `--workspace`, this reports your active workspace. Credits are held per workspace, so a team that runs a lot draws down its own balance rather than a shared pool.

## See where they went

```bash theme={null}
jstm credits ledger
jstm credits ledger --limit 100 --workspace acme-corp/finance
```

The ledger lists entries newest first, showing what consumed credits and when.

Reach for it when a balance drops faster than expected. The usual causes are a schedule firing more often than intended, or an agent staged at `live` retrying a failing step.

## Keeping consumption predictable

**Check what's scheduled.**

```bash theme={null}
jstm agent installations
```

The listing shows each installation's schedule and next fire time. A `*/5 * * * *` schedule left over from testing is the most common surprise.

**Prefer dry runs while iterating.** Dry Run exercises the agent without production side effects, and it's the right mode while you're still shaping a spec.

**Look for retry loops.**

```bash theme={null}
jstm agent stories failed-payment-digest --status failed
```

A `MUST_HAPPEN` step that fails retries with backoff before giving up. A step failing on every run is doing that work repeatedly.

**Clear schedules you no longer need.**

```bash theme={null}
jstm agent schedule clear 8c41f2b9-77de-4a30-b0c5-2e1f6a9d4b77
```

## Scripting

```bash theme={null}
jstm credits balance --json | jq '.balance'
```

## See also

* [Credits](/features/credits)
* [`jstm credits`](/cli/credits) — full reference.