# CircleCI

> Credits by project and workflow, and workflows that spend their credits failing.

opsen reads CircleCI Insights for your organisation: credits used over the last 30 days, per project and per workflow, with run counts and failure rates. It prices credits and finds workflows that spend most of them failing.

## Connect

**Settings → Connections → CircleCI.** Enter the organisation as `gh/your-org`, `bb/your-org` or `circleci/your-org-id` (a link to the organisation in CircleCI works too) and a [personal API token](https://app.circleci.com/settings/user/tokens) from a member of the organisation.

If you pay less than list, enter your price per 25,000 credits and every CircleCI figure uses it.

## Prices

Credits at $15 per 25,000, CircleCI's list rate for extra credits on Performance ($0.0006 a credit). Insights is refreshed daily and is not CircleCI's invoice, so the CircleCI figures are an estimate.

## What it finds

| Finding | Rule | Priced at |
| --- | --- | --- |
| Failing workflows | 40% or more of runs failed in 30 days, and at least 25,000 credits spent | Credits used × share of failed runs |

Fixing these is engineering work, not a setting: the finding links each workflow to its flaky tests and failure history, and the next audit records the credits it stops spending.

## Budgets

CircleCI counts toward the **CI and build minutes** budget, alongside GitHub Actions.