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

# Credits

> Check the credit balance of your team, recent consumption and the estimated runway with one read request, before you start a run or add monitored prompts.

## Check your balance

```bash theme={null}
curl "https://www.qwairy.co/api/v1/credits" \
  -H "Authorization: Bearer $QWAIRY_API_TOKEN"
```

```json theme={null}
{
  "success": true,
  "credits": {
    "balance": 1200,
    "usedLast30Days": 480,
    "averageDailyBurn": 16,
    "runwayDays": 75,
    "subTeams": null
  }
}
```

`runwayDays` estimates how long the balance lasts at the current burn rate, and
is `null` when nothing is being consumed. For a parent organisation, `subTeams`
lists each sub-team balance.

Read this endpoint before starting a run, and again afterwards to see what it
reserved. Pair it with [Estimate a run](https://docs.qwairy.co/developers/endpoints/runs/estimate.md) to
price work before committing to it. Starting a run reserves its full planned
cost. Collecting Pitch Audit responses also consumes credits as answers
complete.

> [!NOTE]
>
> Moving credits between teams and buying more are dashboard actions, not API
> operations. Allocation and payment involve a human decision, so they stay in
> [Team Management](https://www.qwairy.co/dashboard/team/billing).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.