Teams and community / You and your team
See what your account uses
You want to check what your account used, and what it costs. The Billing page shows your plan and what is left of it in this period. It also adds up the CI minutes and the AI of your account in this UTC month, with an estimate at list prices.
7 min read
Note
Billing is off until a site admin turns it on. While it is off, the page shows only the usage of this month, and nothing is charged. See Plans and billing.
You can see the usage of your own account. For an organization, you must be an owner.
1. Open Billing
- Your account: open Billing. In the side menu of your settings, Billing is under Notifications.
- An organization: on the page of the organization, click Manage organization. Then click the Billing tab, the last tab.
Only owners see the Billing tab of an organization. For other people, its address (/organizations/<org>/billing) shows the not-found page.
2. Read the Plan card
While billing is on, the Plan card comes first. It names your plan and the days of this period, for example "Team with 3 seats. This period: October 13, 2026 to November 12, 2026 (UTC)."
| Figure | What it shows |
|---|---|
| CI minutes this period | The CI minutes that this period used, of what your plan includes, and what is left. |
| Forge-paid AI this period | The forge-paid AI that this period used, of what your plan includes, and what is left. |
| Credit balance | Your credits before the charge of this period, and the part that this period used. |
| Overage this period | What overage paid, of your monthly spending limit. While overage is off, it says Overage is off. |
| Debt this period | The usage over your plan that your credits did not pay. It shows only when there is a debt. |
When your plan includes none of an amount, its figure says None included in your plan. On Free, this is the forge-paid AI. Plans and billing says what pays when the plan is used up.
3. Read the four numbers
The card Usage this month names the month, for example "November 2026 (UTC)". It shows four numbers. Three of them count this month. Free public CI minutes counts this billing period.
| Number | What it counts |
|---|---|
| Paid CI minutes | The CI minutes that have a price: the CI jobs of your private repositories, the paid CI of your public repositories, and the agent containers of all your repositories. |
| Free public CI minutes | The free CI of your public repositories in this billing period, of 20,000 CI minutes. Only small jobs are free. When none is left, the note says that public CI counts as paid CI. See Free CI for public repositories. |
| AI on forge-paid models | The AI models that the forge pays for, at 1.5 times their cost to the forge. |
| Estimate at list prices | The list price of the first number, plus the AI. |
One CI minute is one minute of a small CI job. For example, 1 minute of a large CI job is 3.11 CI minutes.
4. See which containers ran
Under the numbers, a table lists each container size that ran this month. The Repositories column says Public for the free CI of your public repositories, and Private for the usage that has a price. Each row shows the run time, the CI minutes and the list price. On a public row, the price is Free.
When no container ran this month, the card shows "No container ran this month."
Done
You see your plan and what is left of it in this period. You also see what your account used this month: its CI minutes, its AI and the estimate at list prices. The table shows the run time of each container size.
The card Usage this month shows only the current UTC month. A new month starts at 00:00 UTC on the first day of the month. The period of a paid plan can start on another day. See The billing period.
What counts
- CI jobs: the run time of the container of each job. On a private repository, it counts at its list price.
- CI jobs of public repositories: a
smalljob is free, and it counts in Free public CI minutes, up to 20,000 CI minutes in each period. Amediumorlargejob, and every job past the limit, counts at its list price. See Free CI for public repositories. - Agents: the containers of the factory agents, of agent workflow jobs and of agent tasks count at their list price, on every repository. An agent run that only reads gets no container, so it adds no CI minutes.
- AI: the models that the forge pays for, in the factory agents, the agent workflows, the PR chat and the architecture chat. They count at 1.5 times their cost to the forge. They are the models of the monthly spend cap.
- Cancels and retries: a cancelled agent run counts the model calls that it made before the cancel. A step of an agent workflow that runs again after a retry counts again.
What does not count
- A model with your own key. You pay its provider.
- The git work of the forge: imports, large pushes and repacks.
- The containers that plan your workflows.
- The build of the node base snapshot, which the forge keeps for all repositories.
The prices
| Container | CI minutes for each minute | List price for each minute |
|---|---|---|
| Small, 1 vCPU | 1 | $0.00645 |
| Medium, 2 vCPU | 1.71 | $0.01103 |
| Large, 4 vCPU | 3.11 | $0.02006 |
| AI container, 0.5 vCPU | 0.57 | $0.00368 |
Each container counts by what one minute of it costs Source. Each CI minute has the same list price, $0.00645. So a CI minute past your plan costs about $0.00645.
- CI jobs and the jobs of agent workflows run on the size that their
sizesets. The default islarge, andsmallin a public repository. See Images and sizes. - The factory agents run on the AI container. Two kinds of runs use a large container: the fix runs of the dependency agent, and the runs of the CI cache agent.
When usage counts
- The forge records each usage at the end of a job, an agent run or a chat answer. The usage counts on the UTC day of that record. So a job that runs past midnight UTC counts on the next day.
- When the forge cannot record a usage at once, it tries again until the usage counts. So a number can show late, but it never counts twice.
- If the container slot of a job expires before the job ends, the forge counts an estimate: the time that the job held the slot. When the job ends, its real run time replaces the estimate. If the billing period of the estimate ended before the job ended, the estimate stays the charge.
From src, REST or MCP
src billing view
src billing view --org acme
src billing viewprints the totals of the page. While billing is on, it prints the plan and the money of the period first. Add--json usageto get JSON, with a line for each day.- REST:
GET /api/v1/user/billingandGET /api/v1/orgs/{org}/billing. See Billing routes. - MCP: the tool
get_billing, withorgfor an organization. - Only people can read billing. Agents, jobs, apps and tokens limited to repositories are refused.
- No command, route or tool turns on overage. See Turn on overage.