Skip to content
Warp

Reference > Errors

insufficient_credits

Open in ChatGPT ↗
Ask ChatGPT about this page
Open in Claude ↗
Ask Claude about this page
Copied!

The principal billed for the run has no remaining credits. Top up the right pool — the triggering user's, or the team owner's for team API key and scheduled runs — 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.
  • Team 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 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

Section titled “Details”
  • HTTP Status: 403 Forbidden
  • Retryable: No
  • Task State: FAILED

When does this occur?

Section titled “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.
  • A team 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? in the Pricing FAQs.

Example response

Section titled “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

Section titled “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 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 team 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.

Section titled “Related”