> For the complete documentation index, see [llms.txt](/llms.txt).
> Markdown versions of each page are available by appending .md to any URL.

# insufficient_credits

The principal billed for the run has no remaining credits. Top up the triggering user's or the team owner's credit pool to continue.

The `insufficient_credits` error occurs when the principal billed for a cloud agent run has no remaining credits to charge against.

On self-serve plans (Build, Max, Business), the billed principal depends on how the run was triggered:

-   **User-triggered runs** draw from the triggering user’s pool: plan-included credits first, then their user-scoped add-on credits.
-   **Agent API key and scheduled runs** draw from the team owner’s pool: the owner’s plan-included credits first, then the owner’s add-on credits.

When both pools are depleted and [auto-reload](/support-and-community/plans-and-billing/add-on-credits/) is off, new runs return this error. On Enterprise plans, runs draw from the team-scoped credit pool per your contract — contact your account manager when the pool is exhausted.

* * *

## Details

-   **HTTP Status:** `403 Forbidden`
-   **Retryable:** No
-   **Task State:** FAILED

* * *

## When does this occur?

This error is returned when:

-   A user-triggered run runs out of the user’s plan-included credits and their user-scoped add-on credits.
-   An agent API key or scheduled run runs out of the team owner’s plan-included credits and the owner’s add-on credits.
-   Auto-reload is off, or auto-reload is on but the team-wide monthly spend cap has been reached.

For the full waterfall, see [How are cloud agent runs on team plans billed when no individual user triggered them?](/support-and-community/plans-and-billing/pricing-faqs/#how-are-cloud-agent-runs-on-team-plans-billed-when-no-individual-user-triggered-them) in the Pricing FAQs.

* * *

## Example response

```
{  "type": "/reference/api-and-sdk/troubleshooting/errors/insufficient-credits/",  "title": "The principal billed for this run has no remaining credits. Purchase add-on credits or raise the team-wide spend cap to continue.",  "status": 403,  "instance": "/api/v1/agent/tasks",  "retryable": false}
```

* * *

## How to resolve

The fix depends on which principal was billed.

**For user-triggered runs (your own pool was exhausted):**

1.  Purchase [add-on credits](/support-and-community/plans-and-billing/add-on-credits/) in **Settings** > **Billing and usage**, or wait for your monthly credits to refresh.
2.  Alternatively, enable auto-reload, subject to your team’s monthly spend cap.
3.  Retry the failed operation.

**For agent API key or scheduled runs (the team owner’s pool was exhausted):**

1.  The team owner tops up their pool: purchase add-on credits or wait for the monthly refresh.
2.  If auto-reload is on but the team-wide spend cap was reached, an admin can raise the cap in **Settings** > **Billing and usage**.
3.  Retry the failed operation.

If you are not a team admin or the team owner, contact them to top up the right pool.

* * *

## Related

-   [Access, billing, and identity permissions](/agent-platform/cloud-agents/team-access-billing-and-identity/) — Credit billing for individual user runs and agent API key runs.
-   [Add-on credits](/support-and-community/plans-and-billing/add-on-credits/) — Purchase additional credits and configure auto-reload.
-   [Platform credits](/support-and-community/plans-and-billing/platform-credits/) — The third credit bucket alongside AI credits and compute credits.
-   [Cloud Agents Overview](/agent-platform/cloud-agents/overview/) — Billing and plan requirements for cloud agents.